mirror of
https://github.com/nickpoida/og-aws.git
synced 2025-02-15 03:11:57 +00:00
Merge pull request #433 from QuinnyPig/indentation
fix formatting on my earlier PR
This commit is contained in:
commit
f02b8ac650
1 changed files with 2 additions and 2 deletions
|
@ -496,8 +496,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).
|
||||
- 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
|
||||
---------------------------------
|
||||
|
|
Loading…
Reference in a new issue