cloudposse/terraform-aws-lb-s3-bucket

Issues

• AWS Account ID doesn't work with newer AWS regions

  #96 opened 2 months ago by akuzkohqs
  0

• Dependency Dashboard

  #45 opened 7 months ago by renovate
  1

• Deployment fails with "MalformedPolicy: Policy has invalid resource" when used as part of terraform-aws-elastic-beanstalk-environment

  #81 opened 7 months ago by benjamin-hg
  1

• Deprecation warnings - bump `cloudposse/s3-log-storage/aws` to 0.28.2

  #55 opened 2 years ago by mwos-sl
  1

• Endless detected changes

  #57 opened 2 years ago by raymondchen625
  0

• Specify exact bucket name

  #41 opened 2 years ago by gregn610
  0

• Vanilla apply results in error

  #49 opened 2 years ago by dutchman80
  1

• s3 bucket policy flaps

  #48 opened 2 years ago by mburns
  5

• Allow for passing additional bucket policy

  #50 opened 2 years ago by razorsedge
  1

• Cannot configure bucket with server side encryption to ALB or NLB

  #9 opened 4 years ago by beingamarnath
  6

• Action Required: Fix Renovate Configuration

  #29 opened 4 years ago by renovate
  0

• Support AWS provider 3.x

  #23 opened 4 years ago by sgrimm
  1

• hi folks, i don't have full context on the test env (but it looks pretty cool!)... since it seems to fail on creating the bucket due to resource/naming conflict (bucket already exists?) i wonder if we could create a random string w/ terraform, use it as part of the bucket name (attributes?), and then retrieve from state so terratest can validate (vs hard-coded name).

  #13 opened 4 years ago by jamengual
  0

• Add Example Usage

  #6 opened 5 years ago by vadim-hleif
  0