You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| delimiter | Delimiter to be used between `namespace`, `stage`, `name` and `attributes`| string |`-`| no |
92
-
| enabled | Set to `false` to prevent the module from creating any resources | bool |`true`| no |
130
+
| delimiter | Delimiter to be used between `namespace`, `environment`, `stage`, `name` and `attributes`| string |`-`| no |
131
+
| enabled | Set to false to prevent the module from creating any resources | bool |`true`| no |
132
+
| environment | Environment, e.g. 'prod', 'staging', 'dev', 'pre-prod', 'UAT' | string | `` | no |
93
133
| force_destroy | A boolean string that indicates all objects should be deleted from the bucket so that the bucket can be destroyed without error. These objects are not recoverable | bool |`false`| no |
94
134
| kms_master_key_arn | The AWS KMS master key ARN used for the `SSE-KMS` encryption. This can only be used when you set the value of `sse_algorithm` as `aws:kms`. The default aws/s3 AWS KMS master key is used if this element is absent while the `sse_algorithm` is `aws:kms`| string | `` | no |
95
135
| lifecycle_rule_enabled | Enable or disable lifecycle rule | bool |`false`| no |
96
-
| name |Name (e.g. `app` or `cluster`)| string |-|yes|
97
-
| namespace | Namespace (e.g. `eg` or `cp`)| string | `` | no |
136
+
| name |Solution name, e.g. 'app' or 'jenkins'| string |``|no|
137
+
| namespace | Namespace, which could be your organization name or abbreviation, e.g. 'eg' or 'cp'| string | `` | no |
98
138
| noncurrent_version_expiration_days | Specifies when noncurrent object versions expire | number |`90`| no |
99
139
| noncurrent_version_transition_days | Number of days to persist in the standard storage tier before moving to the glacier tier infrequent access tier | number |`30`| no |
100
140
| policy | A valid bucket policy JSON document. Note that if the policy document is not specific enough (but still valid), Terraform may view the policy as constantly changing in a terraform plan. In this case, please make sure you use the verbose/specific version of the policy | string | `` | no |
101
141
| prefix | Prefix identifying one or more objects to which the rule applies | string | `` | no |
102
142
| region | If specified, the AWS region this bucket should reside in. Otherwise, the region used by the callee | string | `` | no |
103
143
| sse_algorithm | The server-side encryption algorithm to use. Valid values are `AES256` and `aws:kms`| string |`AES256`| no |
| user_enabled | Set to `true` to create an IAM user with permission to access the bucket | bool |`false`| no |
107
147
| versioning_enabled | A state of versioning. Versioning is a means of keeping multiple variants of an object in the same bucket | bool |`false`| no |
108
148
@@ -146,42 +186,47 @@ Check out these related projects.
146
186
147
187
## Help
148
188
149
-
**Got a question?**
189
+
**Got a question?** We got answers.
150
190
151
191
File a GitHub [issue](https://github.com/cloudposse/terraform-aws-s3-bucket/issues), send us an [email][email] or join our [Slack Community][slack].
Work directly with our team of DevOps experts via email, slack, and video conferencing.
158
-
159
-
We provide [*commercial support*][commercial_support] for all of our [Open Source][github] projects. As a *Dedicated Support* customer, you have access to our team of subject matter experts at a fraction of the cost of a full-time engineer.
-**Questions.** We'll use a Shared Slack channel between your team and ours.
164
-
-**Troubleshooting.** We'll help you triage why things aren't working.
165
-
-**Code Reviews.** We'll review your Pull Requests and provide constructive feedback.
166
-
-**Bug Fixes.** We'll rapidly work to fix any bugs in our projects.
167
-
-**Build New Terraform Modules.** We'll [develop original modules][module_development] to provision infrastructure.
168
-
-**Cloud Architecture.** We'll assist with your cloud strategy and design.
169
-
-**Implementation.** We'll provide hands-on support to implement our reference architectures.
198
+
We are a [**DevOps Accelerator**][commercial_support]. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
Work directly with our team of DevOps experts via email, slack, and video conferencing.
172
203
173
-
## Terraform Module Development
174
-
175
-
Are you interested in custom Terraform module development? Submit your inquiry using [our form][module_development] today and we'll get back to you ASAP.
204
+
We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.
176
205
206
+
-**Reference Architecture.** You'll get everything you need from the ground up built using 100% infrastructure as code.
207
+
-**Release Engineering.** You'll have end-to-end CI/CD with unlimited staging environments.
208
+
-**Site Reliability Engineering.** You'll have total visibility into your apps and microservices.
209
+
-**Security Baseline.** You'll have built-in governance with accountability and audit logs for all changes.
210
+
-**GitOps.** You'll be able to operate your infrastructure via Pull Requests.
211
+
-**Training.** You'll receive hands-on training so your team can operate what we build.
212
+
-**Questions.** You'll have a direct line of communication between our teams via a Shared Slack channel.
213
+
-**Troubleshooting.** You'll get help to triage when things aren't working.
214
+
-**Code Reviews.** You'll receive constructive feedback on Pull Requests.
215
+
-**Bug Fixes.** We'll rapidly work with you to fix any bugs in our projects.
177
216
178
217
## Slack Community
179
218
180
219
Join our [Open Source Community][slack] on Slack. It's **FREE** for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.
181
220
182
221
## Newsletter
183
222
184
-
Signup for [our newsletter][newsletter] that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
223
+
Sign up for [our newsletter][newsletter] that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
224
+
225
+
## Office Hours
226
+
227
+
[Join us every Wednesday via Zoom][office_hours] for our weekly "Lunch & Learn" sessions. It's **FREE** for everyone!
| delimiter | Delimiter to be used between `namespace`, `stage`, `name` and `attributes`| string |`-`| no |
10
-
| enabled | Set to `false` to prevent the module from creating any resources | bool |`true`| no |
9
+
| delimiter | Delimiter to be used between `namespace`, `environment`, `stage`, `name` and `attributes`| string |`-`| no |
10
+
| enabled | Set to false to prevent the module from creating any resources | bool |`true`| no |
11
+
| environment | Environment, e.g. 'prod', 'staging', 'dev', 'pre-prod', 'UAT' | string | `` | no |
11
12
| force_destroy | A boolean string that indicates all objects should be deleted from the bucket so that the bucket can be destroyed without error. These objects are not recoverable | bool |`false`| no |
12
13
| kms_master_key_arn | The AWS KMS master key ARN used for the `SSE-KMS` encryption. This can only be used when you set the value of `sse_algorithm` as `aws:kms`. The default aws/s3 AWS KMS master key is used if this element is absent while the `sse_algorithm` is `aws:kms`| string | `` | no |
13
14
| lifecycle_rule_enabled | Enable or disable lifecycle rule | bool |`false`| no |
14
-
| name |Name (e.g. `app` or `cluster`)| string |-|yes|
15
-
| namespace | Namespace (e.g. `eg` or `cp`)| string | `` | no |
15
+
| name |Solution name, e.g. 'app' or 'jenkins'| string |``|no|
16
+
| namespace | Namespace, which could be your organization name or abbreviation, e.g. 'eg' or 'cp'| string | `` | no |
16
17
| noncurrent_version_expiration_days | Specifies when noncurrent object versions expire | number |`90`| no |
17
18
| noncurrent_version_transition_days | Number of days to persist in the standard storage tier before moving to the glacier tier infrequent access tier | number |`30`| no |
18
19
| policy | A valid bucket policy JSON document. Note that if the policy document is not specific enough (but still valid), Terraform may view the policy as constantly changing in a terraform plan. In this case, please make sure you use the verbose/specific version of the policy | string | `` | no |
19
20
| prefix | Prefix identifying one or more objects to which the rule applies | string | `` | no |
20
21
| region | If specified, the AWS region this bucket should reside in. Otherwise, the region used by the callee | string | `` | no |
21
22
| sse_algorithm | The server-side encryption algorithm to use. Valid values are `AES256` and `aws:kms`| string |`AES256`| no |
0 commit comments