Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Workload lifecycle

Focus mode
Workload lifecycle - Best Practices for Tagging AWS Resources

Review accuracy of supporting operational data. Make sure that there are periodic reviews of the tags associated with your workload lifecycle, and that the appropriate stakeholders are involved in these reviews.

Table 7 – Review operational tags as part of the workload lifecycle

Use Case Tag Key Rationale Example Values
Account Owner example-inc:account-owner:owner The owner of the account and it's contained resources. ops-center, dev-ops, app-team
Account Owner Review example-inc:account-owner:review Review of account ownership details being up to date and correct. <review date in the correct format defined in your tagging library>
Data Owner example-inc:data-owner:owner The data owner of the accounts residing data. bi-team, logistics, security
Data Owner Review example-inc:data-owner:review Review of data ownership details being up to date and correct. <review date in the correct format defined in your tagging library>

Assigning tags to suspending accounts before migrating to the suspended OU

Before suspending an account and moving into the suspended OU as detailed in the Organizing Your AWS Environment Using Multiple Accounts whitepaper, tags should be added to the account to aid in your internal tracing and auditing of an account’s lifecycle. For example, a relative URL or ticket reference on an organization’s ITSM ticketing system, that shows the audit trail for an application being suspended.

Table 8 - Add operational tags when workload lifecycle enters new stage

Use Case Tag Key Rationale Example Values
Account Owner example-inc:account-owner:owner The owner of the account and it's contained resources. ops-center, dev-ops, app-team
Data Owner example-inc:data-owner:owner The data owner of the accounts residing data. bi-team, logistics, security
Suspended Date example-inc:suspension:date The date that the account was suspended <suspended date in the correct format defined in your tagging library>
Approval for suspension example-inc:suspension:approval The link to the approval of account suspension workload/deprecation
PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.