AmazonRoute53FullAccess
Summary
Provides full access to all Amazon Route 53 via the AWS Management Console, as the AWS Managed Policy Reference Guide describes it.
Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.
Identity
- ARN
arn:aws:iam::aws:policy/AmazonRoute53FullAccess- Default version
- v8
- Created
- Last edited
- Services
- apigateway, cloudfront, cloudwatch, ec2, elasticbeanstalk, elasticloadbalancing, es, iam, lightsail, route53, route53domains, s3, sns, tag
Control-plane actions (126)
By access level: 35 List, 33 Read, 3 Tagging, 55 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| API Gateway | 1 of 44 | 1 Read; 1 restricted, 0 conditional | apigateway:GET |
| CloudFront | 3 of 173 | 1 List, 2 Read; 0 restricted, 0 conditional | cloudfront:GetConnectionGroup, cloudfront:GetDistributionTenantByDomain, cloudfront:ListDistributions |
| CloudWatch | 1 of 160 | 1 Read; 0 restricted, 0 conditional | cloudwatch:DescribeAlarms |
| EC2 | 3 of 834 | 3 List; 0 restricted, 0 conditional | ec2:DescribeRegions, ec2:DescribeVpcEndpoints, ec2:DescribeVpcs |
| Elastic Beanstalk | 1 of 50 | 1 List; 0 restricted, 0 conditional | elasticbeanstalk:DescribeEnvironments |
| ELB | 1 of 77 | 1 List; 0 restricted, 0 conditional | elasticloadbalancing:DescribeLoadBalancers |
| OpenSearch Service | 2 of 138 | 2 List; 0 restricted, 0 conditional | es:DescribeDomains, es:ListDomainNames |
| IAM | 1 of 190 | 1 Write; 1 restricted, 1 conditional | iam:CreateServiceLinkedRole |
| Lightsail | 1 of 161 | 1 Read; 0 restricted, 0 conditional | lightsail:GetContainerServices |
| Route 53 | All 71 actions (see the Route 53 page) | 22 List, 16 Read, 1 Tagging, 32 Write; 0 restricted, 0 conditional | route53:* |
| Route 53 Domains | All 36 actions (see the Route 53 Domains page) | 3 List, 9 Read, 2 Tagging, 22 Write; 0 restricted, 0 conditional | route53domains:* |
| S3 | 2 of 155 | 2 Read; 0 restricted, 0 conditional | s3:GetBucketLocation, s3:GetBucketWebsite |
| SNS | 2 of 40 | 2 List; 0 restricted, 0 conditional | sns:ListSubscriptionsByTopic, sns:ListTopics |
| Resource Group Tagging | 1 of 9 | 1 Read; 0 restricted, 0 conditional | tag:GetResources |
API Gateway: 1 actions
- apigateway:GET (Read)
CloudFront: 3 actions
- cloudfront:GetConnectionGroup (Read)
- cloudfront:GetDistributionTenantByDomain (Read)
- cloudfront:ListDistributions (List)
CloudWatch: 1 actions
- cloudwatch:DescribeAlarms (Read)
EC2: 3 actions
- ec2:DescribeRegions (List)
- ec2:DescribeVpcEndpoints (List)
- ec2:DescribeVpcs (List)
Elastic Beanstalk: 1 actions
- elasticbeanstalk:DescribeEnvironments (List)
ELB: 1 actions
- elasticloadbalancing:DescribeLoadBalancers (List)
OpenSearch Service: 2 actions
- es:DescribeDomains (List)
- es:ListDomainNames (List)
IAM: 1 actions
- iam:CreateServiceLinkedRole (Write)
Lightsail: 1 actions
- lightsail:GetContainerServices (Read)
S3: 2 actions
- s3:GetBucketLocation (Read)
- s3:GetBucketWebsite (Read)
SNS: 2 actions
- sns:ListSubscriptionsByTopic (List)
- sns:ListTopics (List)
Resource Group Tagging: 1 actions
- tag:GetResources (Read)
Data-plane actions (3)
By access level: 1 List, 2 Read.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| CloudWatch | 2 of 5 | 2 Read; 0 restricted, 0 conditional | cloudwatch:GetMetricData, cloudwatch:GetMetricStatistics |
| S3 | 1 of 25 | 1 List; 0 restricted, 0 conditional | s3:ListBucket |
CloudWatch: 2 actions
- cloudwatch:GetMetricData (Read)
- cloudwatch:GetMetricStatistics (Read)
S3: 1 actions
- s3:ListBucket (List)
Excluded and conditional actions
No patterns are excluded by NotAction or Deny statements.
Resource scope and attachment
Resource scope across granted actions: mixed.
Can be attached: Yes, to users, groups and roles.
Why this tier
- Grants at least 80% of the write and permissions-management actions of: route53 (32 of 32), route53domains (22 of 22).
Guidance
Practical scope
The first statement allows route53:* and route53domains:* on Resource "*", plus actions for other services: cloudfront:ListDistributions, cloudfront:GetDistributionTenantByDomain, cloudfront:GetConnectionGroup, cloudwatch:DescribeAlarms, cloudwatch:GetMetricStatistics, cloudwatch:GetMetricData, ec2:DescribeVpcs, ec2:DescribeVpcEndpoints, ec2:DescribeRegions, elasticloadbalancing:DescribeLoadBalancers, elasticbeanstalk:DescribeEnvironments, es:ListDomainNames, es:DescribeDomains, lightsail:GetContainerServices, s3:ListBucket, s3:GetBucketLocation, s3:GetBucketWebsite, sns:ListTopics, sns:ListSubscriptionsByTopic and tag:GetResources. apigateway:GET is allowed on arn:aws:apigateway:*::/domainnames. iam:CreateServiceLinkedRole is allowed on all resources when the service name is route53healthchecks.amazonaws.com.
Use cases
- Manage Amazon Route 53 and Route 53 Domains from the AWS Management Console.
Best practices
- AWS managed policies don't grant least privilege permissions. The IAM User Guide suggests using IAM Access Analyzer to see which permissions principals actually use, then writing a custom policy or generating one with only the required permissions.
Security considerations
- route53:* and route53domains:* allow every Route 53 and Route 53 Domains action on all resources.
- The policy also allows iam:CreateServiceLinkedRole on all resources, limited by condition to the route53healthchecks.amazonaws.com service name.
- You cannot change the permissions in an AWS managed policy. If AWS updates the policy, the update affects every user, group and role it is attached to.
Assignment guidance
You can attach this policy to your users, groups and roles. The reference page also links to guidance on creating a permission set using AWS managed policies in IAM Identity Center. It fits where full Route 53 access is intended. Where a narrower scope is needed, AWS recommends customer managed policies specific to your use cases.
Related policies
Same service
- AmazonECSServiceRolePolicy
- AmazonRoute53AutoNamingFullAccess
- AmazonRoute53AutoNamingRegistrantAccess
- AmazonRoute53DomainsFullAccess
- AmazonRoute53DomainsReadOnlyAccess
- AmazonRoute53ReadOnlyAccess
- AWSCloudMapFullAccess
- AWSCloudMapRegisterInstanceAccess
Same domain
- AmazonAPIGatewayAdministrator
- AmazonAPIGatewayInvokeFullAccess
- AmazonApplicationRecoveryControllerRegionSwitchPlanExecutionPolicy
- AmazonECSInfrastructureRoleforExpressGatewayServices
- AmazonECSInfrastructureRoleForGatewayHostSharedALB
- AmazonECSInfrastructureRolePolicyForLoadBalancers
- AmazonECSInfrastructureRolePolicyForVpcLattice
- AmazonEKSClusterPolicy
Frequently asked questions
- When should I attach AmazonRoute53FullAccess?
- The reference page describes it as full access to all Amazon Route 53 via the AWS Management Console, and says you can attach it to users, groups and roles. Attach it where that scope is intended.
- What does AmazonRoute53FullAccess grant?
- It allows route53:* and route53domains:* on all resources, a set of read actions for CloudFront, CloudWatch, EC2, load balancing, Elastic Beanstalk, OpenSearch, Lightsail, S3, SNS and tagging, apigateway:GET on custom domain names, and creating a service-linked role for route53healthchecks.amazonaws.com.
- What are the security risks of AmazonRoute53FullAccess?
- route53:* and route53domains:* allow every action in both services on all resources. AWS managed policies do not grant least privilege permissions, and an AWS update to the policy affects every identity it is attached to.
Policy JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"route53:*",
"route53domains:*",
"cloudfront:ListDistributions",
"cloudfront:GetDistributionTenantByDomain",
"cloudfront:GetConnectionGroup",
"cloudwatch:DescribeAlarms",
"cloudwatch:GetMetricStatistics",
"cloudwatch:GetMetricData",
"ec2:DescribeVpcs",
"ec2:DescribeVpcEndpoints",
"ec2:DescribeRegions",
"elasticloadbalancing:DescribeLoadBalancers",
"elasticbeanstalk:DescribeEnvironments",
"es:ListDomainNames",
"es:DescribeDomains",
"lightsail:GetContainerServices",
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:GetBucketWebsite",
"sns:ListTopics",
"sns:ListSubscriptionsByTopic",
"tag:GetResources"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": "apigateway:GET",
"Resource": "arn:aws:apigateway:*::/domainnames"
},
{
"Effect": "Allow",
"Action": [
"iam:CreateServiceLinkedRole"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"iam:AWSServiceName": "route53healthchecks.amazonaws.com"
}
}
}
]
}
Version history
Current version v8, edited by AWS on 2026-10-08. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.
Attach snippets
AWS CLI
aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AmazonRoute53FullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonRoute53FullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonRoute53FullAccessCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AmazonRoute53FullAccessTerraform
resource "aws_iam_role_policy_attachment" "amazonroute53fullaccess" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AmazonRoute53FullAccess"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AmazonRoute53FullAccess"),
);Sources
- AmazonRoute53FullAccess (AWS Managed Policy Reference Guide) (retrieved ; supports summary, practicalScope, useCases, securityConsiderations, assignmentGuidance, faqs)
- AWS managed policies for job functions (IAM User Guide) (retrieved ; supports bestPractices, faqs)
- Managed policies and inline policies (IAM User Guide) (retrieved ; supports securityConsiderations, faqs)