Skip to content

Add additional callouts about resource provisioning and disposition in sandbox mode #8244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Feb 13, 2025
Merged

Add additional callouts about resource provisioning and disposition in sandbox mode #8244

Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
7f5241d
added indexes and other callouts
AnilMaktala Feb 7, 2025
7b227a9
sandbox env additional callouts
AnilMaktala Feb 10, 2025
b496890
updated callout
AnilMaktala Feb 11, 2025
b2b601f
removed the callout tag
AnilMaktala Feb 11, 2025
1b04b27
updated service names
AnilMaktala Feb 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions src/pages/[platform]/deploy-and-host/sandbox-environments/setup/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,11 +31,15 @@ export function getStaticProps(context) {

You can use a personal cloud sandbox environment that provides an isolated development space to rapidly build, test, and iterate on a fullstack app. Each developer on your team can use their own disposable sandbox environment connected to cloud resources.

<Callout>

Cloud sandbox environments are not intended for production workloads.
**Cloud sandbox environments** are designed for development purposes and are not intended for production workloads. To accelerate deployments, Amplify utilizes **CDK hot swapping** where supported, enabling rapid updates to resources such as Lambda functions and AppSync resolver templates without requiring a full redeployment.

However, certain operations cannot be hot-swapped and require resource recreation to proceed:

- **DynamoDB GSI Operations:** In sandbox environments (but not in production), modifying or deleting a Global Secondary Index (GSI) is a time-intensive process. To simplify this, Amplify drops and recreates the table instead of modifying the index.
- **Cognito User Pool Changes:** Unsupported modifications, such as deleting a required field, result in Amplify dropping and recreating the user pool to ensure a consistent and functional configuration.


</Callout>

![How cloud sandbox environments work](/images/gen2/how-amplify-works/sandbox.png)

Expand Down
Loading