terraform-aws-modules/terraform-aws-efs

Example can cause a lot of AWS spend

Closed this issue · 4 comments

smcpeck commented

Description

Maybe not really "bug"... but not a feature request either, IMO. The example should really be changed a bit given the potential cost implications of running it without scrutiny.

Problem:

The current example can quickly chew up some AWS spend...
image

Suggestion:

  1. Change the region to "YOUR-REGION" so resources don't end up somewhere that the user might not be monitoring. Region should always be a very conscious choice.
  2. Reduce the provisioned_throughput_in_mibps from 256 to something very small.
  3. Better yet, change the example to Elastic Throughput!
bryantbiggs commented

apologies - the examples are intended to show the different configurations a module supports and also to ensure that the different use cases are actually supported and work as intended. In this case, provisioned throughput is shown to ensure users can set and configure that. If we can lower the value, and cost, then please feel free to submit a PR for that

github-actions commented

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

github-actions commented

This issue was automatically closed because of stale in 10 days

github-actions commented

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.