Terraform: AWS provider: aws_s3_bucket resource; missing versioning, lifecycle, logging, etc

Created on 28 Aug 2015  ยท  47Comments  ยท  Source: hashicorp/terraform

AWS s3 APIs support several feature missing the aws_s3_bucket resource.

Terraform does not provide a way to;

  • Turn on / off versioning
  • Lifecycle control policies
  • Logging targets
  • Turn on / off Requestor pays
  • Cross region replication
  • Events

Versioning and lifecycle policies are the features I'm most interested in, but I was trying to be complete (like the format in #3096 h/t: @clstokes )

enhancement provideaws

Most helpful comment

See S3 lifecycle PR in https://github.com/hashicorp/terraform/pull/6220

Feel free to post any feedback related to the implementation there ^

All 47 comments

+1

This would be a feature we are interested in as well. We have lots of buckets that have at least one lifecycle policy and it's a pain to manage them via AWS Console (or API) after a TF run :-/

+1 on events, we need this for our implementation.

+1 lifecyle

+1 lifecyle

+1 lifecycle

I also don't believe you can create a bucket in a specific region (unless I'm wrong).

buckets are created globally as per amazon

Buckets are namespaced globally, but you can indicate which region you want the data stored in. See documentation.

That's what I meant by region sorry as in "cant tell Terraform to use us-west-2" for example.

+1 for lifecycle

+1 for lifecycle.

+1 for lifecycle

:+1:

+1. See also: #4120

missing region as well.

+1 for logging.

+1 for lifecycle

+1 for versioning/lifecycle/logging

Hi all. Thanks for commenting. As of the latest released version (0.6.9) versioning is supported (https://www.terraform.io/docs/providers/aws/r/s3_bucket.html).

In addition, logging support is on the master branch and will form part of the next release, though you can build from source now (clone; make updatedeps, make bin) the meantime assuming you have a Go environment.

Lifecycle policies, requestor pays, cross region replication and events are not yet supported - we will aim to support them soon but have a decent backlog of issues and pull requests to get through at the moment. If anyone wants to take these on in the meantime, either myself or @catsby should be able to review and merge.

+1

+1 cross-region replicaton

+1 events

+1 lifecycle

+1 events

+1 events, lifecycle

+1 lifecycle

+1 events

+1 cross-region replication

+1 for lifecycle

+1 for lifecycle

@packplusplus would you please strike log targets and versioning?

Believe both features shipped.

Cheers!

+1 cross-region replication / lifecycle

+1 cross-region
+1 life-cycle

I am very interested in being able to manage s3 lifecycle policies with Terraform.

+1 cross-region
+1 lifecycle

+1 for cross region replication

+1 lifecycle

+1 lifecycle please!

+1 lifecycle!

See S3 lifecycle PR in https://github.com/hashicorp/terraform/pull/6220

Feel free to post any feedback related to the implementation there ^

Lifecycle PR (#6220) has been merged

Can someone summate what is still missing from this issue? @packplusplus ?

I updated the original issue with strike thrus (good idea @steve-jansen).

@stack72 do you want to see these issues split out so you can wrestle them better, or do you like it in one place to point to?

What's left:

  • Turn on / off Requestor pays - Not hugely important, I was just trying to highlight what wasn't supported that existed in aws. No one has +1'd
  • Cross region replication - Seems pretty popular. Also seems hard, there are IAM components that would have to be either auto created or called out in docs.
  • Events - Also seems popular. covered by pull/5473

nice summation @packplusplus - let's leave this issue as the main place right now :)

Are event notifications covered by https://github.com/hashicorp/terraform/pull/5473? Also, I think adding support for toggling the newly added transfer acceleration feature would be great (landed in the Go SDK yesterday: https://github.com/aws/aws-sdk-go/commit/174327fecba83be58dea4dee0ef1599652e0f2e5):

Hi all

I just split the last 2 remaining items out into #7490 and #7491

Thanks

Paul

I'm going to lock this issue because it has been closed for _30 days_ โณ. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jrnt30 picture jrnt30  ยท  3Comments

carl-youngblood picture carl-youngblood  ยท  3Comments

rjinski picture rjinski  ยท  3Comments

pawelsawicz picture pawelsawicz  ยท  3Comments

ketzacoatl picture ketzacoatl  ยท  3Comments