Amazon Application Recovery Controller uses AWS Identity and Access Management (IAM) service-linked roles. A service-linked role is a unique type of IAM role that is linked directly to a service— in this case, ARC. Service-linked roles are predefined by ARC and include all the permissions that the service requires to call other AWS services on your behalf for specific purposes.
Service-linked roles make setting up ARC easier because you don’t have to manually add the necessary permissions. ARC defines the permissions of its service-linked roles, and unless defined otherwise, only 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 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.
ARC has the following service-linked roles, which are described in this chapter:
ARC uses the service-linked role named Route53RecoveryReadinessServiceRolePolicy to access resources and configurations to check readiness.
ARC uses the service-linked role named for autoshift practice runs, to monitor customer-provided Amazon CloudWatch alarms and customer AWS Health Dashboard events, and to start practice runs.
Service-linked role permissions for Route53RecoveryReadinessServiceRolePolicy
ARC uses a service-linked role named Route53RecoveryReadinessServiceRolePolicy to access resources and configurations to check readiness. This section describes the permissions for the service-linked role, and information about creating, editing, and deleting the role.
Service-linked role permissions for Route53RecoveryReadinessServiceRolePolicy
This service-linked role uses the managed policy Route53RecoveryReadinessServiceRolePolicy.
The Route53RecoveryReadinessServiceRolePolicy service-linked role trusts the following service to assume the role:
-
route53-recovery-readiness.amazonaws.com
To view the permissions for this policy, see Route53RecoveryReadinessServiceRolePolicy in the AWS Managed Policy Reference.
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 the Route53RecoveryReadinessServiceRolePolicy service-linked role for ARC
You don't need to manually create the Route53RecoveryReadinessServiceRolePolicy 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, 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, ARC creates the service-linked role for you again.
Editing the Route53RecoveryReadinessServiceRolePolicy service-linked role for ARC
ARC does not allow you to edit the Route53RecoveryReadinessServiceRolePolicy service-linked role. After you create the service-linked role, you cannot change the name of the role because other 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 the Route53RecoveryReadinessServiceRolePolicy service-linked role for 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 Route53RecoveryReadinessServiceRolePolicy service-linked role. For more information about readiness checks, see Readiness check in ARC. For more information about cross-account authorizations, see Creating cross-account authorizations in ARC.
Note
If the ARC service is using the role when you try to delete the resources, then the service role deletion might fail. If that happens, wait for a few minutes and try the again to delete the role.
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 ARC service-linked role for readiness check
For updates to the AWS managed policies for the ARC service-linked roles, see the AWS managed policies updates table for ARC. You can also subscribe to automatic RSS alerts on the ARC Document history page.
