Skip to main content
IAM Policy Map

AmazonRoute53FullAccess

AdminAWS managedActiveReviewedShow on mapCompare

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.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
API Gateway1 of 441 Read; 1 restricted, 0 conditionalapigateway:GET
CloudFront3 of 1731 List, 2 Read; 0 restricted, 0 conditionalcloudfront:GetConnectionGroup, cloudfront:GetDistributionTenantByDomain, cloudfront:ListDistributions
CloudWatch1 of 1601 Read; 0 restricted, 0 conditionalcloudwatch:DescribeAlarms
EC23 of 8343 List; 0 restricted, 0 conditionalec2:DescribeRegions, ec2:DescribeVpcEndpoints, ec2:DescribeVpcs
Elastic Beanstalk1 of 501 List; 0 restricted, 0 conditionalelasticbeanstalk:DescribeEnvironments
ELB1 of 771 List; 0 restricted, 0 conditionalelasticloadbalancing:DescribeLoadBalancers
OpenSearch Service2 of 1382 List; 0 restricted, 0 conditionales:DescribeDomains, es:ListDomainNames
IAM1 of 1901 Write; 1 restricted, 1 conditionaliam:CreateServiceLinkedRole
Lightsail1 of 1611 Read; 0 restricted, 0 conditionallightsail:GetContainerServices
Route 53All 71 actions (see the Route 53 page)22 List, 16 Read, 1 Tagging, 32 Write; 0 restricted, 0 conditionalroute53:*
Route 53 DomainsAll 36 actions (see the Route 53 Domains page)3 List, 9 Read, 2 Tagging, 22 Write; 0 restricted, 0 conditionalroute53domains:*
S32 of 1552 Read; 0 restricted, 0 conditionals3:GetBucketLocation, s3:GetBucketWebsite
SNS2 of 402 List; 0 restricted, 0 conditionalsns:ListSubscriptionsByTopic, sns:ListTopics
Resource Group Tagging1 of 91 Read; 0 restricted, 0 conditionaltag: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.

Data-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
CloudWatch2 of 52 Read; 0 restricted, 0 conditionalcloudwatch:GetMetricData, cloudwatch:GetMetricStatistics
S31 of 251 List; 0 restricted, 0 conditionals3: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.

Same service

Same domain

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

Download 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/AmazonRoute53FullAccess

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AmazonRoute53FullAccess

Terraform

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