N2WS-19829 - can't create S3 Repository for bucket located in enabled region with assume role account type

• 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 ...

• Copy of RDS to DR target account may fail with Reason code: Unable to create the resource. Verify that you have permission to create service linked role.

   DR copy job may fail with the following error: Error: RDS DR copy failed for region EU Paris (any region can apply) with reason code: Unable to create the resource. Verify that you have permission to create service-linked role. Otherwise, wait and ...

• 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: ...

• Cross region copy of RDS snapshots may fail with error: RDS DR copy snapshot failed (in Backup account). No matching KMS alias in target region

  Issue: The Following error may appear in the CPM Server logs: ERROR: start_copy_region(dr_rds.py:301) RDS DR copy snapshot failed (in Backup account). No matching KMS alias on target region (source EU (Frankfurt), target Asia Pacific (Singapore), RDS ...

• Moving Policy Lifecycles to a Different Repository

  Moving Policy Lifecycles to a Different Repository Overview This article provides the best procedure for moving policy lifecycles to a different storage repository in N2WS. It also addresses common questions regarding the impact of changing the ...