-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
477 | Enable ALB access logs for EKS clusters #484
Conversation
💰 Infracost estimate: monthly cost will not change
129 projects have no cost estimate changes. Infracost output
This comment will be updated when the cost estimate changes. Is this comment useful? Yes, No, Other |
@Franr Cisco there's anything else pending before we can change this PR from draft? Let's us know and we could review it when needed. |
yes, I was not able to bring up the cluster to be able to test it... there were some errors and I desisted. |
@exequielrafaela alright Exe, I was finally able to test it! Moving the PR into ready to review. |
@Franr small one related to CI test for terraform canonical format => https://app.circleci.com/pipelines/github/binbashar/le-tf-infra-aws/3095/workflows/b22009a1-7f14-47b9-b243-b51deb4be59a/jobs/3876 easily fixed with |
apps-devstg/us-east-1/k8s-eks-demoapps/k8s-components/networking-ingress.tf
Outdated
Show resolved
Hide resolved
apps-devstg/us-east-1/k8s-eks/k8s-components/networking-ingress.tf
Outdated
Show resolved
Hide resolved
Co-authored-by: Diego OJeda (BinBash) <[email protected]>
What?
We are adding a variable to create a bucket and enable access logs on the EKS ALB.
Why?
For security/traceability.
References
closes #477