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

* added indexes and other callouts

* sandbox env additional callouts

* updated callout

* removed the callout tag

* updated service names

Author: AnilMaktala

src/pages/[platform]/deploy-and-host/sandbox-environments/setup/index.mdx

@@ -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 AWS Lambda functions and AWS AppSync resolver templates without requiring a full redeployment.  
+
+However, certain operations cannot be hot-swapped and require resource recreation to proceed:  
+
+- **Amazon 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.  
+- **Amazon 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)