Create Elastic File System In AWS
What Is EFS?
EFS is an acronym of Elastic File System.
It is a fully managed NFS Service in the aws cloud ,Which is used to share files across the systems.
Amazon EFS is very simple to create , manage and scale as per the requirements.
It can scale up to petabytes without making any issue to the existing connections , Also It automatically shrinks and expands the storage as per the usage.
Amazon EFS can be used with the services in the aws cloud and the On-Premise servers.
Supported Protocols
- NFS v4.0
- NFS v4.1
Types Of Storage Classes Offered
- Standard Access – The standard storage class stores the files that are very frequently used or accessed by the applications or other services.
- Infrequent Access – It is a cost effective storage class where the files stored are not frequently accessible.
How EFS Works?
Amazon provides file storage for the EFS cloud. Using which we can create a file system and mount the file systems across the instances are application where the files are used in common.
Applications hosted in the EC2 instances will read and write data to the EFS file system.
Create Elastic File System
To Create a Elastic file system , Login to AWS Console and Under Storage , Choose EFS
Click Create file system , In the first step , We need to configure the network access for the file system.
We have to create the EFS in the VPC where the applications are hosted in the EC2 Instances.
Hence Make sure , The VPC of the EC2 Instances and the EFS should be the same.
For VPC , Select the VPC. Instance can be connected with the file system using mount points.
For Create mount targets , If you have EC2 instances across Availability zones , We have to create mount points accordingly.
Check all the Availability zones listed below.
An automatic IP address will be assigned to each of the mount points across the AZ’s.
Select the Subnets and It will assigned with the default Security group. We can modify the security group later.
Click Next step
Add a tag to the Elastic file system.
Enable lifecycle management , In order to move the files which are not accessed for for a particular days.
It will be then moved to the infrequent access storage class for cost savings.
Available life cycle polices are , 7 days , 14 days , 30 days , 60 days , 90 days.
As per the policy you choose , Files will be moved to infrequent access storage class.
For Choose throughput mode , Leave it to default value => Bursting
For Choose performance mode , It recommended to use the General purpose for most of the file systems.
As a security concern , We can enable encryption for the data in the elastic file system to be at rest.
Choose Next step , Under Configure Client access,
We have to apply the file system policy for all the client machines (EC2 instances) connecting to the elastic file system.
We can either choose the policy settings or we can use the JSON to provide the policy document for the EFS.
We will use the default settings for the client access system policy and Access points.
Then Choose Next step , Here you can review the settings of the Elastic File system.
And then choose Create File System
From the File system page , You can see the File system ID and the State of the File system be Available.
Conclusion
We have successfully created a Elastic File system in the aws cloud.It acts as a centralised storage for all the applications running in the EC2 Instances.
Hope you find it helpful.Thanks for reading this article.
Do check out my other publications.