Using service-linked roles for Route 53 ARC - Amazon Route 53 Application Recovery Controller

Using service-linked roles for Route 53 ARC

Amazon Route 53 Application Recovery Controller uses a AWS Identity and Access Management (IAM) service-linked role. A service-linked role is a unique type of IAM role that is linked directly to Route 53 ARC. The service-linked role is predefined by Route 53 ARC and includes all the permissions that the service requires to call other AWS services on your behalf.

A service-linked role makes setting up Route 53 ARC easier because you don’t have to manually add the necessary permissions. Route 53 ARC defines the permissions of its service-linked role, and unless defined otherwise, only Route 53 ARC can assume its roles. The defined permissions include the trust policy and the permissions policy, and that permissions policy cannot be attached to any other IAM entity.

You can delete a service-linked role only after first deleting its related resources. This protects your Route 53 ARC resources because you can't inadvertently remove permission to access the resources.

For information about other services that support service-linked roles, see AWS Services that work with IAM and look for the services that have Yes in the Service-linked role column. Choose a Yes with a link to view the service-linked role documentation for that service.

Service-linked role permissions for Route 53 ARC

Route 53 ARC uses the service-linked role named Route53RecoveryReadinessServiceRolePolicy to access resources and configurations to check readiness.

The Route53RecoveryReadinessServiceRolePolicy service-linked role trusts the following service to assume the role:

  • route53-recovery-readiness.amazonaws.com

The role permissions policy allows Route 53 ARC to complete the following actions on the specified resources:

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "dynamodb:DescribeReservedCapacity", "dynamodb:DescribeReservedCapacityOfferings" ], "Resource": "arn:aws:dynamodb:*:*:*" }, { "Effect": "Allow", "Action": [ "dynamodb:DescribeTable", "dynamodb:DescribeTimeToLive" ], "Resource": "arn:aws:dynamodb:*:*:table/*" }, { "Effect": "Allow", "Action": [ "iam:CreateServiceLinkedRole" ], "Resource": "arn:aws:iam::*:role/aws-service-role/servicequotas.amazonaws.com/AWSServiceRoleForServiceQuotas", "Condition": { "StringLike": { "iam:AWSServiceName": "servicequotas.amazonaws.com" } } }, { "Effect": "Allow", "Action": [ "lambda:GetFunctionConcurrency", "lambda:GetFunctionConfiguration", "lambda:GetProvisionedConcurrencyConfig", "lambda:ListProvisionedConcurrencyConfigs", "lambda:ListAliases", "lambda:ListVersionsByFunction" ], "Resource": "arn:aws:lambda:*:*:function:*" }, { "Effect": "Allow", "Action": [ "rds:DescribeDBClusters" ], "Resource": "arn:aws:rds:*:*:cluster:*" }, { "Effect": "Allow", "Action": [ "rds:DescribeDBInstances" ], "Resource": "arn:aws:rds:*:*:db:*" }, { "Effect": "Allow", "Action": [ "route53:ListResourceRecordSets" ], "Resource": "arn:aws:route53:::hostedzone/*" }, { "Effect": "Allow", "Action": [ "route53:GetHealthCheck", "route53:GetHealthCheckStatus" ], "Resource": "arn:aws:route53:::healthcheck/*" }, { "Effect": "Allow", "Action": [ "servicequotas:RequestServiceQuotaIncrease" ], "Resource": "arn:aws:servicequotas:*:*:*" }, { "Effect": "Allow", "Action": [ "sns:GetTopicAttributes", "sns:ListSubscriptionsByTopic" ], "Resource": "arn:aws:sns:*:*:*" }, { "Effect": "Allow", "Action": [ "sqs:GetQueueAttributes", "sqs:GetQueueUrl" ], "Resource": "arn:aws:sqs:*:*:*" }, { "Effect": "Allow", "Action": [ "apigateway:GET", "application-autoscaling:DescribeScalableTargets", "application-autoscaling:DescribeScalingPolicies", "autoscaling:DescribeAccountLimits", "autoscaling:DescribeAutoScalingGroups", "autoscaling:DescribeAutoScalingInstances", "autoscaling:DescribeLifecycleHooks", "autoscaling:DescribeLoadBalancers", "autoscaling:DescribeLoadBalancerTargetGroups", "autoscaling:DescribeNotificationConfigurations", "autoscaling:DescribePolicies", "cloudwatch:GetMetricData", "cloudwatch:DescribeAlarms", "dynamodb:DescribeLimits", "dynamodb:ListGlobalTables", "dynamodb:ListTables", "ec2:DescribeAvailabilityZones", "ec2:DescribeInstances", "ec2:DescribeSubnets", "ec2:DescribeVolumes", "ec2:DescribeVpcs", "ec2:DescribeVpnConnections", "ec2:GetEbsEncryptionByDefault", "ec2:GetEbsDefaultKmsKeyId", "elasticloadbalancing:DescribeInstanceHealth", "elasticloadbalancing:DescribeLoadBalancerAttributes", "elasticloadbalancing:DescribeLoadBalancers", "elasticloadbalancing:DescribeTargetGroups", "elasticloadbalancing:DescribeTargetHealth", "kafka:DescribeCluster", "kafka:DescribeConfigurationRevision", "lambda:ListEventSourceMappings", "lambda:ListFunctions", "rds:DescribeAccountAttributes", "route53:GetHostedZone", "servicequotas:ListAWSDefaultServiceQuotas", "servicequotas:ListRequestedServiceQuotaChangeHistory", "servicequotas:ListServiceQuotas", "servicequotas:ListServices", "sns:GetEndpointAttributes", "sns:GetSubscriptionAttributes" ], "Resource": "*" } ] }

You must configure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see Service-linked role permissions in the IAM User Guide.

Creating a service-linked role for Route 53 ARC

You don't need to manually create a service-linked role. When you create the first readiness check or cross account authorization in the AWS Management Console, the AWS CLI, or the AWS API, Route 53 ARC creates the service-linked role for you.

If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you create the first readiness check or cross account authorization, Route 53 ARC creates the service-linked role for you again.

Editing a service-linked role for Route 53 ARC

Route 53 ARC does not allow you to edit the Route53RecoveryReadinessServiceRolePolicy service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see Editing a service-linked role in the IAM User Guide.

Deleting a service-linked role for Route 53 ARC

If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don’t have an unused entity that is not actively monitored or maintained. However, you must clean up the resources for your service-linked role before you can manually delete it.

After you have removed your readiness checks and your cross-account authorizations, then you can delete the service-linked role. For more information about readiness checks, see Readiness check in Amazon Route 53 Application Recovery Controller. For more information about cross-account authorizations, see Create cross-account authorizations in Route 53 ARC.

Note

If the Route 53 ARC service is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again.

To manually delete the service-linked role using IAM

Use the IAM console, the AWS CLI, or the AWS API to delete the Route53RecoveryReadinessServiceRolePolicy service-linked role. For more information, see Deleting a service-linked role in the IAM User Guide.

Updates to the Route 53 ARC service-linked role (an AWS managed policy)

View details about updates to the service-linked role for Route 53 ARC since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the Document history for the Amazon Route 53 Application Recovery Controller Developer Guide page.

Change Description Date

Route53RecoveryReadinessServiceRolePolicy – Updated policy

Route 53 ARC added a new permission to query information about Lambda functions.

Route 53 ARC uses the following permission to query information about Lambda functions to run readiness checks and determine the readiness status for the functions.

lambda:ListProvisionedConcurrencyConfigs

August 31, 2022

Route53RecoveryReadinessServiceRolePolicy – Updated policy

Route 53 ARC added a new permission to query information about Amazon API Gateway.

Route 53 ARC uses the permission, apigateway:GET, to query information about API Gateway to run readiness checks and determine the readiness status.

October 28, 2021

Route53RecoveryReadinessServiceRolePolicy – Updated policy

Route 53 ARC added new permissions to query information about Lambda functions.

Route 53 ARC uses the following permissions to query information about Lambda functions to run readiness checks and determine the readiness status for those functions.

lambda:GetFunctionConcurrency

lambda:GetFunctionConfiguration

lambda:GetProvisionedConcurrencyConfig

lambda:ListAliases

lambda:ListVersionsByFunction

lambda:ListEventSourceMappings

lambda:ListFunctions

October 8, 2021

Route 53 ARC started tracking changes

Route 53 ARC started tracking changes for its AWS service-linked role.

October 8, 2021

Supported Regions for Route 53 ARC service-linked roles

Route 53 ARC supports using service-linked roles in AWS Regions where Amazon Route 53 is supported.

For a list of the AWS Regions where Amazon Route 53 and other services are currently supported, see the AWS Region Table.