Browse Source

Merge pull request #567 from open-guides/cost-allocation

Cost allocation tagging.
Corey Quinn 2 years ago
No account linked to committer's email address
1 changed files with 1 additions and 0 deletions
  1. 1

+ 1
- 0 View File

@@ -528,6 +528,7 @@ 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
- To (once enabled) [allocate cost]( Note that cost allocation tags only apply on a forward-looking basis; you can't retroactively apply them to items already billed.
- 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]( to 50 tags per resource.
- 🔹In 2017, AWS introduced the ability to [enforce tagging]( on instance and volume creation, deprecating portions of third party tools such as [Cloud Custodian](