Hi Everyone, I am glad to join this amazing pulumi community and I am new here 🙂 , I am here to request some assistance on some pulumi related questions please, shown below 👇 We are using pulumi typescript to automate our AWS related infrastructure/services, & have been using to automate AWS EFS (Elastic FileSystem) creation along with an EFS '*replica*' created on a given AWS region. Highly appreciate if somebody give me a hand to assist me on getting the following working please? • EFS replica created isn't created with any "Name" and it doesn't have any AWS tags (Name is blank because the "Name" key value pair is empty), it appears to be having something like below. • The reason is we noticed that https://github.com/pulumi/pulumi-aws/blob/master/sdk/nodejs/efs/replicationConfiguration.ts#L185-L194 typescript interface doesn't support adding tags • Also EFSReplicationConfiguration doesn't seem to support adding LifeCyclePolicies for the EFSReplicationConfiguration object? (This means that I am able to add LifeCycle Management to the "primary" EFS but not to the "replica" EFS Looking forward to your advices...

export interface ReplicationConfigurationArgs {
    /**
     * A destination configuration block (documented below).
     */
    destination: pulumi.Input<inputs.efs.ReplicationConfigurationDestination>;
    /**
     * The ID of the file system that is to be replicated.
     */
    sourceFileSystemId: pulumi.Input<string>;
}

This is all limited by AWS, not Pulumi. You can't do these things via the SDK or CLI, either.

Thank you Paul, oh alright then it makes sense to me now

I think so. EFS replication might not be the best tool for you. Are you using replication for backing up only or parallel (active-active) or redundant (active-passive) access?

ah actually sorry i forgot to mention the context, so the EFS replica will be in the Disaster Recovery site/region (Canada) & therefore the EFS primary will be in the main site (eg: us-east-1) . The intention of having EFS replica is if some disaster happens (By us or AWS) then we failover to the DR region , therefore we will then start using the EFS replica. That's the main goal to achieve

Yep. So the failover time is important. If you need seconds, this is your only managed option and you'll need to pay for it; your only other option afaik would be to set up two separate EFS volumes and mirror them using 3rd party software.

cool, yeah i suppose we go with the managed option as it seems to be the suitable one for our scenario (Few seconds/mins is something our application can cope). Thanks again for your advices Paul, much appreciated.

Going more cloud native will help 🙂 EFS and EBS are services I deal with much less often these days; cloud native services often render them surplus to requirements.

yeah absolutely, high time i guess 🙂