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

• Related Articles

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

• S3 Cleanup may fail after upgrade to v2.6.0 if there is no worker configuration for the account/region in which S3 Repository resides

  S3 Cleanup may fail after upgrade to v2.6.0 if there is no worker configuration for the account/region in which S3 Repository resides The following errors may be printed in the S3 Cleanup Log: Policy 'PolicyName' (Wed 07/10/2019 09:36:23 AM) Info All ...

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

• How to backup EC2 instance located in another account

  Background: You can backup ec2 instances that are located in a different account then the N2WS server, This Guide shows the needed configuration for this AWS Configuration You need to create a role in the target account IAM that has the following: 1. ...

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