Organization-Environment Naming Convention on AWS
ACM.357 Modifying our naming convention for cross-account resource policies
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
⚙️ Check out my series on Automating Cybersecurity Metrics | Code.
🔒 Related Stories: AWS Security | Secure Code | IAM | AWS Organizations
💻 Free Content on Jobs in Cybersecurity | ✉️ Sign up for the Email List
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In the last post I enabled S3 Bucket Keys on my S3 bucket to reduce costs.
In this post, I need to fix a few things in my S3, KMS and IAM policies related to cross-account deployments.
Renaming buckets to simplify policy deployments
I want to rename my bucket to make it easier to calculate the name of the bucket when deploying buckets.
I want my bucket name, domain name, and repo name to match to some degree — or rather one can easily be calculated from the other. That makes policy creation and consistency easier.
