AWS prescriptive-guidance documentation change
Summary
Updated terminology from 'S3 bucket' to 'Amazon S3 bucket' for consistency, clarified bucket deletion/reuse timing (48-72 hours), fixed example formatting, and emphasized versioning recommendations.
Security assessment
Changes focus on terminology consistency, operational guidance (e.g., bucket reuse timing), and formatting. While versioning is mentioned as a security-adjacent feature, the updates only reinforce existing recommendations rather than introducing new security content or addressing vulnerabilities.
Diff
diff --git a/prescriptive-guidance/latest/defining-bucket-names-data-lakes/faq.md b/prescriptive-guidance/latest/defining-bucket-names-data-lakes/faq.md index dc51eb666..29e4d6426 100644 --- a//prescriptive-guidance/latest/defining-bucket-names-data-lakes/faq.md +++ b//prescriptive-guidance/latest/defining-bucket-names-data-lakes/faq.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Defining S3 bucket and path names for data lake layers on the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Defining Amazon S3 bucket and path names for data lake layers](welcome.html) @@ -5 +5 @@ -What name should I use for a multi-Region Amazon Simple Storage Service (Amazon S3) bucket?Do I need to use raw, stage, and analytics as the names for my data lake layers?Is it possible to rename an S3 bucket?What happens if I delete an S3 bucket and want to reuse the name?Are there limitations on what I can include in my S3 bucket or path's name? Can I use more layers than the landing zone, raw, stage, and analytics layers in my data lake?What happens if I have not defined my parameters?How can I track costs at the business unit level?What features should I consider when creating an S3 bucket naming standard? +What name should I use for a multi-Region bucket?Do I need to use raw, stage, and analytics as the names for my data lake layers?Is it possible to rename an Amazon S3 bucket?What happens if I delete a bucket and want to reuse the name?Are there limitations on what I can include in my bucket name or path name?Can I use more layers than the landing zone, raw, stage, and analytics layers in my data lake?What happens if I have not defined my parameters?How can I track costs at the business unit level?What features should I consider when creating a naming standard? @@ -9 +9 @@ What name should I use for a multi-Region Amazon Simple Storage Service (Amazon -This section provides answers to commonly raised questions about defining S3 bucket and path names for data lake layers on the AWS Cloud. +This section provides answers to commonly raised questions about defining Amazon Simple Storage Service (Amazon S3) bucket and path names for data lake layers on the AWS Cloud. @@ -11 +11 @@ This section provides answers to commonly raised questions about defining S3 buc -## What name should I use for a multi-Region Amazon Simple Storage Service (Amazon S3) bucket? +## What name should I use for a multi-Region bucket? @@ -13 +13 @@ This section provides answers to commonly raised questions about defining S3 buc -You can use our recommended S3 bucket naming format and change the AWS Region identifier. For example, `examplecompany-raw-**useast1** -12345-dev` and `examplecoompany-raw-**uswest1** -12345-dev`. +You can use our recommended Amazon S3 bucket naming format and change the AWS Region identifier. Examples include `examplecompany-raw-useast1-12345-dev` and `examplecoompany-raw-uswest1-12345-dev`. @@ -17 +17 @@ You can use our recommended S3 bucket naming format and change the AWS Region id -No, you can name your layers according to your requirements. However, we strongly recommended that you use an S3 bucket for the data layer that contains the original file formats and that has versioning enabled. +No, you can name your layers according to your requirements. However, we strongly recommended that you use an Amazon S3 bucket for the data layer that contains the original file formats and enable versioning for this bucket. @@ -19 +19 @@ No, you can name your layers according to your requirements. However, we strongl -## Is it possible to rename an S3 bucket? +## Is it possible to rename an Amazon S3 bucket? @@ -21 +21 @@ No, you can name your layers according to your requirements. However, we strongl -No. If you want to use a different S3 bucket name, you must create a new bucket with the new name. This one reason why we recommend having a clearly defined and consistent naming approach for S3 buckets. +No. If you want to use a different Amazon S3 bucket name, you must create a new bucket with the new name. This is one reason why we recommend having a clearly defined and consistent naming approach for Amazon S3 buckets. @@ -23 +23 @@ No. If you want to use a different S3 bucket name, you must create a new bucket -## What happens if I delete an S3 bucket and want to reuse the name? +## What happens if I delete a bucket and want to reuse the name? @@ -25 +25 @@ No. If you want to use a different S3 bucket name, you must create a new bucket -If you delete an S3 bucket and want to create a new bucket with the same name, you must wait several minutes for the name to become available again. S3 bucket names are globally unique and all AWS accounts share the same namespace. +If you delete an Amazon S3 bucket and want to create a new bucket with the same name, you must wait for the name to become available again. It can take 48–72 hours for the changes to take effect. It's a best practice to wait at least 48 hours before creating a new bucket that reuses a previous name. Amazon S3 bucket names are globally unique, and all AWS accounts share the same namespace. @@ -27 +27 @@ If you delete an S3 bucket and want to create a new bucket with the same name, y -## Are there limitations on what I can include in my S3 bucket or path's name? +## Are there limitations on what I can include in my bucket name or path name? @@ -29 +29 @@ If you delete an S3 bucket and want to create a new bucket with the same name, y -Only lowercase letters, numbers, dashes, and dots are allowed in S3 bucket names. Bucket names must be three to 63 characters in length, must begin and end with a number or letter, and cannot be in an IP address format. The names must also be globally unique. +Only lowercase letters, numbers, dashes, and dots are allowed in Amazon S3 bucket names. Bucket names must be 3–63 characters in length, must begin and end with a number or letter, and cannot be in an IP address format. The names must also be globally unique. @@ -31 +31 @@ Only lowercase letters, numbers, dashes, and dots are allowed in S3 bucket names -For S3 bucket paths, you can use uppercase letters, but we recommend that you only use lowercase letters. Paths can also include additional symbols, but we recommend that you only use underscores, dashes, slashes, and numbers. +For Amazon S3 bucket paths, you can use uppercase letters, but we recommend that you only use lowercase letters. Paths can also include additional symbols, but we recommend that you use only underscores, dashes, slashes, and numbers. @@ -39 +39 @@ Yes, you can use as many layers as you want. However, we recommend having a land -Certain parameters (for example, business units) don't need to be incorporated into the S3 bucket name but can be part of the path. This means that they don't need to be immediately determined because paths can be added after an S3 bucket is created. +Certain parameters, such as business units, don't need to be incorporated into the Amazon S3 bucket name but can be part of the path. This means that they don't need to be immediately determined because paths can be added after an Amazon S3 bucket is created. @@ -43 +43 @@ Certain parameters (for example, business units) don't need to be incorporated i -This depends on your account strategy. If you have business units split up into different AWS accounts, you can assign cost allocation tags to S3 buckets that reflect the bucket costs for each business unit. +This depends on your account strategy. If your business units have separate AWS accounts, you can assign cost allocation tags to Amazon S3 buckets that reflect the bucket costs for each business unit. @@ -45 +45 @@ This depends on your account strategy. If you have business units split up into -If your account strategy doesn't separate out business units into different AWS accounts, then you can use different buckets for each business unit by adding the business unit to the bucket name (for example, `exampleco-businessunit1-raw-useast1-12345-dev`). However, this means that you have to manage many S3 buckets. +If your account strategy doesn't separate business units into different AWS accounts, then you can use different buckets for each business unit. Add the business unit to the bucket name, such as `exampleco-businessunit1-raw-useast1-12345-dev`. However, this means that you have to manage many Amazon S3 buckets. @@ -47 +47 @@ If your account strategy doesn't separate out business units into different AWS -## What features should I consider when creating an S3 bucket naming standard? +## What features should I consider when creating a naming standard? @@ -49 +49 @@ If your account strategy doesn't separate out business units into different AWS -You must ensure that your S3 bucket names use features that are only available at the bucket level. For example, cost tags, bucket encryption, and versioning are features that are only available for an entire S3 bucket. This means that they apply to all objects and paths in the S3 bucket. +You must make sure that your Amazon S3 bucket names use features that are only available at the bucket level. For example, cost tags, bucket encryption, and versioning are features that are only available for an entire Amazon S3 bucket. This means that they apply to all objects and paths in the bucket. @@ -51 +51 @@ You must ensure that your S3 bucket names use features that are only available a -Object versioning is also an important feature to consider. You should turn on versioning for your raw layer's S3 buckets, because you want to make sure that you can see previous versions if there are changes to the data. However, versioning might not be necessary for all the layers in your data lake and retaining multiple versions can cause unnecessary costs. +Object versioning is also an important feature to consider. You should turn on versioning for your raw layer's Amazon S3 buckets. This makes sure that you can access previous versions if there are changes to the data. However, versioning might not be necessary for all the layers in your data lake, and retaining multiple versions can cause unnecessary costs.