[EKS] [Cost Optimization]: Ability to choose log class to be Standard or Infrequent Access
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
EKS logging right now support Standard log class for both Control Plane and Data Plane. If we can enable Infrequent Access Log class for customer, that will save 60% of logging cost for them.
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
There is no option to create Infrequent Access log class while setup of EKS cluster. Also, there is no mechanism to change Log Class post log group is created.
**Are you currently working around this issue?**
No workaround as of now.
Contributor guide
Research direction
No repository files, tests, or implementation entry points are mentioned. Start by clarifying the EKS logging and log-group lifecycle requirements; done means customers can choose Standard or Infrequent Access during cluster setup and change the class after the log group is created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100