AWSElasticDisasterRecoveryRecoveryInstancePolicy
Summary
This policy is attached to the instance role of Elastic Disaster Recovery's Recovery Instance. This policy allows the Elastic Disaster Recovery (DRS) Recovery Instance, which are EC2 instances launched by Elastic Disaster Recovery - to communicate with the DRS service, and to be able to failback to their original source infrastructure. An IAM role with this policy is attached (as an EC2 Instance Profile) by Elastic Disaster Recovery to the DRS Recovery Instances. We do not recommend that you attach this policy to your IAM users or roles.
Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.
Identity
- ARN
arn:aws:iam::aws:policy/service-role/AWSElasticDisasterRecoveryRecoveryInstancePolicy- Default version
- v4
- Created
- Last edited
- Services
- drs, ec2, sts
Control-plane actions (20)
By access level: 1 List, 6 Read, 2 Tagging, 11 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| DRS | 17 of 110 | 6 Read, 1 Tagging, 10 Write; 13 restricted, 3 conditional | drs:CreateSourceServerForDrs, drs:DescribeRecoveryInstances, drs:GetAgentCommandForDrs, drs:GetAgentConfirmedResumeInfoForDrs, drs:GetAgentInstallationAssetsForDrs, drs:GetAgentReplicationInfoForDrs, drs:GetAgentRuntimeConfigurationForDrs, drs:NotifyReplicationServerAuthenticationForDrs, drs:SendAgentLogsForDrs, drs:SendAgentMetricsForDrs, drs:SendClientLogsForDrs, drs:TagResource and 5 more |
| EC2 | 1 of 834 | 1 List; 0 restricted, 0 conditional | ec2:DescribeInstanceTypes |
| STS | 2 of 16 | 1 Tagging, 1 Write; 2 restricted, 2 conditional | sts:AssumeRole, sts:TagSession |
DRS: 17 actions
- drs:CreateSourceServerForDrs (Write)
- drs:DescribeRecoveryInstances (Read)
- drs:GetAgentCommandForDrs (Read)
- drs:GetAgentConfirmedResumeInfoForDrs (Read)
- drs:GetAgentInstallationAssetsForDrs (Read)
- drs:GetAgentReplicationInfoForDrs (Read)
- drs:GetAgentRuntimeConfigurationForDrs (Read)
- drs:NotifyReplicationServerAuthenticationForDrs (Write)
- drs:SendAgentLogsForDrs (Write)
- drs:SendAgentMetricsForDrs (Write)
- drs:SendClientLogsForDrs (Write)
- drs:TagResource (Tagging)
- drs:UpdateAgentBacklogForDrs (Write)
- drs:UpdateAgentConversionInfoForDrs (Write)
- drs:UpdateAgentReplicationInfoForDrs (Write)
- drs:UpdateAgentSourcePropertiesForDrs (Write)
- drs:UpdateReplicationCertificateForDrs (Write)
EC2: 1 actions
- ec2:DescribeInstanceTypes (List)
STS: 2 actions
- sts:AssumeRole (Write)
- sts:TagSession (Tagging)
Data-plane actions (0)
By access level: none.
This policy grants no actions in this plane.
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 13 write, tagging or permissions-management actions, short of full control of any service.
- 2 granted write or permissions-management actions have no data-plane classification from AWS, so the data-plane rule cannot assess them.
Guidance
Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.
Related policies
Same service
- AmazonElasticContainerRegistryPublicReadOnly
- AWS-SSM-DiagnosisAutomation-OperationalAccountAdministrationRolePolicy
- AWS-SSM-RemediationAutomation-OperationalAccountAdministrationRolePolicy
- AWSApplicationDiscoveryAgentlessCollectorAccess
- AWSConfigThirdPartyServiceRolePolicy
- AWSElasticDisasterRecoveryAgentInstallationPolicy
- AWSElasticDisasterRecoveryAgentPolicy
- AWSElasticDisasterRecoveryConsoleFullAccess
Same domain
Frequently asked questions
Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.
Policy JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "DRSRecoveryInstancePolicy1",
"Effect": "Allow",
"Action": [
"drs:SendAgentMetricsForDrs",
"drs:SendAgentLogsForDrs",
"drs:UpdateAgentSourcePropertiesForDrs",
"drs:UpdateAgentReplicationInfoForDrs",
"drs:UpdateAgentConversionInfoForDrs",
"drs:GetAgentCommandForDrs",
"drs:GetAgentConfirmedResumeInfoForDrs",
"drs:GetAgentRuntimeConfigurationForDrs",
"drs:UpdateAgentBacklogForDrs",
"drs:GetAgentReplicationInfoForDrs",
"drs:UpdateReplicationCertificateForDrs",
"drs:NotifyReplicationServerAuthenticationForDrs"
],
"Resource": "arn:aws:drs:*:*:recovery-instance/*",
"Condition": {
"StringEquals": {
"drs:EC2InstanceARN": "${ec2:SourceInstanceARN}"
}
}
},
{
"Sid": "DRSRecoveryInstancePolicy2",
"Effect": "Allow",
"Action": [
"drs:DescribeRecoveryInstances"
],
"Resource": "*"
},
{
"Sid": "DRSRecoveryInstancePolicy3",
"Effect": "Allow",
"Action": [
"ec2:DescribeInstanceTypes"
],
"Resource": "*"
},
{
"Sid": "DRSRecoveryInstancePolicy4",
"Effect": "Allow",
"Action": [
"drs:GetAgentInstallationAssetsForDrs",
"drs:SendClientLogsForDrs",
"drs:CreateSourceServerForDrs"
],
"Resource": "*"
},
{
"Sid": "DRSRecoveryInstancePolicy5",
"Effect": "Allow",
"Action": [
"drs:TagResource"
],
"Resource": "arn:aws:drs:*:*:source-server/*",
"Condition": {
"StringEquals": {
"drs:CreateAction": "CreateSourceServerForDrs"
}
}
},
{
"Sid": "DRSRecoveryInstancePolicy6",
"Effect": "Allow",
"Action": [
"drs:SendAgentMetricsForDrs",
"drs:SendAgentLogsForDrs",
"drs:UpdateAgentSourcePropertiesForDrs",
"drs:UpdateAgentReplicationInfoForDrs",
"drs:UpdateAgentConversionInfoForDrs",
"drs:GetAgentCommandForDrs",
"drs:GetAgentConfirmedResumeInfoForDrs",
"drs:GetAgentRuntimeConfigurationForDrs",
"drs:UpdateAgentBacklogForDrs",
"drs:GetAgentReplicationInfoForDrs"
],
"Resource": "arn:aws:drs:*:*:source-server/*"
},
{
"Sid": "DRSRecoveryInstancePolicy7",
"Effect": "Allow",
"Action": [
"sts:AssumeRole",
"sts:TagSession"
],
"Resource": [
"arn:aws:iam::*:role/service-role/DRSCrossAccountAgentAuthorizedRole_*"
],
"Condition": {
"StringLike": {
"aws:RequestTag/SourceInstanceARN": "${ec2:SourceInstanceARN}"
},
"ForAnyValue:StringEquals": {
"sts:TransitiveTagKeys": "SourceInstanceARN"
}
}
}
]
}
Version history
Current version v4, edited by AWS on 2023-11-27. 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/service-role/AWSElasticDisasterRecoveryRecoveryInstancePolicy
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/service-role/AWSElasticDisasterRecoveryRecoveryInstancePolicy
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/service-role/AWSElasticDisasterRecoveryRecoveryInstancePolicyCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/service-role/AWSElasticDisasterRecoveryRecoveryInstancePolicyTerraform
resource "aws_iam_role_policy_attachment" "service_role_awselasticdisasterrecoveryrecoveryinstancepolicy" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/service-role/AWSElasticDisasterRecoveryRecoveryInstancePolicy"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("service-role/AWSElasticDisasterRecoveryRecoveryInstancePolicy"),
);Sources
Pending editorial review. No editorial sources are listed yet.