[EKS] [request]: Control Plane Logs to S3
<!-- Please keep this note for the community --> ### 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 <!-- Thank you for keeping this note for the community --> **Tell us about your request** EKS currently supports control plane logging to CloudWatch Logs (#26), but it would be helpful to support S3 as an alternative log destination. This would be in line with many other AWS services that support logging both to both CloudWatch and S3. **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?** Enabling S3 as a log destination would help with a few issues. **_Cost_**: CloudWatch Logs is much more expensive than S3 for both ingestion and storage of logs, and it can easily cost in the hundreds of dollars a month to ingest the control plane logs even for a small cluster. In my experience, the **_cost of CloudWatch Log ingestion for many clusters exceeds the cost of EKS itself_**. For customers that have compliance requirements that require the collection of audit
Posted by mike-stewart on Nov 14, 2020, 10:35 PM
Tags
Related issues
- >Beef is already too expensive for most people.
- I gave this a go a couple of years ago.
- I haven't seen any use cases around me, although I'm not that advanced user.
- [BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
- > Unfortunately it doesn't offer free hosting for hobbyists.
- Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
pricing (Software)
>Beef is already too expensive for most people.
I gave this a go a couple of years ago.
I haven't seen any use cases around me, although I'm not that advanced user.
[BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
> Unfortunately it doesn't offer free hosting for hobbyists.
Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
This criticism seems like a complete non-sequitur to me.
Bring back the GitHub Copilot in the CLI commands to not break workflows
[EKS] [request]: Control Plane Logs to S3
<!-- Please keep this note for the community --> ### 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 <!-- Thank you for keeping this note for the community --> **Tell us about your request** EKS currently supports control plane logging to CloudWatch Logs (#26), but it would be helpful to support S3 as an alternative log destination. This would be in line with many other AWS services that support logging both to both CloudWatch and S3. **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?** Enabling S3 as a log destination would help with a few issues. **_Cost_**: CloudWatch Logs is much more expensive than S3 for both ingestion and storage of logs, and it can easily cost in the hundreds of dollars a month to ingest the control plane logs even for a small cluster. In my experience, the **_cost of CloudWatch Log ingestion for many clusters exceeds the cost of EKS itself_**. For customers that have compliance requirements that require the collection of audit
Comments (0)
No comments yet. Start the discussion.