c729bdff43
Users commonly ask how the S3 backend can be used in an organization that splits its infrastructure across many AWS accounts. We've traditionally shied away from making specific recommendations here because we can't possibly anticipate the different standards and regulations that constrain each user. This new section attempts to describe one possible approach that works well with Terraform's workflow, with the goal that users make adjustments to it taking into account their unique needs. Since we are intentionally not being prescriptive here -- instead considering this just one of many approaches -- it deviates from our usual active writing style in several places to avoid giving the impression that these are instructions to be followed exactly, which in some cases requires the use of passive voice even though that is contrary to our documentation style guide. For similar reasons, this section is also light on specific code examples, since we do not wish to encourage users to just copy-paste the examples without thinking through the consequences. |
||
|---|---|---|
| .. | ||
| backends | ||
| commands | ||
| configuration | ||
| import | ||
| internals | ||
| modules | ||
| plugins | ||
| providers | ||
| provisioners | ||
| registry | ||
| state | ||
| index.html.markdown | ||