> For the complete documentation index, see [llms.txt](https://mamawhocode.gitbook.io/aws/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mamawhocode.gitbook.io/aws/services/web-and-mobile/amplify.md).

# Amplify

Build, deploy, host, and manage scalable web and mobile apps

[Cypress test](https://docs.aws.amazon.com/amplify/latest/userguide/running-tests.html) |

## Overview

* Amplify is a *<mark style="color:red;">set of products and tools</mark>* that enable mobile and front-end web developers to build and deploy secure, scalable full-stack applications,
* Amplify Framework is a comprehensive set of SDKs, libraries, tools, and documentation for client app development.

## Features

### Amplify Studio

* A visual development environment -> build frontend UI
* Model data, create UI components, bind UI to data, set up authentication, file storage, and functions using a visual interface.
* You can import Figma prototypes

### Amplify Hosting

* Fully managed CI/CD and hosting service.
* Under the hood, it deploys your applications to Amazon CloudFront’s content delivery network

### Amplify Libraries

* Open-source JavaScript libraries in the Amplify Framework

### Amplify CLI

* A CLI toolchain that you can use to configure and maintain your app backend straight from your local desktop
* Easy integration with Amplify's CI/CD workflow

## Trivia

* You can run end-to-end (E2E) tests in the test phase of your Amplify app to catch regressions before pushing code to production. The test phase can be configured in the build specification YAML. Currently, you can run only the Cypress testing framework during a build.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://mamawhocode.gitbook.io/aws/services/web-and-mobile/amplify.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.