The issue arises with enable_loadbalancer_logs = true
Deployment fails, because the EB's ELB does not get permissions to access the bucket.
This is caused by terraform failing to create the policy.
The policy creation fails because it is invalid.
The policy is invalid because a wrong bucket name is used as resource in some of the policy statements.
The bug seems to be that the bucket name is not set properly at
Describe the Bug
The issue arises with
enable_loadbalancer_logs = true
Deployment fails, because the EB's ELB does not get permissions to access the bucket. This is caused by terraform failing to create the policy. The policy creation fails because it is invalid. The policy is invalid because a wrong bucket name is used as resource in some of the policy statements.
The bug seems to be that the bucket name is not set properly at
https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/blob/0.51.2/main.tf#L1107
Expected Behavior
The created policy statements reference the bucket with the correct name
Steps to Reproduce
Screenshots
No response
Environment
modules:
Additional Context
Related to https://github.com/cloudposse/terraform-aws-lb-s3-bucket/issues/81