aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
Unable to control EKS cluster owner at creation time.
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::EKS::Cluster
### Resource name
_No response_
### Description
When creating an EKS cluster the user/role running the CloudFormation becomes the owner of the Cluster, with implicit and unrevokable access via the system:masters RBAC group. This ownership cannot be changed or revoked. Additionally, this root-level permission does not show up in the `aws-auth` configmap. The only way to determine the owner/creator after the fact is by querying CloudTrail for the cluster creation event (assuming that the event still exists).
Designation of cluster ownership should be explicit, mutable, and easily discoverable from the AWS EKS API.
### Other Details
_No response_
Contributor guide
Research direction
Start with the AWS::EKS::Cluster resource and the EKS API behavior described in the issue, then review how CloudTrail and the aws-auth ConfigMap currently expose cluster access. Done means cluster ownership can be explicitly designated, changed or revoked, and discovered through the EKS API rather than only through the creation event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100