Amazon EFS now supports AWS PrivateLink
You can now use AWS PrivateLink to create Amazon VPC interface endpoints for Amazon Elastic File System (Amazon EFS). AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises applications, securely on the Amazon network. Amazon EFS customers can now use private IP connectivity and security groups to meet their specific compliance requirements.
You can now use AWS PrivateLink to create Amazon VPC interface endpoints for Amazon Elastic File System (Amazon EFS). AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises applications, securely on the Amazon network. Amazon EFS customers can now use private IP connectivity and security groups to meet their specific compliance requirements.
Amazon EFS provides a simple, scalable, elastic NFS file system for Linux-based workloads for use with AWS Cloud services and on-premises resources. Amazon EFS already supports industry standard TLS to secure encryption of data in transit, and all clients connect to Amazon EFS from within their Virtual Private Cloud (VPC). With today’s launch, you can improve your compliance posture by using AWS PrivateLink to automate the creation and management of your Amazon EFS file systems using the EFS API, without using public IP addresses and without any traffic traversing the internet.
To use AWS PrivateLink, create an interface VPC endpoint for Amazon EFS in your VPC using the Amazon VPC console, SDK or CLI. You can also access the VPC endpoint from on-premises environments or from other VPCs using AWS VPN, AWS Direct Connect, or VPC Peering.
This feature is available in all regions where Amazon EFS is available. To learn more, visit the Amazon EFS website, read the EFS VPC endpoint documentation, or get started in the AWS Console.