Naming S3 buckets in your data layers - AWS Prescriptive Guidance

Naming S3 buckets in your data layers

The following sections provide naming structures for Amazon Simple Storage Service (Amazon S3) buckets in your data lake layers. However, you can customize the S3 bucket and path names according to your organization's requirements. We recommend that you create separate S3 buckets for each individual layer because archiving, versioning, access, and encryption requirements can vary for each layer.

The following diagram shows the recommended naming structure for S3 buckets in the three recommended data lake layers, including separating multiple business units, file formats, and partitions. You can adapt data partitions according to your organization's requirements, but you should use lowercase and key-value pairs (For example, year=yyyy, not yyyy) so that you can update the catalog with the MSCK REPAIR TABLE command.

The naming approach varies for S3 buckets according to the data layer that they are intended for.

S3 buckets must follow the naming guidelines from Bucket naming rules in the Amazon S3 documentation.