Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
packplusplus opened this issue Aug 28, 2015 · 47 comments

Comments

@packplusplus
Copy link

packplusplus commented Aug 28, 2015

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 )

@ghost
Copy link

ghost commented Oct 9, 2015

+1

@tisba
Copy link

tisba commented Oct 13, 2015

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 :-/

@tecnobrat
Copy link

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

@sstarcher
Copy link

+1 lifecyle

1 similar comment
@mseiwald
Copy link

mseiwald commented Dec 3, 2015

+1 lifecyle

@rmldsky
Copy link

rmldsky commented Dec 4, 2015

+1 lifecycle

@scalp42
Copy link
Contributor

scalp42 commented Dec 4, 2015

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

@cordoval
Copy link

cordoval commented Dec 4, 2015

buckets are created globally as per amazon

@packplusplus
Copy link
Author

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

@scalp42
Copy link
Contributor

scalp42 commented Dec 4, 2015

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

@brikis98
Copy link
Contributor

brikis98 commented Dec 8, 2015

+1 for lifecycle

@chrisferry
Copy link

+1 for lifecycle.

@ben-nz
Copy link

ben-nz commented Dec 9, 2015

+1 for lifecycle

@amuraru
Copy link

amuraru commented Dec 10, 2015

👍

@iulian-radu
Copy link

+1. See also: #4120

@failshell
Copy link

missing region as well.

+1 for logging.

@jasonyoumans
Copy link

+1 for lifecycle

@ktseytlin
Copy link

+1 for versioning/lifecycle/logging

@ecneladis
Copy link

@jen20
Copy link
Contributor

jen20 commented Jan 16, 2016

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.

@nagas
Copy link

nagas commented Jan 16, 2016

+1

@kingpong
Copy link

+1 cross-region replicaton

@dabdine-r7
Copy link

+1 events

@davido-bs
Copy link

+1 lifecycle

@curena
Copy link

curena commented Mar 2, 2016

+1 events

@egoldschmidt
Copy link

+1 events, lifecycle

@ruippeixotog
Copy link
Contributor

+1 lifecycle

@conorgil
Copy link

conorgil commented Mar 9, 2016

+1 events

@gtmtech
Copy link

gtmtech commented Mar 10, 2016

+1 cross-region replication

@panda87
Copy link

panda87 commented Mar 15, 2016

+1 for lifecycle

@JetStreamPilot
Copy link

+1 for lifecycle

@steve-jansen
Copy link
Contributor

@packplusplus would you please strike log targets and versioning?

Believe both features shipped.

Cheers!

@netflash
Copy link

+1 cross-region replication / lifecycle

@saswatp
Copy link

saswatp commented Mar 30, 2016

+1 cross-region
+1 life-cycle

@jbiel
Copy link

jbiel commented Apr 12, 2016

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

@eyespies
Copy link

+1 cross-region
+1 lifecycle

@alfonso-cabrera
Copy link
Contributor

+1 for cross region replication

@davidblewett
Copy link

+1 lifecycle

@aviflax
Copy link

aviflax commented Apr 15, 2016

+1 lifecycle please!

@ajlanghorn
Copy link
Contributor

+1 lifecycle!

@radeksimko
Copy link
Member

See S3 lifecycle PR in #6220

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

@stack72
Copy link
Contributor

stack72 commented Apr 20, 2016

Lifecycle PR (#6220) has been merged

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

@packplusplus
Copy link
Author

packplusplus commented Apr 20, 2016

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

@stack72
Copy link
Contributor

stack72 commented Apr 20, 2016

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

@hectcastro
Copy link
Contributor

Are event notifications covered by #5473? Also, I think adding support for toggling the newly added transfer acceleration feature would be great (landed in the Go SDK yesterday: aws/aws-sdk-go@174327f):

@stack72
Copy link
Contributor

stack72 commented Jul 5, 2016

Hi all

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

Thanks

Paul

@ghost
Copy link

ghost commented Apr 24, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests