From c607c0e84653adf2f8466b11c45b9e240f170328 Mon Sep 17 00:00:00 2001 From: Corey Quinn Date: Thu, 13 Apr 2017 16:47:58 -0700 Subject: [PATCH] Flesh out tagging --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index a8cced5..9d27860 100644 --- a/README.md +++ b/README.md @@ -494,6 +494,8 @@ So if you’re not going to manage your AWS configurations manually, what should - To label lifecycles, such as temporary resources or one that should be deprovisioned in the future - To distinguish production-critical infrastructure (e.g. serving systems vs backend pipelines) - To distinguish resources with special security or compliance requirements +- 🔸For many years, there was a notorious 10 tag limit per resource, which could not be raised and caused many companies significant pain. As of 2016, this was [raised](https://aws.amazon.com/blogs/security/now-organize-your-aws-resources-by-using-up-to-50-tags-per-resource/) to 50 tags per resource. +- In 2017, AWS introduced the ability to [enforce tagging](https://aws.amazon.com/blogs/aws/new-tag-ec2-instances-ebs-volumes-on-creation/) on instance and volume creation, deprecating portions of third party tools such as [Cloud Custodian](https://github.com/capitalone/cloud-custodian). Managing Servers and Applications ---------------------------------