- Newest
- Most votes
- Most comments
This is a known AWS Backup limitation where the AWSServiceRoleForBackup service-linked role lacks necessary EKS permissions for clusters using API_AND_CONFIG_MAP authentication mode. Since you cannot modify AWS-managed service-linked roles, you have three options:
Create a custom service role for AWS Backup instead of using the service-linked role, giving it the required eks:CreateAccessEntry permission along with your backup policies, then specify this role when configuring the backup plan.
Manually create the access entry yourself before backup runs: use eks:CreateAccessEntry to grant the AWSServiceRoleForBackup role principal ARN access to your cluster with appropriate permissions (typically eks:AccessEntryAdmin or similar).
Temporarily switch authentication modes (if possible) by recreating the cluster or specific node groups with CONFIG_MAP-only mode, though this may not be feasible for existing production clusters.
This option worked for my case - I created a custom service role for AWS Backup instead of using the service-linked role, I gave the role the required eks:CreateAccessEntry permission along with other backup policies, then I specified this role when configuring the backup plan.
Relevant content
asked 7 months ago
asked 10 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
