v2 Getting Started (AWS)

public/_redirects

@@ -397,7 +397,8 @@
 /tutorials/replicate-aws-resources-localstack-extension/ /aws/tutorials/replicate-aws-resources-localstack-extension 301
 /user-guide/tools/localstack-sdk/python/ /aws/tooling/localstack-sdks/python 301
 /user-guide/lambda-tools/hot-reloading/ /aws/tooling/lambda-tools/hot-reloading 301
-/getting-started/quickstart/ /aws/getting-started/quickstart 301
+/getting-started/quickstart/ /aws/getting-started/local-development/ 301
+/aws/getting-started/quickstart/ /aws/getting-started/local-development/ 301
 /overview/ /aws 301
 /user-guide/aws/glue/ /aws/services/glue 301
 /getting-started/ /aws/getting-started 301
@@ -804,7 +805,8 @@
 /tutorials/replicate-aws-resources-localstack-extension /aws/tutorials/replicate-aws-resources-localstack-extension 301
 /user-guide/tools/localstack-sdk/python /aws/tooling/localstack-sdks/python 301
 /user-guide/lambda-tools/hot-reloading /aws/tooling/lambda-tools/hot-reloading 301
-/getting-started/quickstart /aws/getting-started/quickstart 301
+/getting-started/quickstart /aws/getting-started/local-development/ 301
+/aws/getting-started/quickstart /aws/getting-started/local-development/ 301
 /overview /aws 301
 /user-guide/aws/glue /aws/services/glue 301
 /getting-started /aws/getting-started 301

scripts/redirects/redirects_config.json

@@ -1975,7 +1975,12 @@
     },
     {
       "old_link": "/getting-started/quickstart/",
-      "new_link": "/aws/getting-started/quickstart",
+      "new_link": "/aws/getting-started/local-development/",
+      "status_code": 301
+    },
+    {
+      "old_link": "/aws/getting-started/quickstart/",
+      "new_link": "/aws/getting-started/local-development/",
       "status_code": 301
     },
     {

src/content/docs/aws/capabilities/cloud-sandbox/ephemeral-instances.md

@@ -87,7 +87,7 @@ If you have created a Cloud Pod from an older version of LocalStack, you need to
 
 ## Ephemeral Instances CLI
 
-The Ephemeral Instances CLI is included in the [LocalStack CLI installation](/aws/getting-started/installation/#installing-localstack-cli), so no additional installations are needed to start using it.
+The Ephemeral Instances CLI is included in the [LocalStack CLI installation](/aws/getting-started/installation/#install-localstack-cli), so no additional installations are needed to start using it.
 If you're a licensed user, setting the `LOCALSTACK_AUTH_TOKEN` as an environment variable is recommended to access all features of the Ephemeral Instances CLI.
 
 Access the Ephemeral Instances CLI by running the `localstack ephemeral` command from your terminal.

src/content/docs/aws/capabilities/security-testing/custom-tls-certificates.mdx

@@ -30,7 +30,7 @@ They all can be summarised as:
 
 ## Creating a custom docker image
 
-If you run LocalStack in a docker container (which includes using [the CLI](/aws/getting-started/installation/#installing-localstack-cli), [docker](/aws/getting-started/installation/#docker), [docker-compose](/aws/getting-started/installation/#docker-compose), or [helm](/aws/getting-started/installation/#helm)), to include a custom TLS root certificate a new docker image should be created.
+If you run LocalStack in a docker container (which includes using [the CLI](/aws/getting-started/installation/#install-localstack-cli), [docker](/aws/getting-started/installation/#docker-compose), [docker-compose](/aws/getting-started/installation/#docker-compose), or [helm](/aws/getting-started/installation/#helm-kubernetes)), to include a custom TLS root certificate a new docker image should be created.
 
 Create a `Dockerfile` containing the following commands:
 

src/content/docs/aws/capabilities/state-management/cloud-pods.mdx

@@ -28,7 +28,7 @@ You can save and load the persistent state of Cloud Pods, you can use the [Cloud
 LocalStack provides a remote storage backend that can be used to store the state of your running application and share it with your team members.
 You can interact with the Cloud Pods over the storage backend via the LocalStack Web Application.
 
-Cloud Pods CLI is included in the [LocalStack CLI installation](/aws/getting-started/installation/#installing-localstack-cli), so there's no need for additional installations to begin using it.
+Cloud Pods CLI is included in the [LocalStack CLI installation](/aws/getting-started/installation/#install-localstack-cli), so there's no need for additional installations to begin using it.
 If you're a licensed user, we suggest setting the `LOCALSTACK_AUTH_TOKEN` as an environment variable.
 This enables you to access the complete range of LocalStack Cloud Pods features.
 
@@ -451,7 +451,7 @@ localstack pod list s3-storage-aws
 
 :::note
 Full S3 remotes support is available in the CLI from version 3.2.0.
-If you experience any difficulties, update your [LocalStack CLI](/aws/getting-started/installation/#updating-localstack-cli).
+If you experience any difficulties, update your [LocalStack CLI](/aws/getting-started/installation/#update-localstack-cli).
 :::
 
 ### ORAS remote storage

src/content/docs/aws/getting-started/ai-workflows.mdx

@@ -0,0 +1,92 @@
+---
+title: AI & Agent Workflows
+description: Use LocalStack with AI coding assistants, MCP clients, and agent-driven infrastructure workflows.
+template: doc
+sidebar:
+  order: 6
+---
+
+## Introduction
+
+LocalStack gives AI coding assistants a local AWS-compatible environment to work against. Instead of letting an agent experiment in a real AWS account, you can ask it to create infrastructure, deploy code, inspect logs, and test resources in LocalStack first.
+
+This is useful when you want to:
+
+- Prototype AWS applications & infrastructure code from natural language prompts.
+- Validate AI-generated Terraform, CDK, or AWS CLI commands before using a cloud account.
+- Give an AI assistant a safe place to inspect resources, debug logs, and iterate on deployments.
+- Use reusable agent instructions for LocalStack-aware infrastructure workflows.
+
+## Common workflows
+
+There are three common ways to use LocalStack in AI-assisted development:
+
+- Use the [LocalStack MCP Server](/aws/tooling/mcp-server/) when your AI assistant supports MCP clients such as Cursor, Claude, Codex, or OpenCode.
+- Use [LocalStack Skills](https://github.com/localstack/skills) when you want reusable agent instructions for deploying and testing AWS architectures against LocalStack.
+- Use LocalStack with `tflocal`, `cdklocal`, or `awslocal` when you want the agent to generate infrastructure code or commands that you review and run locally.
+
+You do not need all three approaches to get started. If your editor supports MCP, start with the LocalStack MCP Server. Or, you can use Skills if you want reusable agent instructions. If not, ask your assistant to generate Terraform, CDK, or AWS CLI steps and run them with LocalStack's local wrappers.
+
+## Connect an MCP client
+
+The LocalStack MCP Server connects MCP-compatible clients to your LocalStack environment. Once configured, your AI assistant can use LocalStack tools to start the container, deploy infrastructure, run AWS CLI commands, inspect logs, manage state, and query resources.
+
+:::note
+The MCP server runs locally and talks to your LocalStack instance. Your AI assistant is the MCP client. For setup instructions and the full tool reference, see the [LocalStack MCP Server guide](/aws/tooling/mcp-server/).
+:::
+
+All MCP server tools require a valid [Auth Token](/aws/getting-started/auth-token/) configured as `LOCALSTACK_AUTH_TOKEN`.
+
+## Use agent skills
+
+[LocalStack Skills](https://github.com/localstack/skills) provide reusable instructions for AI agents working with LocalStack. They help agents follow LocalStack-specific conventions when creating infrastructure, deploying resources, running tests, and inspecting local cloud state.
+
+Skills are most useful when you want the assistant to follow a repeatable workflow, for example:
+
+- Scaffold a local AWS application and deploy it to LocalStack.
+- Convert an AWS architecture idea into Terraform or CDK that targets LocalStack first.
+- Debug a failing local deployment by checking resources, logs, and configuration.
+- Save or restore LocalStack state as part of an iterative development loop.
+
+Refer to the [LocalStack Skills repository](https://github.com/localstack/skills) for available skills and setup instructions.
+
+## Example prompt sequence
+
+After LocalStack and your preferred AI tooling are configured, you can use a sequence like this:
+
+```text
+Create a Terraform application with an S3 bucket, a Lambda function, and a DynamoDB table.
+Make it deployable to LocalStack with tflocal.
+```
+
+```text
+Deploy the application to LocalStack and fix any errors from the deployment.
+```
+
+```text
+Invoke the Lambda function locally, inspect the DynamoDB table, and summarize what resources were created.
+```
+
+```text
+Add an integration test that verifies the Lambda writes an item to DynamoDB.
+Run the test against LocalStack.
+```
+
+This keeps the feedback loop local while still giving the assistant a realistic AWS-compatible target.
+
+## Review before applying to AWS
+
+AI-generated infrastructure still needs review. Treat LocalStack as the first validation step, not as a replacement for code review, tests, or production deployment controls.
+
+Before applying changes to AWS, check that:
+
+- The generated infrastructure matches your intended architecture.
+- Resource names, IAM policies, and environment variables are appropriate for your project.
+- Tests pass against LocalStack.
+- You understand any changes the assistant made to application code or deployment configuration.
+
+## Next steps
+
+- Configure the [LocalStack MCP Server](/aws/tooling/mcp-server/) if your AI assistant supports MCP.
+- Review [LocalStack Skills](https://github.com/localstack/skills) for reusable agent workflows.
+- Browse the [LocalStack for AWS services](/aws/services/) reference, or check the [Getting Started FAQ](/aws/getting-started/faq/) for common setup questions.