This is an archive version of the document. To get the most up-to-date information, see the current version.

Repository IAM Role Permissions

To allow Veeam Backup for AWS to create backup repositories in an Amazon S3 bucket and to access the repository when performing backup and restore operations, IAM roles specified in the repository settings must be granted the following permissions:

{

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

"Statement": [

{

"Effect": "Allow",

"Action": [

"s3:DeleteObject",

"s3:DeleteObjectVersion",

"s3:GetObject",

"s3:GetObjectRetention",

"s3:GetObjectVersion",

"s3:PutObject",

"s3:PutObjectRetention",

"s3:RestoreObject"

"Resource": "arn:aws:s3:::<yourbucketname>/*"

{

"Effect": "Allow",

"Action": [

"s3:ListBucket",

"s3:ListBucketVersions",

"s3:GetBucketLocation",

"s3:GetBucketObjectLockConfiguration",

"s3:GetBucketVersioning"

"Resource": "arn:aws:s3:::<yourbucketname>"

{

"Effect": "Allow",

"Action": [

"ec2:DescribeRegions",

"iam:GetContextKeysForPrincipalPolicy",

"iam:ListAccountAliases",

"iam:SimulatePrincipalPolicy",

"s3:ListAllMyBuckets"

"Resource": "*"

}

]

}

To encrypt data stored in backup repositories using AWS KMS keys, IAM roles used to create the backup repositories must be granted the following permissions:

{

"Effect": "Allow",

"Action": [

"kms:Decrypt",

"kms:DescribeKey",

"kms:Encrypt",

"kms:ListAliases",

"kms:ListKeys"

"Resource": "*"

}

Important

If you plan to use KMS key encryption for backup repositories, consider the following:

The key policy of an AWS KMS key that will be used to encrypt a repository must allow the IAM role specified in the repository settings access to the key.
AWS managed keys cannot be used to encrypt repositories due to AWS limitations.

To learn how to create IAM roles and assign them the required permissions, see Appendix A. Creating IAM Roles in AWS.