How to upgrade an IAM Role to match new requirements
| KB ID: | 3199 |
| Product: | Veeam Backup for AWS |
| Version: | 2.x and later |
| Published: | 2020-06-24 |
| Last Modified: | 2020-12-11 |
Challenge
After upgrading Veeam Backup for AWS you can receive the following notifications:
- “Role for account <Account Name> has insufficient permissions for workers management. You need to grant them first”
- “Role for account <Account Name> has insufficient permissions to use change-tracking in policies. You need to grant them first”
You might also want to add the missing IAM Role permissions after the Check Permissions operation performing - here you will find information on how to create access keys and a list of necessary permissions for the user, whose keys you will use to upgrade an IAM role.
Solution
Within Veeam Backup for AWS, this happens when several new features and improvements are introduced. As a result, it requires new permissions for Worker IAM Role to operate normally. You will see these notifications if any role on the accounts page is missing some permissions.
The usual cause is the Worker IAM Role missing required permissions from the list below.
To resolve this issue manually, you should add the following permissions to your Worker IAM Role.
The usual cause is the Worker IAM Role missing required permissions from the list below.
To resolve this issue manually, you should add the following permissions to your Worker IAM Role.
"ec2:AttachVolume",
"ec2:CopySnapshot",
"ec2:CreateTags",
"ec2:CreateVolume",
"ec2:DeleteSnapshot",
"ec2:DeleteVolume",
"ec2:DescribeAvailabilityZones",
"ec2:DescribeConversionTasks",
"ec2:DescribeImages",
"ec2:DescribeInstanceAttribute",
"ec2:DescribeInstances",
"ec2:DescribeInstanceStatus",
"ec2:DescribeInstanceTypes",
"ec2:DescribeKeyPairs",
"ec2:DescribeRegions",
"ec2:DescribeSecurityGroups",
"ec2:DescribeSnapshots",
"ec2:DescribeSubnets",
"ec2:DescribeVolumes",
"ec2:DescribeVpcs",
"ec2:DetachVolume",
"ec2:GetEbsDefaultkmsKeyId",
"ec2:ModifyInstanceAttribute",
"ec2:RunInstances",
"ec2:StartInstances",
"ec2:StopInstances",
"ec2:TerminateInstances",
"iam:GetContextKeysForPrincipalPolicy",
"iam:PassRole",
"iam:SimulatePrincipalPolicy",
"kms:CreateGrant",
"kms:DescribeKey",
"kms:GetKeyPolicy",
"kms:ListAliases",
"kms:ListKeys",
"kms:ReEncryptFrom",
"kms:ReEncryptTo",Alternatively, you can use the Check Permissions button on the Accounts page within the Configuration section to see the list of missing permissions.
To let Veeam Backup for AWS grant the missing permissions:
- Click on the notification message.
- In the IAM Roles Update window, provide access keys of an IAM user that is authorized to update permissions of the IAM role, and then click Apply.
Veeam Backup for AWS does not store one-time access keys in the configuration database.
- To make sure that the missing permissions were successfully granted, perform Check AWS Permissions for the updated role on the Accounts page.
How to generate access keys for automatically IAM Role update
To learn how to create access keys, see the AWS Documentation.
The user whose keys you will use to upgrade an IAM role should have the following permissions:
"iam:CreatePolicy",
"iam:GetRole",
"iam:GetPolicy",
"iam:AttachRolePolicy"| KB ID: | 3199 |
| Product: | Veeam Backup for AWS |
| Version: | 2.x and later |
| Published: | 2020-06-24 |
| Last Modified: | 2020-12-11 |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
