Decommissioning Resources
Chapter 15, Improving Deployment, discussed at length the importance of tagging and monitoring resources in order to better understand resources and their usage patterns. This not only helps track resources but also helps identify the orphaned ones that, in most cases, are decommissioned. In this last section of the chapter, you will explore a few key best practices for decommissioning resources on AWS as well as how to implement them. The following are the key considerations:
- Tracking and monitoring resources: In order to effectively track resources, tagging can be set up automatically using automation or AWS Managed Services and performed manually by developers and operational teams on a case-by-case basis, for example, by using cost allocation tags (Chapter 4, Ensuring Cost Optimization). Tags can be set up based on an application’s modernization goals, and an automated workload review and decommission process can also be initiated accordingly...
