Contents

One Zone Lifecycle Managed AWS EFS can be cheaper than standard

In 2025 I created 63 One Zone Lifecycle Managed Amazon Web Services (AWS) Elastic File System (EFS). One for each Availability Zone where supported that I have access to.

Each AWS Region is completely independent and designed to be isolated from the other AWS Regions. Each Region is a separate geographic area. Amazon Web Services (AWS) has multiple Availability Zones for each of it's regions.

AWS Availability Zones and subnets

Availability Zones are multiple, isolated locations within each Region. By launching your instances in separate Availability Zones, you can protect your applications from the failure of a single location in the Region. The code for an Availability Zone (AZ) is its Region code followed by a letter identifier. For example, us-west-2d. AWS might restrict you from launching an instance in a constrained Availability Zone and might also remove the constrained Availability Zone from the list of Availability Zones for new accounts. Therefore, your account might have a different number of available Availability Zones in a Region than another account. AWS independently maps Availability Zones to codes for each AWS account and an Availability Zone might not be the same physical location as for another AWS account. AZ IDs are unique and consistent identifiers for an Availability Zone.

Each subnet must reside entirely within one Availability Zone and cannot span zones. A subnet is a range of IP addresses in your VPC. AWS accounts include a default VPC in each AWS Region. The default VPC includes a subnet for each Availability Zone the account has access to in a region. The default subnets AWS creates for the default VPC in each region use only IPv4 addresses I modify AWS VPC for IPv6 so that I can have a public IP address without paying for an AWS public IPv4 address.

When you launch an instance, you select a Region and a virtual private cloud (VPC), and then you can either select a subnet for one of the Availability Zones or let AWS choose one for you. When you launch your initial instances, AWS recommends that you accept the default Availability Zone, because this allows AWS to select the best Availability Zone for you based on system health and available capacity.

AWS Elastic File System (EFS) and Availability Zones

(AWS) Elastic File System (EFS) is supported in all 32 REGIONs enabled for my AWS account, as of January 2025, including support for Standard and Lifecycle Management EFS but a number of Availability Zones including all for many REGIONs do not yet support One Zone Lifecycle Managed EFS. One Zone Lifecycle Managed EFS is now used as a replacement for the Elastic Block Store (EBS) volume I was using for the Zz cloud backup.

This page details Availability Zones with No One Zone EFS support by the LAM AWS VPC subnet id I would use to launch an instance in that AZ. The only reason I have specified a specific Availability Zone when launching an instance was to connect to the Zz volume in us-west2d until I began testing where One Zone EFS is available.

AWS LAM VPC Availability Zone subnet id

I use the subnet id to start an EC2 instance from Command line in a specific Availability Zone for a region. I normally omit this parameter and let AWS choose the Availability Zone for the new instance.

On the Launch an instance page you can edit "Network settings" and select a specific subnet id from a drop-down list that shows all the subnets for the VPC along with the IPv4 CIDR block and Availability Zone. When launching from the command line the "aws ec2 run-instances" command has a --subnet-id parameter which can be used along with the --region parameter to insure the instance runs in a particular Availability Zone. Prior to 2025 I had only used Regional EFS. For testing I needed for instances to launch in the specific Availability Zone where where I had created a One Zone EFS. This document was created primarily to facilitate me setting the --subnet-id parameter when I want to launch an instance in a specific Availability Zone and also covers documenting where I found that a One Zone EFS is not currently supported. 

aws ec2 describe-availability-zones --region us-west-2

Following is the subnet id for each Availability Zone of the AWS LAM VPC in each region:

United States

  • us-west-2 Oregon vpc-71322b17 172.31.0.0/16 2600:1f14:3d86:2c00::/56
    • SUBNET_ID=subnet-19f7d37f # us-west-2a 172.31.16.0/20 2600:1f14:3d86:2c0a::/64
    • SUBNET_ID=subnet-1888cc50 # us-west-2b 172.31.32.0/20 2600:1f14:3d86:2c0b::/64
    • SUBNET_ID=subnet-11ffe14a # us-west-2c 172.31.0.0/20 2600:1f14:3d86:2c0c::/64
    • SUBNET_ID=subnet-2b13c400 # us-west-2d 172.31.48.0/20 2600:1f14:3d86:2c00::/64
  • us-east-1 N. Virginia vpc-035d821c28c919b90 172.31.0.0/16 2600:1f18:3370:6900::/56
    • SUBNET_ID=subnet-0092cbc7da4b544f8 # us-east-1a 172.31.16.0/20 2600:1f18:3370:690a::/64
    • SUBNET_ID=subnet-06bc676b4785c0bf9 # us-east-1b 172.31.32.0/20 2600:1f18:3370:690b::/64
    • SUBNET_ID=subnet-0d8404f0c0a0d63ec # us-east-1c 172.31.0.0/20 2600:1f18:3370:690c::/64
    • SUBNET_ID=subnet-0cb345dcb13199378 # us-east-1d 172.31.80.0/20 2600:1f18:3370:690d::/64
    • SUBNET_ID=subnet-093e315d658934beb # us-east-1e 172.31.48.0/20 2600:1f18:3370:690e::/64 No One Zone EFS, t3.nano t3a.nano or t4g.nano
    • SUBNET_ID=subnet-007fc03fcc382788c # us-east-1f 172.31.64.0/20 2600:1f18:3370:690f::/64
  • us-west-1 N. California vpc-0db5b335f70043223 172.31.0.0/16 2600:1f1c:920:e400::/56
    • SUBNET_ID=subnet-0644a45d8a37273fb # us-west-1a 172.31.16.0/20 2600:1f1c:920:e40a::/64
    • SUBNET_ID=subnet-055c929bf5e782cd6 # us-west-1c 172.31.0.0/20 2600:1f1c:920:e40c::/64
  • us-east-2 Ohio vpc-2fa45047 172.31.0.0/16 2600:1f16:1e4e:7000::/56
    • SUBNET_ID=subnet-e2b74e8a # us-east-2a 172.31.0.0/20 2600:1f16:1e4e:700a::/64
    • SUBNET_ID=subnet-f0e9d48b # us-east-2b 172.31.16.0/20 2600:1f16:1e4e:700b::/64
    • SUBNET_ID=subnet-ec314ca1 # us-east-2c 172.31.32.0/20 2600:1f16:1e4e:700c::/64

Africa

  • af-south-1 Cape Town (South Africa) vpc-044d4935148dd7100 172.31.0.0/16 2406:da11:79f:c900::/56
    • SUBNET_ID=subnet-0bd06bc462a58f79f # af-south-1a 172.31.0.0/20 2406:da11:79f:c90a::/64
    • SUBNET_ID=subnet-03720be5faae5d22b # af-south-1b 172.31.32.0/20 2406:da11:79f:c90b::/64
    • SUBNET_ID=subnet-01eba4556348aa1d5 # af-south-1c 172.31.16.0/20 2406:da11:79f:c90c::/64

Asia Pacific

  • ap-east-1 Hong Kong vpc-0ee1ac602773753d 172.31.0.0/16 2406:da1e:ee0:4b00::/56
    • SUBNET_ID=subnet-0b274624984de468f # ap-east-1a 172.31.16.0/20 2406:da1e:ee0:4b0a::/64
    • SUBNET_ID=subnet-0080494b306578605 # ap-east-1b 172.31.0.0/20 2406:da1e:ee0:4b0b::/64
    • SUBNET_ID=subnet-08686462be2b1e362 # ap-east-1c 172.31.32.0/20 2406:da1e:ee0:4b0c::/64
  • ap-south-2 Hyderabad (India) vpc-0306265fa925185cf 172.31.0.0/16 2406:da1b:ad5:d700::/56
    • SUBNET_ID=subnet-024131dd54bff4d9f # ap-south-2a 172.31.0.0/20 2406:da1b:ad5:d70a::/64 No One Zone EFS
    • SUBNET_ID=subnet-059fbf5ac5c6405dd # ap-south-2b 172.31.32.0/20 2406:da1b:ad5:d70b::/64 No One Zone EFS
    • SUBNET_ID=subnet-0545e20be34a0c6df # ap-south-2c 172.31.16.0/20 2406:da1b:ad5:d70c::/64 No One Zone EFS
  • ap-southeast-3 Jakarta (Indonesia) vpc-04e042bd372ada58f 172.31.0.0/16 2406:da19:cf5:dc00::/56
    • SUBNET_ID=subnet-0b83a2596d5167853 # ap-southeast-3a 172.31.0.0/20 2406:da19:cf5:dc0a::/64 No One Zone EFS
    • SUBNET_ID=subnet-0cd44af6df8fbb47f # ap-southeast-3b 172.31.32.0/20 2406:da19:cf5:dc0b::/64 No One Zone EFS
    • SUBNET_ID=subnet-0d9c4505c8cfecaef $ ap-southeast-3c 172.31.16.0/20 2406:da19:cf5:dc0c::/64 No One Zone EFS
  • ap-southeast-5 Malaysia vpc-0458abb6cd6d3e13a 172.31.0.0/16 2406:da10:8bc3:8000::/56
    • SUBNET_ID=subnet-0d8da75e2e14b6784 # ap-southeast-5a 172.31.0.0/20 2406:da10:8bc3:800a::/64 No One Zone EFS
    • SUBNET_ID=subnet-099c820bdb4a08dea # ap-southeast-5b 172.31.16.0/20 2406:da10:8bc3:800b::/64 No One Zone EFS
    • SUBNET_ID=subnet-0fe8f02afa7510556 # ap-southeast-5c 172.31.32.0/20 2406:da10:8bc3:800c::/64 No One Zone EFS
  • ap-southeast-4 Melbourne (Australia) vpc-050e6a13f61233e16 172.31.0.0/16 2406:da1f:cf5:6d00::/56
    • SUBNET_ID=subnet-004dab206ce6b42f9 # ap-southeast-4a 172.31.16.0/20 2406:da1f:cf5:6d0a::/64 No One Zone EFS
    • SUBNET_ID=subnet-0db47ec97fd76306f # ap-southeast-4b 172.31.0.0/20 2406:da1f:cf5:6d0b::/64 No One Zone EFS
    • SUBNET_ID=subnet-092cd6e10dd4d848c # ap-southeast-4c 172.31.32.0/20 2406:da1f:cf5:6d0c::/64 No One Zone EFS
  • ap-south-1 Mumbai (India) vpc-083f2e2f1043f9baf 172.31.0.0/16 2406:da1a:d73:6f00::/56
    • SUBNET_ID=subnet-06a0b4790cea226b7 # ap-south-1a 172.31.32.0/20 2406:da1a:d73:6f0a::/64
    • SUBNET_ID=subnet-07eaadfaa1dbe1574 # ap-south-1b 172.31.0.0/20 2406:da1a:d73:6f0b::/64
    • SUBNET_ID=subnet-08a8152a4789f029c # ap-south-1c 172.31.16.0/20 2406:da1a:d73:6f0c::/64
  • ap-northeast-3 Osaka (Japan) vpc-02d2e3b97082021d5 172.31.0.0/16 2406:da16:57c:ed00::/56
    • SUBNET_ID=subnet-06b6e68d8c91dc266 # ap-northeast-3a 172.31.32.0/20 2406:da16:57c:ed0a::/64
    • SUBNET_ID=subnet-0d50bae2fa8b3060e # ap-northeast-3b 172.31.16.0/20 2406:da16:57c:ed0b::/64
    • SUBNET_ID=subnet-0148d030cb44c9ba6 # ap-northeast-3c 172.31.0.0/20 2406:da16:57c:ed0c::/64
  • ap-northeast-2 Seoul (South Korea) vpc-013046897f4e7945d 172.31.0.0/16 2406:da12:e63:8e00::/56
    • SUBNET_ID=subnet-077b6fabc4e5f8e84 # ap-northeast-2a 172.31.0.0/20 2406:da12:e63:8e0a::/64
    • SUBNET_ID=subnet-0540703fa4a6cd510 # ap-northeast-2b 172.31.16.0/20 2406:da12:e63:8e0b::/64
    • SUBNET_ID=subnet-08fc4c8496d4740b1 # ap-northeast-2c 172.31.32.0/20 2406:da12:e63:8e0c::/64
    • SUBNET_ID=subnet-01b8bd04ac6b0099a # ap-northeast-2d 172.31.48.0/20 2406:da12:e63:8e0d::/64 No One Zone EFS
  • ap-southeast-1 Singapore vpc-0a3baacfa1dbccc69 172.31.0.0/16 2406:da18:5b1:8700::/56
    • SUBNET_ID=subnet-096c125aa8f150e7e # ap-southeast-1a 172.31.16.0/20 2406:da18:5b1:870a::/64
    • SUBNET_ID=subnet-002b0a1ca4d87513b # ap-southeast-1b 172.31.32.0/20 2406:da18:5b1:870b::/64
    • SUBNET_ID=subnet-0acdc36da57a3c1ed # ap-southeast-1c 172.31.0.0/20 2406:da18:5b1:870c::/64 No One Zone EFS
  • ap-southeast-2 Sydney (Australia) vpc-065b4760a63954c73 172.31.0.0/16 2406:da1c:255:a800::/56
    • SUBNET_ID=subnet-059ec3e9a9d9ab128 # ap-southeast-2a 172.31.32.0/20 2406:da1c:255:a80a::/64
    • SUBNET_ID=subnet-0d706a035c09fdd2d # ap-southeast-2b 172.31.0.0/20 2406:da1c:255:a80b::/64
    • SUBNET_ID=subnet-0533cda05fa4b7606 # ap-southeast-2c 172.31.16.0/20 2406:da1c:255:a80c::/64
  • ap-southeast-7 Thailand vpc-0da02874a0c9b00ce 172.31.0.0/16 2406:da14:862d:8d00::/56
    • SUBNET_ID=subnet-00314214c34b65702 # ap-southeast-7a 172.31.16.0/20 2406:da14:862d:8d0a::/64 No One Zone EFS
    • SUBNET_ID=subnet-045bce508818a2069 # ap-southeast-7b 172.31.0.0/20 2406:da14:862d:8d0b::/64 No One Zone EFS
    • SUBNET_ID=subnet-0a0b5d80f8c772d69 # ap-southeast-7c 172.31.32.0/20 2406:da14:862d:8d0c::/64 No One Zone EFS
  • ap-northeast-1 Tokyo (Japan) vpc-0e1b2bb4de2b6c588 172.31.0.0/16 2406:da14:f5c:c900::/56
    • SUBNET_ID=subnet-036f7e02ca4ffc438 # ap-northeast-1a 172.31.32.0/20 2406:da14:f5c:c90a::/64
    • SUBNET_ID=subnet-0880f3c91cad791fe # ap-northeast-1c 172.31.0.0/20 2406:da14:f5c:c90c::/64
    • SUBNET_ID=subnet-02bce10cacfd74c99 # ap-northeast-1d 172.31.16.0/20 2406:da14:f5c:c90d::/64 No One Zone EFS

Canada

  • ca-central-1 Canada vpc-0de19055175f2bd9a 172.31.0.0/16 2600:1f11:e3:1500::/56
    • SUBNET_ID=subnet-0e87c64e10d324500 # ca-central-1a 172.31.16.0/20 2600:1f11:e3:150a::/64
    • SUBNET_ID=subnet-02788867436b1cba2 # ca-central-1b 172.31.0.0/20 2600:1f11:e3:150b::/64
    • SUBNET_ID=subnet-028f9f94c0904aefe # ca-central-1d 172.31.32.0/20 2600:1f11:e3:150d::/64 No One Zone EFS
  • ca-west-1 Calgary vpc-0f7f63453b8423fb3 172.31.0.0/16 2600:1f1a:49a2:3500::/56
    • SUBNET_ID=subnet-0647e463be34d0cb3 # ca-west-1a 172.31.32.0/20 2600:1f1a:49a2:350a::/64 No One Zone EFS
    • SUBNET_ID=subnet-0605a65bab1617583 # ca-west-1b 172.31.16.0/20 2600:1f1a:49a2:350b::/64 No One Zone EFS
    • SUBNET_ID=subnet-042fed6964e7a3a99 # ca-west-1c 172.31.0.0/20 2600:1f1a:49a2:350c::/64 No One Zone EFS

Europe

  • eu-central-1 Frankfurt (Germany) vpc-019870683f68a3e8c 172.31.0.0/16 2a05:d014:3c:9000::/56
    • SUBNET_ID=subnet-00e6cbdbd92b983ba # eu-central-1a 172.31.16.0/20 2a05:d014:3c:900a::/64
    • SUBNET_ID=subnet-04b3754db91a642f1 # eu-central-1b 172.31.32.0/20 2a05:d014:3c:900b::/64
    • SUBNET_ID=subnet-07b43b273864248c9 # eu-central-1c 172.31.0.0/20 2a05:d014:3c:900c::/64
  • eu-west-1 Ireland vpc-09b267a4fba50db4d 172.31.0.0/16 2a05:d018:e47:4700::/56
    • SUBNET_ID=subnet-0bff2a8c333b476f7 # eu-west-1a 172.31.0.0/20 2a05:d018:e47:470a::/64
    • SUBNET_ID=subnet-08a54608e8d16de27 # eu-west-1b 172.31.16.0/20 2a05:d018:e47:470b::/64
    • SUBNET_ID=subnet-0094802941ab4fd45 # eu-west-1c 172.31.32.0/20 2a05:d018:e47:470c::/64
  • eu-west-2 London (United Kingdom) vpc-0781200e8b247ab59 172.31.0.0/16 2a05:d01c:dc5:e00::/56
    • SUBNET_ID=subnet-009c5818bc8f692dc # eu-west-2a 172.31.16.0/20 2a05:d01c:dc5:e0a::/64
    • SUBNET_ID=subnet-000bf4ce19ef31037 # eu-west-2b 172.31.32.0/20 2a05:d01c:dc5:e0b::/64 No One Zone EFS
    • SUBNET_ID=subnet-0d1ffd58cb74f4c69 # eu-west-2c 172.31.0.0/20 2a05:d01c:dc5:e0c::/64
  • eu-south-1 Milan (Italy) vpc-0e7873f104b471b75 172.31.0.0/16 2a05:d01a:454:b900::/56
    • SUBNET_ID=subnet-06893cfded4671073 # eu-south-1a 172.31.32.0/20 2a05:d01a:454:b90a::/64
    • SUBNET_ID=subnet-01c49a4382c617aeb # eu-south-1b 172.31.0.0/20 2a05:d01a:454:b90b::/64
    • SUBNET_ID=subnet-06449b145048b5d2a # eu-south-1c 172.31.16.0/20 2a05:d01a:454:b90c::/64
  • eu-west-3 Paris (France) vpc-0b925df1e50d41329 172.31.0.0/16 2a05:d012:faa:da00::/56
    • SUBNET_ID=subnet-0e67241b9b3c6af66 # eu-west-3a 172.31.0.0/20 2a05:d012:faa:da0a::/64
    • SUBNET_ID=subnet-085653eab7dc282e3 # eu-west-3b 172.31.16.0/20 2a05:d012:faa:da0b::/64 No One Zone EFS
    • SUBNET_ID=subnet-08a391278f1c3c914 # eu-west-3c 172.31.32.0/20 2a05:d012:faa:da0c::/64
  • eu-south-2 Spain vpc-0f40e7691c6804e33 172.31.0.0/16 2a05:d011:9ab:4400::/56
    • SUBNET_ID=subnet-0a96a6621889232cd # eu-south-2a 172.31.32.0/20 2a05:d011:9ab:440a::/64 No One Zone EFS
    • SUBNET_ID=subnet-0b58b1b03d2bcb684 # eu-south-2b 172.31.16.0/20 2a05:d011:9ab:440b::/64 No One Zone EFS
    • SUBNET_ID=subnet-05cfbcf1a9a223783 # eu-south-2c 172.31.0.0/20 2a05:d011:9ab:440c::/64 No One Zone EFS
  • eu-north-1 Stockholm (Sweden) vpc-0c21b7400450d2459 172.31.0.0/16 2a05:d016:6d7:ca00::/56
    • SUBNET_ID=subnet-0ac85ff2069cbf7e5 # eu-north-1a 172.31.16.0/20 2a05:d016:6d7:ca0a::/64
    • SUBNET_ID=subnet-0bc8fcfb87c9e2214 # eu-north-1b 172.31.32.0/20 2a05:d016:6d7:ca0b::/64
    • SUBNET_ID=subnet-00d33e016fc7d3e53 # eu-north-1c 172.31.0.0/20 2a05:d016:6d7:ca0c::/64
  • eu-central-2 Zurich (Switzerland) vpc-0950a85e695facc0f 172.31.0.0/16 2a05:d019:113:7b00::/56
    • SUBNET_ID=subnet-0742abe4e686a9da4 # eu-central-2a 172.31.0.0/20 2a05:d019:113:7b0a::/64 No One Zone EFS
    • SUBNET_ID=subnet-0818ffae2db13b626 # eu-central-2b 172.31.16.0/20 2a05:d019:113:7b0b::/64 No One Zone EFS
    • SUBNET_ID=subnet-0bd0fc6883a071d62 # eu-central-2c 172.31.32.0/20 2a05:d019:113:7b0c::/64 No One Zone EFS

Mexico

  • mx-central-1 Mexico vpc-094bce8ecd3243444 172.31.0.0/16 2600:1f17:4050:7a00::/56
    • SUBNET_ID=subnet-02b23bb5282680493 # mx-central-1a 172.31.32.0/20 2600:1f17:4050:7a0a::/64 No One Zone EFS
    • SUBNET_ID=subnet-0cfbbf3ad97a5f2b9 # mx-central-1b 172.31.16.0/20 2600:1f17:4050:7a0b::/64 No One Zone EFS
    • SUBNET_ID=subnet-01a015dd123bb5e09 # mx-central-1c 172.31.0.0/20 2600:1f17:4050:7a0c::/64 No One Zone EFS

Middle East

  • me-south-1 Bahrain vpc-0c9277686201ded3c 172.31.0.0/16 2a05:d01e:ccf:6400::/56
    • SUBNET_ID=subnet-0ce1fae020a577691 # me-south-1a 172.31.0.0/20 2a05:d01e:ccf:640a::/64
    • SUBNET_ID=subnet-04ca5ec124b2c6fe9 # me-south-1b 172.31.16.0/20 2a05:d01e:ccf:640b::/64
    • SUBNET_ID=subnet-09715bb7aa78368b8 # me-south-1c n172.31.32.0/20 2a05:d01e:ccf:640c::/64
  • me-central-1 United Arab Emirates (UAE) vpc-063bea1bfb197d1e0 172.31.0.0/16 2406:da17:250:5f00::/56
    • SUBNET_ID=subnet-030d8a90e352dd6a7 # me-central-1a 172.31.32.0/20 2406:da17:250:5f0a::/64 No One Zone EFS
    • SUBNET_ID=subnet-03984a2fbe751af4d # me-central-1b 172.31.16.0/20 2406:da17:250:5f0b::/64 No One Zone EFS
    • SUBNET_ID=subnet-0a5758bd3cefb44ea # me-central-1c 172.31.0.0/20 2406:da17:250:5f0c::/64 No One Zone EFS

Israel

  • il-central-1 Tel Aviv vpc-001300aab3fff96a3 172.31.0.0/16 2a05:d025:b2e:d900::/56
    • SUBNET_ID=subnet-0b10e71d7c20f9be1 # il-central-1a 172.31.32.0/20 2a05:d025:b2e:d90a::/64 No One Zone EFS
    • SUBNET_ID=subnet-003c8a27228061d84 # il-central-1b 172.31.16.0/20 2a05:d025:b2e:d90b::/64 No One Zone EFS
    • SUBNET_ID=subnet-0138fe3871346a436 # il-central-1c 172.31.0.0/20 2a05:d025:b2e:d90c::/64 No One Zone EFS

South America

  • sa-east-1 Sao Paulo (Brazil) vpc-0e5046b6cc3667535 172.31.0.0/16 2600:1f1e:c9c:8300::/56
    • SUBNET_ID=subnet-0f338185ace77d10e # sa-east-1a 172.31.0.0/20 2600:1f1e:c9c:830a::/64
    • SUBNET_ID=subnet-08ab8eeee68923465 # sa-east-1b 172.31.16.0/20 2600:1f1e:c9c:830b::/64
    • SUBNET_ID=subnet-0503f679d0bd4969f # sa-east-1c 172.31.32.0/20 2600:1f1e:c9c:830c::/64

Log

  • Published to: https://lamurakami.github.io/blog/2025/02/07/I_created_63_One_Zone_Lifecycle_Managed_AWS_EFS.html
  • February 13, 2025 It looks like it was 11 regions with No One Zone EFS but I did not note eu-central-2 Zurich (Switzerland) until today.
  • On Monday, February 3, 2025 I completed the last test of the new EFS3 filesystems early in the morning after midnight.
    • I found 10 regions where One Zone storage classes are not supported and 7 Availability Zones where One Zone storage classes are not supported but other AZs in the region do support them.
    • For all the rest of the Availability Zones a One Zone EFS was created utilizing Lifecycle Management and the Infrequent Access One Zone storage class.
    • It look like I created and tested 63 EFS for 63 AZs among the 22 Regions where the where One Zone storage classes are available.
  • This page was created in 2025 to facilitate testing my addition of a One Zone EFS with Lifecycle Management in every Availability Zone it was available for at the beginning of 2025.
    • I am only using the filesystem in the us-west-2d Oregon Availability Zone where I put the Zz files and expect to see a 75% reduction in cost over the EBS volume I was using.

up Top of this document up Thursday, February 13, 2025 @ 5:46:47 PM (Alaska Time)