Indexing IAM Role Permissions

In this article

    When performing EFS indexing operations, Veeam Backup for AWS launches worker instances in the same AWS account where file systems processed by backup policies belong. To communicate with these instances, Veeam Backup for AWS attaches to the instances Indexing IAM roles. To learn how EFS indexing works, see EFS Backup.

    Indexing IAM Role Permissions

    To allow Veeam Backup for AWS to create indexes of the backed up EFS file systems, IAM roles specified in the EFS backup policy settings must meet the following requirements:

    1. The IAM roles must be included at least in one instance profile. For more information on instance profiles, see AWS Documentation.
    2. The backup appliance must be granted permissions to assume the IAM roles.

    To allow the backup appliance to assume an IAM role, configure trusted relationships for the role and add the following statement to the trusted policy.

    {

     "Version": "2012-10-17",

     "Statement": [

       {

         "Effect": "Allow",

         "Action": "sts:AssumeRole",

         "Principal": {

           "AWS": "<Role ARN>"

         }

       }

     ]

    }

    Where <Role ARN> is the ARN either of the Impersonation IAM role attached to the backup appliance or of an AWS account to which the backup appliance belongs. For more information on the Impersonation IAM role, see Required IAM Permissions. To learn how to configure trust relationships for a role and to find the Impersonation IAM role ARN, see Appendix A. Creating IAM Roles in AWS.

    1. The Amazon EC2 service must be granted permissions to assume the IAM roles.

    To allow the Amazon EC2 service to assume an IAM role, configure trusted relationships for the role and add the following statement to the trusted policy.

    {

     "Version": "2012-10-17",

     "Statement": [

       {

         "Effect": "Allow",

         "Action": "sts:AssumeRole",

         "Principal": {

           "Service": "ec2.amazonaws.com"

         }

       }

     ]

    }

    To learn how to configure trusted relationships, see Appendix A. Creating IAM Roles in AWS.

    1. The IAM roles must be granted the following permissions:

    {

       "Version": "2012-10-17",

       "Statement": [

           {

               "Action": [

                   "ec2messages:AcknowledgeMessage",

                   "ec2messages:DeleteMessage",

                   "ec2messages:FailMessage",

                   "ec2messages:GetEndpoint",

                   "ec2messages:GetMessages",

                   "ec2messages:SendReply",

                   "iam:GetContextKeysForPrincipalPolicy",

                   "iam:GetRole",

                   "iam:ListAccountAliases",

                   "iam:ListInstanceProfilesForRole",

                   "iam:SimulatePrincipalPolicy",

                   "ssm:DescribeAssociation",

                   "ssm:DescribeDocument",

                   "ssm:GetDeployablePatchSnapshotForInstance",

                   "ssm:GetDocument",

                   "ssm:GetManifest",

                   "ssm:GetParameter",

                   "ssm:GetParameters",

                   "ssm:ListAssociations",

                   "ssm:ListInstanceAssociations",

                   "ssm:PutComplianceItems",

                   "ssm:PutConfigurePackageResult",

                   "ssm:PutInventory",

                   "ssm:UpdateAssociationStatus",

                   "ssm:UpdateInstanceAssociationStatus",

                   "ssm:UpdateInstanceInformation",

                   "ssmmessages:CreateControlChannel",

                   "ssmmessages:CreateDataChannel",

                   "ssmmessages:OpenControlChannel",

                   "ssmmessages:OpenDataChannel",

                   "sts:AssumeRole"

               ],

                         "Resource": "*",

                         "Effect": "Allow"

             }

       ]

    }