Beanstalk Application Load Balancer Access Logs WILL NOT DISABLE in console

0

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:

Enter image description here

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:

Enter image description here

Enter image description here

Thanks!

  • 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..

profile picture
00 111
asked a year ago387 views
3 Answers
0

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
profile picture
EXPERT
answered a year ago
0

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. Enter image description here

profile picture
00 111
answered a year ago
0

UPDATE: confirmed it was a bug that they fixed and that I tested to being as "fixed." Enter image description here

profile picture
00 111
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions