aws_efs_access_point cost estimation
An EFS access point is free. It is an application-specific entry point into an EFS file system, and the cost is the EFS storage and throughput it maps into.
An aws_efs_access_point is a named entry point into an EFS file system that enforces a root directory and a POSIX user and group for every client that mounts through it. It is how you give different applications or containers their own isolated view of one shared file system. Access points cost nothing to create or use.
The cost is entirely the aws_efs_file_system behind the access point. EFS bills per GB-month of stored data at Standard (roughly $0.30/GB-month) and Infrequent Access (roughly $0.016/GB-month) rates, plus optional Provisioned Throughput. An access point does not add storage or a separate meter; it only scopes where a client can read and write within the file system that is already being billed.
Because access points enforce a root directory per application, they make it easy to run many workloads on a single file system instead of provisioning one file system each. That consolidation is the cost angle: fewer file systems to manage, one storage pool to tier with lifecycle policies, and no per-access-point charge. c3x prices the underlying file system's storage and throughput and treats each access point as the free access control it is.
Terraform example
A minimal but realistic configuration that C3X can estimate.
resource "aws_efs_access_point" "app" {
file_system_id = aws_efs_file_system.shared.id
posix_user {
uid = 1000
gid = 1000
}
root_directory {
path = "/app"
creation_info {
owner_uid = 1000
owner_gid = 1000
permissions = "0755"
}
}
}Pricing dimensions
What you actually pay for when you provision aws_efs_access_point.
| Dimension | Unit | What's being charged |
|---|---|---|
| Access point | free | Creating and mounting through an access point has no charge. $0 |
| EFS storage | per GB-month | The data stored in the file system the access point maps into. Standard: ~$0.30/GB-month |
| Provisioned throughput | per MB/s-month | Optional sustained bandwidth on the file system, billed only if enabled. ~$6.00/MB/s-month |
Optimization tips
Common ways to reduce aws_efs_access_point cost without changing the workload.
Consolidate apps onto one file system
Access points isolate applications by root directory, so you can run many on a single EFS file system instead of provisioning one each. One storage pool is cheaper to manage and tier.
Tier cold data to Infrequent Access
Up to 90% on cold dataThe cost is the file system's storage. A lifecycle policy that moves rarely-read files to IA drops them from about $0.30 to about $0.016/GB-month.
Leave throughput on bursting mode
Bursting throughput is included in the storage price. Only enable Provisioned Throughput for workloads that genuinely need sustained bandwidth, since it is billed on top.
FAQ
Does an EFS access point cost money?
No. Access points are free to create and mount through. You pay only for the EFS file system's stored data and any provisioned throughput, regardless of how many access points map into it.
Do more access points increase EFS cost?
No. There is no per-access-point charge and no extra storage. Access points only scope where each client can read and write within the same file system that is already billed by GB-month.
Why use an access point instead of separate file systems?
To run several applications on one file system with isolated root directories, which is cheaper and simpler to tier than provisioning and managing a separate file system per application.
Related resources
Estimate this resource in your own Terraform
Free, open source, no API key. C3X parses your Terraform and shows line-item cost for every resource, including aws_efs_access_point.