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
|`name`| `` | Name (_e.g._`app` or `cluster`) | Yes |
86
-
|`hash_key`| `` | DynamoDB table Hash Key | Yes |
87
-
|`range_key`| `` | DynamoDB table Range Key | Yes |
88
-
|`ttl_attribute`| `` | DynamoDB table TTL attribute | No |
89
-
|`enable_streams`|`false`| Enable DynamoDB streams | No |
90
-
|`stream_view_type`| `` | When an item in the table is modified, what information is written to the stream | If `enable_streams` is true |
91
-
|`enable_encryption`|`true`| Enable DynamoDB server-side encryption | No |
92
-
|`enable_point_in_time_recovery`|`true`| Enable DynamoDB point-in-time recovery | No |
93
-
|`attributes`|`[]`| Additional attributes (_e.g._`policy` or `role`) | No |
94
-
|`tags`|`{}`| Additional tags (_e.g._`map("BusinessUnit","XYZ")`| No |
95
-
|`delimiter`|`-`| Delimiter to be used between `namespace`, `stage`, `name`, and `attributes`| No |
96
-
|`autoscale_write_target`|`50`| The target value (in %) for DynamoDB write autoscaling | No |
97
-
|`autoscale_read_target`|`50`| The target value (in %) for DynamoDB read autoscaling | No |
98
-
|`autoscale_min_read_capacity`|`5`| DynamoDB autoscaling min read capacity | No |
99
-
|`autoscale_max_read_capacity`|`20`| DynamoDB autoscaling max read capacity | No |
100
-
|`autoscale_min_write_capacity`|`5`| DynamoDB autoscaling min write capacity | No |
101
-
|`autoscale_max_write_capacity`|`20`| DynamoDB autoscaling max write capacity | No |
102
-
|`enable_autoscaler`|`true`| Flag to enable/disable DynamoDB autoscaling | No |
103
-
|`dynamodb_attributes`|`[]`| List of maps that describe extra DynamoDB attributes | No |
104
-
|`global_secondary_index_map`|`[]`| List of maps that describes additional secondary index properties | No |
105
-
106
-
107
-
## A note about DynamoDB attributes
108
-
109
-
Only define attributes on the table object that are going to be used as:
110
-
111
-
* Table hash key or range key
112
-
* LSI or GSI hash key or range key
113
-
114
-
The DynamoDB API expects attribute structure (name and type) to be passed along when creating or updating GSI/LSIs or creating the initial table. In these cases it expects the Hash / Range keys to be provided; because these get re-used in numerous places (i.e the table's range key could be a part of one or more GSIs), they are stored on the table object to prevent duplication and increase consistency. If you add attributes here that are not used in these scenarios it can cause an infinite loop in planning.
115
-
116
-
Additional details see [dynamodb_table](https://www.terraform.io/docs/providers/aws/r/dynamodb_table.html)
96
+
97
+
98
+
99
+
100
+
101
+
## Makefile Targets
102
+
```
103
+
Available targets:
104
+
105
+
help This help screen
106
+
help/all Display help for all targets
107
+
lint Lint terraform code
108
+
109
+
```
110
+
111
+
## Inputs
112
+
113
+
| Name | Description | Type | Default | Required |
114
+
|------|-------------|:----:|:-----:|:-----:|
115
+
| attributes | Additional attributes (e.g. `policy` or `role`) | list |`<list>`| no |
116
+
| autoscale_max_read_capacity | DynamoDB autoscaling max read capacity | string |`20`| no |
117
+
| autoscale_max_write_capacity | DynamoDB autoscaling max write capacity | string |`20`| no |
118
+
| autoscale_min_read_capacity | DynamoDB autoscaling min read capacity | string |`5`| no |
119
+
| autoscale_min_write_capacity | DynamoDB autoscaling min write capacity | string |`5`| no |
120
+
| autoscale_read_target | The target value (in %) for DynamoDB read autoscaling | string |`50`| no |
121
+
| autoscale_write_target | The target value (in %) for DynamoDB write autoscaling | string |`50`| no |
122
+
| delimiter | Delimiter to be used between `namespace`, `stage`, `name`, and `attributes`| string |`-`| no |
123
+
| dynamodb_attributes | Additional DynamoDB attributes in the form of a list of mapped values | list |`<list>`| no |
124
+
| enable_autoscaler | Flag to enable/disable DynamoDB autoscaling | string |`true`| no |
-[terraform-aws-dynamodb-autoscaler](https://github.com/cloudposse/terraform-aws-dynamodb-autoscaler) - Terraform module to provision DynamoDB autoscaler
157
+
-[terraform-aws-tfstate-backend](https://github.com/cloudposse/terraform-aws-tfstate-backend) - Provision an S3 bucket to store terraform.tfstate file and a DynamoDB table to lock the state file to prevent concurrent modifications and state corruption
158
+
-[terraform-aws-elasticache-redis](https://github.com/cloudposse/terraform-aws-elasticache-redis) - Terraform module to provision an ElastiCache Redis Cluster
159
+
-[terraform-aws-elasticache-memcached](https://github.com/cloudposse/terraform-aws-elasticache-memcached) - Terraform Module for ElastiCache Memcached Cluster
160
+
-[terraform-aws-elasticache-cloudwatch-sns-alarms](https://github.com/cloudposse/terraform-aws-elasticache-cloudwatch-sns-alarms) - Terraform module that configures CloudWatch SNS alerts for ElastiCache
161
+
-[terraform-aws-rds-cluster](https://github.com/cloudposse/terraform-aws-rds-cluster) - Terraform module to provision an RDS Aurora cluster for MySQL or Postgres
162
+
-[terraform-aws-rds](https://github.com/cloudposse/terraform-aws-rds) - Terraform module to provision AWS RDS instances
163
+
125
164
126
165
127
166
## Help
128
167
129
168
**Got a question?**
130
169
131
-
File a GitHub [issue](https://github.com/cloudposse/terraform-aws-dynamodb/issues), send us an [email](mailto:hello@cloudposse.com) or reach out to us on [Gitter](https://gitter.im/cloudposse/).
170
+
File a GitHub [issue](https://github.com/cloudposse/terraform-aws-dynamodb/issues), send us an [email][email] or join our [Slack Community][slack].
171
+
172
+
## Commerical Support
173
+
174
+
Work directly with our team of DevOps experts via email, slack, and video conferencing.
175
+
176
+
We provide *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 fulltime engineer.
-**Questions.** We'll use a Shared Slack channel between your team and ours.
181
+
-**Troubleshooting.** We'll help you triage why things aren't working.
182
+
-**Code Reviews.** We'll review your Pull Requests and provide constructive feedback.
183
+
-**Bug Fixes.** We'll rapidly work to fix any bugs in our projects.
184
+
-**Build New Terraform Modules.** We'll develop original modules to provision infrastructure.
185
+
-**Cloud Architecture.** We'll assist with your cloud strategy and design.
186
+
-**Implementation.** We'll provide hands on support to implement our reference architectures.
187
+
188
+
189
+
## Community Forum
190
+
191
+
Get access to our [Open Source Community Forum][slack] on Slack. It's **FREE** to join 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 *sweet* infrastructure.
133
192
134
193
## Contributing
135
194
@@ -139,22 +198,28 @@ Please use the [issue tracker](https://github.com/cloudposse/terraform-aws-dynam
139
198
140
199
### Developing
141
200
142
-
If you are interested in being a contributor and want to get involved in developing `terraform-aws-dynamodb`, we would love to hear from you! Shoot us an [email](mailto:hello@cloudposse.com).
201
+
If you are interested in being a contributor and want to get involved in developing this project or [help out](https://github.com/orgs/cloudposse/projects/3) with our other projects, we would love to hear from you! Shoot us an [email](mailto:hello@cloudposse.com).
143
202
144
203
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
145
204
146
205
1.**Fork** the repo on GitHub
147
206
2.**Clone** the project to your own machine
148
207
3.**Commit** changes to your own branch
149
208
4.**Push** your work back up to your fork
150
-
5. Submit a **Pull request** so that we can review your changes
209
+
5. Submit a **Pull Request** so that we can review your changes
210
+
211
+
**NOTE:** Be sure to merge the latest changes from "upstream" before making a pull request!
212
+
151
213
152
-
**NOTE:** Be sure to merge the latest from "upstream" before making a pull request!
0 commit comments