- Newest
- Most votes
- Most comments
Hello,
The behavior you are witnessing is generally observed when the IAM role that is initiating the backup job for S3 is missing permissions required to create S3 backups such as, AWSBackupServiceRolePolicyForS3Backup and AWSBackupServiceRolePolicyForS3Restore.
Note : the above mentioned policies are different from AWSBackupServiceRolePolicyForBackup and AWSBackupServiceRolePolicyForRestore and are required as one time setup for creating S3 backups/restore. You may find this specified in the following document.
[+] Permissions and policies for Amazon S3 backup and restore - https://docs.aws.amazon.com/aws-backup/latest/devguide/s3-backups.html#one-time-permissions-setup
Thus, you may once verify if the said permissions are missing and append those.
Further, internal Backup team is aware that the reflected error could be misleading and hence is actively working on addressing this.
Thank you !
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago