Restructure some pages to create new "Connecting" section

astro.config.mjs

@@ -334,6 +334,48 @@ export default defineConfig({
               label: 'Sample Apps',
               slug: 'aws/sample-apps',
             },
+            {
+              label: 'Connecting',
+              collapsed: true,
+              items: [
+                {
+                  label: 'Overview',
+                  slug: 'aws/connecting',
+                },
+                {
+                  label: 'AWS CLI',
+                  slug: 'aws/connecting/aws-cli',
+                },
+                {
+                  label: 'AWS SDKs',
+                  autogenerate: {
+                    directory: '/aws/connecting/aws-sdks',
+                  },
+                  collapsed: true,
+                },
+                {
+                  label: 'Infrastructure as Code',
+                  autogenerate: {
+                    directory: '/aws/connecting/infrastructure-as-code',
+                  },
+                  collapsed: true,
+                },
+                {
+                  label: 'LocalStack Console',
+                  autogenerate: {
+                    directory: '/aws/connecting/console',
+                  },
+                  collapsed: true,
+                },
+                {
+                  label: 'IDE Extensions',
+                  autogenerate: {
+                    directory: '/aws/connecting/ides',
+                  },
+                  collapsed: true,
+                },
+              ],
+            },
             {
               label: 'Capabilities',
               collapsed: true,
@@ -446,10 +488,6 @@ export default defineConfig({
                   ],
                   collapsed: true,
                 },
-                {
-                  label: 'LocalStack Toolkit VS Code',
-                  slug: 'aws/tooling/vscode-extension',
-                },
                 {
                   label: 'Lambda Tools',
                   autogenerate: {
@@ -494,27 +532,6 @@ export default defineConfig({
                   },
                   collapsed: true,
                 },
-                {
-                  label: 'AWS SDKs',
-                  autogenerate: {
-                    directory: '/aws/integrations/aws-sdks',
-                  },
-                  collapsed: true,
-                },
-                {
-                  label: 'AWS Native Tools',
-                  autogenerate: {
-                    directory: '/aws/integrations/aws-native-tools',
-                  },
-                  collapsed: true,
-                },
-                {
-                  label: 'Infrastructure as Code',
-                  autogenerate: {
-                    directory: '/aws/integrations/infrastructure-as-code',
-                  },
-                  collapsed: true,
-                },
                 {
                   label: 'Containers',
                   autogenerate: {

public/js/icon-loader.js

@@ -10,6 +10,7 @@
     Features: 'cube-icon',
     'Feature Coverage': 'buildings-icon',
     'Sample Apps': 'file-icon',
+    Connecting: 'plug-icon',
     Capabilities: 'starburst-icon',
     Tooling: 'wrench-icon',
     Integrations: 'connections-icon',

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

@@ -65,7 +65,7 @@ To query the list of S3 buckets in the Ephemeral Instance, run the following com
 aws --endpoint-url=<EPHEMERAL_INSTANCE_ENDPOINT_URL> s3 ls
 ```
 
-You can also use integrations, such as [CDK](/aws/integrations/aws-native-tools/aws-cdk/), [SAM CLI](/aws/integrations/aws-native-tools/aws-sam/), and [Terraform](/aws/integrations/infrastructure-as-code/terraform/), to interact with the Ephemeral Instance.
+You can also use integrations, such as [CDK](/aws/connecting/infrastructure-as-code/aws-cdk/), [SAM CLI](/aws/connecting/infrastructure-as-code/aws-sam/), and [Terraform](/aws/connecting/infrastructure-as-code/terraform/), to interact with the Ephemeral Instance.
 In these integrations, you can change the `AWS_ENDPOINT_URL` environment variable to the endpoint URL of the Ephemeral Instance.
 
 ### View the Logs of the Ephemeral Instance

src/content/docs/aws/capabilities/networking/index.mdx

@@ -20,7 +20,7 @@ LocalStack only binds to IPv4 addresses (e.g. `127.0.0.1`). Make sure you're not
 
 ## [Using the endpoint URL](/aws/capabilities/networking/accessing-endpoint-url)
 
-For example, setting the `endpoint_url` parameter with an [AWS SDK](/aws/integrations/aws-sdks/).
+For example, setting the `endpoint_url` parameter with an [AWS SDK](/aws/connecting/aws-sdks/).
 
 <CardGridLayout cards={[
   {

src/content/docs/aws/capabilities/networking/transparent-endpoint-injection.md

@@ -109,7 +109,7 @@ Make sure to use this only for local testing, and never in production.
 ## Current Limitations
 
 - The mechanism to disable certificate validation for these requests is not currently functional with Go Lambdas.
-  To work around this issue, you'll need to manually set your endpoint when creating your AWS SDK client, as detailed in our documentation on the [Go AWS SDK](/aws/integrations/aws-sdks/go).
+  To work around this issue, you'll need to manually set your endpoint when creating your AWS SDK client, as detailed in our documentation on the [Go AWS SDK](/aws/connecting/aws-sdks/go).
 - Transparent Endpoint Injection does not work when code runs inside the LocalStack container. If you need to connect to LocalStack from within the container, here are a couple of alternative approaches:
   - Set the AWS_ENDPOINT_URL environment variable:
 Set `AWS_ENDPOINT_URL=http://localhost.localstack.cloud:4566`. This is the recommended approach as it directly points your AWS client to the LocalStack endpoint.

src/content/docs/aws/capabilities/web-app/app-inspector.md

@@ -39,9 +39,9 @@ App Inspector runs against the LocalStack emulator, which monitors use of IAM po
 
 ## LocalStack Toolkit for VS Code
 
-App Inspector is built into the [LocalStack Toolkit for VS Code](/aws/tooling/vscode-extension), so you can trace operation flows and inspect payloads without leaving your editor. Once LocalStack is running, open the App Inspector panel directly in the LocalStack Toolkit extension to view operations and drill into service interactions.
+App Inspector is built into the [LocalStack Toolkit for VS Code](/aws/connecting/ides/vscode-extension), so you can trace operation flows and inspect payloads without leaving your editor. Once LocalStack is running, open the App Inspector panel directly in the LocalStack Toolkit extension to view operations and drill into service interactions.
 
-If you haven't set up the toolkit yet, see [LocalStack Toolkit for VS Code](/aws/tooling/vscode-extension) to get started.
+If you haven't set up the toolkit yet, see [LocalStack Toolkit for VS Code](/aws/connecting/ides/vscode-extension) to get started.
 
 ![App Inspector panel in the LocalStack Toolkit for VS Code showing a live event stream](/images/aws/app-inspector/app-inspector-vscode.png)
 

src/content/docs/aws/integrations/aws-native-tools/aws-cli.md → src/content/docs/aws/connecting/aws-cli.md

@@ -9,7 +9,7 @@ sidebar:
 ## Introduction
 
 The [AWS Command Line Interface (CLI)](https://aws.amazon.com/cli/) is a unified tool for creating and managing AWS services via a command line interface.
-All CLI commands applicable to services implemented within [LocalStack](/aws/integrations/aws-native-tools/aws-cli/) can be executed when operating against LocalStack.
+All CLI commands applicable to services implemented within [LocalStack](/aws/connecting/aws-cli/) can be executed when operating against LocalStack.
 
 You can use the AWS CLI with LocalStack using either of the following approaches:
 

src/content/docs/aws/integrations/aws-sdks/cpp.md → src/content/docs/aws/connecting/aws-sdks/cpp.md

@@ -1,5 +1,5 @@
 ---
-title: AWS C++
+title: AWS SDK for C++
 description: How to use the C++ AWS SDK with LocalStack.
 template: doc
 sidebar:

src/content/docs/aws/integrations/aws-sdks/go.mdx → src/content/docs/aws/connecting/aws-sdks/go.mdx

@@ -1,5 +1,5 @@
 ---
-title: AWS Go
+title: AWS SDK for Go
 description: How to use the Go AWS SDK with LocalStack.
 template: doc
 sidebar:

src/content/docs/aws/integrations/aws-sdks/index.md → src/content/docs/aws/connecting/aws-sdks/index.mdx

@@ -6,6 +6,8 @@ sidebar:
   order: 1
 ---
 
+import SectionCards from '../../../../../components/SectionCards.astro';
+
 ## Introduction
 
 LocalStack integrates with official AWS Software Development Kits (SDKs) so you can connect to LocalStack services using the same SDKs you use for AWS services.
@@ -20,3 +22,10 @@ To connect to LocalStack services using AWS SDKs, you can use one of the followi
 - **Transparent endpoint injection (recommended):** Connect to LocalStack services without modifying your application code.
   Transparent endpoint injection uses the integrated DNS server to resolve AWS API calls to target LocalStack.
   Refer to the [Transparent Endpoint Injection](/aws/capabilities/networking/transparent-endpoint-injection/) guide for more information.
+
+## Supported SDKs
+
+<SectionCards
+  basePath="aws/connecting/aws-sdks/"
+  useDirectFiles={true}
+/>

src/content/docs/aws/integrations/aws-sdks/java.mdx → src/content/docs/aws/connecting/aws-sdks/java.mdx

@@ -1,5 +1,5 @@
 ---
-title: AWS Java
+title: AWS SDK for Java
 description: How to use the Java AWS SDK with LocalStack.
 template: doc
 sidebar:

src/content/docs/aws/integrations/aws-sdks/javascript.mdx → src/content/docs/aws/connecting/aws-sdks/javascript.mdx

@@ -1,5 +1,5 @@
 ---
-title: AWS JavaScript
+title: AWS SDK for JavaScript
 description: How to use the JavaScript AWS SDK with LocalStack.
 template: doc
 sidebar:

src/content/docs/aws/integrations/aws-sdks/net.md → src/content/docs/aws/connecting/aws-sdks/net.md

@@ -1,5 +1,5 @@
 ---
-title: AWS .NET
+title: AWS SDK for .NET
 description: How to use the .NET AWS SDK with LocalStack.
 template: doc
 sidebar:

src/content/docs/aws/integrations/aws-sdks/php.md → src/content/docs/aws/connecting/aws-sdks/php.md

@@ -1,5 +1,5 @@
 ---
-title: AWS PHP
+title: AWS SDK for PHP
 description: How to use the PHP AWS SDK with LocalStack.
 template: doc
 sidebar:

src/content/docs/aws/integrations/aws-sdks/python-boto3.md → src/content/docs/aws/connecting/aws-sdks/python-boto3.md

@@ -1,5 +1,5 @@
 ---
-title: AWS Python Boto3
+title: AWS SDK for Python (Boto3)
 description: How to use the Python Boto3 AWS SDK with LocalStack.
 template: doc
 sidebar:

src/content/docs/aws/integrations/aws-sdks/ruby.md → src/content/docs/aws/connecting/aws-sdks/ruby.md

@@ -1,5 +1,5 @@
 ---
-title: AWS Ruby
+title: AWS SDK for Ruby
 description: How to use the Ruby AWS SDK with LocalStack.
 template: doc
 sidebar:

src/content/docs/aws/connecting/console/index.mdx

@@ -0,0 +1,17 @@
+---
+title: Overview
+description: Use the LocalStack web app as a local equivalent of the AWS Console to inspect and manage resources running on LocalStack.
+template: doc
+editUrl: false
+sidebar:
+    order: 1
+---
+
+import SectionCards from '../../../../../components/SectionCards.astro';
+
+If you use the AWS Console today to inspect resources, navigate stacks, or check on your environment, the LocalStack web app gives you the same kind of view for the resources running on your LocalStack instance. Sign in once, and you can browse and manage your local AWS resources without leaving the browser.
+
+<SectionCards
+  basePath="aws/connecting/console/"
+  useDirectFiles={true}
+/>

src/content/docs/aws/connecting/ides/aws-toolkit-for-vscode.md

@@ -0,0 +1,21 @@
+---
+title: AWS Toolkit for VS Code
+description: Use the AWS Toolkit for VS Code to browse and operate on AWS resources running on LocalStack.
+template: doc
+sidebar:
+    order: 2
+---
+
+## Introduction
+
+The [AWS Toolkit for VS Code](https://docs.aws.amazon.com/toolkit-for-vscode/) is an Amazon-maintained extension for Visual Studio Code that lets you interact with AWS resources directly from the editor.
+
+When configured with a `localstack` profile, the AWS Toolkit operates against your local LocalStack instance instead of a real AWS account, giving you the same AWS-style resource browser experience you already use against AWS.
+
+## AWS Explorer
+
+Once installed, the AWS Toolkit adds an **AWS Explorer** view to the VS Code activity bar. Selecting the `localstack` profile points the Explorer at your local LocalStack instance, where you can browse the resources you have provisioned.
+
+![AWS Explorer view in the AWS Toolkit for VS Code](/images/aws/lambda-remote-debugging/explorer.png)
+
+For installation, profile setup, and the full set of features the AWS Toolkit provides, see the [AWS Toolkit for VS Code User Guide](https://docs.aws.amazon.com/toolkit-for-vscode/).

src/content/docs/aws/connecting/ides/index.mdx

@@ -0,0 +1,17 @@
+---
+title: Overview
+description: Connect to LocalStack from your IDE — install, configure, run, and inspect LocalStack without leaving your editor.
+template: doc
+editUrl: false
+sidebar:
+    order: 1
+---
+
+import SectionCards from '../../../../../components/SectionCards.astro';
+
+Use IDE extensions to install, configure, run, and inspect LocalStack alongside the code you are developing — without leaving your editor. The LocalStack Toolkit manages the LocalStack lifecycle from VS Code, and the AWS Toolkit for VS Code lets you browse and operate on the resources running on your LocalStack instance from a familiar AWS-style explorer.
+
+<SectionCards
+  basePath="aws/connecting/ides/"
+  useDirectFiles={true}
+/>

src/content/docs/aws/tooling/vscode-extension.md → src/content/docs/aws/connecting/ides/vscode-extension.md

@@ -2,6 +2,8 @@
 title: LocalStack Toolkit for VS Code
 description: Install, configure, and run LocalStack without leaving VS Code.
 template: doc
+sidebar:
+    order: 1
 tags: ['Hobby']
 ---
 

src/content/docs/aws/connecting/index.mdx

@@ -0,0 +1,23 @@
+---
+title: Overview
+description: Connect to LocalStack using the same AWS tools you already use — CLI, SDKs, IaC, the web console, and IDE integrations.
+template: doc
+editUrl: false
+sidebar:
+    order: 1
+---
+
+import SectionCards from '../../../../components/SectionCards.astro';
+
+If you already run an application on AWS, you almost certainly connect to it through familiar tools — the AWS CLI, an AWS SDK, an Infrastructure as Code tool such as Terraform or AWS CDK, or an IDE plugin. Running that same application against LocalStack means continuing to use those tools; you only need to point them at LocalStack instead of AWS.
+
+<SectionCards
+  basePath="aws/connecting/"
+  customTitles={{
+    "aws-cli": "AWS CLI",
+    "aws-sdks": "AWS SDKs",
+    "console": "LocalStack Console",
+    "infrastructure-as-code": "Infrastructure as Code",
+    "ides": "IDE Extensions",
+  }}
+/>

src/content/docs/aws/integrations/aws-native-tools/aws-cdk.md → src/content/docs/aws/connecting/infrastructure-as-code/aws-cdk.md

@@ -3,7 +3,7 @@ title: AWS CDK
 description: Use the AWS CDK (Cloud Development Kit) with LocalStack.
 template: doc
 sidebar:
-  order: 2
+  order: 4
 ---
 
 ![AWS CDK](public/images/aws/aws-cdk-logo.svg)

src/content/docs/aws/integrations/aws-native-tools/aws-chalice.mdx → src/content/docs/aws/connecting/infrastructure-as-code/aws-chalice.mdx

@@ -3,7 +3,7 @@ title: AWS Chalice
 description: Use AWS Chalice with LocalStack.
 template: doc
 sidebar:
-    order: 4
+    order: 7
 ---
 
 import { FileTree } from '@astrojs/starlight/components';

src/content/docs/aws/integrations/aws-native-tools/aws-copilot-cli.mdx → src/content/docs/aws/connecting/infrastructure-as-code/aws-copilot-cli.mdx

@@ -3,7 +3,7 @@ title: AWS Copilot CLI
 description: Build, release, and operate containerized applications on AWS with AWS Copilot CLI.
 template: doc
 sidebar:
-    order: 5
+    order: 8
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 

src/content/docs/aws/integrations/infrastructure-as-code/cloud-custodian.md → src/content/docs/aws/connecting/infrastructure-as-code/cloud-custodian.md

@@ -3,7 +3,7 @@ title: Cloud Custodian
 description: Use Cloud Custodian with LocalStack
 template: doc
 sidebar:
-    order: 4
+    order: 10
 ---
 
 ## Introduction

src/content/docs/aws/integrations/infrastructure-as-code/crossplane.md → src/content/docs/aws/connecting/infrastructure-as-code/crossplane.md

@@ -3,7 +3,7 @@ title: Crossplane
 description: Use the Crossplane cloud-native control plane framework with LocalStack.
 template: doc
 sidebar:
-  order: 3
+  order: 9
 ---
 
 ## Overview

src/content/docs/aws/integrations/infrastructure-as-code/former2.md → src/content/docs/aws/connecting/infrastructure-as-code/former2.md

@@ -3,7 +3,7 @@ title: Former2
 description: Use Former2 to generate Infrastructure-as-Code outputs from existing resources with LocalStack.
 template: doc
 sidebar:
-  order: 5
+  order: 11
 ---
 
 ## Introduction

src/content/docs/aws/connecting/infrastructure-as-code/index.mdx

@@ -0,0 +1,17 @@
+---
+title: Overview
+description: Deploy resources to LocalStack using the same Infrastructure as Code tools you already use against AWS.
+template: doc
+editUrl: false
+sidebar:
+    order: 1
+---
+
+import SectionCards from '../../../../../components/SectionCards.astro';
+
+If you provision AWS resources with an Infrastructure as Code (IaC) tool today, you can keep using the same templates, modules, and stacks against LocalStack. Each integration shows how to point your IaC tool at LocalStack so the resources are created locally instead of in your AWS account.
+
+<SectionCards
+  basePath="aws/connecting/infrastructure-as-code/"
+  useDirectFiles={true}
+/>