Skip to content

Commit 799d61d

Browse files
committed
refactor implementing tagging policy step in blog
1 parent a3c0261 commit 799d61d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/blog/tag-strat-blog.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ This structure allowed us to clearly distinguish between different environments
3535

3636
### Step 2: Implementing Tagging Policy
3737

38-
With our accounts organized, we moved on to enforce a tagging policy across all our AWS accounts. We established a set of mandatory tags that would be required for every resource, ensuring that all resources were labeled with essential information like the owner, team, and environment.
38+
With our accounts organized, we moved on to enforce a tagging policy across all our AWS accounts. We established a set of mandatory tags that would be required for specific resource, ensuring that resources were labeled with essential information like the owner, management of the rescource etc.
3939

4040
To ensure compliance, we implemented Service Control Policies (SCPs) that blocked the creation of any resources without the necessary tags. This enforcement layer gave us the confidence that our tagging strategy would be consistently applied across all environments.
4141

0 commit comments

Comments
 (0)