Hidden Facts About Amazon S3 Storage

 

We all think we know S3. It's an endless hard drive in the cloud, right? Simple. But what if I told you that some of its most basic behaviors are elegant illusions, purposely made for a global scale? Let’s uncover the surprising truths that make S3 one of the most powerful and misunderstood services in the cloud.

1. That Bucket Name You Want? It's Probably Already Taken.

When you create your first S3 bucket, you'll quickly face a startling wall: your bucket name has to be globally unique. Not just in your account, or even your region, but across every single AWS account out there.

"Your bucket name must be unique across all regions and all accounts ever created in AWS."

Here's the catch that surprises many developers. The reason for this odd behavior is brilliant: S3 buckets can be accessed via HTTP endpoints, such as bucket-name.s3.region.amazonaws.com. Your bucket name is part of a globally unique DNS entry. This forces a creative approach to naming, which is why you see formats like stephane-demo-s3-v5. It’s a practical solution to a global design constraint.

2. S3 Looks Global, But It's Built on a Regional Foundation.

Here's the first major illusion of S3. You open the management console, and it shows a single, unified list of all your buckets from around the world. It feels like one massive, global service. This is a common point of confusion and a trap for beginners.

The truth is that every single S3 bucket is created in and lives within a specific AWS region you choose at the start. While the management interface is global for convenience, your data's physical location is always regional. This distinction is important for understanding data locality, reducing latency for your users, and meeting compliance rules.

3. The Folders Are a Lie.

You can click "Create folder" in the S3 console, upload files into it, and navigate a directory tree that feels completely familiar. But this is just a convenient illusion designed to make you feel comfortable. The reality is more interesting.

"Amazon S3 does not have a concept of directories per se... anything and everything in Amazon S3 is actually a key."

S3 is a large, flat key-value store. Each object is identified by a "key," which is simply its full path. For a file beach.jpg inside what appears to be an images folder, the key is images/beach.jpg. This key comes from the prefix (images/) and the object name (beach.jpg). This "lie" is the key to S3's incredible scalability. By skipping the complexity of traditional hierarchical filesystems—like complex inode lookups and directory navigation limits—S3 can retrieve any object with the same speed, whether you have ten files or ten trillion.

4. Deleting a File Might Not Actually Delete It.

This is where things get intriguing. Once you turn on Versioning for a bucket—a smart move to protect your data—the delete action changes its meaning. When you delete an object from a versioned bucket, it doesn't disappear. Instead, S3 places a "delete marker" on top of it, making that delete marker the new "current" version of the object.

This behavior acts as a powerful safety net. It protects you from accidental deletions and makes rollbacks easy. To restore your "deleted" file, you don’t need a backup; you just delete the delete marker, and the previous version is back. A "permanent delete" only happens when you specifically target and delete a certain version ID—a much more intentional action.

5. Making a Bucket Public Requires Turning Two Keys.

Here's a classic developer experience: you want to make an object public. You carefully create a JSON Bucket Policy, setting the Principal to "*" (everyone) and the Action to s3:GetObject. You apply it, refresh the page, and get "Access Denied."

This annoying experience reveals a crucial truth. Making a bucket public requires two keys. The Bucket Policy is the first, but it can be overridden by the second, more powerful key: the "Block Public Access" settings. These settings are a safety switch that AWS added to avoid accidental data leaks. Even with a perfect public policy, if "Block Public Access" is turned on, your bucket will never be public. It’s a deliberate design choice that shows a commitment to security by default, forcing you to be clear and intentional when sharing data with the world.

Conclusion

S3's simplicity is its greatest strength—and its most clever trick. These "surprising truths" aren't quirks; they are the key parts that let it work at an unprecedented scale. The next time you create a bucket, you won't just be storing a file; you'll be using one of the most powerful and purposefully designed systems on the web.

AWS EFS Features and Limitations Explained

Managing traditional shared file storage can be a constant headache. The ongoing cycle of maintenance, configuring backups, and handling growing security concerns often feels like a full-time job. This is the problem that Amazon Elastic File System (EFS) aims to solve. It is a serverless, scalable file storage system designed for 11 nines durability and 99.9% availability. EFS handles the heavy lifting so you can focus on your applications.

While EFS is a powerful and flexible service, some of its key features and operational realities are not immediately clear. A closer look reveals important details that can make a big difference in your architecture. This article shares five impactful and surprising truths about EFS that every cloud professional should know to avoid common mistakes and make the most of its potential.

1. You Don't Provision Capacity. It Starts at 6 KB

First, it's important to understand what "serverless" and "elastic" mean in this context. With EFS, you never have to provision or manage storage capacity. The file system grows and shrinks automatically as you add or remove files. This takes away the guesswork of capacity planning. Surprisingly, a new, empty file system has a metered size of just 6 KB.

EFS allows you to share file data without pre-provisioning or managing storage capacity and performance.

This elastic capacity relies on an architecture designed for resilience. EFS is a regional service, meaning it automatically stores your data within and across multiple availability zones by default. This gives you two major benefits: you don’t have to worry about running out of disk space, and you get high availability without any manual setup. This combination of no provisioning and built-in multi-AZ resilience makes EFS a powerful tool for creating durable applications without complex storage management.

2. Cross-Region Replication Is a One-Way Street

EFS provides a robust disaster recovery and content distribution feature called inter-region replication. This allows you to create and maintain a copy of your file system in a different AWS region. While this is great for building resilient, distributed applications, there is an important limitation to keep in mind.

The only catch is that when the data gets replicated to a different region, the copy becomes read-only. You won’t be able to write back to it.

The replicated copy of your file system in the other region is strictly read-only. This design is ideal for disaster recovery, where the secondary region can be used for analysis or promoted to primary, but it does not support an active-active model that requires immediate write capabilities. You must clearly define your disaster recovery strategy. EFS replication is for failover and content distribution, not concurrent multi-region writes.

3. Security Is a Two-Way Handshake Between Security Groups

A common mistake when connecting an EC2 instance to an EFS file system is misconfiguring the security group. Many engineers set the outbound rules on their instance's security group correctly but forget that the EFS side also needs explicit permission.

You need to ensure that the security group protecting your EFS mount target allows NFS traffic on port 2049 from your EC2 instance's security group.

To establish a successful connection, the security group attached to the EFS Mount Target—the network interface that EFS places in your VPC—must have an inbound rule that allows traffic on the NFS port (2049) from the EC2 instance's security group. This two-way handshake is a basic security control that prevents unauthorized access. Getting this wrong is the leading cause of "mount" command timeouts and connection failures.

4. Some Configuration Choices Are Permanent

When you create an EFS file system, you encounter several performance settings. Two key settings are Throughput Mode (e.g., Enhanced or Bursting) and Performance Mode (General Purpose or Max I/O). It’s important to understand the long-term effects of these choices. You can modify the Throughput Mode later, but the Performance Mode is a permanent decision.

Remember that these choices are interconnected. If you select the recommended Enhanced throughput mode with the Elastic option, AWS limits your Performance Mode choice to General Purpose only. You cannot choose Max I/O with this configuration. This makes upfront workload analysis essential. A mismatch between your application needs and the chosen performance mode means you’ll need to fully migrate to a new EFS file system.

5. It's Linux Only (For Now)

Amazon EFS is based on the Network File System (NFS) protocol, specifically supporting versions 4.0 and 4.1, which are native to Linux environments. This choice leads to a major limitation: EFS is designed only for Linux-based instances and cannot be mounted on Windows.

As of now, you still cannot use it with Windows-based instances. You need to attach it to Linux-based instances.

However, EFS can also be mounted by on-premises Linux servers using AWS Direct Connect or a VPN, making it a suitable solution for hybrid cloud setups. For teams planning a cloud architecture, this is an important consideration: if your workload is Windows-based, you should explore services like Amazon FSx, but if it's Linux-based (cloud or on-prem), EFS is a strong option.

Conclusion

Amazon EFS is a powerful service. Its true value emerges when you understand its underlying details. By internalizing these five truths—from its 6 KB starting size and read-only replication to its permanent performance modes and specific security needs—you shift from simply using EFS to strategically designing with it. You will avoid costly mistakes, easily pass security audits, and build resilient applications.

Now that you know these EFS insights, what architectural opportunity will you explore next?