diff --git a/public/images/gen2/getting-started/authenticator-localhost-(720p).png b/public/images/gen2/getting-started/authenticator-localhost-(720p).png
new file mode 100644
index 00000000000..ee07e8a581c
Binary files /dev/null and b/public/images/gen2/getting-started/authenticator-localhost-(720p).png differ
diff --git a/src/pages/[platform]/start/quickstart/index.mdx b/src/pages/[platform]/start/quickstart/index.mdx
index ae339cb1935..e75e2e0584a 100644
--- a/src/pages/[platform]/start/quickstart/index.mdx
+++ b/src/pages/[platform]/start/quickstart/index.mdx
@@ -21,11 +21,11 @@ export const meta = {
};
-export const getStaticPaths = async () => {
+export function getStaticPaths() {
return getCustomStaticPath(meta.platforms);
-};
+}
-export function getStaticProps(context) {
+export function getStaticProps() {
const childPageNodes = getChildPageNodes(meta.route);
return {
props: {
@@ -39,56 +39,56 @@ export function getStaticProps(context) {
👋 Welcome to AWS Amplify! In this quickstart guide, you will:
-1. Deploy a Vanilla JavaScript app with Vite
+1. Deploy a Vanilla JavaScript app with [Vite](https://vitejs.dev/)
2. Build and connect to a database with real-time data updates
3. Configure authentication and authorization rules
-
## Create project
-Create a new Vanilla JavaScript app with vite using the following commands, create the directory (`amplify-js-app`) and files for the app.
+Create a new Vanilla JavaScript app with Vite using the following commands, create the directory (`amplify-js-app`) and files for the app.
-```bash
+```bash title="Terminal" showLineNumbers={false}
npm create vite@latest
✔ Project name: amplify-js-app
✔ Select a framework: › Vanilla
✔ Select a variant: › TypeScript
```
-Initialize npm and install dependencies and dev dependencies.
-```bash
+Use npm to install dependencies and start Vite's local development server.
+
+```bash title="Terminal" showLineNumbers={false}
cd amplify-js-app
npm install
npm run dev
```
-This runs a development server and allows you to see the output generated by the build. You can see the running app by navigating to [http://localhost:5173](http://localhost:5173).
+The development server allows you to see the output generated by the build. You can see the running app by navigating to [`http://localhost:5173`](http://localhost:5173).
Add the following to the `index.html` file:
```html title="index.html"
-
-
+
```
@@ -165,11 +165,11 @@ a {
```
{/* cSpell:enable */}
-In `main.js` remove the boilerplate code and leave it empty. Then refresh the browser to see the changes.
+In `main.ts` remove the boilerplate code and leave it empty. Then refresh the browser to see the changes.
## Create Backend
-The easiest way to get started with AWS Amplify is through npm with `create-amplify` command. You can run it from your base project directory.
+The easiest way to get started with AWS Amplify is through npm with [`create-amplify`](https://www.npmjs.com/package/create-amplify) package. It is recommended to be run from the root of your project's directory.
```bash title="Terminal" showLineNumbers={false}
npm create amplify@latest
@@ -185,6 +185,7 @@ Running this command will scaffold Amplify backend files in your current project
│ ├── data/
│ │ └── resource.ts
│ ├── backend.ts
+│ ├── tsconfig.json
│ └── package.json
├── node_modules/
├── index.html
@@ -197,9 +198,9 @@ Running this command will scaffold Amplify backend files in your current project
### Set up local AWS credentials
-To make backend updates, we are going to require AWS credentials to deploy backend updates from our local machine.
+To make backend updates, you will need AWS credentials to deploy backend updates from your local machine.
-**Skip ahead to step 8**, if you already have an AWS profile with credentials on your local machine, and your AWS profile has the `AmplifyBackendDeployFullAccess` permission policy.
+**Skip ahead** if you already have an AWS profile with credentials on your local machine, and your AWS profile has the `AmplifyBackendDeployFullAccess` permission policy.
Otherwise, **[set up local AWS credentials](/[platform]/start/account-setup/)** that grant Amplify permissions to deploy backend updates from your local machine.
@@ -215,67 +216,66 @@ Once the sandbox environment is deployed, it will create a GraphQL API, database
## Connect frontend to backend
-The initial scaffolding already has a pre-configured data backend defined in the `amplify/data/resource.ts` file. The default example will create a Todo model with `content` field. Update your main.js file to create new to-do items.
+The initial scaffolding already has a pre-configured data backend defined in the `amplify/data/resource.ts` file. The default example will create a Todo model with `content` field. Update your `main.ts` file to create new to-do items.
-```typescript title="src/main.ts"
-import { generateClient } from "aws-amplify/data";
-import type { Schema } from "../amplify/data/resource";
-import './style.css';
+```ts title="src/main.ts"
+import type { Schema } from '../amplify/data/resource';
+import { generateClient } from 'aws-amplify/data';
import { Amplify } from 'aws-amplify';
import outputs from '../amplify_outputs.json';
+import './style.css';
Amplify.configure(outputs);
-
const client = generateClient();
-document.addEventListener("DOMContentLoaded", function () {
- const todos: Array = [];
- const todoList = document.getElementById("todoList") as HTMLUListElement;
- const addTodoButton = document.getElementById("addTodo") as HTMLButtonElement;
+document.addEventListener('DOMContentLoaded', function () {
+ const todos: Array = [];
+ const todoList = document.getElementById('todoList') as HTMLUListElement;
+ const addTodoButton = document.getElementById('addTodo') as HTMLButtonElement;
+
+ addTodoButton.addEventListener('click', createTodo);
- addTodoButton.addEventListener("click", createTodo);
+ function updateUI() {
+ todoList.innerHTML = '';
+ todos.forEach((todo) => {
+ const li = document.createElement('li');
+ li.textContent = todo.content ?? '';
+ todoList.appendChild(li);
+ });
+ }
- function updateUI() {
- todoList.innerHTML = '';
- todos.forEach(todo => {
- const li = document.createElement('li');
- li.textContent = todo.content ?? '';
- todoList.appendChild(li);
+ function createTodo() {
+ console.log('createTodo');
+ const content = window.prompt('Todo content');
+ if (content) {
+ client.models.Todo.create({ content })
+ .then((response) => {
+ if (response.data && !response.errors) {
+ todos.push(response.data);
+ updateUI();
+ } else {
+ console.error('Error creating todo:', response.errors);
+ alert('Failed to create todo.');
+ }
+ })
+ .catch((error) => {
+ console.error('Network or other error:', error);
+ alert('Failed to create todo due to a network or other error.');
});
}
-
- function createTodo() {
- console.log('createTodo');
- const content = window.prompt("Todo content");
- if (content) {
- client.models.Todo.create({ content }).then(response => {
- if (response.data && !response.errors) {
- todos.push(response.data);
- updateUI();
- } else {
- console.error('Error creating todo:', response.errors);
- alert('Failed to create todo.');
- }
- }).catch(error => {
- console.error('Network or other error:', error);
- alert('Failed to create todo due to a network or other error.');
- });
- }
}
-
- client.models.Todo.observeQuery().subscribe({
- next: (data) => {
- todos.splice(0, todos.length, ...data.items);
- updateUI();
- }
- });
+ client.models.Todo.observeQuery().subscribe({
+ next: (data) => {
+ todos.splice(0, todos.length, ...data.items);
+ updateUI();
+ }
+ });
});
```
-
👋 Welcome to AWS Amplify! In this quickstart guide, you will:
@@ -284,247 +284,226 @@ document.addEventListener("DOMContentLoaded", function () {
2. Build and connect to a database with real-time data updates
3. Configure authentication and authorization rules
-## Deploy a fullstack app to AWS
+## Create your project
-We've created a starter "To-do" application to help get started faster. First, you will create a repository in your GitHub account using our starter React template.
+To get started, create a Vite app with React using the [`create-vite`](https://www.npmjs.com/package/create-vite) package:
-### 1. Create the repository
+```bash title="Terminal" showLineNumbers={false}
+npm create vite@latest -- --template react-ts
+```
-Use our starter template to create a repository in your GitHub account. This template scaffolds `create-vite-app` with Amplify backend capabilities.
+Then follow the prompts to generate the boilerplate for your Vite React application.
-
-
-Create repository from template
-
+Next, scaffold your Amplify backend using the [`create-amplify`](https://www.npmjs.com/package/create-amplify) package:
-Use the form in GitHub to finalize your repo's creation.
+```bash title="Terminal" showLineNumbers={false}
+npm create amplify@latest
+```
-### 2. Deploy the starter app
+Follow the prompts to scaffold your Amplify backend, which copies template files for auth and data resources, and installs required dependencies to your project. The creation flow is intended to be run from the same directory as your frontend project, however it can be executed from any directory.
-Now that the repository has been created, deploy it with Amplify.
+This will add the following files to your project's directory:
-
-
-Deploy to AWS
-
+```text
+├── amplify/
+│ ├── auth/
+│ │ └── resource.ts
+│ ├── data/
+│ │ └── resource.ts
+│ ├── backend.ts
+│ ├── tsconfig.json
+│ └── package.json
+```
-Select **GitHub**. After you give Amplify access to your GitHub account via the popup window, pick the repository and `main` branch to deploy. Make no other changes and click through the flow to **Save and deploy**.
+If you prefer setting up your project from scratch, refer to the [documentation for manual installation](https://docs.amplify.aws/react/start/manual-installation/).
-
+
-### 3. View deployed app
+**Prefer a template?** [Start a new project from the Vite React template](https://github.com/new?template_name=amplify-vite-react-template&template_owner=aws-samples)
-
+
-Let's take a tour of the project structure in this starter repository by opening it on GitHub. The starter application has pre-written code for a to-do list app. It gives you a real-time database with a feed of all to-do list items and the ability to add new items.
+## Set up local AWS credentials
-```text
-├── amplify/ # Folder containing your Amplify backend configuration
-│ ├── auth/ # Definition for your auth backend
-│ │ └── resource.tsx
-│ ├── data/ # Definition for your data backend
-│ │ └── resource.ts
-| ├── backend.ts
-│ └── tsconfig.json
-├── src/ # React UI code
-│ ├── App.tsx # UI code to sync todos in real-time
-│ ├── index.css # Styling for your app
-│ └── main.tsx # Entrypoint of the Amplify client library
-├── package.json
-└── tsconfig.json
-```
-
+To make backend updates, we are going to require AWS credentials to deploy backend updates from our local machine.
- When the build completes, visit the newly deployed branch by selecting "Visit deployed URL". Since the build deployed an API, database, and authentication backend, you will be able to create new to-do items.
+**Skip ahead**, if you already have an AWS profile with credentials on your local machine, and your AWS profile has the `AmplifyBackendDeployFullAccess` permission policy.
-
+Otherwise, **[set up local AWS credentials](/[platform]/start/account-setup/)** that grant Amplify permissions to deploy backend updates from your local machine.
-In the Amplify console, click into the deployment branch (in this case **main**) > select **Data** in the left-hand menu > **Data manager** to see the data entered in your database.
+## Deploy cloud sandbox
-
+To update your backend without affecting the production branch, use Amplify's cloud sandbox. This feature provides a separate backend environment for each developer on a team, ideal for local development and testing.
-## Make frontend updates
+To start your cloud sandbox, run the following command in a **new Terminal window**:
-Let's learn how to enhance the app functionality by creating a delete flow for to-do list items.
+```bash title="Terminal" showLineNumbers={false}
+npx ampx sandbox
+```
-### 4. Set up local environment
+Once the cloud sandbox has been fully deployed (~5 min), you'll see the `amplify_outputs.json` file updated with connection information to a new isolated authentication and data backend.
-Now let's set up our local development environment to add features to the frontend. Click on your deployed branch and you will land on the **Deployments** page which shows you your build history and a list of deployed backend resources.
+
-
+The `npx ampx sandbox` command should run concurrently to your `npm run dev`. You can think of the cloud sandbox as the "localhost-equivalent for your app backend".
-At the bottom of the page you will see a tab for **Deployed backend resources**. Click on the tab and then click the **Download amplify_outputs.json file** button.
+
-
+## Configure your frontend with Amplify
-Clone the repository locally.
+Now that your personal cloud sandbox is deployed and connection information is populated, you will need to configure the Amplify library to interact with your backend resources by using the `amplify_outputs.json` file.
-```bash title="Terminal" showLineNumbers={false}
-git clone https://github.com//amplify-vite-react-template.git
-cd amplify-vite-react-template && npm install
-```
+```tsx title="src/main.tsx"
+// highlight-next-line
+import { Amplify } from 'aws-amplify';
+import { StrictMode } from 'react';
+import { createRoot } from 'react-dom/client';
+import App from './App.tsx';
+// highlight-next-line
+import outputs from '../amplify_outputs.json';
+import './index.css';
-Now move the `amplify_outputs.json` file you downloaded above to the root of your project.
+// highlight-next-line
+Amplify.configure(outputs);
-```text
-├── amplify
-├── src
-├── amplify_outputs.json <== backend outputs file
-├── package.json
-└── tsconfig.json
+createRoot(document.getElementById('root')!).render(
+
+
+
+);
```
+
The **amplify_outputs.json** file contains backend endpoint information, publicly-viewable API keys, authentication flow information, and more. The Amplify client library uses this outputs file to connect to your Amplify Backend. You can review how the outputs file is imported within the `main.tsx` file and then passed into the `Amplify.configure(...)` function of the Amplify client library.
-
+To learn more, visit the [reference page for `amplify_outputs.json`](/[platform]/reference/amplify_outputs/)
+
-### 5. Implement delete functionality
+By doing so, Amplify will be able to communicate with your backend resources like Auth and Data when you use APIs such as `signIn()` or `generateClient()` without requiring you to pass context manually on each call.
-Go to the **src/App.tsx** file and add in a new `deleteTodo` functionality and pass function into the `
` element's `onClick` handler.
+## Add authentication to your frontend
-```tsx title="src/App.tsx"
-function App() {
- // ...
- // highlight-start
- function deleteTodo(id: string) {
- client.models.Todo.delete({ id })
- }
- // highlight-end
+Once the Amplify library is configured you are ready to add authentication to your app. The easiest way to get started is by using the [Amplify Authenticator connected component](https://ui.docs.amplify.aws/react/connected-components/authenticator).
- return (
-
-
-
- )
-}
-```
-
-Try out the deletion functionality now by starting the local dev server:
+First, install the Amplify UI library for React:
```bash title="Terminal" showLineNumbers={false}
-npm run dev
+npm add @aws-amplify/ui-react
```
-This should start a local dev server at http://localhost:5173.
-
-
-
-### 6. Implement login UI
-
-The starter application already has a pre-configured auth backend defined in the **amplify/auth/resource.ts** file. We've configured it to support email and password login but you can extend it to support a variety of login mechanisms, including Google, Amazon, Sign In With Apple, and Facebook.
-
-The fastest way to get your login experience up and running is to use our Authenticator UI component. In your **src/App.tsx** file, import the Authenticator UI component and wrap your `` element.
+Then, open your `src/App.tsx` file and wrap the existing content with ``. The Authenticator component auto-detects your auth backend settings and renders the correct UI state based on the auth backend's authentication flow.
```tsx title="src/App.tsx"
-// highlight-start
-import { Authenticator } from '@aws-amplify/ui-react'
-import '@aws-amplify/ui-react/styles.css'
-// highlight-end
-// ... other imports
+// highlight-next-line
+import { Authenticator } from '@aws-amplify/ui-react';
+import { useState } from 'react';
+import reactLogo from './assets/react.svg';
+import viteLogo from '/vite.svg';
+// highlight-next-line
+import '@aws-amplify/ui-react/styles.css';
+import './App.css';
function App() {
- // ...
+ const [count, setCount] = useState(0);
+
return (
- // highlight-start
+ // highlight-next-line
- {({ signOut }) => (
- // highlight-end
-
- {/*...*/}
- // highlight-next-line
-
-
- // highlight-start
- )}
+
+ Click on the Vite and React logos to learn more
+
+ // highlight-next-line
- // highlight-end
- )
+ );
}
-```
-
-The Authenticator component auto-detects your auth backend settings and renders the correct UI state based on the auth backend's authentication flow.
-Try out your application in your localhost environment again. You should be presented with a login experience now.
-
-
-
-To get these changes to the cloud, commit them to git and push the changes upstream.
-
-```bash title="Terminal" showLineNumbers={false}
-git commit -am "added authenticator"
-git push
+export default App;
```
-Amplify automatically deploys the latest version of your app based on your git commits. In just a few minutes, when the application rebuilds, the hosted app will be updated to support the deletion functionality.
-
-## Make backend updates
+
-Let's update our backend to implement per-user authorization rules, allowing each user to only access their own to-dos.
+CSS files generated by [`create-vite`](https://www.npmjs.com/package/create-vite) clash with the default styling for Amplify UI. For demo purposes, remove the `index.css` import in `src/main.tsx`
-### 7. Set up local AWS credentials
+```tsx title="src/main.tsx"
+import { Amplify } from 'aws-amplify';
+import { StrictMode } from 'react';
+import { createRoot } from 'react-dom/client';
+import App from './App.tsx';
+import outputs from '../amplify_outputs.json';
+// highlight-next-line
+// import "./index.css"
-To make backend updates, we are going to require AWS credentials to deploy backend updates from our local machine.
+Amplify.configure(outputs);
-**Skip ahead to step 8**, if you already have an AWS profile with credentials on your local machine, and your AWS profile has the `AmplifyBackendDeployFullAccess` permission policy.
+createRoot(document.getElementById('root')!).render(
+
+
+
+);
+```
-Otherwise, **[set up local AWS credentials](/[platform]/start/account-setup/)** that grant Amplify permissions to deploy backend updates from your local machine.
+And remove `text-align: center` from the generated `App.css` file:
+```css title="src/App.css"
+#root {
+ max-width: 1280px;
+ margin: 0 auto;
+ padding: 2rem;
+ // highlight-next-line
+ /* text-align: center; */
+}
-### 8. Deploy cloud sandbox
+/* ... */
+```
-To update your backend without affecting the production branch, use Amplify's cloud sandbox. This feature provides a separate backend environment for each developer on a team, ideal for local development and testing.
+
-To start your cloud sandbox, run the following command in a **new Terminal window**:
+Lastly, start your frontend's development server by running the `dev` script.
```bash title="Terminal" showLineNumbers={false}
-npx ampx sandbox
+npm run dev
```
-Once the cloud sandbox has been fully deployed (~5 min), you'll see the `amplify_outputs.json` file updated with connection information to a new isolated authentication and data backend.
+Visit [`http://localhost:5173`](http://localhost:5173) to view the changes and create your first user account!
-
+.png)
-The `npx ampx sandbox` command should run concurrently to your `npm run dev`. You can think of the cloud sandbox as the "localhost-equivalent for your app backend".
+By default, Amplify Auth resources are created with email and password login. To learn more about Amplify Auth visit the [documentation for setting up Auth](/[platform]/build-a-backend/auth/set-up-auth).
-
+## Add data to your frontend
-### 9. Implement per-user authorization
+Now that you have your application's backend deployed, Amplify library configured, and your first user account created, you are ready to begin adding data to your frontend application. Amplify Data is scaffolded at `amplify/data/resource.ts` with a basic `Todo` model which we will use for this example. You define a schema with `a.schema()` that is used to generate a type for the frontend client to use for intellisense and fast iterations.
-The to-do items in the starter are currently shared across all users, but, in most cases, you want data to be isolated on a per-user basis.
-
-To isolate the data on a per-user basis, you can use an "owner-based authorization rule". Let's apply the owner-based authorization rule to your to-do items:
+Before you make changes to your frontend, open `amplify/data/resource.ts` and modify the default authorization rule to allow owners to create, read, update, and delete their own To-dos. By default, your Data resource is created using `iam` as the default authorization method, however in this demo we will want each user to have their own To-do records. To learn more about the available authorization methods, visit the [documentation for customizing authorization rules](/[platform]/build-a-backend/data/customize-authz/).
```ts title="amplify/data/resource.ts"
-import { type ClientSchema, a, defineData } from '@aws-amplify/backend';
-
+// ...
const schema = a.schema({
- Todo: a.model({
- content: a.string(),
+ Todo: a
+ .model({
+ content: a.string()
+ })
// highlight-next-line
- }).authorization(allow => [allow.owner()]),
+ .authorization((allow) => [allow.owner()])
});
export type Schema = ClientSchema;
@@ -532,57 +511,134 @@ export type Schema = ClientSchema;
export const data = defineData({
schema,
authorizationModes: {
- // This tells the data client in your app (generateClient())
- // to sign API requests with the user authentication token.
- // highlight-next-line
- defaultAuthorizationMode: 'userPool',
- },
+ // highlight-start
+ // change "iam" to "userPool"
+ defaultAuthorizationMode: 'userPool'
+ // highlight-end
+ }
});
```
-In the application client code, let's also render the username to distinguish different users once they're logged in. Go to your **src/App.tsx** file and render the `user` property.
+Then let's revisit your `App.tsx` file to list existing To-dos and create new To-dos.
```tsx title="src/App.tsx"
-// ... imports
+import type { FormEvent } from 'react';
+import type { Schema } from '../amplify/data/resource';
+import { useEffect, useState } from 'react';
+import { Authenticator } from '@aws-amplify/ui-react';
+import { generateClient } from 'aws-amplify/api';
+import '@aws-amplify/ui-react/styles.css';
+import './App.css';
+
+const client = generateClient();
function App() {
- // ...
+ const [todos, setTodos] = useState();
+
+ async function listTodos() {
+ const todos = await client.models.Todo.list();
+ setTodos(todos.data);
+ }
+
+ useEffect(() => {
+ // list Todos on mount
+ listTodos();
+ }, []);
+
+ async function handleSubmitCreate(event: FormEvent) {
+ event.preventDefault();
+ const form = event.currentTarget as HTMLFormElement;
+ const data = new FormData(form);
+ const content = data.get('content') as string;
+ if (!content) throw new Error('Invalid content');
+ // create the new Todo using content from the form
+ await client.models.Todo.create({
+ content
+ });
+ // refresh the todo list
+ await listTodos();
+ // clear the form
+ form.reset();
+ }
+
return (
- // highlight-next-line
- {({ signOut, user }) => (
-
- // highlight-next-line
-
{user?.signInDetails?.loginId}'s todos
- {/* ... rest of the UI */}
-
- )}
+
+
+
Create to-do
+
+
+
+
To-do list
+
{todos?.map((todo) =>
{todo.content}
)}
+
+
- )
+ );
}
+
+export default App;
```
-Now, let's go back to your local application and test out the user isolation of the to-do items.
+Now when you visit [`http://localhost:5173`](http://localhost:5173) you are able to log in as a user and create a To-do record bound to your user! To learn more about the possibilities with your data resource, visit the [documentation for setting up Amplify Data](/[platform]/build-a-backend/data/set-up-data/).
-You will need to sign up new users again because now you're working with the cloud sandbox instead of your production backend.
+## Deploy to AWS
-
+By this step, you have a working React-based frontend application with authentication and operations to list and create new data in your application's backend. Prepare a GitHub repository for your fullstack application and proceed with deployment to AWS with Amplify!
-To get these changes to the cloud, commit them to git and push the changes upstream.
+After the repository has been created, deploy it with Amplify.
+
+
+
+Deploy to AWS
+
+
+Select **GitHub**. After you give Amplify access to your GitHub account via the popup window, pick the repository and `main` branch to deploy. Make no other changes and click through the flow to **Save and deploy**.
+
+
+
+## View deployed app
+
+When the build completes, visit the newly deployed branch by selecting "Visit deployed URL". Since the build deployed an API, database, and authentication backend, you will be able to create new to-do items.
+
+In the Amplify console, click into the deployment branch (in this case **main**) > select **Data** in the left-hand menu > **Data manager** to see the data entered in your database.
+
+
+
+### Downloading outputs file for deployed app
+
+As you build your backend with Amplify and your personal cloud sandbox, changes to the resource metadata are reflected in `amplify_outputs.json`. If you wish to use resource metadata from your deployed branch, you can download the `amplify_outputs.json` file from the Amplify console.
+
+
+
+Alternatively you can use the backend CLI to _generate outputs_:
```bash title="Terminal" showLineNumbers={false}
-git commit -am "added per-user data isolation"
-git push
+npx ampx generate outputs --app-id --branch
```
-Once your build completes in the Amplify Console, the `main` backend will update to support the changes made within the cloud sandbox. The data in the cloud sandbox is fully isolated and won't pollute your production database.
-
-
+[Learn more about backend CLI commands.](/[platform]/reference/cli-commands)
+## Deploy changes
+As you continue to build out your application with your personal cloud sandbox, each time your commit and push changes to your git repository your changes are deployed to the cloud.
+```bash title="Terminal" showLineNumbers={false}
+git commit -am "add a feature"
+git push
+```
+Once your build completes in the Amplify Console, the `main` backend will update to support the changes made within the cloud sandbox. The data in the cloud sandbox is fully isolated and won't pollute your production database.
+
👋 Welcome to AWS Amplify! In this quickstart guide, you will:
@@ -596,9 +652,6 @@ We have two Quickstart guides you can follow:
-
-
-
👋 Welcome to AWS Amplify! In this quickstart guide, you will:
@@ -912,13 +965,6 @@ git push
Once your build completes in the Amplify Console, the `main` backend will update to support the changes made within the cloud sandbox. The data in the cloud sandbox is fully isolated and won't pollute your production database.
-
-
-
-
-
-
-
👋 Welcome to AWS Amplify! In this quickstart guide, you will:
@@ -1238,12 +1284,6 @@ Once your build completes in the Amplify Console, the `main` backend will update
-
-
-
-
-
-
## Prerequisites
@@ -1678,16 +1718,6 @@ You can terminate the sandbox environment now to clean up the project.
Publishing changes to the cloud requires a remote git repository. Amplify offers fullstack branch deployments that allow you to automatically deploy infrastructure and application code changes from feature branches. To learn more, visit the [fullstack branch deployments guide](/[platform]/deploy-and-host/fullstack-branching/branch-deployments).
-
-
-
-
-
-
-
-
-
-
## Prerequisites
@@ -2137,10 +2167,6 @@ You can terminate the sandbox environment now to clean up the project.
Publishing changes to the cloud requires a remote git repository. Amplify offers fullstack branch deployments that allow you to automatically deploy infrastructure and application code changes from feature branches. To learn more, visit the [fullstack branch deployments guide](/[platform]/deploy-and-host/fullstack-branching/branch-deployments).
-
-
-
-
👋 Welcome to AWS Amplify! In this quickstart guide, you will:
@@ -2601,15 +2627,6 @@ npx @aws-amplify/backend-cli generate outputs --out-dir app/src/main/res/raw --a
-
-
-
-
-
-
-
-
-
## Prerequisites
@@ -2934,7 +2951,6 @@ You can terminate the sandbox environment now to clean up the project.
Publishing changes to the cloud requires a remote git repository. Amplify offers fullstack branch deployments that allow you to automatically deploy infrastructure and application code changes from feature branches. To learn more, visit the [fullstack branch deployments guide](/[platform]/deploy-and-host/fullstack-branching/branch-deployments).
-
## 🥳 Success