Beanstalk Application Load Balancer Access Logs WILL NOT DISABLE in console
I am using Elastic Beanstalk on Platform Python 3.8 running on 64bit Amazon Linux 2/3.5.2. I used this guide to create the bucket with appropriate permissions and yes it works: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/enable-access-logging.html Now I want to turn it off.. yet it is "stuck" on enabled in Beanstalk. I can turn it off in the Load Balancer in EC2; see below screenshot:
In the Beanstalk configuration console I keep unchecking the Store Logs from "enabled" yet it never changes.. It keeps my log settings on. I deleted the bucket and it still "sticks" to my configuration. I don't want to mess with the load balancer outside Beanstalk anymore. I want my logs to be DISABLED; I am testing out the load balancers and buckets right now. I have also restarted the environment many times. I prefer not to rebuild; everything works fine.
Here are images of it in Beanstalk:
Thanks!
- Newest
- Most votes
- Most comments
What about configuring ".ebextensions" to disable ALB access logging?
I thought that the access log could be disabled by setting the following.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-elb.html
Resources:
AWSEBLoadBalancer:
Type: AWS::ElasticLoadBalancing::LoadBalancer
Properties:
AccessLoggingPolicy:
Enabled: false
S3BucketName: eb-elb-logs-xxx
If you look at the information from AWS CLI instead of the management console, it may change. The management console may be slow to reflect. However, it is unclear which command can be used to check information about the access log. https://awscli.amazonaws.com/v2/documentation/api/latest/reference/elasticbeanstalk/index.html
Does the operation history when unchecked not remain as a CloudTrail event? If there are still events there, there may be errors, etc. Are the events logged in the changelogs listed in the following documents? https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.changehistory.html?icmpid=docs_elasticbeanstalk_console
After that, it could be a bug in the UI, etc.I am tempted to try the .ebextensions route.. but I don't want to deploy yet right now. Why would the console "break"?
I checked the operation history.. great observation. I think it is a bug; look at my answer for the image.
I think you should report bugs to AWS support.
AccessLogsS3Enabled: true
This never changes back to false.. when I uncheck. It just gets ignored in the config.
How do we report this bug? It's very bad; it basically stays on once it's TRUE. Also the aws:elbv2:loadbalancer gets listed as a "change made" which is weird because the logs DID not turn off. Nothing changed.. It's just stuck in this endless on loop.
UPDATE: confirmed it was a bug that they fixed and that I tested to being as "fixed."
Relevant content
- Accepted Answerasked 2 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 12 days ago
I just changed to a new bucket and checked "Enabled" under "Store logs". It works; then I went back to uncheck it and the environment updates fine; then I go back and it is still CHECKED. What gives? I can only leave it on? This is pretty bad..