|
Amazon Elastic File System (Amazon EFS) permits EC2 cases, AWS Lambda capabilities, and containers to share entry to a fully-managed file system. First introduced in 2015 and usually out there in 2016, Amazon EFS delivers low-latency efficiency for all kinds of workloads and might scale to hundreds of concurrent shoppers or connections. For the reason that 2016 launch we’ve continued to hear and to innovate, and have added many new options and capabilities in response to your suggestions. These embrace on-premises entry through Direct Join (2016), encryption of information at relaxation (2017), provisioned throughput and encryption of information in transit (2018), an rare entry storage class (2019), IAM authorization & entry factors (2020), lower-cost one zone storage lessons (2021), and extra.
Introducing Replication
At the moment I’m comfortable to announce that you would be able to now use replication to routinely keep copies of your EFS file programs for enterprise continuity or that can assist you to fulfill compliance necessities as a part of your catastrophe restoration technique. You possibly can set this up in minutes for brand spanking new or present EFS file programs, with replication both inside a single AWS area or between two AWS areas in the identical AWS partition.
As soon as configured, replication begins instantly. All replication site visitors stays on the AWS world spine, and most modifications are replicated inside a minute, with an total Restoration Level Goal (RPO) of 15 minutes for many file programs. Replication doesn’t devour any burst credit and it doesn’t depend in opposition to the provisioned throughput of the file system.
Configuring Replication
To configure replication, I open the Amazon EFS Console , view the file system that I wish to replicate, and choose the Replication tab:
I click on Create replication, select the specified vacation spot area, and choose the specified storage (Regional or One Zone). I can use the default KMS key for encryption or I can select one other one. I overview my settings and click on Create replication to proceed:
Replication begins instantly and I can see the brand new, read-only file system instantly:
A brand new CloudWatch metric, TimeSinceLastSync, is revealed when the preliminary replication is full, and periodically after that:
The reproduction is created within the chosen area. I create any essential mount targets and mount the reproduction on an EC2 occasion:
EFS tracks modifications to the blocks (at present four MB) which might be used to retailer recordsdata and metadata, and replicates the modifications at a price of as much as 300 MB per second. As a result of replication is block-based, it isn’t crash-consistent; for those who want crash-consistency it’s your decision to try AWS Backup.
After I’ve arrange replication, I can change the lifecycle administration, clever tiering, throughput mode, and automated backup setting for the vacation spot file system. The efficiency mode is chosen when the file system is created, and can’t be modified.
Initiating a Fail-Over
If I have to fail over to the reproduction, I merely delete the replication. I can do that from both aspect (supply or vacation spot), by clicking Delete and confirming my intent:
I enter delete, and click on Delete replication to proceed:
The previous read-only reproduction is now a writable file system that I can use as a part of my restoration course of. To fail-back, I create a duplicate within the unique location, await replication to complete, and delete the replication.
I also can use the command line and the EFS APIs to handle replication. For instance:
create-replication-configuration / CreateReplicationConfiguration – Set up replication for an present file system.
describe-replication-configurations / DescribeReplicationConfigurations – See the replication configuration for a supply or vacation spot file system, or for all replication configurations in an AWS account. The info returned for a vacation spot file system additionally contains LastReplicatedTimestamp, the time of the final profitable sync.
delete-replication-configuration / DeleteReplicationConfiguration – Finish replication for a file system.
Out there Now
This new function is offered now and you can begin utilizing it right this moment within the AWS US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Eire), Europe (London), Europe (Paris), Europe (Stockholm), South America (São Paulo), and GovCloud Areas.
You pay the standard storage charges for the unique and reproduction file programs and any relevant cross-region or intra-region information switch prices.
— Jeff;
