Sr. Technical Account Manager at a tech vendor with 1,001-5,000 employees
Real User
Top 20
Dec 4, 2025
There are different approaches you can utilize if your use case involves multi-tenancy. You can define access points based on each of your tenants and utilize those access points as part of your multi-tenancy workload. Access points are basically integrated with IAM. For encryption, you can utilize KMS as a service for encrypting your file system at rest. One of the other important features I would mention is the archive class. Initially, this was not supported with Amazon EFS (Elastic File System), but now it has been added. If you have cold data in your Amazon EFS (Elastic File System) file system, you do not have to pay for it at full price. The idea is to move that data to the archive tier so that you pay less instead of paying for it under the standard class. I have utilized AWS DataSync with Amazon EFS (Elastic File System) as well. If you are looking to migrate your workload from on-premise to AWS and you want to use a NAS operating system or network attached storage at the back end, and your workload is Linux only, then Amazon EFS (Elastic File System) is the best choice. I would rate this product a 9 out of 10.
We are not using Elastic Disaster Recovery at present. Concerning AWS Identity and Access Management, we are not integrating as we majorly use it over the network layer, the TCP layer, and the private network. Regarding the performance differences between General Purpose and Max I/O modes in Amazon EFS (Elastic File System), we are using General Purpose for general use cases, and it works sufficiently. I rate Amazon EFS (Elastic File System) seven out of ten.
Our project is up and running without any issues, so after that point, we have not needed to make many adjustments. We deploy Lambda, which means we do not have servers. We run our functions on Lambda and use serverless mode deployment method. AWS Lambda is used for our cloud storage. We do not use EC2 now, as we are using serverless mode database and Lambda only due to on-demand costing. We moved away from EC2 because it requires regular payments. The performance of Amazon EFS (Elastic File System) is the same as when you deploy something to a physical server. You just run the engine when needed; otherwise, it will not run. Separate tools come in, and it is secured at the enterprise level. For the moment, CodePipeline, which is built in AWS, is sufficient. We use Jira for lifecycle management, along with Bitbucket and CodePipeline, integrating all our release pipelines.
For users evaluating EFS, it's better to use S3 or EBS volumes if they don't have specific use cases requiring EFS. Medium or small enterprises may not need EFS. Overall, I rate EFS as eight out of ten, mainly due to cost considerations.
Learn what your peers think about Amazon EFS (Elastic File System). Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
EFS can also be mounted to other AWS services like Lambda, making it versatile and cost-effective compared to other solutions like S3. Additionally, I have not faced any downtime issues; it has been consistently reliable. If your business is in its early stages and doesn't require high scalability, you might avoid using this solution initially. However, shifting to it becomes more sensible as your business grows and you require more reliable and cost-effective storage. I rate it a ten out of ten.
In terms of security, there are multiple ways to connect the product via MFA or route authentication. You can sort out APIs and log files. I recommend the product to those who plan to use it. The integration of Amazon EFS (Elastic File System) with other platforms has improved areas like storage and security for our company. I think that it will be great for others to have Amazon EFS (Elastic File System) on the cloud. I rate the tool an eight out of ten.
Senior Cloud Engineer at a tech consulting company with 10,001+ employees
Real User
Top 10
Mar 6, 2024
I will recommend the product to others. We are partners. Our clients moved from on-premise setup to the cloud. We suggested AWS to them. We have configured the product based on the best practices. We also monitor the solution for recommendations in the Security Hub. We try to get the data encrypted properly within our repository. Overall, I rate the product a nine out of ten.
Information Technology Specialist at Infiniti Creation
Real User
Aug 3, 2023
I would recommend Amazon EFS (Elastic File System) or NFS to those planning to use it, and Amazon EBS can be considered as a secondary option. I rate the overall solution a seven out of ten.
It a great scalable and stable solution, but just use Unix or Linux servers on-premises or in the Amazon cloud. I won't recommend using a Network File System to connect to Windows Servers. I would rate Amazon EFS a nine out of ten.
Amazon Elastic File System (Amazon EFS) provides simple, scalable file storage for use with Amazon EC2 instances in the AWS Cloud. Amazon EFS is easy to use and offers a simple interface that allows you to create and configure file systems quickly and easily. With Amazon EFS, storage capacity is elastic, growing and shrinking automatically as you add and remove files, so your applications have the storage they need, when they need it.
When mounted to Amazon EC2 instances, an Amazon EFS file...
There are different approaches you can utilize if your use case involves multi-tenancy. You can define access points based on each of your tenants and utilize those access points as part of your multi-tenancy workload. Access points are basically integrated with IAM. For encryption, you can utilize KMS as a service for encrypting your file system at rest. One of the other important features I would mention is the archive class. Initially, this was not supported with Amazon EFS (Elastic File System), but now it has been added. If you have cold data in your Amazon EFS (Elastic File System) file system, you do not have to pay for it at full price. The idea is to move that data to the archive tier so that you pay less instead of paying for it under the standard class. I have utilized AWS DataSync with Amazon EFS (Elastic File System) as well. If you are looking to migrate your workload from on-premise to AWS and you want to use a NAS operating system or network attached storage at the back end, and your workload is Linux only, then Amazon EFS (Elastic File System) is the best choice. I would rate this product a 9 out of 10.
We are not using Elastic Disaster Recovery at present. Concerning AWS Identity and Access Management, we are not integrating as we majorly use it over the network layer, the TCP layer, and the private network. Regarding the performance differences between General Purpose and Max I/O modes in Amazon EFS (Elastic File System), we are using General Purpose for general use cases, and it works sufficiently. I rate Amazon EFS (Elastic File System) seven out of ten.
Our project is up and running without any issues, so after that point, we have not needed to make many adjustments. We deploy Lambda, which means we do not have servers. We run our functions on Lambda and use serverless mode deployment method. AWS Lambda is used for our cloud storage. We do not use EC2 now, as we are using serverless mode database and Lambda only due to on-demand costing. We moved away from EC2 because it requires regular payments. The performance of Amazon EFS (Elastic File System) is the same as when you deploy something to a physical server. You just run the engine when needed; otherwise, it will not run. Separate tools come in, and it is secured at the enterprise level. For the moment, CodePipeline, which is built in AWS, is sufficient. We use Jira for lifecycle management, along with Bitbucket and CodePipeline, integrating all our release pipelines.
For users evaluating EFS, it's better to use S3 or EBS volumes if they don't have specific use cases requiring EFS. Medium or small enterprises may not need EFS. Overall, I rate EFS as eight out of ten, mainly due to cost considerations.
I would recommend Elastic File Systems to others because it is beneficial software. I rate Elastic File Systems a seven out of ten.
I would rate Amazon EFS a seven out of ten. I would recommend this product to others, ensuring they have the required expertise for initial setup.
Overall, I would rate it a seven out of ten.
EFS can also be mounted to other AWS services like Lambda, making it versatile and cost-effective compared to other solutions like S3. Additionally, I have not faced any downtime issues; it has been consistently reliable. If your business is in its early stages and doesn't require high scalability, you might avoid using this solution initially. However, shifting to it becomes more sensible as your business grows and you require more reliable and cost-effective storage. I rate it a ten out of ten.
In terms of security, there are multiple ways to connect the product via MFA or route authentication. You can sort out APIs and log files. I recommend the product to those who plan to use it. The integration of Amazon EFS (Elastic File System) with other platforms has improved areas like storage and security for our company. I think that it will be great for others to have Amazon EFS (Elastic File System) on the cloud. I rate the tool an eight out of ten.
I will recommend the product to others. We are partners. Our clients moved from on-premise setup to the cloud. We suggested AWS to them. We have configured the product based on the best practices. We also monitor the solution for recommendations in the Security Hub. We try to get the data encrypted properly within our repository. Overall, I rate the product a nine out of ten.
I would rate the overall solution an eight out of 10.
I would recommend Amazon EFS (Elastic File System) or NFS to those planning to use it, and Amazon EBS can be considered as a secondary option. I rate the overall solution a seven out of ten.
I recommend the solution to others and rate it a nine out of ten. It is a good service and provides faster loading of packages.
I rate this solution a nine out of ten. I would have rated it ten if not for the upcycle.
It a great scalable and stable solution, but just use Unix or Linux servers on-premises or in the Amazon cloud. I won't recommend using a Network File System to connect to Windows Servers. I would rate Amazon EFS a nine out of ten.
I would definitely recommend this solution. I would rate it an eight out of ten. They should look into what Google and other providers are offering.