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

Glacier for Cloudtrail just increases bill #17

Closed
etwillbefine opened this issue Oct 5, 2019 · 0 comments · Fixed by #20
Closed

Glacier for Cloudtrail just increases bill #17

etwillbefine opened this issue Oct 5, 2019 · 0 comments · Fixed by #20

Comments

@etwillbefine
Copy link
Contributor

Hey,

I was wondering about accessed glacier data and related costs. The Cloudtrail Bucket uses the module to create the bucket. Imo using glacier for cloudtrail files just increases costs without benefiting from it.

Hint from AWS when opening lifecycle rules:

Transitioning small objects to Glacier or Glacier Deep Archive will increase costs.
Before creating a lifecycle rule that transitions small objects to Glacier or Glacier Deep Archive, consider how many objects will be transitioned and how long you plan to keep the objects. Lifecycle request charges for these objects will increase your costs. Learn more or see Amazon S3 pricing

In https://github.com/cloudposse/terraform-aws-s3-log-storage I see the transition being applied without additional conditions.

Would it still be possible (especially for Terraform 0.12 versions) to optionally disable the glacier transition?

maximmi pushed a commit to cloudposse/terraform-aws-s3-log-storage that referenced this issue Feb 12, 2020
* optional transitions to glacier
relates cloudposse/terraform-aws-cloudtrail-s3-bucket#17

* add enable_glacier_transition to README
maximmi added a commit that referenced this issue Feb 24, 2020
* make glacier transition optional
closes #17
relates to cloudposse/terraform-aws-s3-log-storage#23

* do not enable glacier transition by default

* Updated README.md

* Executed 'terraform fmt'

Co-authored-by: Maxim Mironenko <simixido@gmail.com>
Co-authored-by: actions-bot <58130806+actions-bot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant