Skip to main content
In this lesson we’ll demonstrate how to add tags to an AWS CloudFormation stack using the AWS Management Console, and how those stack-level tags are propagated to supported underlying resources (for example, an S3 bucket created by the stack). Tagging stacks centrally is useful for cost allocation, environment identification, and lifecycle management.

​
Quick step-by-step summary

  1. Open the CloudFormation console and choose the stack you want to update.
  2. Choose Update stack → Use current template → Next.
  3. On the Configure stack options page, add the tag you want (for example: Key = Status, Value = Active).
  4. Continue through the wizard and submit the update.
  5. Wait for the update to complete, then verify the tag on the stack and on any supported resources.
How it works: when you add a tag at the stack level through the console, CloudFormation attaches that tag to the stack and attempts to propagate it to the resources created by that stack — but only for resource types that natively support tags (S3, EC2, RDS, etc.). Below is the Configure stack options page showing the Status: Active tag being added.
A screenshot of the AWS CloudFormation console on the "Configure stack options" step, showing the Tags section with a key "Status" and value "Active." The left pane shows the stack update progress (Step 1–4) and the page includes controls to add or remove tags.
After you submit the update, wait for the CloudFormation update to finish. Then open the stack’s details page and inspect the Tags section to confirm the new tag appears at the stack level. Next, navigate to the resource created by the stack (S3 in this example) and verify that the tag was propagated. In the S3 console, open the bucket created by the stack and check the Properties or Tags tab. You should see the Status: Active tag alongside CloudFormation-generated tags such as aws:cloudformation:stack-name and aws:cloudformation:logical-id.
A screenshot of the AWS S3 console showing the Tags page for the bucket "eden-kodekloud-xcvt-bkt", listing tag keys and values like Status: Active, aws:cloudformation:stack-name: DemoStack, Environment: Development, and aws:cloudformation:logical-id: MyS3Bucket. One of the tags shows a developer name (displayed in the image).
Common tag values you might use include:
  • Active, Deprecated (lifecycle status)
  • Development, Staging, Production (environment)
  • CostCenter or Owner (billing and ownership)
When you add tags through the CloudFormation console, those tags are associated with the stack. CloudFormation will propagate them to resources created by the stack only if the resource type supports tagging (S3 and many other AWS services do). Resources that do not support tags will not receive the stack tags. For authoritative details on supported resources, see the AWS CloudFormation documentation.

​
Verification checklist

  • Stack Updates: Confirm the stack update completed successfully in CloudFormation.
  • Stack Tags: Open the stack’s Tags section and verify the new tag(s).
  • Resource Tags: Open each resource created by the stack (S3 bucket, EC2 instances, RDS, etc.) and confirm tags were propagated where supported.
  • Billing & Reporting: Ensure your cost allocation/reporting tools can read the tag keys you added (keys are case-sensitive).
That covers how to add and verify CloudFormation stack tags using the AWS Management Console, and how stack-level tags can appear on resources created by that stack.

Watch Video

Practice Lab