Fine-grained Amazon Route 53 access with IAM condition keys (Part 3)
Networking & Content Delivery Blog
This article demonstrates how to implement fine-grained Route 53 access for federated users in AWS IAM Identity Center using session tags derived from user attributes.
- Use IAM Identity Center session tags with user attributes to control DNS record access without individual policies
- Map user attributes to ABAC attributes in IAM Identity Center for dynamic permission evaluation
- Create permission sets with conditional policies using route53:ChangeResourceRecordSetsNormalizedRecordNames
- Federated users can manage only DNS records matching their assigned attribute values in shared hosted zones
- Automatically adapts permissions when user attributes change without policy updates
This approach eliminates the need for per-user policies while maintaining least-privilege access for federated users managing shared Route 53 hosted zones.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Apr 28
2026
2026
Implementing fine-grained Amazon Route 53 access using IAM condition keys (Part 2)
Aug 25
2025
2025
Implementing fine-grained Amazon Route 53 access using AWS IAM condition keys (Part 1)
Jun 4
2026
2026
Achieve least-privilege access for Amazon Route 53 Profiles
Mar 25
2026
2026
Amazon Route 53 Profiles now supports granular IAM permissions for resource and VPC associations
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.