Skip to content

Commit 2349764

Browse files
committed
add step for handling existing resources without tags
1 parent 24f1a82 commit 2349764

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

content/blog/tag-strat-blog.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -173,6 +173,13 @@ After defining the policies, the next crucial step is to attach them to the appr
173173
- Go to the `Tag policies` tab and click `Create policy` to define your Tag Policy.
174174
- After creating the policy, click on `Targets` to attach it to the desired OU.
175175

176+
### Handling Existing Resources Without Tags
177+
178+
Addressing the challenge of existing resources that were created before implementing the tagging policy was crucial. To bring these resources into compliance without causing any unexpected downtime, we followed a structured approach:
179+
180+
- **Tagging Existing Resources**:
181+
We utilized the AWS Tag Editor to identify all untagged resources. This tool enabled us to efficiently apply the necessary tags to multiple resources across various regions and accounts, ensuring consistency and compliance.
182+
176183
## Testing the Policy
177184

178185
After implementing the tagging and scp policies, we conducted rigorous testing to ensure compliance across our EC2 resources. We deployed several EC2 instances with and without the mandatory tags to verify the enforcement mechanisms.

0 commit comments

Comments
 (0)