AWSElasticDisasterRecoveryFailbackPolicy

OperatorService roleActivePermissions reviewedShow on map Compare

Summary

This policy allows using the Elastic Disaster Recovery Failback Client, which is used to failback Recovery Instances back to your original source infrastructure. 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/AWSElasticDisasterRecoveryFailbackPolicy
Default version: v3
Created: 2021-11-17
Last edited: 2026-07-22
Services: drs

Control-plane actions (18)

By access level: 6 Read, 12 Write.

Control-plane actions by service
Service	Granted	Access levels and limits	Granted by
DRS	18 of 110	6 Read, 12 Write; 12 restricted, 0 conditional	drs:DescribeRecoveryInstances, drs:DescribeReplicationServerAssociationsForDrs, drs:GetAgentSnapshotCreditsForDrs, drs:GetChannelCommandsForDrs, drs:GetFailbackCommandForDrs, drs:GetFailbackLaunchRequestedForDrs, drs:IssueAgentCertificateForDrs, drs:NotifyAgentAuthenticationForDrs, drs:NotifyAgentConnectedForDrs, drs:NotifyAgentDisconnectedForDrs, drs:NotifyAgentReplicationProgressForDrs, drs:NotifyConsistencyAttainedForDrs and 6 more

DRS: 18 actions

drs:DescribeRecoveryInstances (Read)
drs:DescribeReplicationServerAssociationsForDrs (Read)
drs:GetAgentSnapshotCreditsForDrs (Read)
drs:GetChannelCommandsForDrs (Read)
drs:GetFailbackCommandForDrs (Read)
drs:GetFailbackLaunchRequestedForDrs (Read)
drs:IssueAgentCertificateForDrs (Write)
drs:NotifyAgentAuthenticationForDrs (Write)
drs:NotifyAgentConnectedForDrs (Write)
drs:NotifyAgentDisconnectedForDrs (Write)
drs:NotifyAgentReplicationProgressForDrs (Write)
drs:NotifyConsistencyAttainedForDrs (Write)
drs:SendChannelCommandResultForDrs (Write)
drs:SendClientLogsForDrs (Write)
drs:SendClientMetricsForDrs (Write)
drs:SendVolumeStatsForDrs (Write)
drs:UpdateAgentReplicationProcessStateForDrs (Write)
drs:UpdateFailbackClientLastSeenForDrs (Write)

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 12 write, tagging or permissions-management actions, short of full control of any service.
3 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.

Same service

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

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "DRSFailbackPolicy1",
      "Effect": "Allow",
      "Action": [
        "drs:SendClientMetricsForDrs",
        "drs:SendClientLogsForDrs"
      ],
      "Resource": "*"
    },
    {
      "Sid": "DRSFailbackPolicy2",
      "Effect": "Allow",
      "Action": [
        "drs:GetChannelCommandsForDrs",
        "drs:SendChannelCommandResultForDrs"
      ],
      "Resource": "*"
    },
    {
      "Sid": "DRSFailbackPolicy3",
      "Effect": "Allow",
      "Action": [
        "drs:DescribeReplicationServerAssociationsForDrs",
        "drs:DescribeRecoveryInstances"
      ],
      "Resource": "*"
    },
    {
      "Sid": "DRSFailbackPolicy4",
      "Effect": "Allow",
      "Action": [
        "drs:GetFailbackCommandForDrs",
        "drs:UpdateFailbackClientLastSeenForDrs",
        "drs:NotifyAgentAuthenticationForDrs",
        "drs:UpdateAgentReplicationProcessStateForDrs",
        "drs:NotifyAgentReplicationProgressForDrs",
        "drs:NotifyAgentConnectedForDrs",
        "drs:NotifyAgentDisconnectedForDrs",
        "drs:NotifyConsistencyAttainedForDrs",
        "drs:GetFailbackLaunchRequestedForDrs",
        "drs:IssueAgentCertificateForDrs",
        "drs:GetAgentSnapshotCreditsForDrs",
        "drs:SendVolumeStatsForDrs"
      ],
      "Resource": "arn:aws:drs:*:*:recovery-instance/${aws:SourceIdentity}"
    }
  ]
}

Version history

Current version v3, edited by AWS on 2026-07-22. 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/AWSElasticDisasterRecoveryFailbackPolicy
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/service-role/AWSElasticDisasterRecoveryFailbackPolicy
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/service-role/AWSElasticDisasterRecoveryFailbackPolicy

CloudFormation

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

Terraform

resource "aws_iam_role_policy_attachment" "service_role_awselasticdisasterrecoveryfailbackpolicy" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/service-role/AWSElasticDisasterRecoveryFailbackPolicy"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("service-role/AWSElasticDisasterRecoveryFailbackPolicy"),
);

Sources

Pending editorial review. No editorial sources are listed yet.