Code360 powered by Coding Ninjas X Naukri.com. Code360 powered by Coding Ninjas X Naukri.com
Table of contents
1.
Introduction
2.
AWS Elastic file system with Quick Create
3.
Create an EFS file system
3.1.
Creating an EFS File system
4.
Mount the EFS File System to the Instance
4.1.
Mount the file system
5.
Test the file system
5.1.
To verify that the file system is mounted, follow these steps:
6.
Clean up
7.
Frequently Asked Questions
7.1.
What applications does Amazon EFS support?
7.2.
How do I put information into a file system?
7.3.
How much data can I store?
7.4.
How many file systems am I allowed to create?
8.
Conclusion
Last Updated: Mar 27, 2024
Easy

AWS Elastic File System

Author Akshit Mehra
0 upvote
Master Python: Predicting weather forecasts
Speaker
Ashwin Goyal
Product Manager @

Introduction

An EFS is a Network File System (NFS) that uses a logical file structure to manage data. Data is arranged in folders and sub-folders in a path-based manner.

Amazon EFS is a cloud-based file storage service for Amazon Web Services public cloud applications and workloads. Amazon EFS offers scalable file storage for Amazon EC2. An EFS file system may be used as a shared data source for workloads and programs operating on numerous instances. AWS automatically creates and manages Elastic File System (EFS) infrastructure dispersed over an infinite number of servers to prevent performance bottlenecks.

Elastic File Systems is an excellent choice for storing:

  1. Data from the organisation
  2. Individual data on a file server
  3. Application data
    Also see, Amazon Hirepro

AWS Elastic file system with Quick Create

When you use EFS Quick create to create an EFS file system, the file system is built with the following service recommended settings:

  1. Automatic backups have already been enabled. 
  2. Mount targets in the specified VPC's default subnets using the VPC's default security group.
  3. Performance mode for general use. 
  4. Method of burst throughput.
  5. Data at rest encryption is enabled for Amazon EFS (AWS/elastic file system) using your default key. 
  6. With a 30-day policy, Amazon EFS lifecycle management is enabled.
Get the tech career you deserve, faster!
Connect with our expert counsellors to understand how to hack your way to success
User rating 4.7/5
1:1 doubt support
95% placement record
Akash Pal
Senior Software Engineer
326% Hike After Job Bootcamp
Himanshu Gusain
Programmer Analyst
32 LPA After Job Bootcamp
After Job
Bootcamp

Create an EFS file system

The process of Creating and Mounting an Elastic File System is divided into four steps:

Creating an EFS File system

You may use Amazon EFS to establish a file system that many instances can access and mount simultaneously. In the Amazon Elastic File System User Guide, see Creating Resources for Amazon EFS for further details.

For creating a file system, below are the steps followed:

  1. Go to https://console.aws.amazon.com/efs/ to access the Amazon Elastic File System console.
  2. Select Create file system.
  3. (Optional) Enter a name for the file system in the Name field. This generates a tag with Name as the key and the file system name as the value.
  4. Select the Virtual Private Cloud (VPC) to utilize for your instances.
  5. Select Create.
  6. Take note of the file system ID when it has been created. It will be utilized later in the tutorial.
  7. Select the file system ID.
  8. Select Network, Manage from the file systems screen. View the mount targets created by Amazon EFS in each Availability Zone in the Region where your VPC is located. 
  9. Select Save.

Mount the EFS File System to the Instance

Mount the file system

For launching instances followed by mounting an EFS file system:

  1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/ Choose an Amazon Machine Image (AMI), and select an Amazon Linux AMI.
  2. Choose Launch Instance. Choose an Instance Type, keep the default instance type, t2.micro, and choose Next: Configure Instance Details.
  3. Configure Instance Details, do the following:
  4. Specify the Number of instances.
  5. [Default VPC] If you have a default VPC, that is the Network value.
  6. [Nonstandard VPC] Choose your VPC as Network and a public subnet as Subnet. Select Enable for Auto-assign Public IP. Otherwise, your instances will not be assigned public IP addresses or DNS names.
  7. Select Add file system under File systems. Check that the value corresponds to the file system ID you generated in Step 1. 
  8. Proceed to the wizard's Step 6.
  9. Select Configure Security Group on the Configure Security Group page. Choose an existing security group and the security group you created in Prerequisites.
  10. Choose Review and Launch.
  11. Pick an existing security group and select the security group that you created in Prerequisites on the Configure Security Group page. Then, choose Review and Launch.
  12. Select Launch from the Review Instance Launch page.
  13. Select an existing or create a new key pair in the Select an existing key pair or create a new key pair dialogue box. Check the acknowledgment box and then click Launch Instances.
  14. Select Instances from the navigation pane to view the status of your instances. Their initial status is pending. Your instances are ready to utilize once the status changes to running.
  15. Your instance is now set to mount the Amazon EFS file system at startup, and every time it reboots.

Test the file system

To verify that the file system is mounted, follow these steps:

  1. Link to your instances. See Connect to your Linux instance for additional details.
  2. Run the df -T command from the terminal window for each instance to ensure that the EFS file system is mounted.
$ df -T
Filesystem     Type              1K-blocks    Used          Available Use% Mounted on
/dev/xvda1     ext4                8123812 1949800            6073764  25% /
devtmpfs       devtmpfs            4078468      56            4078412   1% /dev
tmpfs          tmpfs               4089312       0            4089312   0% /dev/shm
efs-dns        nfs4       9007199254740992       0   9007199254740992   0% /mnt/efs
The file system name, shown in the sample output as efs-DNS, has the following format.
file-system-id.efs.aws-region.amazonaws.com:/

Clean up

After completing this instruction, you can end the instances and erase the file system.

To stop the instances:

  1. Go to https://console.aws.amazon.com/ec2/ to access the Amazon EC2 console.
  2. Select Instances from the navigation pane.
  3. Choose which instances to terminate.
  4. Select Instance state, then Terminate instance.
  5. When requested for confirmation, choose Terminate.

 

To get rid of the file system.

  1. Go to https://console.aws.amazon.com/efs/ to access the Amazon Elastic File System console.
  2. Choose the file system to be deleted.
  3. Select Actions, then Delete File System.
  4. Enter the file system ID and choose a Delete file system when asked.

Frequently Asked Questions

What applications does Amazon EFS support?

Amazon EFS is designed to handle diverse workloads and applications, such as Big Data and analytics, media processing workflows, content management, web serving, and home directories.

How do I put information into a file system?

To transport data files to Amazon EFS, you may also utilize conventional Linux copy tools. For further information, refer to the On-premises Access section of this FAQ.

How much data can I store?

Petabytes of data may be stored on Amazon EFS file systems. Amazon EFS file systems are elastic, meaning they expand and contract as you add and delete data. You do not pre-provision file system size, and you only pay for what you use.

How many file systems am I allowed to create?

Each area can have up to 1,000 file systems. Please refer to the Amazon EFS Limits page for further details.

Encrypting your data has little to no impact on I/O latency and performance.

Conclusion

So, we end our above blog here. Above, we have extensively discussed AWS Elastic File System. We studied how to create a File system and Mount it on the instance. Further, we also saw how to test and clean the File System. We hope that this blog has helped you enhance your knowledge regarding AWS Elastic File System and if you would like to learn more.

Check out this article - File System Vs DBMS

Refer to our guided paths on Coding Ninjas Studio to learn more about DSA, Competitive Programming, System Design, JavaScript, etc. Enroll in our courses, refer to the mock test and problems available, interview puzzles, and look at the interview bundle and interview experiences for placement preparations.

Do upvote our blog to help other ninjas grow. Happy Coding!”

Next article
AWS EBS vs EFS
Live masterclass