42 | > Watch demo of using Atmos with Terraform
43 | > 
44 | > Example of running atmos to manage infrastructure from our Quick Start tutorial.
45 | >
46 |
47 |
48 |
49 |
50 |
51 | ## Usage
52 |
53 | For a complete example, see [examples/complete](examples/complete).
54 |
55 | For automated tests of the complete example using [bats](https://github.com/bats-core/bats-core) and [Terratest](https://github.com/gruntwork-io/terratest)
56 | (which tests and deploys the example on AWS), see [test](test).
57 |
58 | ```hcl
59 | data "aws_ssm_parameter" "github_pat" {
60 | name = var.github_personal_access_token_secret_path
61 | with_decryption = true
62 | }
63 |
64 | module "amplify_app" {
65 | source = "cloudposse/amplify-app/aws"
66 | # Cloud Posse recommends pinning every module to a specific version
67 | # version = "x.x.x"
68 |
69 | access_token = data.aws_ssm_parameter.github_pat.value
70 |
71 | description = "Test Amplify App"
72 | repository = "https://github.com/cloudposse/amplify-test2"
73 | platform = "WEB"
74 |
75 | enable_auto_branch_creation = false
76 | enable_branch_auto_build = true
77 | enable_branch_auto_deletion = true
78 | enable_basic_auth = false
79 |
80 | iam_service_role_enabled = true
81 |
82 | iam_service_role_actions = [
83 | "logs:CreateLogStream",
84 | "logs:CreateLogGroup",
85 | "logs:DescribeLogGroups",
86 | "logs:PutLogEvents"
87 | ]
88 |
89 | auto_branch_creation_patterns = [
90 | "*",
91 | "*/**"
92 | ]
93 |
94 | auto_branch_creation_config = {
95 | # Enable auto build for the created branches
96 | enable_auto_build = true
97 | }
98 |
99 | # The build spec for React
100 | build_spec = <<-EOT
101 | version: 0.1
102 | frontend:
103 | phases:
104 | preBuild:
105 | commands:
106 | - yarn install
107 | build:
108 | commands:
109 | - yarn run build
110 | artifacts:
111 | baseDirectory: build
112 | files:
113 | - '**/*'
114 | cache:
115 | paths:
116 | - node_modules/**/*
117 | EOT
118 |
119 | custom_rules = [
120 | {
121 | source = "/<*>"
122 | status = "404"
123 | target = "/index.html"
124 | }
125 | ]
126 |
127 | environment_variables = {
128 | ENV = "test"
129 | }
130 |
131 | environments = {
132 | main = {
133 | branch_name = "main"
134 | enable_auto_build = true
135 | backend_enabled = false
136 | enable_performance_mode = true
137 | enable_pull_request_preview = false
138 | framework = "React"
139 | stage = "PRODUCTION"
140 | }
141 | dev = {
142 | branch_name = "dev"
143 | enable_auto_build = true
144 | backend_enabled = false
145 | enable_performance_mode = false
146 | enable_pull_request_preview = true
147 | framework = "React"
148 | stage = "DEVELOPMENT"
149 | }
150 | }
151 |
152 | domains = {
153 | "test.net" = {
154 | enable_auto_sub_domain = true
155 | wait_for_verification = false
156 | sub_domain = [
157 | {
158 | branch_name = "main"
159 | prefix = ""
160 | },
161 | {
162 | branch_name = "dev"
163 | prefix = "dev"
164 | }
165 | ]
166 | }
167 | }
168 |
169 | context = module.label.context
170 | }
171 | ```
172 |
173 | > [!IMPORTANT]
174 | > In Cloud Posse's examples, we avoid pinning modules to specific versions to prevent discrepancies between the documentation
175 | > and the latest released versions. However, for your own projects, we strongly advise pinning each module to the exact version
176 | > you're using. This practice ensures the stability of your infrastructure. Additionally, we recommend implementing a systematic
177 | > approach for updating versions to avoid unexpected changes.
178 |
179 |
180 |
181 |
182 |
183 | ## Examples
184 |
185 | Here is an example of using this module:
186 | - [`examples/complete`](https://github.com/cloudposse/terraform-aws-amplify-app/) - complete example of using this module
187 |
188 |
189 |
190 |
191 |
192 | ## Requirements
193 |
194 | | Name | Version |
195 | |------|---------|
196 | | [terraform](#requirement\_terraform) | >= 1.3.0 |
197 | | [aws](#requirement\_aws) | >= 4.0 |
198 |
199 | ## Providers
200 |
201 | | Name | Version |
202 | |------|---------|
203 | | [aws](#provider\_aws) | >= 4.0 |
204 |
205 | ## Modules
206 |
207 | | Name | Source | Version |
208 | |------|--------|---------|
209 | | [role](#module\_role) | cloudposse/iam-role/aws | 0.18.0 |
210 | | [this](#module\_this) | cloudposse/label/null | 0.25.0 |
211 |
212 | ## Resources
213 |
214 | | Name | Type |
215 | |------|------|
216 | | [aws_amplify_app.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/amplify_app) | resource |
217 | | [aws_amplify_backend_environment.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/amplify_backend_environment) | resource |
218 | | [aws_amplify_branch.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/amplify_branch) | resource |
219 | | [aws_amplify_domain_association.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/amplify_domain_association) | resource |
220 | | [aws_amplify_webhook.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/amplify_webhook) | resource |
221 | | [aws_iam_policy_document.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document) | data source |
222 |
223 | ## Inputs
224 |
225 | | Name | Description | Type | Default | Required |
226 | |------|-------------|------|---------|:--------:|
227 | | [access\_token](#input\_access\_token) | The personal access token for a third-party source control system for the Amplify app.
The personal access token is used to create a webhook and a read-only deploy key. The token is not stored.
Make sure that the account where the token is created has access to the repository. | `string` | `null` | no |
228 | | [additional\_tag\_map](#input\_additional\_tag\_map) | Additional key-value pairs to add to each map in `tags_as_list_of_maps`. Not added to `tags` or `id`.
This is for some rare cases where resources want additional configuration of tags
and therefore take a list of maps with tag key, value, and additional configuration. | `map(string)` | `{}` | no |
229 | | [attributes](#input\_attributes) | ID element. Additional attributes (e.g. `workers` or `cluster`) to add to `id`,
in the order they appear in the list. New attributes are appended to the
end of the list. The elements of the list are joined by the `delimiter`
and treated as a single ID element. | `list(string)` | `[]` | no |
230 | | [auto\_branch\_creation\_config](#input\_auto\_branch\_creation\_config) | The automated branch creation configuration for the Amplify app | object({
basic_auth_credentials = optional(string)
build_spec = optional(string)
enable_auto_build = optional(bool)
enable_basic_auth = optional(bool)
enable_performance_mode = optional(bool)
enable_pull_request_preview = optional(bool)
environment_variables = optional(map(string))
framework = optional(string)
pull_request_environment_name = optional(string)
stage = optional(string)
}) | `null` | no |
231 | | [auto\_branch\_creation\_patterns](#input\_auto\_branch\_creation\_patterns) | The automated branch creation glob patterns for the Amplify app | `list(string)` | `[]` | no |
232 | | [basic\_auth\_credentials](#input\_basic\_auth\_credentials) | The credentials for basic authorization for the Amplify app | `string` | `null` | no |
233 | | [build\_spec](#input\_build\_spec) | The [build specification](https://docs.aws.amazon.com/amplify/latest/userguide/build-settings.html) (build spec) for the Amplify app.
If not provided then it will use the `amplify.yml` at the root of your project / branch. | `string` | `null` | no |
234 | | [context](#input\_context) | Single object for setting entire context at once.
See description of individual variables for details.
Leave string and numeric variables as `null` to use default value.
Individual variable settings (non-null) override settings in context object,
except for attributes, tags, and additional\_tag\_map, which are merged. | `any` | {
"additional_tag_map": {},
"attributes": [],
"delimiter": null,
"descriptor_formats": {},
"enabled": true,
"environment": null,
"id_length_limit": null,
"label_key_case": null,
"label_order": [],
"label_value_case": null,
"labels_as_tags": [
"unset"
],
"name": null,
"namespace": null,
"regex_replace_chars": null,
"stage": null,
"tags": {},
"tenant": null
} | no |
235 | | [custom\_headers](#input\_custom\_headers) | The custom headers for the Amplify app, allows specifying headers for every HTTP response. Must adhere to AWS's format: https://docs.aws.amazon.com/amplify/latest/userguide/custom-headers.html | `string` | `null` | no |
236 | | [custom\_rules](#input\_custom\_rules) | The custom rules to apply to the Amplify App | list(object({
condition = optional(string)
source = string
status = optional(string)
target = string
})) | `[]` | no |
237 | | [delimiter](#input\_delimiter) | Delimiter to be used between ID elements.
Defaults to `-` (hyphen). Set to `""` to use no delimiter at all. | `string` | `null` | no |
238 | | [description](#input\_description) | The description for the Amplify app | `string` | `null` | no |
239 | | [descriptor\_formats](#input\_descriptor\_formats) | Describe additional descriptors to be output in the `descriptors` output map.
Map of maps. Keys are names of descriptors. Values are maps of the form
`{
format = string
labels = list(string)
}`
(Type is `any` so the map values can later be enhanced to provide additional options.)
`format` is a Terraform format string to be passed to the `format()` function.
`labels` is a list of labels, in order, to pass to `format()` function.
Label values will be normalized before being passed to `format()` so they will be
identical to how they appear in `id`.
Default is `{}` (`descriptors` output will be empty). | `any` | `{}` | no |
240 | | [domain\_config](#input\_domain\_config) | DEPRECATED: Use the `domains` variable instead.
Amplify custom domain configuration. | object({
domain_name = string
enable_auto_sub_domain = optional(bool, false)
wait_for_verification = optional(bool, false)
sub_domain = list(object({
branch_name = string
prefix = string
}))
}) | `null` | no |
241 | | [domains](#input\_domains) | Amplify custom domain configurations | map(object({
enable_auto_sub_domain = optional(bool, false)
wait_for_verification = optional(bool, false)
sub_domain = list(object({
branch_name = string
prefix = string
}))
})) | `{}` | no |
242 | | [enable\_auto\_branch\_creation](#input\_enable\_auto\_branch\_creation) | Enables automated branch creation for the Amplify app | `bool` | `false` | no |
243 | | [enable\_basic\_auth](#input\_enable\_basic\_auth) | Enables basic authorization for the Amplify app.
This will apply to all branches that are part of this app. | `bool` | `false` | no |
244 | | [enable\_branch\_auto\_build](#input\_enable\_branch\_auto\_build) | Enables auto-building of branches for the Amplify App | `bool` | `true` | no |
245 | | [enable\_branch\_auto\_deletion](#input\_enable\_branch\_auto\_deletion) | Automatically disconnects a branch in the Amplify Console when you delete a branch from your Git repository | `bool` | `false` | no |
246 | | [enabled](#input\_enabled) | Set to false to prevent the module from creating any resources | `bool` | `null` | no |
247 | | [environment](#input\_environment) | ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT' | `string` | `null` | no |
248 | | [environment\_variables](#input\_environment\_variables) | The environment variables for the Amplify app | `map(string)` | `{}` | no |
249 | | [environments](#input\_environments) | The configuration of the environments for the Amplify App | map(object({
branch_name = optional(string)
basic_auth_credentials = optional(string)
backend_enabled = optional(bool, false)
environment_name = optional(string)
deployment_artifacts = optional(string)
stack_name = optional(string)
display_name = optional(string)
description = optional(string)
enable_auto_build = optional(bool)
enable_basic_auth = optional(bool)
enable_notification = optional(bool)
enable_performance_mode = optional(bool)
enable_pull_request_preview = optional(bool)
environment_variables = optional(map(string))
framework = optional(string)
pull_request_environment_name = optional(string)
stage = optional(string)
ttl = optional(number)
webhook_enabled = optional(bool, false)
})) | `{}` | no |
250 | | [iam\_service\_role\_actions](#input\_iam\_service\_role\_actions) | List of IAM policy actions for the AWS Identity and Access Management (IAM) service role for the Amplify app.
If not provided, the default set of actions will be used for the role if the variable `iam_service_role_enabled` is set to `true`. | `list(string)` | `[]` | no |
251 | | [iam\_service\_role\_arn](#input\_iam\_service\_role\_arn) | The AWS Identity and Access Management (IAM) service role for the Amplify app.
If not provided, a new role will be created if the variable `iam_service_role_enabled` is set to `true`. | `list(string)` | `[]` | no |
252 | | [iam\_service\_role\_enabled](#input\_iam\_service\_role\_enabled) | Flag to create the IAM service role for the Amplify app | `bool` | `false` | no |
253 | | [id\_length\_limit](#input\_id\_length\_limit) | Limit `id` to this many characters (minimum 6).
Set to `0` for unlimited length.
Set to `null` for keep the existing setting, which defaults to `0`.
Does not affect `id_full`. | `number` | `null` | no |
254 | | [label\_key\_case](#input\_label\_key\_case) | Controls the letter case of the `tags` keys (label names) for tags generated by this module.
Does not affect keys of tags passed in via the `tags` input.
Possible values: `lower`, `title`, `upper`.
Default value: `title`. | `string` | `null` | no |
255 | | [label\_order](#input\_label\_order) | The order in which the labels (ID elements) appear in the `id`.
Defaults to ["namespace", "environment", "stage", "name", "attributes"].
You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present. | `list(string)` | `null` | no |
256 | | [label\_value\_case](#input\_label\_value\_case) | Controls the letter case of ID elements (labels) as included in `id`,
set as tag values, and output by this module individually.
Does not affect values of tags passed in via the `tags` input.
Possible values: `lower`, `title`, `upper` and `none` (no transformation).
Set this to `title` and set `delimiter` to `""` to yield Pascal Case IDs.
Default value: `lower`. | `string` | `null` | no |
257 | | [labels\_as\_tags](#input\_labels\_as\_tags) | Set of labels (ID elements) to include as tags in the `tags` output.
Default is to include all labels.
Tags with empty values will not be included in the `tags` output.
Set to `[]` to suppress all generated tags.
**Notes:**
The value of the `name` tag, if included, will be the `id`, not the `name`.
Unlike other `null-label` inputs, the initial setting of `labels_as_tags` cannot be
changed in later chained modules. Attempts to change it will be silently ignored. | `set(string)` | [
"default"
]
| no |
258 | | [name](#input\_name) | ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.
This is the only ID element not also included as a `tag`.
The "name" tag is set to the full `id` string. There is no tag with the value of the `name` input. | `string` | `null` | no |
259 | | [namespace](#input\_namespace) | ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique | `string` | `null` | no |
260 | | [oauth\_token](#input\_oauth\_token) | The OAuth token for a third-party source control system for the Amplify app.
The OAuth token is used to create a webhook and a read-only deploy key.
The OAuth token is not stored. | `string` | `null` | no |
261 | | [platform](#input\_platform) | The platform or framework for the Amplify app | `string` | `"WEB"` | no |
262 | | [regex\_replace\_chars](#input\_regex\_replace\_chars) | Terraform regular expression (regex) string.
Characters matching the regex will be removed from the ID elements.
If not set, `"/[^a-zA-Z0-9-]/"` is used to remove all characters other than hyphens, letters and digits. | `string` | `null` | no |
263 | | [repository](#input\_repository) | The repository for the Amplify app | `string` | `null` | no |
264 | | [stage](#input\_stage) | ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release' | `string` | `null` | no |
265 | | [tags](#input\_tags) | Additional tags (e.g. `{'BusinessUnit': 'XYZ'}`).
Neither the tag keys nor the tag values will be modified by this module. | `map(string)` | `{}` | no |
266 | | [tenant](#input\_tenant) | ID element \_(Rarely used, not included by default)\_. A customer identifier, indicating who this instance of a resource is for | `string` | `null` | no |
267 |
268 | ## Outputs
269 |
270 | | Name | Description |
271 | |------|-------------|
272 | | [arn](#output\_arn) | Amplify App ARN |
273 | | [backend\_environments](#output\_backend\_environments) | Created backend environments |
274 | | [branch\_names](#output\_branch\_names) | The names of the created Amplify branches |
275 | | [default\_domain](#output\_default\_domain) | Amplify App domain (non-custom) |
276 | | [domain\_associations](#output\_domain\_associations) | Created domain associations |
277 | | [id](#output\_id) | Amplify App Id |
278 | | [name](#output\_name) | Amplify App name |
279 | | [webhooks](#output\_webhooks) | Created webhooks |
280 |
281 |
282 |
283 |
284 |
285 |
286 |
287 |
288 | ## Related Projects
289 |
290 | Check out these related projects.
291 |
292 | - [terraform-null-label](https://github.com/cloudposse/terraform-null-label) - Terraform module designed to generate consistent names and tags for resources. Use terraform-null-label to implement a strict naming convention.
293 |
294 |
295 | ## References
296 |
297 | For additional context, refer to some of these links.
298 |
299 | - [AWS Amplify Documentation](https://docs.aws.amazon.com/amplify/index.html) - Use AWS Amplify to develop and deploy cloud-powered mobile and web apps
300 | - [Setting up Amplify access to GitHub repositories](https://docs.aws.amazon.com/amplify/latest/userguide/setting-up-GitHub-access.html) - Amplify uses the GitHub Apps feature to authorize Amplify read-only access to GitHub repositories. With the Amplify GitHub App, permissions are more fine-tuned, enabling you to grant Amplify access to only the repositories that you specify
301 | - [Getting started with existing code](https://docs.aws.amazon.com/amplify/latest/userguide/getting-started.html) - Documentation on how to continuously build, deploy, and host a modern web app using existing code
302 | - [Deploy a Web App on AWS Amplify](https://aws.amazon.com/getting-started/guides/deploy-webapp-amplify/) - A guide on deploying a web application with AWS Amplify
303 | - [Getting started with fullstack continuous deployments](https://docs.aws.amazon.com/amplify/latest/userguide/deploy-backend.html) - Tutorial on how to set up a fullstack CI/CD workflow with Amplify
304 | - [Cloud Posse Documentation](https://docs.cloudposse.com) - The Cloud Posse Developer Hub (documentation)
305 | - [Terraform Standard Module Structure](https://www.terraform.io/docs/language/modules/develop/structure.html) - HashiCorp's standard module structure is a file and directory layout we recommend for reusable modules distributed in separate repositories.
306 | - [Terraform Module Requirements](https://www.terraform.io/docs/registry/modules/publish.html#requirements) - HashiCorp's guidance on all the requirements for publishing a module. Meeting the requirements for publishing a module is extremely easy.
307 | - [Terraform Version Pinning](https://www.terraform.io/docs/language/settings/index.html#specifying-a-required-terraform-version) - The required_version setting can be used to constrain which versions of the Terraform CLI can be used with your configuration
308 | - [Masterpoint.io](https://github.com/masterpointio/terraform-aws-amplify-app/) - This repo was inspired by masterpoint's original amplify-app terraform module
309 |
310 |
311 |
312 | > [!TIP]
313 | > #### Use Terraform Reference Architectures for AWS
314 | >
315 | > Use Cloud Posse's ready-to-go [terraform architecture blueprints](https://cloudposse.com/reference-architecture/) for AWS to get up and running quickly.
316 | >
317 | > ✅ We build it together with your team.
318 | > ✅ Your team owns everything.
319 | > ✅ 100% Open Source and backed by fanatical support.
320 | >
321 | >
322 | > 📚 Learn More
323 | >
324 | >
325 | >
326 | > Cloud Posse is the leading [**DevOps Accelerator**](https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-amplify-app&utm_content=commercial_support) for funded startups and enterprises.
327 | >
328 | > *Your team can operate like a pro today.*
329 | >
330 | > Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.
331 | > #### Day-0: Your Foundation for Success
332 | > - **Reference Architecture.** You'll get everything you need from the ground up built using 100% infrastructure as code.
333 | > - **Deployment Strategy.** Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.
334 | > - **Site Reliability Engineering.** Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.
335 | > - **Security Baseline.** Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.
336 | > - **GitOps.** Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.
337 | >
338 | >
339 | >
340 | > #### Day-2: Your Operational Mastery
341 | > - **Training.** Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.
342 | > - **Support.** Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.
343 | > - **Troubleshooting.** Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.
344 | > - **Code Reviews.** Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.
345 | > - **Bug Fixes.** Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.
346 | > - **Migration Assistance.** Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.
347 | > - **Customer Workshops.** Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.
348 | >
349 | >
350 | >
351 |
352 |
353 | ## ✨ Contributing
354 |
355 | This project is under active development, and we encourage contributions from our community.
356 |
357 |
358 |
359 | Many thanks to our outstanding contributors:
360 |
361 |
362 |
363 |
364 |
365 | For 🐛 bug reports & feature requests, please use the [issue tracker](https://github.com/cloudposse/terraform-aws-amplify-app/issues).
366 |
367 | In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
368 | 1. Review our [Code of Conduct](https://github.com/cloudposse/terraform-aws-amplify-app/?tab=coc-ov-file#code-of-conduct) and [Contributor Guidelines](https://github.com/cloudposse/.github/blob/main/CONTRIBUTING.md).
369 | 2. **Fork** the repo on GitHub
370 | 3. **Clone** the project to your own machine
371 | 4. **Commit** changes to your own branch
372 | 5. **Push** your work back up to your fork
373 | 6. Submit a **Pull Request** so that we can review your changes
374 |
375 | **NOTE:** Be sure to merge the latest changes from "upstream" before making a pull request!
376 |
377 |
378 | ## Running Terraform Tests
379 |
380 | We use [Atmos](https://atmos.tools) to streamline how Terraform tests are run. It centralizes configuration and wraps common test workflows with easy-to-use commands.
381 |
382 | All tests are located in the [`test/`](test) folder.
383 |
384 | Under the hood, tests are powered by Terratest together with our internal [Test Helpers](https://github.com/cloudposse/test-helpers) library, providing robust infrastructure validation.
385 |
386 | Setup dependencies:
387 | - Install Atmos ([installation guide](https://atmos.tools/install/))
388 | - Install Go [1.24+ or newer](https://go.dev/doc/install)
389 | - Install Terraform or OpenTofu
390 |
391 | To run tests:
392 |
393 | - Run all tests:
394 | ```sh
395 | atmos test run
396 | ```
397 | - Clean up test artifacts:
398 | ```sh
399 | atmos test clean
400 | ```
401 | - Explore additional test options:
402 | ```sh
403 | atmos test --help
404 | ```
405 | The configuration for test commands is centrally managed. To review what's being imported, see the [`atmos.yaml`](https://raw.githubusercontent.com/cloudposse/.github/refs/heads/main/.github/atmos/terraform-module.yaml) file.
406 |
407 | Learn more about our [automated testing in our documentation](https://docs.cloudposse.com/community/contribute/automated-testing/) or implementing [custom commands](https://atmos.tools/core-concepts/custom-commands/) with atmos.
408 |
409 | ### 🌎 Slack Community
410 |
411 | Join our [Open Source Community](https://cpco.io/slack?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-amplify-app&utm_content=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.
412 |
413 | ### 📰 Newsletter
414 |
415 | Sign up for [our newsletter](https://cpco.io/newsletter?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-amplify-app&utm_content=newsletter) and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know.
416 | Dropped straight into your Inbox every week — and usually a 5-minute read.
417 |
418 | ### 📆 Office Hours
419 |
420 | [Join us every Wednesday via Zoom](https://cloudposse.com/office-hours?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-amplify-app&utm_content=office_hours) for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a _live Q&A_ that you can’t find anywhere else.
421 | It's **FREE** for everyone!
422 | ## License
423 |
424 |
425 |
426 |
427 | Preamble to the Apache License, Version 2.0
428 |
429 |
430 |
431 | Complete license is available in the [`LICENSE`](LICENSE) file.
432 |
433 | ```text
434 | Licensed to the Apache Software Foundation (ASF) under one
435 | or more contributor license agreements. See the NOTICE file
436 | distributed with this work for additional information
437 | regarding copyright ownership. The ASF licenses this file
438 | to you under the Apache License, Version 2.0 (the
439 | "License"); you may not use this file except in compliance
440 | with the License. You may obtain a copy of the License at
441 |
442 | https://www.apache.org/licenses/LICENSE-2.0
443 |
444 | Unless required by applicable law or agreed to in writing,
445 | software distributed under the License is distributed on an
446 | "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
447 | KIND, either express or implied. See the License for the
448 | specific language governing permissions and limitations
449 | under the License.
450 | ```
451 |
452 |
453 | ## Trademarks
454 |
455 | All other trademarks referenced herein are the property of their respective owners.
456 |
457 |
458 | ## Copyrights
459 |
460 | Copyright © 2023-2025 [Cloud Posse, LLC](https://cloudposse.com)
461 |
462 |
463 |
464 |
465 |
466 |
467 |
--------------------------------------------------------------------------------