Unexpected issues may occur when editing an account created by CPM CLI

• Related Articles

• Permission check may fail with an error "Could not assume role"

  Issue: Permission check may fail with this error message: ERROR:  get_assume_role_credentials(aws_utils.py:1337)  Could not assume role arn arn:<AWS account ARN:RoleName> from account <CPM Account> (<CPM user>), reason User arn:<AWS account ARN:IAM ...

• EFS - cross account tag scan may fail with Error: Invalid IAM role ARN

  When adding EFS to a policy via a tag, it may fail with one of the following errors: (tag for example: efstesting+vault=n2ws+exp_opt=D+exp_opt_val=30+role_arn=arn:aws:iam::12345678:role/CPM) Critical Error - Can't update EFS to backup targets. Error: ...

• Cannot complete server configuration "please attach an IAM role to continue" - converting an IAM user to an IAM role

  On a new install or after upgrading CPM, you may be met with an error on step 3 of initial configuration which does not allow you to proceed. "It seems this instance does not have an IAM role associated with it. Please attach an IAM role to continue" ...

• How to add an additional AWS account to CPM for Backup or DR

  When adding an additional AWS account to CPM for Backup or DR, there are two ways to grant CPM access to the account: Authentication: Assume Role or IAM User "CPM Instance IAM role" can only access the account the CPM server is running in and cannot ...

• FLR or Copy to S3 with Exception: could not assume role

  Issues: When doing file level recovery(FLR) or copy to S3 operation in the same account, N2WS might need to assume its own role to generate a token for the worker, this could lead to the below error ERROR: ...