- Newest
- Most votes
- Most comments
Hello,
From your query description, I understand you noticed that you have been trying to enforce tagging strategy using Service Control Policy (SCP) for resources in your AWS organization using the reference document [1] providing example for EC2 instances.
However, you were not able to replicate the same for other resources like DynamoDB tables, RDS cluster and S3 buckets. Please, let me know if my understanding is incorrect.
The cause for the same is that not all AWS services does not support Tag Based Access Control .In order to check whether an AWS service supports authorization based on tags, see the following document “AWS services that work with IAM” and look for the services that have Yes in the Authorization based on tags (ABAC) column. Choose the name of the service to view the authorization and access control documentation for that service. [2]
Thus, looking into the list, I could validate that DynamoDB does not support ABAC while Amazon S3 supports tag-based authorization for only object resources. However, I was able to enforces tags based authorization for the RDS cluster using the SCP below:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Statement1",
"Effect": "Deny",
"Action": ["rds:CreateDBCluster"],
"Resource": ["arn:aws:rds:*:*:cluster:*"],
"Condition": {
"Null": {
"aws:RequestTag/test": "true"
}
}
}
]
}
I hope this helps. If you need further info, let me know in the comments; otherwise I'd appreciate if you mark my answer as "ACCEPTED".
Kind regards,
Arpit C.
References:
[1] Implement AWS resource tagging strategy using AWS Tag Policies and Service Control Policies (SCPs)
DynamoDb does now support ABAC: https://aws.amazon.com/about-aws/whats-new/2024/09/amazon-dynamodb-attribute-based-access-control/
However, you must enable it in order to get it to work. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/abac-enable-ddb.html
Relevant content
- asked 3 years ago
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
