diff --git a/astro.config.mjs b/astro.config.mjs index 12ebe42d8..d807d0f5c 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -457,6 +457,10 @@ export default defineConfig({ }, ], }, + { + label: 'Credentials', + slug: 'aws/connecting/credentials', + }, ], }, { @@ -487,6 +491,10 @@ export default defineConfig({ label: 'LocalStack MCP Server', slug: 'aws/developer-tools/running-localstack/mcp-server', }, + { + label: 'LocalStack Desktop', + slug: 'aws/developer-tools/running-localstack/localstack-desktop', + }, ], }, { @@ -554,35 +562,26 @@ export default defineConfig({ }, ], }, + { + label: 'CI Pipelines', + collapsed: true, + items: [{ autogenerate: { directory: '/aws/ci-pipelines' } }], + }, { label: 'Configuration', collapsed: true, items: [ { label: 'Overview', - slug: 'aws/capabilities', + slug: 'aws/configuration', }, { - label: 'LocalStack Web App', - collapsed: true, - items: [ - { - autogenerate: { - directory: '/aws/capabilities/web-app', - }, - }, - ], + label: 'Configuration Options', + slug: 'aws/configuration/configuration-options', }, { - label: 'Config', - collapsed: true, - items: [ - { - autogenerate: { - directory: '/aws/capabilities/config', - }, - }, - ], + label: 'Logging', + slug: 'aws/configuration/logging', }, { label: 'Networking', @@ -590,52 +589,66 @@ export default defineConfig({ items: [ { autogenerate: { - directory: '/aws/capabilities/networking', + directory: '/aws/configuration/networking', }, }, ], }, { - label: 'LocalStack SDKs', + label: 'Advanced Features', collapsed: true, items: [ { autogenerate: { - directory: '/aws/capabilities/localstack-sdks', + directory: '/aws/configuration/advanced', }, }, ], }, + ], + }, + { + label: 'Advanced Installation', + collapsed: true, + items: [ + { + label: 'Overview', + slug: 'aws/advanced-installation', + }, + { + label: 'Docker Images', + slug: 'aws/advanced-installation/docker-images', + }, + { + label: 'Enterprise Image', + slug: 'aws/advanced-installation/enterprise-image', + }, + { + label: 'Podman', + slug: 'aws/advanced-installation/podman', + }, + { + label: 'Rancher Desktop', + slug: 'aws/advanced-installation/rancher-desktop', + }, { - label: 'Extensions', + label: 'Kubernetes', + collapsed: true, items: [ { autogenerate: { - directory: '/aws/capabilities/extensions', + directory: '/aws/advanced-installation/kubernetes', }, }, - { - label: 'Official Extensions', - link: 'https://app.localstack.cloud/extensions/library/', - }, ], - collapsed: true, }, { - label: 'DNS Server', - slug: 'aws/capabilities/dns-server', - }, - { - label: 'Testing Utils', - slug: 'aws/capabilities/testing-utils', + label: 'DevContainers', + slug: 'aws/advanced-installation/devcontainers', }, { label: 'LocalStack Docker Extension', - slug: 'aws/capabilities/localstack-docker-extension', - }, - { - label: 'LocalSurf', - slug: 'aws/capabilities/localsurf', + slug: 'aws/advanced-installation/localstack-docker-extension', }, ], }, @@ -648,45 +661,38 @@ export default defineConfig({ slug: 'aws/integrations', }, { - label: 'Continuous Integration', + label: 'LocalStack Extensions', collapsed: true, items: [ { autogenerate: { - directory: '/aws/integrations/continuous-integration', + directory: '/aws/integrations/extensions', }, }, - ], - }, - { - label: 'Containers', - collapsed: true, - items: [ { - autogenerate: { - directory: '/aws/integrations/containers', - }, + label: 'Official Extensions', + link: 'https://app.localstack.cloud/extensions/library/', }, ], }, { - label: 'App Frameworks', + label: 'LocalStack SDKs', collapsed: true, items: [ { autogenerate: { - directory: '/aws/integrations/app-frameworks', + directory: '/aws/integrations/localstack-sdks', }, }, ], }, { - label: 'Messaging', + label: 'App Frameworks', collapsed: true, items: [ { autogenerate: { - directory: '/aws/integrations/messaging', + directory: '/aws/integrations/app-frameworks', }, }, ], @@ -705,31 +711,37 @@ export default defineConfig({ ], }, { - label: 'Enterprise', + label: 'Team Workspaces', collapsed: true, items: [ { label: 'Overview', - slug: 'aws/enterprise', + slug: 'aws/team-workspaces', }, { - label: 'Kubernetes', - collapsed: true, - items: [ - { - autogenerate: { directory: '/aws/enterprise/kubernetes' }, - }, - ], + label: 'Accounts', + slug: 'aws/team-workspaces/accounts', + }, + { + label: 'Workspace', + slug: 'aws/team-workspaces/workspaces', + }, + { + label: 'Users and Licenses', + slug: 'aws/team-workspaces/managing-users-licenses', }, { label: 'Single Sign-On', + collapsed: true, items: [ - { autogenerate: { directory: '/aws/enterprise/sso' } }, + { + autogenerate: { directory: '/aws/team-workspaces/sso' }, + }, ], }, { - label: 'Enterprise Image', - slug: 'aws/enterprise/enterprise-image', + label: 'Stack Insights', + slug: 'aws/team-workspaces/stack-insights', }, ], }, diff --git a/public/_redirects b/public/_redirects index d055d7f26..c97596e2b 100644 --- a/public/_redirects +++ b/public/_redirects @@ -2,7 +2,7 @@ /references/coverage/coverage_elb/ /aws/services/elb 301 /user-guide/aws/batch/ /aws/services/batch 301 /references/coverage/coverage_scheduler/ /aws/services/scheduler 301 -/user-guide/extensions/ /aws/capabilities/extensions 301 +/user-guide/extensions/ /aws/integrations/extensions 301 /tutorials/s3-static-website-terraform/ /aws/tutorials/s3-static-website-terraform 301 /references/coverage/coverage_sso-admin/ /aws/services/sso-admin/ 301 /references/coverage/coverage_rds-data/ /aws/services/rds 301 @@ -19,13 +19,13 @@ /references/coverage/coverage_xray/ /aws/services/xray 301 /references/coverage/coverage_cognito-identity/ /aws/services/cognito-idp 301 /user-guide/aws/ecs/ /aws/services/ecs 301 -/references/usage-tracking/ /aws/capabilities/config/usage-tracking 301 +/references/usage-tracking/ /aws/configuration/advanced/usage-tracking 301 /user-guide/aws/dms/ /aws/services/dms 301 /references/coverage/coverage_managedblockchain/ /aws/services/managedblockchain 301 /applications/search-application-with-lambda-kinesis-firehose-elasticsearch-s3/ https://github.com/localstack-samples/sample-fuzzy-movie-search-lambda-kinesis-elasticsearch 301 -/references/regions-coverage/ /aws/capabilities/config/regions-coverage/ 301 +/references/regions-coverage/ /aws/configuration/advanced/regions-coverage/ 301 /tutorials/elb-load-balancing/ /aws/tutorials/elb-load-balancing 301 -/references/docker-images/ /aws/capabilities/config/docker-images 301 +/references/docker-images/ /aws/advanced-installation/docker-images 301 /user-guide/aws/eks/ /aws/services/eks 301 /applications/appsync-graphql-apis-for-dynamodb-and-rds-aurora-postgresql/ https://github.com/localstack-samples/sample-appsync-graphql-api 301 /user-guide/aws/cloudfront/ /aws/services/cloudfront 301 @@ -34,8 +34,8 @@ /references/coverage/coverage_s3control/ /aws/services/s3 301 /references/custom-tls-certificates/ /aws/developer-tools/security-testing/custom-tls-certificates 301 /references/coverage/coverage_codecommit/ /aws/services/codecommit 301 -/user-guide/localstack-enterprise/enterprise-image/ /aws/enterprise/enterprise-image 301 -/user-guide/tools/testing-utils/ /aws/capabilities/testing-utils 301 +/user-guide/localstack-enterprise/enterprise-image/ /aws/advanced-installation/enterprise-image 301 +/user-guide/tools/testing-utils/ /aws/integrations/localstack-sdks/testing-utils 301 /user-guide/aws/codedeploy/ /aws/services/codedeploy 301 /references/coverage/coverage_serverlessrepo/ /aws/services/serverlessrepo 301 /user-guide/aws/resource_groups/ /aws/services/resource_groups 301 @@ -47,25 +47,25 @@ /user-guide/integrations/sdks/python/ /aws/connecting/aws-sdks/net/python 301 /user-guide/integrations/crossplane/ /aws/connecting/infrastructure-as-code/crossplane 301 /references/coverage/coverage_elbv2/ /aws/services/elb 301 -/user-guide/integrations/openshift/ /aws/integrations/containers/openshift 301 +/user-guide/integrations/openshift/ /aws/advanced-installation/kubernetes/openshift 301 /user-guide/aws/memorydb/ /aws/services/memorydb 301 -/user-guide/integrations/devcontainers/ /aws/integrations/containers/devcontainers 301 +/user-guide/integrations/devcontainers/ /aws/advanced-installation/devcontainers 301 /references/coverage/coverage_secretsmanager/ /aws/services/secretsmanager 301 -/user-guide/ci/travis-ci/ /aws/integrations/continuous-integration/travis-ci 301 +/user-guide/ci/travis-ci/ /aws/ci-pipelines/travis-ci 301 /applications/serverless-microservices-with-amazon-api-gateway-dynamodb-sqs-and-lambda/ https://github.com/localstack-samples/sample-microservices-apigateway-lambda-dynamodb-sqs 301 /user-guide/lambda-tools/ /aws/developer-tools/lambda-tools 301 /user-guide/integrations/aws-cdk/ /aws/connecting/infrastructure-as-code/aws-cdk 301 -/references/podman/ /aws/capabilities/config/podman 301 +/references/podman/ /aws/advanced-installation/podman 301 /references/coverage/coverage_memorydb/ /aws/services/memorydb 301 /user-guide/integrations/former2/ /aws/connecting/infrastructure-as-code/former2 301 -/user-guide/localstack-enterprise/k8s-operator/ /aws/enterprise/k8s-operator 301 +/user-guide/localstack-enterprise/k8s-operator/ /aws/advanced-installation/k8s-operator 301 /user-guide/integrations/aws-cli/ /aws/connecting/aws-cli 301 /references/coverage/coverage_kinesisanalyticsv2/ /aws/services/kinesisanalyticsv2 301 /references/coverage/coverage_amplify/ /aws/services/amplify 301 /user-guide/aws/events/ /aws/services/events 301 /user-guide/aws/pipes/ /aws/services/pipes 301 -/user-guide/ci/circle-ci/ /aws/integrations/continuous-integration/circle-ci 301 -/references/network-troubleshooting/transparent-endpoint-injection/ /aws/capabilities/networking/transparent-endpoint-injection 301 +/user-guide/ci/circle-ci/ /aws/ci-pipelines/circle-ci 301 +/references/network-troubleshooting/transparent-endpoint-injection/ /aws/configuration/networking/transparent-endpoint-injection 301 /references/coverage/coverage_kafka/ /aws/services/kafka 301 /references/coverage/coverage_servicediscovery/ /aws/services/servicediscovery 301 /references/coverage/coverage_apigateway/ /aws/services/apigateway 301 @@ -80,22 +80,22 @@ /user-guide/aws/logs/ /aws/services/logs 301 /academy/localstack-deployment/infra-cloudformation/ https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=K0OgQ5eq588&feature=youtu.be 301 /user-guide/cloud-sandbox/ /aws/developer-tools/cloud-sandbox 301 -/user-guide/localstack-enterprise/ci-analytics/ /aws/enterprise/ 301 -/aws/enterprise/ci-analytics/ /aws/enterprise/ 301 +/user-guide/localstack-enterprise/ci-analytics/ /aws/advanced-installation/ 301 +/aws/advanced-installation/ci-analytics/ /aws/advanced-installation/ 301 /references/changelog/ /aws/changelog 301 -/references/credentials/ /aws/capabilities/config/credentials 301 +/references/credentials/ /aws/connecting/credentials 301 /references/coverage/coverage_elasticbeanstalk/ /aws/services/elasticbeanstalk 301 -/user-guide/web-application/instance-management/ /aws/capabilities/web-app/instance-management 301 +/user-guide/web-application/instance-management/ /aws/connecting/console/instance-management 301 /references/coverage/coverage_qldb/ /aws/services/qldb 301 /academy/localstack-deployment/iam-policy-stream/ https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=TOBLG2Z6xAM&feature=youtu.be 301 -/references/cross-account-access/ /aws/capabilities/config/cross-account-access 301 +/references/cross-account-access/ /aws/configuration/advanced/cross-account-access 301 /tutorials/reproducible-machine-learning-cloud-pods/ /aws/tutorials/reproducible-machine-learning-cloud-pods 301 /references/coverage/coverage_ecs/ /aws/services/ecs 301 /references/coverage/coverage_acm/ /aws/services/acm 301 /references/coverage/coverage_cloudtrail/ /aws/services/cloudtrail 301 /user-guide/aws/ /aws/services/ 301 /references/lambda-provider-v2/ /aws/services/lambda 301 -/user-guide/web-application/ci-keys/ /aws/capabilities/web-app/ci-keys 301 +/user-guide/web-application/ci-keys/ /aws/team-workspaces/ci-keys 301 /academy/localstack-deployment/ls-integrations/ https://www.youtube.com/watch?v=YV0Zs6UNI9I&feature=youtu.be 301 /references/coverage/coverage_appconfigdata/ /aws/services/appconfig 301 /applications/serverless-image-resizer-with-aws-lambda-s3-sns-and-ses/ https://github.com/localstack-samples/sample-serverless-image-resizer-s3-lambda 301 @@ -104,26 +104,26 @@ /user-guide/aws/bedrock/ /aws/services/bedrock 301 /user-guide/aws/sts/ /aws/services/sts 301 /user-guide/aws/docdb/ /aws/services/docdb 301 -/user-guide/tools/transparent-endpoint-injection/ /aws/capabilities/networking/transparent-endpoint-injection 301 +/user-guide/tools/transparent-endpoint-injection/ /aws/configuration/networking/transparent-endpoint-injection 301 /user-guide/aws/account/ /aws/services/account 301 /references/coverage/coverage_efs/ /aws/services/efs 301 -/user-guide/localstack-enterprise/ /aws/enterprise/ 301 +/user-guide/localstack-enterprise/ /aws/advanced-installation/ 301 /getting-started/auth-token/ /aws/getting-started/auth-token 301 -/user-guide/localstack-enterprise/enterprise-support/ /aws/enterprise/enterprise-support 301 +/user-guide/localstack-enterprise/enterprise-support/ /aws/advanced-installation/enterprise-support 301 /user-guide/aws/support/ /aws/services/support 301 /references/coverage/coverage_resourcegroupstaggingapi/ /aws/services/resource-groups 301 -/references/external-ports/ /aws/capabilities/networking/external-port-range 301 +/references/external-ports/ /aws/configuration/networking/external-port-range 301 /references/coverage/coverage_ce/ /aws/services/ce 301 -/user-guide/extensions/getting-started/ /aws/capabilities/extensions/getting-started 301 +/user-guide/extensions/getting-started/ /aws/integrations/extensions/getting-started 301 /references/coverage/coverage_codeartifact/ /aws/services/codeartifact/ 301 /user-guide/integrations/sdks/ /aws/connecting/aws-sdks/ 301 -/user-guide/localstack-enterprise/single-sign-on/azure-ad/ /aws/enterprise/sso/azure-ad 301 -/user-guide/tools/localstack-desktop/ /aws/capabilities/web-app/localstack-desktop 301 +/user-guide/localstack-enterprise/single-sign-on/azure-ad/ /aws/team-workspaces/sso/azure-ad 301 +/user-guide/tools/localstack-desktop/ /aws/developer-tools/running-localstack/localstack-desktop 301 /references/coverage/coverage_es/ /aws/services/es 301 /user-guide/integrations/sdks/javascript/ /aws/connecting/aws-sdks/net/javascript 301 /references/coverage/coverage_iam/ /aws/services/iam 301 -/user-guide/tools/localsurf/ /aws/capabilities/localsurf 301 -/user-guide/extensions/extensions-library/ /aws/capabilities/extensions/extensions-library 301 +/user-guide/tools/localsurf/ /aws/configuration/networking/localsurf 301 +/user-guide/extensions/extensions-library/ /aws/integrations/extensions/extensions-library 301 /tutorials/ecs-ecr-container-app/ /aws/tutorials/ecs-ecr-container-app 301 /references/coverage/coverage_elastictranscoder/ /aws/services/elastictranscoder 301 /user-guide/aws/feature-coverage/ /aws/services/ 301 @@ -150,10 +150,10 @@ /user-guide/aws/msk/ /aws/services/kafka 301 /user-guide/state-management/ /aws/developer-tools/snapshots/ 301 /user-guide/integrations/copilot/ /aws/connecting/infrastructure-as-code/ 301 -/user-guide/integrations/eksctl/ /aws/integrations/containers/eksctl/ 301 +/user-guide/integrations/eksctl/ /aws/advanced-installation/kubernetes/eksctl/ 301 /getting-started/faq/ /aws/getting-started/faq 301 /user-guide/aws/elb/ /aws/services/elb 301 -/user-guide/integrations/kubernetes/ /aws/integrations/containers/kubernetes/ 301 +/user-guide/integrations/kubernetes/ /aws/advanced-installation/kubernetes/ 301 /user-guide/aws/lakeformation/ /aws/services/lakeformation 301 /developer-hub/ /aws/sample-apps 301 /references/coverage/coverage_firehose/ /aws/services/firehose 301 @@ -165,7 +165,7 @@ /references/coverage/coverage_sqs/ /aws/services/sqs 301 /user-guide/aws/appsync/ /aws/services/appsync 301 /tutorials/schema-evolution-glue-msk/ /aws/tutorials/schema-evolution-glue-msk 301 -/user-guide/ci/bitbucket/ /aws/integrations/continuous-integration/bitbucket 301 +/user-guide/ci/bitbucket/ /aws/ci-pipelines/bitbucket 301 /contributing/ https://github.com/localstack/localstack/blob/main/docs/CONTRIBUTING.md 301 /user-guide/aws/scheduler/ /aws/services/scheduler 301 /user-guide/integrations/quarkus/ /aws/integrations/app-frameworks/quarkus 301 @@ -181,19 +181,19 @@ /user-guide/integrations/sdks/java/ /aws/connecting/aws-sdks/net/java 301 /references/coverage/coverage_logs/ /aws/services/logs 301 /references/coverage/coverage_mediastore/ /aws/services/mediastore 301 -/user-guide/integrations/kafka/ /aws/integrations/messaging/selfmanaged-kafka-cluster/ 301 +/user-guide/integrations/kafka/ /aws/integrations/app-frameworks/selfmanaged-kafka-cluster/ 301 /user-guide/chaos-engineering/fault-injection-service/ /aws/developer-tools/chaos-engineering/fault-injection-service 301 -/references/logging/ /aws/capabilities/config/logging 301 +/references/logging/ /aws/configuration/logging 301 /tutorials/java-notification-app/ /aws/tutorials/java-notification-app 301 /applications/serverless-transcription-application-using-transcribe-s3-lambda-sqs-and-ses/ https://github.com/localstack-samples/sample-serverless-transcribe 301 /user-guide/aws/route53resolver/ /aws/services/route53resolver 301 /references/coverage/coverage_wafv2/ /aws/services/waf 301 /user-guide/integrations/sdks/cpp/ /aws/connecting/aws-sdks/net/cpp 301 /user-guide/integrations/testcontainers/ /aws/integrations/testing/testcontainers 301 -/references/internal-endpoints/ /aws/capabilities/networking/internal-endpoints 301 +/references/internal-endpoints/ /aws/configuration/networking/internal-endpoints 301 /tutorials/lambda-ecr-container-images/ /aws/tutorials/lambda-ecr-container-images 301 /user-guide/aws/fis/ /aws/services/fis 301 -/user-guide/tools/localstack-docker-extension/ /aws/capabilities/localstack-docker-extension/ 301 +/user-guide/tools/localstack-docker-extension/ /aws/advanced-installation/localstack-docker-extension/ 301 /user-guide/aws/cloudformation/ /aws/services/cloudformation 301 /tutorials/route-53-failover/ /aws/tutorials/route-53-failover 301 /user-guide/web-application/resource-browser/ /aws/connecting/console/resource-browser 301 @@ -203,38 +203,38 @@ /references/coverage/coverage_redshift/ /aws/services/redshift 301 /user-guide/integrations/lambdatest-hyperexecute/ /aws/integrations/testing/lambdatest-hyperexecute/ 301 /applications/ /aws/sample-apps/ 301 -/user-guide/web-application/users-and-licenses/ /aws/capabilities/web-app/users-and-licenses 301 -/user-guide/tools/localstack-sdk/ /aws/capabilities/localstack-sdks/ 301 +/user-guide/web-application/users-and-licenses/ /aws/team-workspaces/users-and-licenses 301 +/user-guide/tools/localstack-sdk/ /aws/integrations/localstack-sdks/ 301 /references/coverage/coverage_apigatewaymanagementapi/ /aws/services/apigateway 301 /references/coverage/coverage_transfer/ /aws/services/transfer 301 /references/coverage/coverage_codeconnections/ /aws/services/codeconnections/ 301 /user-guide/aws/athena/ /aws/services/athena 301 -/user-guide/extensions/official-extensions/ /aws/capabilities/extensions/official-extensions 301 +/user-guide/extensions/official-extensions/ /aws/integrations/extensions/official-extensions 301 /user-guide/aws/textract/ /aws/services/textract 301 /tutorials/iam-policy-stream/ /aws/tutorials/iam-policy-stream 301 /references/coverage/coverage_ses/ /aws/services/ses 301 /tutorials/gitlab_ci_testcontainers/ /aws/tutorials/gitlab-ci-testcontainers 301 /user-guide/integrations/aws-sam/ /aws/connecting/infrastructure-as-code/aws-sam 301 /user-guide/aws/firehose/ /aws/services/firehose 301 -/user-guide/web-application/ /aws/capabilities/web-app/ 301 +/user-guide/web-application/ /aws/team-workspaces/ 301 /references/coverage/coverage_sagemaker/ /aws/services/sagemaker 301 -/references/arm64-support/ /aws/capabilities/config/arm64-support/ 301 +/references/arm64-support/ /aws/configuration/advanced/arm64-support/ 301 /user-guide/aws/shield/ /aws/services/shield 301 /user-guide/integrations/terraform/ /aws/connecting/infrastructure-as-code/terraform 301 /user-guide/aws/es/ /aws/services/es 301 /references/coverage/coverage_dms/ /aws/services/dms 301 -/user-guide/extensions/developing-extensions/ /aws/capabilities/extensions/developing-extensions 301 +/user-guide/extensions/developing-extensions/ /aws/integrations/extensions/developing-extensions 301 /user-guide/security-testing/explainable-iam/ /aws/developer-tools/security-testing/explainable-iam 301 /user-guide/aws/ram/ /aws/services/ram 301 /references/coverage/coverage_ssm/ /aws/services/ssm 301 -/references/network-troubleshooting/created-resources/ /aws/capabilities/networking/created-resources 301 +/references/network-troubleshooting/created-resources/ /aws/configuration/networking/created-resources 301 /user-guide/aws/swf/ /aws/services/swf 301 -/user-guide/ci/github-actions/ /aws/integrations/continuous-integration/github-actions 301 +/user-guide/ci/github-actions/ /aws/ci-pipelines/github-actions 301 /user-guide/aws/serverlessrepo/ /aws/services/serverlessrepo 301 /user-guide/aws/sqs/ /aws/services/sqs 301 /references/coverage/coverage_ram/ /aws/services/ram 301 /user-guide/aws/secretsmanager/ /aws/services/secretsmanager 301 -/user-guide/web-application/stack-insights/ /aws/capabilities/web-app/stack-insights 301 +/user-guide/web-application/stack-insights/ /aws/team-workspaces/stack-insights 301 /user-guide/aws/autoscaling/ /aws/services/autoscaling 301 /references/coverage/coverage_opensearch/ /aws/services/opensearch 301 /academy/localstack-101/cloud-pods/ https://www.youtube.com/watch?list=PLTew28KOwGxPqbkFiW518eeIfiV495bm0&v=InqTdSvxuag&feature=youtu.be 301 @@ -243,7 +243,7 @@ /user-guide/aws/elasticbeanstalk/ /aws/services/elasticbeanstalk 301 /references/coverage/coverage_mediaconvert/ /aws/services/mediaconvert 301 /user-guide/state-management/launchpad/ /aws/developer-tools/snapshots/launchpad 301 -/user-guide/ci/codebuild/ /aws/integrations/continuous-integration/codebuild 301 +/user-guide/ci/codebuild/ /aws/ci-pipelines/codebuild 301 /user-guide/aws/iot-data/ /aws/services/iot-data 301 /references/coverage/coverage_textract/ /aws/services/textract 301 /references/coverage/coverage_codebuild/ /aws/services/codebuild 301 @@ -269,30 +269,30 @@ /academy/localstack-deployment/course-overview/ https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=XDIat6laW28&feature=youtu.be 301 /references/coverage/coverage_codepipeline/ /aws/services/codepipeline 301 /academy/localstack-deployment/infra-terraform/ https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=lsF3kewOeBU&feature=youtu.be 301 -/references/network-troubleshooting/ /aws/capabilities/networking/ 301 -/user-guide/ci/gitlab-ci/ /aws/integrations/continuous-integration/gitlab-ci 301 +/references/network-troubleshooting/ /aws/configuration/networking/ 301 +/user-guide/ci/gitlab-ci/ /aws/ci-pipelines/gitlab-ci 301 /user-guide/aws/kms/ /aws/services/kms 301 /references/coverage/coverage_stepfunctions/ /aws/services/stepfunctions 301 /references/coverage/coverage_sesv2/ /aws/services/ses 301 /references/coverage/coverage_events/ /aws/services/events 301 /references/coverage/coverage_timestream-query/ /aws/services/timestream-query 301 -/references/network-troubleshooting/endpoint-url/ /aws/capabilities/networking/endpoint-url 301 +/references/network-troubleshooting/endpoint-url/ /aws/configuration/networking/endpoint-url 301 /tutorials/ephemeral-application-previews/ /aws/tutorials/ephemeral-application-previews 301 -/user-guide/web-application/accounts/ /aws/capabilities/web-app/accounts 301 +/user-guide/web-application/accounts/ /aws/team-workspaces/accounts 301 /references/coverage/coverage_appsync/ /aws/services/appsync 301 /references/coverage/coverage_ecr/ /aws/services/ecr 301 /academy/localstack-deployment/ https://www.youtube.com/playlist?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&si=R-Ed-JQKOxXP473O 301 /references/coverage/coverage_application-autoscaling/ /aws/services/application-autoscaling 301 /user-guide/lambda-tools/debugging/ /aws/developer-tools/lambda-tools/debugging 301 /references/coverage/coverage_codestar-connections/ /aws/services/codeconnections/ 301 -/user-guide/integrations/rancher-desktop/ /aws/integrations/containers/rancher-desktop 301 +/user-guide/integrations/rancher-desktop/ /aws/advanced-installation/rancher-desktop 301 /user-guide/integrations/sdks/ruby/ /aws/connecting/aws-sdks/net/ruby 301 /user-guide/aws/mwaa/ /aws/services/mwaa 301 /academy/localstack-deployment/deploy-app-ls/ https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=qIB79b-iw2U&feature=youtu.be 301 /user-guide/aws/organizations/ /aws/services/organizations 301 /academy/localstack-deployment/github-action-ls/ https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=XNh8aSaT9v0&feature=youtu.be 301 /user-guide/aws/sagemaker/ /aws/services/sagemaker 301 -/references/configuration/ /aws/capabilities/config/configuration 301 +/references/configuration/ /aws/configuration/configuration-options 301 /user-guide/chaos-engineering/chaos-api/ /aws/developer-tools/chaos-engineering/chaos-api 301 /user-guide/aws/glacier/ /aws/services/glacier 301 /references/coverage/coverage_qldb-session/ /aws/services/qldb 301 @@ -300,7 +300,7 @@ /user-guide/aws/cloudtrail/ /aws/services/cloudtrail 301 /references/coverage/coverage_s3/ /aws/services/s3 301 /user-guide/aws/emr/ /aws/services/emr 301 -/user-guide/tools/dns-server/ /aws/capabilities/dns-server 301 +/user-guide/tools/dns-server/ /aws/configuration/networking/dns-server 301 /user-guide/chaos-engineering/chaos-application-dashboard/ /aws/developer-tools/chaos-engineering/chaos-application-dashboard 301 /references/coverage/coverage_route53/ /aws/services/route53 301 /references/coverage/coverage_dynamodbstreams/ /aws/services/dynamodbstreams 301 @@ -308,7 +308,7 @@ /user-guide/aws/ec2/ /aws/services/ec2 301 /user-guide/cloud-sandbox/application-previews/ /aws/developer-tools/cloud-sandbox/app-preview/ 301 /user-guide/integrations/spring-cloud-function/ /aws/integrations/app-frameworks/spring-cloud-function 301 -/references/multi-account-setups/ /aws/capabilities/config/multi-account-setups/ 301 +/references/multi-account-setups/ /aws/configuration/advanced/multi-account-setups/ 301 /user-guide/aws/elementalmediaconvert/ /aws/services/mediaconvert 301 /references/coverage/coverage_shield/ /aws/services/shield 301 /user-guide/aws/dynamodb/ /aws/services/dynamodb 301 @@ -323,7 +323,7 @@ /references/coverage/coverage_iot/ /aws/services/iot 301 /getting-started/installation/ /aws/getting-started/installation 301 /user-guide/integrations/architect/ /aws/integrations/app-frameworks/architect/ 301 -/user-guide/integrations/gitpod/ /aws/integrations/containers/gitpod/ 301 +/user-guide/integrations/gitpod/ /aws/advanced-installation/gitpod/ 301 /user-guide/aws/managedblockchain/ /aws/services/managedblockchain 301 /applications/query-data-in-s3-bucket-with-amazon-athena-glue-catalog-cloudformation/ https://github.com/localstack-samples/sample-query-data-s3-athena-glue 301 /academy/localstack-101/web-app-resource-browser/ https://www.youtube.com/watch?list=PLTew28KOwGxPqbkFiW518eeIfiV495bm0&v=SoXtngYp-8k&feature=youtu.be 301 @@ -333,12 +333,12 @@ /references/coverage/coverage_sagemaker-runtime/ /aws/services/sagemaker 301 /applications/messaging-processing-application-with-sqs-dynamodb-and-fargate/ https://github.com/localstack-samples/sample-cdk-sqs-fargate-dynamodb 301 /user-guide/aws/mq/ /aws/services/mq 301 -/user-guide/localstack-enterprise/kubernetes-executor/ /aws/enterprise/kubernetes-executor 301 +/user-guide/localstack-enterprise/kubernetes-executor/ /aws/advanced-installation/kubernetes-executor 301 /user-guide/aws/iot/ /aws/services/iot 301 /user-guide/aws/backup/ /aws/services/backup 301 /references/coverage/coverage_organizations/ /aws/services/organizations 301 /user-guide/aws/kinesisanalytics/ /aws/services/kinesisanalytics 301 -/user-guide/localstack-enterprise/single-sign-on/ /aws/enterprise/sso 301 +/user-guide/localstack-enterprise/single-sign-on/ /aws/team-workspaces/sso 301 /user-guide/aws/redshift/ /aws/services/redshift 301 /references/coverage/coverage_verifiedpermissions/ /aws/services/verifiedpermissions 301 /academy/localstack-101/full-project-demo/ https://www.youtube.com/watch?list=PLTew28KOwGxPqbkFiW518eeIfiV495bm0&v=cQxg3Dnteyc&feature=youtu.be 301 @@ -364,12 +364,12 @@ /tutorials/using-terraform-with-testcontainers-and-localstack/ /aws/tutorials/using-terraform-with-testcontainers-and-localstack 301 /references/coverage/coverage_cloudfront/ /aws/services/cloudfront 301 /user-guide/tools/localstack-sdk/java/ /aws/user-guide/tools/localstack-sdk/java 301 -/references/network-troubleshooting/readme/ /aws/capabilities/networking/ 301 +/references/network-troubleshooting/readme/ /aws/configuration/networking/ 301 /user-guide/aws/codecommit/ /aws/services/codecommit 301 /references/coverage/coverage_swf/ /aws/services/swf 301 /user-guide/integrations/sdks/go/ /aws/connecting/aws-sdks/go 301 /persistence/ /aws/developer-tools/snapshots/persistence/ 301 -/references/init-hooks/ /aws/capabilities/config/initialization-hooks/ 301 +/references/init-hooks/ /aws/configuration/advanced/initialization-hooks/ 301 /references/coverage/coverage_support/ /aws/services/support 301 /user-guide/ /aws/ 301 /user-guide/aws/qldb/ /aws/services/qldb 301 @@ -392,24 +392,24 @@ /references/api-key/ /aws/getting-started/auth-token/#how-do-i-activate-older-versions-of-localstack-before-v30 301 /references/coverage/coverage_eks/ /aws/services/eks 301 /references/coverage/coverage_cognito-idp/ /aws/services/cognito-idp 301 -/user-guide/web-application/workspace/ /aws/capabilities/web-app/workspace 301 +/user-guide/web-application/workspace/ /aws/team-workspaces/workspace 301 /references/coverage/coverage_cloudcontrol/ /aws/services/cloudcontrol 301 /tutorials/replicate-aws-resources-localstack-extension/ /aws/tutorials/replicate-aws-resources-localstack-extension 301 -/user-guide/tools/localstack-sdk/python/ /aws/capabilities/localstack-sdks/python 301 +/user-guide/tools/localstack-sdk/python/ /aws/integrations/localstack-sdks/python 301 /user-guide/lambda-tools/hot-reloading/ /aws/developer-tools/lambda-tools/hot-reloading 301 /getting-started/quickstart/ /aws/getting-started/quickstart 301 /overview/ /aws 301 /user-guide/aws/glue/ /aws/services/glue 301 /getting-started/ /aws/getting-started 301 -/user-guide/extensions/managing-extensions/ /aws/capabilities/extensions/managing-extensions 301 -/references/filesystem/ /aws/capabilities/config/filesystem/ 301 -/references/ /aws/capabilities/config/ 301 +/user-guide/extensions/managing-extensions/ /aws/integrations/extensions/managing-extensions 301 +/references/filesystem/ /aws/configuration/advanced/filesystem/ 301 +/references/ /aws/configuration/ 301 /academy/localstack-101/getting-started/ https://www.youtube.com/watch?v=CzX4mfiS058&feature=youtu.be 301 /legal/third-party-software-tools /aws/legal/third-party-software-tools 301 /references/coverage/coverage_elb /aws/services/elb 301 /user-guide/aws/batch /aws/services/batch 301 /references/coverage/coverage_scheduler /aws/services/scheduler 301 -/user-guide/extensions /aws/capabilities/extensions 301 +/user-guide/extensions /aws/integrations/extensions 301 /tutorials/s3-static-website-terraform /aws/tutorials/s3-static-website-terraform 301 /references/coverage/coverage_sso-admin /aws/services/sso-admin/ 301 /references/coverage/coverage_rds-data /aws/services/rds 301 @@ -426,13 +426,13 @@ /references/coverage/coverage_xray /aws/services/xray 301 /references/coverage/coverage_cognito-identity /aws/services/cognito-idp 301 /user-guide/aws/ecs /aws/services/ecs 301 -/references/usage-tracking /aws/capabilities/config/usage-tracking 301 +/references/usage-tracking /aws/configuration/advanced/usage-tracking 301 /user-guide/aws/dms /aws/services/dms 301 /references/coverage/coverage_managedblockchain /aws/services/managedblockchain 301 /applications/search-application-with-lambda-kinesis-firehose-elasticsearch-s3 https://github.com/localstack-samples/sample-fuzzy-movie-search-lambda-kinesis-elasticsearch 301 -/references/regions-coverage /aws/capabilities/config/regions-coverage/ 301 +/references/regions-coverage /aws/configuration/advanced/regions-coverage/ 301 /tutorials/elb-load-balancing /aws/tutorials/elb-load-balancing 301 -/references/docker-images /aws/capabilities/config/docker-images 301 +/references/docker-images /aws/advanced-installation/docker-images 301 /user-guide/aws/eks /aws/services/eks 301 /applications/appsync-graphql-apis-for-dynamodb-and-rds-aurora-postgresql https://github.com/localstack-samples/sample-appsync-graphql-api 301 /user-guide/aws/cloudfront /aws/services/cloudfront 301 @@ -441,8 +441,8 @@ /references/coverage/coverage_s3control /aws/services/s3 301 /references/custom-tls-certificates /aws/developer-tools/security-testing/custom-tls-certificates 301 /references/coverage/coverage_codecommit /aws/services/codecommit 301 -/user-guide/localstack-enterprise/enterprise-image /aws/enterprise/enterprise-image 301 -/user-guide/tools/testing-utils /aws/capabilities/testing-utils 301 +/user-guide/localstack-enterprise/enterprise-image /aws/advanced-installation/enterprise-image 301 +/user-guide/tools/testing-utils /aws/integrations/localstack-sdks/testing-utils 301 /user-guide/aws/codedeploy /aws/services/codedeploy 301 /references/coverage/coverage_serverlessrepo /aws/services/serverlessrepo 301 /user-guide/aws/resource_groups /aws/services/resource_groups 301 @@ -454,25 +454,25 @@ /user-guide/integrations/sdks/python /aws/connecting/aws-sdks/net/python 301 /user-guide/integrations/crossplane /aws/connecting/infrastructure-as-code/crossplane 301 /references/coverage/coverage_elbv2 /aws/services/elb 301 -/user-guide/integrations/openshift /aws/integrations/containers/openshift 301 +/user-guide/integrations/openshift /aws/advanced-installation/kubernetes/openshift 301 /user-guide/aws/memorydb /aws/services/memorydb 301 -/user-guide/integrations/devcontainers /aws/integrations/containers/devcontainers 301 +/user-guide/integrations/devcontainers /aws/advanced-installation/devcontainers 301 /references/coverage/coverage_secretsmanager /aws/services/secretsmanager 301 -/user-guide/ci/travis-ci /aws/integrations/continuous-integration/travis-ci 301 +/user-guide/ci/travis-ci /aws/ci-pipelines/travis-ci 301 /applications/serverless-microservices-with-amazon-api-gateway-dynamodb-sqs-and-lambda https://github.com/localstack-samples/sample-microservices-apigateway-lambda-dynamodb-sqs 301 /user-guide/lambda-tools /aws/developer-tools/lambda-tools 301 /user-guide/integrations/aws-cdk /aws/connecting/infrastructure-as-code/aws-cdk 301 -/references/podman /aws/capabilities/config/podman 301 +/references/podman /aws/advanced-installation/podman 301 /references/coverage/coverage_memorydb /aws/services/memorydb 301 /user-guide/integrations/former2 /aws/connecting/infrastructure-as-code/former2 301 -/user-guide/localstack-enterprise/k8s-operator /aws/enterprise/k8s-operator 301 +/user-guide/localstack-enterprise/k8s-operator /aws/advanced-installation/k8s-operator 301 /user-guide/integrations/aws-cli /aws/connecting/aws-cli 301 /references/coverage/coverage_kinesisanalyticsv2 /aws/services/kinesisanalyticsv2 301 /references/coverage/coverage_amplify /aws/services/amplify 301 /user-guide/aws/events /aws/services/events 301 /user-guide/aws/pipes /aws/services/pipes 301 -/user-guide/ci/circle-ci /aws/integrations/continuous-integration/circle-ci 301 -/references/network-troubleshooting/transparent-endpoint-injection /aws/capabilities/networking/transparent-endpoint-injection 301 +/user-guide/ci/circle-ci /aws/ci-pipelines/circle-ci 301 +/references/network-troubleshooting/transparent-endpoint-injection /aws/configuration/networking/transparent-endpoint-injection 301 /references/coverage/coverage_kafka /aws/services/kafka 301 /references/coverage/coverage_servicediscovery /aws/services/servicediscovery 301 /references/coverage/coverage_apigateway /aws/services/apigateway 301 @@ -487,22 +487,22 @@ /user-guide/aws/logs /aws/services/logs 301 /academy/localstack-deployment/infra-cloudformation https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=K0OgQ5eq588&feature=youtu.be 301 /user-guide/cloud-sandbox /aws/developer-tools/cloud-sandbox 301 -/user-guide/localstack-enterprise/ci-analytics /aws/enterprise/ 301 -/aws/enterprise/ci-analytics /aws/enterprise/ 301 +/user-guide/localstack-enterprise/ci-analytics /aws/advanced-installation/ 301 +/aws/advanced-installation/ci-analytics /aws/advanced-installation/ 301 /references/changelog /aws/changelog 301 -/references/credentials /aws/capabilities/config/credentials 301 +/references/credentials /aws/connecting/credentials 301 /references/coverage/coverage_elasticbeanstalk /aws/services/elasticbeanstalk 301 -/user-guide/web-application/instance-management /aws/capabilities/web-app/instance-management 301 +/user-guide/web-application/instance-management /aws/connecting/console/instance-management 301 /references/coverage/coverage_qldb /aws/services/qldb 301 /academy/localstack-deployment/iam-policy-stream https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=TOBLG2Z6xAM&feature=youtu.be 301 -/references/cross-account-access /aws/capabilities/config/cross-account-access 301 +/references/cross-account-access /aws/configuration/advanced/cross-account-access 301 /tutorials/reproducible-machine-learning-cloud-pods /aws/tutorials/reproducible-machine-learning-cloud-pods 301 /references/coverage/coverage_ecs /aws/services/ecs 301 /references/coverage/coverage_acm /aws/services/acm 301 /references/coverage/coverage_cloudtrail /aws/services/cloudtrail 301 /user-guide/aws /aws/services/ 301 /references/lambda-provider-v2 /aws/services/lambda 301 -/user-guide/web-application/ci-keys /aws/capabilities/web-app/ci-keys 301 +/user-guide/web-application/ci-keys /aws/team-workspaces/ci-keys 301 /academy/localstack-deployment/ls-integrations https://www.youtube.com/watch?v=YV0Zs6UNI9I&feature=youtu.be 301 /references/coverage/coverage_appconfigdata /aws/services/appconfig 301 /applications/serverless-image-resizer-with-aws-lambda-s3-sns-and-ses https://github.com/localstack-samples/sample-serverless-image-resizer-s3-lambda 301 @@ -511,26 +511,26 @@ /user-guide/aws/bedrock /aws/services/bedrock 301 /user-guide/aws/sts /aws/services/sts 301 /user-guide/aws/docdb /aws/services/docdb 301 -/user-guide/tools/transparent-endpoint-injection /aws/capabilities/networking/transparent-endpoint-injection 301 +/user-guide/tools/transparent-endpoint-injection /aws/configuration/networking/transparent-endpoint-injection 301 /user-guide/aws/account /aws/services/account 301 /references/coverage/coverage_efs /aws/services/efs 301 -/user-guide/localstack-enterprise /aws/enterprise/ 301 +/user-guide/localstack-enterprise /aws/advanced-installation/ 301 /getting-started/auth-token /aws/getting-started/auth-token 301 -/user-guide/localstack-enterprise/enterprise-support /aws/enterprise/enterprise-support 301 +/user-guide/localstack-enterprise/enterprise-support /aws/advanced-installation/enterprise-support 301 /user-guide/aws/support /aws/services/support 301 /references/coverage/coverage_resourcegroupstaggingapi /aws/services/resource-groups 301 -/references/external-ports /aws/capabilities/networking/external-port-range 301 +/references/external-ports /aws/configuration/networking/external-port-range 301 /references/coverage/coverage_ce /aws/services/ce 301 -/user-guide/extensions/getting-started /aws/capabilities/extensions/getting-started 301 +/user-guide/extensions/getting-started /aws/integrations/extensions/getting-started 301 /references/coverage/coverage_codeartifact /aws/services/codeartifact/ 301 /user-guide/integrations/sdks /aws/connecting/aws-sdks/ 301 -/user-guide/localstack-enterprise/single-sign-on/azure-ad /aws/enterprise/sso/azure-ad 301 -/user-guide/tools/localstack-desktop /aws/capabilities/web-app/localstack-desktop 301 +/user-guide/localstack-enterprise/single-sign-on/azure-ad /aws/team-workspaces/sso/azure-ad 301 +/user-guide/tools/localstack-desktop /aws/developer-tools/running-localstack/localstack-desktop 301 /references/coverage/coverage_es /aws/services/es 301 /user-guide/integrations/sdks/javascript /aws/connecting/aws-sdks/net/javascript 301 /references/coverage/coverage_iam /aws/services/iam 301 -/user-guide/tools/localsurf /aws/capabilities/localsurf 301 -/user-guide/extensions/extensions-library /aws/capabilities/extensions/extensions-library 301 +/user-guide/tools/localsurf /aws/configuration/networking/localsurf 301 +/user-guide/extensions/extensions-library /aws/integrations/extensions/extensions-library 301 /tutorials/ecs-ecr-container-app /aws/tutorials/ecs-ecr-container-app 301 /references/coverage/coverage_elastictranscoder /aws/services/elastictranscoder 301 /user-guide/aws/feature-coverage /aws/services/ 301 @@ -557,10 +557,10 @@ /user-guide/aws/msk /aws/services/kafka 301 /user-guide/state-management /aws/developer-tools/snapshots/ 301 /user-guide/integrations/copilot /aws/connecting/infrastructure-as-code/ 301 -/user-guide/integrations/eksctl /aws/integrations/containers/eksctl/ 301 +/user-guide/integrations/eksctl /aws/advanced-installation/kubernetes/eksctl/ 301 /getting-started/faq /aws/getting-started/faq 301 /user-guide/aws/elb /aws/services/elb 301 -/user-guide/integrations/kubernetes /aws/integrations/containers/kubernetes/ 301 +/user-guide/integrations/kubernetes /aws/advanced-installation/kubernetes/ 301 /user-guide/aws/lakeformation /aws/services/lakeformation 301 /developer-hub /aws/sample-apps 301 /references/coverage/coverage_firehose /aws/services/firehose 301 @@ -572,7 +572,7 @@ /references/coverage/coverage_sqs /aws/services/sqs 301 /user-guide/aws/appsync /aws/services/appsync 301 /tutorials/schema-evolution-glue-msk /aws/tutorials/schema-evolution-glue-msk 301 -/user-guide/ci/bitbucket /aws/integrations/continuous-integration/bitbucket 301 +/user-guide/ci/bitbucket /aws/ci-pipelines/bitbucket 301 /contributing https://github.com/localstack/localstack/blob/master/docs/CONTRIBUTING.md 301 /user-guide/aws/scheduler /aws/services/scheduler 301 /user-guide/integrations/quarkus /aws/integrations/app-frameworks/quarkus 301 @@ -588,19 +588,19 @@ /user-guide/integrations/sdks/java /aws/connecting/aws-sdks/net/java 301 /references/coverage/coverage_logs /aws/services/logs 301 /references/coverage/coverage_mediastore /aws/services/mediastore 301 -/user-guide/integrations/kafka /aws/integrations/messaging/selfmanaged-kafka-cluster/ 301 +/user-guide/integrations/kafka /aws/integrations/app-frameworks/selfmanaged-kafka-cluster/ 301 /user-guide/chaos-engineering/fault-injection-service /aws/developer-tools/chaos-engineering/fault-injection-service 301 -/references/logging /aws/capabilities/config/logging 301 +/references/logging /aws/configuration/logging 301 /tutorials/java-notification-app /aws/tutorials/java-notification-app 301 /applications/serverless-transcription-application-using-transcribe-s3-lambda-sqs-and-ses https://github.com/localstack-samples/sample-serverless-transcribe 301 /user-guide/aws/route53resolver /aws/services/route53resolver 301 /references/coverage/coverage_wafv2 /aws/services/waf 301 /user-guide/integrations/sdks/cpp /aws/connecting/aws-sdks/net/cpp 301 /user-guide/integrations/testcontainers /aws/integrations/testing/testcontainers 301 -/references/internal-endpoints /aws/capabilities/networking/internal-endpoints 301 +/references/internal-endpoints /aws/configuration/networking/internal-endpoints 301 /tutorials/lambda-ecr-container-images /aws/tutorials/lambda-ecr-container-images 301 /user-guide/aws/fis /aws/services/fis 301 -/user-guide/tools/localstack-docker-extension /aws/capabilities/localstack-docker-extension/ 301 +/user-guide/tools/localstack-docker-extension /aws/advanced-installation/localstack-docker-extension/ 301 /user-guide/aws/cloudformation /aws/services/cloudformation 301 /tutorials/route-53-failover /aws/tutorials/route-53-failover 301 /user-guide/web-application/resource-browser /aws/connecting/console/resource-browser 301 @@ -610,38 +610,38 @@ /references/coverage/coverage_redshift /aws/services/redshift 301 /user-guide/integrations/lambdatest-hyperexecute /aws/integrations/testing/lambdatest-hyperexecute/ 301 /applications /aws/sample-apps/ 301 -/user-guide/web-application/users-and-licenses /aws/capabilities/web-app/users-and-licenses 301 -/user-guide/tools/localstack-sdk /aws/capabilities/localstack-sdks/ 301 +/user-guide/web-application/users-and-licenses /aws/team-workspaces/users-and-licenses 301 +/user-guide/tools/localstack-sdk /aws/integrations/localstack-sdks/ 301 /references/coverage/coverage_apigatewaymanagementapi /aws/services/apigateway 301 /references/coverage/coverage_transfer /aws/services/transfer 301 /references/coverage/coverage_codeconnections /aws/services/codeconnections/ 301 /user-guide/aws/athena /aws/services/athena 301 -/user-guide/extensions/official-extensions /aws/capabilities/extensions/official-extensions 301 +/user-guide/extensions/official-extensions /aws/integrations/extensions/official-extensions 301 /user-guide/aws/textract /aws/services/textract 301 /tutorials/iam-policy-stream /aws/tutorials/iam-policy-stream 301 /references/coverage/coverage_ses /aws/services/ses 301 /tutorials/gitlab_ci_testcontainers /aws/tutorials/gitlab-ci-testcontainers 301 /user-guide/integrations/aws-sam /aws/connecting/infrastructure-as-code/aws-sam 301 /user-guide/aws/firehose /aws/services/firehose 301 -/user-guide/web-application /aws/capabilities/web-app/ 301 +/user-guide/web-application /aws/team-workspaces/ 301 /references/coverage/coverage_sagemaker /aws/services/sagemaker 301 -/references/arm64-support /aws/capabilities/config/arm64-support/ 301 +/references/arm64-support /aws/configuration/advanced/arm64-support/ 301 /user-guide/aws/shield /aws/services/shield 301 /user-guide/integrations/terraform /aws/connecting/infrastructure-as-code/terraform 301 /user-guide/aws/es /aws/services/es 301 /references/coverage/coverage_dms /aws/services/dms 301 -/user-guide/extensions/developing-extensions /aws/capabilities/extensions/developing-extensions 301 +/user-guide/extensions/developing-extensions /aws/integrations/extensions/developing-extensions 301 /user-guide/security-testing/explainable-iam /aws/developer-tools/security-testing/explainable-iam 301 /user-guide/aws/ram /aws/services/ram 301 /references/coverage/coverage_ssm /aws/services/ssm 301 -/references/network-troubleshooting/created-resources /aws/capabilities/networking/created-resources 301 +/references/network-troubleshooting/created-resources /aws/configuration/networking/created-resources 301 /user-guide/aws/swf /aws/services/swf 301 -/user-guide/ci/github-actions /aws/integrations/continuous-integration/github-actions 301 +/user-guide/ci/github-actions /aws/ci-pipelines/github-actions 301 /user-guide/aws/serverlessrepo /aws/services/serverlessrepo 301 /user-guide/aws/sqs /aws/services/sqs 301 /references/coverage/coverage_ram /aws/services/ram 301 /user-guide/aws/secretsmanager /aws/services/secretsmanager 301 -/user-guide/web-application/stack-insights /aws/capabilities/web-app/stack-insights 301 +/user-guide/web-application/stack-insights /aws/team-workspaces/stack-insights 301 /user-guide/aws/autoscaling /aws/services/autoscaling 301 /references/coverage/coverage_opensearch /aws/services/opensearch 301 /academy/localstack-101/cloud-pods https://www.youtube.com/watch?list=PLTew28KOwGxPqbkFiW518eeIfiV495bm0&v=InqTdSvxuag&feature=youtu.be 301 @@ -650,7 +650,7 @@ /user-guide/aws/elasticbeanstalk /aws/services/elasticbeanstalk 301 /references/coverage/coverage_mediaconvert /aws/services/mediaconvert 301 /user-guide/state-management/launchpad /aws/developer-tools/snapshots/launchpad 301 -/user-guide/ci/codebuild /aws/integrations/continuous-integration/codebuild 301 +/user-guide/ci/codebuild /aws/ci-pipelines/codebuild 301 /user-guide/aws/iot-data /aws/services/iot-data 301 /references/coverage/coverage_textract /aws/services/textract 301 /references/coverage/coverage_codebuild /aws/services/codebuild 301 @@ -676,30 +676,30 @@ /academy/localstack-deployment/course-overview https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=XDIat6laW28&feature=youtu.be 301 /references/coverage/coverage_codepipeline /aws/services/codepipeline 301 /academy/localstack-deployment/infra-terraform https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=lsF3kewOeBU&feature=youtu.be 301 -/references/network-troubleshooting /aws/capabilities/networking/ 301 -/user-guide/ci/gitlab-ci /aws/integrations/continuous-integration/gitlab-ci 301 +/references/network-troubleshooting /aws/configuration/networking/ 301 +/user-guide/ci/gitlab-ci /aws/ci-pipelines/gitlab-ci 301 /user-guide/aws/kms /aws/services/kms 301 /references/coverage/coverage_stepfunctions /aws/services/stepfunctions 301 /references/coverage/coverage_sesv2 /aws/services/ses 301 /references/coverage/coverage_events /aws/services/events 301 /references/coverage/coverage_timestream-query /aws/services/timestream-query 301 -/references/network-troubleshooting/endpoint-url /aws/capabilities/networking/endpoint-url 301 +/references/network-troubleshooting/endpoint-url /aws/configuration/networking/endpoint-url 301 /tutorials/ephemeral-application-previews /aws/tutorials/ephemeral-application-previews 301 -/user-guide/web-application/accounts /aws/capabilities/web-app/accounts 301 +/user-guide/web-application/accounts /aws/team-workspaces/accounts 301 /references/coverage/coverage_appsync /aws/services/appsync 301 /references/coverage/coverage_ecr /aws/services/ecr 301 /academy/localstack-deployment https://www.youtube.com/playlist?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&si=R-Ed-JQKOxXP473O 301 /references/coverage/coverage_application-autoscaling /aws/services/application-autoscaling 301 /user-guide/lambda-tools/debugging /aws/developer-tools/lambda-tools/debugging 301 /references/coverage/coverage_codestar-connections /aws/services/codeconnections/ 301 -/user-guide/integrations/rancher-desktop /aws/integrations/containers/rancher-desktop 301 +/user-guide/integrations/rancher-desktop /aws/advanced-installation/rancher-desktop 301 /user-guide/integrations/sdks/ruby /aws/connecting/aws-sdks/net/ruby 301 /user-guide/aws/mwaa /aws/services/mwaa 301 /academy/localstack-deployment/deploy-app-ls https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=qIB79b-iw2U&feature=youtu.be 301 /user-guide/aws/organizations /aws/services/organizations 301 /academy/localstack-deployment/github-action-ls https://www.youtube.com/watch?list=PLTew28KOwGxPdtdW00WNXZLZnstvRQyTF&v=XNh8aSaT9v0&feature=youtu.be 301 /user-guide/aws/sagemaker /aws/services/sagemaker 301 -/references/configuration /aws/capabilities/config/configuration 301 +/references/configuration /aws/configuration/configuration-options 301 /user-guide/chaos-engineering/chaos-api /aws/developer-tools/chaos-engineering/chaos-api 301 /user-guide/aws/glacier /aws/services/glacier 301 /references/coverage/coverage_qldb-session /aws/services/qldb 301 @@ -707,7 +707,7 @@ /user-guide/aws/cloudtrail /aws/services/cloudtrail 301 /references/coverage/coverage_s3 /aws/services/s3 301 /user-guide/aws/emr /aws/services/emr 301 -/user-guide/tools/dns-server /aws/capabilities/dns-server 301 +/user-guide/tools/dns-server /aws/configuration/networking/dns-server 301 /user-guide/chaos-engineering/chaos-application-dashboard /aws/developer-tools/chaos-engineering/chaos-application-dashboard 301 /references/coverage/coverage_route53 /aws/services/route53 301 /references/coverage/coverage_dynamodbstreams /aws/services/dynamodbstreams 301 @@ -715,7 +715,7 @@ /user-guide/aws/ec2 /aws/services/ec2 301 /user-guide/cloud-sandbox/application-previews /aws/developer-tools/cloud-sandbox/app-preview/ 301 /user-guide/integrations/spring-cloud-function /aws/integrations/app-frameworks/spring-cloud-function 301 -/references/multi-account-setups /aws/capabilities/config/multi-account-setups/ 301 +/references/multi-account-setups /aws/configuration/advanced/multi-account-setups/ 301 /user-guide/aws/elementalmediaconvert /aws/services/mediaconvert 301 /references/coverage/coverage_shield /aws/services/shield 301 /user-guide/aws/dynamodb /aws/services/dynamodb 301 @@ -730,7 +730,7 @@ /references/coverage/coverage_iot /aws/services/iot 301 /getting-started/installation /aws/getting-started/installation 301 /user-guide/integrations/architect /aws/integrations/app-frameworks/architect/ 301 -/user-guide/integrations/gitpod /aws/integrations/containers/gitpod/ 301 +/user-guide/integrations/gitpod /aws/advanced-installation/gitpod/ 301 /user-guide/aws/managedblockchain /aws/services/managedblockchain 301 /applications/query-data-in-s3-bucket-with-amazon-athena-glue-catalog-cloudformation https://github.com/localstack-samples/sample-query-data-s3-athena-glue 301 /academy/localstack-101/web-app-resource-browser https://www.youtube.com/watch?list=PLTew28KOwGxPqbkFiW518eeIfiV495bm0&v=SoXtngYp-8k&feature=youtu.be 301 @@ -740,12 +740,12 @@ /references/coverage/coverage_sagemaker-runtime /aws/services/sagemaker 301 /applications/messaging-processing-application-with-sqs-dynamodb-and-fargate https://github.com/localstack-samples/sample-cdk-sqs-fargate-dynamodb 301 /user-guide/aws/mq /aws/services/mq 301 -/user-guide/localstack-enterprise/kubernetes-executor /aws/enterprise/kubernetes-executor 301 +/user-guide/localstack-enterprise/kubernetes-executor /aws/advanced-installation/kubernetes-executor 301 /user-guide/aws/iot /aws/services/iot 301 /user-guide/aws/backup /aws/services/backup 301 /references/coverage/coverage_organizations /aws/services/organizations 301 /user-guide/aws/kinesisanalytics /aws/services/kinesisanalytics 301 -/user-guide/localstack-enterprise/single-sign-on /aws/enterprise/sso 301 +/user-guide/localstack-enterprise/single-sign-on /aws/team-workspaces/sso 301 /user-guide/aws/redshift /aws/services/redshift 301 /references/coverage/coverage_verifiedpermissions /aws/services/verifiedpermissions 301 /academy/localstack-101/full-project-demo https://www.youtube.com/watch?list=PLTew28KOwGxPqbkFiW518eeIfiV495bm0&v=cQxg3Dnteyc&feature=youtu.be 301 @@ -771,12 +771,12 @@ /tutorials/using-terraform-with-testcontainers-and-localstack /aws/tutorials/using-terraform-with-testcontainers-and-localstack 301 /references/coverage/coverage_cloudfront /aws/services/cloudfront 301 /user-guide/tools/localstack-sdk/java /aws/user-guide/tools/localstack-sdk/java 301 -/references/network-troubleshooting/readme /aws/capabilities/networking/ 301 +/references/network-troubleshooting/readme /aws/configuration/networking/ 301 /user-guide/aws/codecommit /aws/services/codecommit 301 /references/coverage/coverage_swf /aws/services/swf 301 /user-guide/integrations/sdks/go /aws/connecting/aws-sdks/go 301 /persistence /aws/developer-tools/snapshots/persistence/ 301 -/references/init-hooks /aws/capabilities/config/initialization-hooks/ 301 +/references/init-hooks /aws/configuration/advanced/initialization-hooks/ 301 /references/coverage/coverage_support /aws/services/support 301 /user-guide /aws/ 301 /user-guide/aws/qldb /aws/services/qldb 301 @@ -799,30 +799,30 @@ /references/api-key /aws/getting-started/auth-token/#how-do-i-activate-older-versions-of-localstack-before-v30 301 /references/coverage/coverage_eks /aws/services/eks 301 /references/coverage/coverage_cognito-idp /aws/services/cognito-idp 301 -/user-guide/web-application/workspace /aws/capabilities/web-app/workspace 301 +/user-guide/web-application/workspace /aws/team-workspaces/workspace 301 /references/coverage/coverage_cloudcontrol /aws/services/cloudcontrol 301 /tutorials/replicate-aws-resources-localstack-extension /aws/tutorials/replicate-aws-resources-localstack-extension 301 -/user-guide/tools/localstack-sdk/python /aws/capabilities/localstack-sdks/python 301 +/user-guide/tools/localstack-sdk/python /aws/integrations/localstack-sdks/python 301 /user-guide/lambda-tools/hot-reloading /aws/developer-tools/lambda-tools/hot-reloading 301 /getting-started/quickstart /aws/getting-started/quickstart 301 /overview /aws 301 /user-guide/aws/glue /aws/services/glue 301 /getting-started /aws/getting-started 301 -/user-guide/extensions/managing-extensions /aws/capabilities/extensions/managing-extensions 301 -/references/filesystem /aws/capabilities/config/filesystem/ 301 -/references /aws/capabilities/config/ 301 +/user-guide/extensions/managing-extensions /aws/integrations/extensions/managing-extensions 301 +/references/filesystem /aws/configuration/advanced/filesystem/ 301 +/references /aws/configuration/ 301 /academy/localstack-101/getting-started https://www.youtube.com/watch?v=CzX4mfiS058&feature=youtu.be 301 /user-guide/materalized-views /snowflake/features/materialized-views/ 301 /user-guide/materalized-views/ /snowflake/features/materialized-views/ 301 /snowflake/features/materalized-views/ /snowflake/features/materialized-views/ 301 -/user-guide/ci /aws/integrations/continuous-integration/ 301 -/user-guide/ci/ /aws/integrations/continuous-integration/ 301 -/aws/user-guide/ci /aws/integrations/continuous-integration/ 301 -/aws/user-guide/ci/ /aws/integrations/continuous-integration/ 301 +/user-guide/ci /aws/ci-pipelines/ 301 +/user-guide/ci/ /aws/ci-pipelines/ 301 +/aws/user-guide/ci /aws/ci-pipelines/ 301 +/aws/user-guide/ci/ /aws/ci-pipelines/ 301 /aws/tooling/lambda-tools/vscode-extension/ /aws/connecting/ides/vscode-extension/ 301 /aws/tooling/lambda-tools/vscode-extension /aws/connecting/ides/vscode-extension/ 301 -/aws/capabilities/cloud-sandbox/application-previews/ /aws/developer-tools/cloud-sandbox/app-preview/ 301 -/aws/capabilities/cloud-sandbox/application-previews /aws/developer-tools/cloud-sandbox/app-preview/ 301 +/aws/configuration/cloud-sandbox/application-previews/ /aws/developer-tools/cloud-sandbox/app-preview/ 301 +/aws/configuration/cloud-sandbox/application-previews /aws/developer-tools/cloud-sandbox/app-preview/ 301 /aws/integrations/aws-native-tools/aws-cli/ /aws/connecting/aws-cli/ 301 /aws/integrations/aws-native-tools/aws-cli /aws/connecting/aws-cli/ 301 /aws/integrations/aws-native-tools/aws-cdk/ /aws/connecting/infrastructure-as-code/aws-cdk/ 301 @@ -853,10 +853,10 @@ /aws/integrations/infrastructure-as-code/pulumi /aws/connecting/infrastructure-as-code/pulumi/ 301 /aws/integrations/app-frameworks/serverless-framework/ /aws/connecting/infrastructure-as-code/serverless-framework/ 301 /aws/integrations/app-frameworks/serverless-framework /aws/connecting/infrastructure-as-code/serverless-framework/ 301 -/aws/capabilities/web-app/resource-browser/ /aws/connecting/console/resource-browser/ 301 -/aws/capabilities/web-app/resource-browser /aws/connecting/console/resource-browser/ 301 -/aws/capabilities/web-app/stack-overview/ /aws/connecting/console/stack-overview/ 301 -/aws/capabilities/web-app/stack-overview /aws/connecting/console/stack-overview/ 301 +/aws/team-workspaces/resource-browser/ /aws/connecting/console/resource-browser/ 301 +/aws/team-workspaces/resource-browser /aws/connecting/console/resource-browser/ 301 +/aws/team-workspaces/stack-overview/ /aws/connecting/console/stack-overview/ 301 +/aws/team-workspaces/stack-overview /aws/connecting/console/stack-overview/ 301 /aws/tooling/vscode-extension/ /aws/connecting/ides/vscode-extension/ 301 /aws/tooling/vscode-extension /aws/connecting/ides/vscode-extension/ 301 /aws/integrations/aws-native-tools/aws-chalice/ /aws/connecting/infrastructure-as-code/aws-chalice/ 301 @@ -875,61 +875,61 @@ /aws/integrations/aws-native-tools /aws/connecting/ 301 /aws/integrations/infrastructure-as-code/ /aws/connecting/infrastructure-as-code/ 301 /aws/integrations/infrastructure-as-code /aws/connecting/infrastructure-as-code/ 301 -/aws/capabilities/state-management/cli-commands /aws/developer-tools/snapshots/cli-commands 301 -/aws/capabilities/state-management/cli-commands/ /aws/developer-tools/snapshots/cli-commands 301 -/aws/capabilities/state-management/export-import-state /aws/developer-tools/snapshots/export-import-state 301 -/aws/capabilities/state-management/export-import-state/ /aws/developer-tools/snapshots/export-import-state 301 -/aws/capabilities/state-management/ /aws/developer-tools/snapshots/ 301 -/aws/capabilities/state-management/launchpad /aws/developer-tools/snapshots/launchpad 301 -/aws/capabilities/state-management/launchpad/ /aws/developer-tools/snapshots/launchpad 301 -/aws/capabilities/state-management/cloud-pods /aws/developer-tools/snapshots/cloud-pods 301 -/aws/capabilities/state-management/cloud-pods/ /aws/developer-tools/snapshots/cloud-pods 301 -/aws/capabilities/state-management/persistence /aws/developer-tools/snapshots/persistence 301 -/aws/capabilities/state-management/persistence/ /aws/developer-tools/snapshots/persistence 301 -/aws/capabilities/cloud-sandbox/app-preview /aws/developer-tools/cloud-sandbox/app-preview 301 -/aws/capabilities/cloud-sandbox/app-preview/ /aws/developer-tools/cloud-sandbox/app-preview 301 -/aws/capabilities/cloud-sandbox/ephemeral-instances /aws/developer-tools/cloud-sandbox/ephemeral-instances 301 -/aws/capabilities/cloud-sandbox/ephemeral-instances/ /aws/developer-tools/cloud-sandbox/ephemeral-instances 301 -/aws/capabilities/cloud-sandbox/ /aws/developer-tools/cloud-sandbox/ 301 -/aws/capabilities/chaos-engineering/aws-fault-injection /aws/developer-tools/chaos-engineering/aws-fault-injection 301 -/aws/capabilities/chaos-engineering/aws-fault-injection/ /aws/developer-tools/chaos-engineering/aws-fault-injection 301 -/aws/capabilities/chaos-engineering/chaos-api /aws/developer-tools/chaos-engineering/chaos-api 301 -/aws/capabilities/chaos-engineering/chaos-api/ /aws/developer-tools/chaos-engineering/chaos-api 301 -/aws/capabilities/chaos-engineering/chaos-engineering-dashboard /aws/developer-tools/chaos-engineering/chaos-engineering-dashboard 301 -/aws/capabilities/chaos-engineering/chaos-engineering-dashboard/ /aws/developer-tools/chaos-engineering/chaos-engineering-dashboard 301 -/aws/capabilities/chaos-engineering/ /aws/developer-tools/chaos-engineering/ 301 -/aws/capabilities/security-testing/explainable-iam /aws/developer-tools/security-testing/explainable-iam 301 -/aws/capabilities/security-testing/explainable-iam/ /aws/developer-tools/security-testing/explainable-iam 301 -/aws/capabilities/security-testing/iam-coverage /aws/developer-tools/security-testing/iam-coverage 301 -/aws/capabilities/security-testing/iam-coverage/ /aws/developer-tools/security-testing/iam-coverage 301 -/aws/capabilities/security-testing/iam-policy-enforcement /aws/developer-tools/security-testing/iam-policy-enforcement 301 -/aws/capabilities/security-testing/iam-policy-enforcement/ /aws/developer-tools/security-testing/iam-policy-enforcement 301 -/aws/capabilities/security-testing/iam-policy-stream /aws/developer-tools/security-testing/iam-policy-stream 301 -/aws/capabilities/security-testing/iam-policy-stream/ /aws/developer-tools/security-testing/iam-policy-stream 301 -/aws/capabilities/security-testing/ /aws/developer-tools/security-testing/ 301 -/aws/capabilities/security-testing/custom-tls-certificates /aws/developer-tools/security-testing/custom-tls-certificates 301 -/aws/capabilities/security-testing/custom-tls-certificates/ /aws/developer-tools/security-testing/custom-tls-certificates 301 +/aws/configuration/state-management/cli-commands /aws/developer-tools/snapshots/cli-commands 301 +/aws/configuration/state-management/cli-commands/ /aws/developer-tools/snapshots/cli-commands 301 +/aws/configuration/state-management/export-import-state /aws/developer-tools/snapshots/export-import-state 301 +/aws/configuration/state-management/export-import-state/ /aws/developer-tools/snapshots/export-import-state 301 +/aws/configuration/state-management/ /aws/developer-tools/snapshots/ 301 +/aws/configuration/state-management/launchpad /aws/developer-tools/snapshots/launchpad 301 +/aws/configuration/state-management/launchpad/ /aws/developer-tools/snapshots/launchpad 301 +/aws/configuration/state-management/cloud-pods /aws/developer-tools/snapshots/cloud-pods 301 +/aws/configuration/state-management/cloud-pods/ /aws/developer-tools/snapshots/cloud-pods 301 +/aws/configuration/state-management/persistence /aws/developer-tools/snapshots/persistence 301 +/aws/configuration/state-management/persistence/ /aws/developer-tools/snapshots/persistence 301 +/aws/configuration/cloud-sandbox/app-preview /aws/developer-tools/cloud-sandbox/app-preview 301 +/aws/configuration/cloud-sandbox/app-preview/ /aws/developer-tools/cloud-sandbox/app-preview 301 +/aws/configuration/cloud-sandbox/ephemeral-instances /aws/developer-tools/cloud-sandbox/ephemeral-instances 301 +/aws/configuration/cloud-sandbox/ephemeral-instances/ /aws/developer-tools/cloud-sandbox/ephemeral-instances 301 +/aws/configuration/cloud-sandbox/ /aws/developer-tools/cloud-sandbox/ 301 +/aws/configuration/chaos-engineering/aws-fault-injection /aws/developer-tools/chaos-engineering/aws-fault-injection 301 +/aws/configuration/chaos-engineering/aws-fault-injection/ /aws/developer-tools/chaos-engineering/aws-fault-injection 301 +/aws/configuration/chaos-engineering/chaos-api /aws/developer-tools/chaos-engineering/chaos-api 301 +/aws/configuration/chaos-engineering/chaos-api/ /aws/developer-tools/chaos-engineering/chaos-api 301 +/aws/configuration/chaos-engineering/chaos-engineering-dashboard /aws/developer-tools/chaos-engineering/chaos-engineering-dashboard 301 +/aws/configuration/chaos-engineering/chaos-engineering-dashboard/ /aws/developer-tools/chaos-engineering/chaos-engineering-dashboard 301 +/aws/configuration/chaos-engineering/ /aws/developer-tools/chaos-engineering/ 301 +/aws/configuration/security-testing/explainable-iam /aws/developer-tools/security-testing/explainable-iam 301 +/aws/configuration/security-testing/explainable-iam/ /aws/developer-tools/security-testing/explainable-iam 301 +/aws/configuration/security-testing/iam-coverage /aws/developer-tools/security-testing/iam-coverage 301 +/aws/configuration/security-testing/iam-coverage/ /aws/developer-tools/security-testing/iam-coverage 301 +/aws/configuration/security-testing/iam-policy-enforcement /aws/developer-tools/security-testing/iam-policy-enforcement 301 +/aws/configuration/security-testing/iam-policy-enforcement/ /aws/developer-tools/security-testing/iam-policy-enforcement 301 +/aws/configuration/security-testing/iam-policy-stream /aws/developer-tools/security-testing/iam-policy-stream 301 +/aws/configuration/security-testing/iam-policy-stream/ /aws/developer-tools/security-testing/iam-policy-stream 301 +/aws/configuration/security-testing/ /aws/developer-tools/security-testing/ 301 +/aws/configuration/security-testing/custom-tls-certificates /aws/developer-tools/security-testing/custom-tls-certificates 301 +/aws/configuration/security-testing/custom-tls-certificates/ /aws/developer-tools/security-testing/custom-tls-certificates 301 /aws/tooling/lambda-tools/ /aws/developer-tools/lambda-tools/ 301 /aws/tooling/lambda-tools/hot-reloading /aws/developer-tools/lambda-tools/hot-reloading 301 /aws/tooling/lambda-tools/hot-reloading/ /aws/developer-tools/lambda-tools/hot-reloading 301 /aws/tooling/lambda-tools/remote-debugging /aws/developer-tools/lambda-tools/remote-debugging 301 /aws/tooling/lambda-tools/remote-debugging/ /aws/developer-tools/lambda-tools/remote-debugging 301 -/aws/tooling/localstack-sdks/ /aws/capabilities/localstack-sdks/ 301 -/aws/tooling/localstack-sdks/java-sdk /aws/capabilities/localstack-sdks/java-sdk 301 -/aws/tooling/localstack-sdks/java-sdk/ /aws/capabilities/localstack-sdks/java-sdk 301 -/aws/tooling/localstack-sdks/python-sdk /aws/capabilities/localstack-sdks/python-sdk 301 -/aws/tooling/localstack-sdks/python-sdk/ /aws/capabilities/localstack-sdks/python-sdk 301 -/aws/tooling/extensions/extensions-library /aws/capabilities/extensions/extensions-library 301 -/aws/tooling/extensions/extensions-library/ /aws/capabilities/extensions/extensions-library 301 -/aws/tooling/extensions/ /aws/capabilities/extensions/ 301 -/aws/tooling/extensions/mailhog /aws/capabilities/extensions/mailhog 301 -/aws/tooling/extensions/mailhog/ /aws/capabilities/extensions/mailhog 301 -/aws/tooling/extensions/developing-extensions /aws/capabilities/extensions/developing-extensions 301 -/aws/tooling/extensions/developing-extensions/ /aws/capabilities/extensions/developing-extensions 301 -/aws/tooling/extensions/managing-extensions /aws/capabilities/extensions/managing-extensions 301 -/aws/tooling/extensions/managing-extensions/ /aws/capabilities/extensions/managing-extensions 301 -/aws/capabilities/web-app/app-inspector /aws/developer-tools/app-inspector 301 -/aws/capabilities/web-app/app-inspector/ /aws/developer-tools/app-inspector 301 +/aws/tooling/localstack-sdks/ /aws/integrations/localstack-sdks/ 301 +/aws/tooling/localstack-sdks/java-sdk /aws/integrations/localstack-sdks/java-sdk 301 +/aws/tooling/localstack-sdks/java-sdk/ /aws/integrations/localstack-sdks/java-sdk 301 +/aws/tooling/localstack-sdks/python-sdk /aws/integrations/localstack-sdks/python-sdk 301 +/aws/tooling/localstack-sdks/python-sdk/ /aws/integrations/localstack-sdks/python-sdk 301 +/aws/tooling/extensions/extensions-library /aws/integrations/extensions/extensions-library 301 +/aws/tooling/extensions/extensions-library/ /aws/integrations/extensions/extensions-library 301 +/aws/tooling/extensions/ /aws/integrations/extensions/ 301 +/aws/tooling/extensions/mailhog /aws/integrations/extensions/mailhog 301 +/aws/tooling/extensions/mailhog/ /aws/integrations/extensions/mailhog 301 +/aws/tooling/extensions/developing-extensions /aws/integrations/extensions/developing-extensions 301 +/aws/tooling/extensions/developing-extensions/ /aws/integrations/extensions/developing-extensions 301 +/aws/tooling/extensions/managing-extensions /aws/integrations/extensions/managing-extensions 301 +/aws/tooling/extensions/managing-extensions/ /aws/integrations/extensions/managing-extensions 301 +/aws/team-workspaces/app-inspector /aws/developer-tools/app-inspector 301 +/aws/team-workspaces/app-inspector/ /aws/developer-tools/app-inspector 301 /aws/tooling/aws-replicator /aws/developer-tools/aws-replicator 301 /aws/tooling/aws-replicator/ /aws/developer-tools/aws-replicator 301 /aws/tooling/localstack-cli /aws/developer-tools/running-localstack/localstack-cli 301 @@ -938,13 +938,68 @@ /aws/tooling/lstk/ /aws/developer-tools/running-localstack/lstk 301 /aws/tooling/mcp-server /aws/developer-tools/running-localstack/mcp-server 301 /aws/tooling/mcp-server/ /aws/developer-tools/running-localstack/mcp-server 301 -/aws/tooling/dns-server /aws/capabilities/dns-server 301 -/aws/tooling/dns-server/ /aws/capabilities/dns-server 301 -/aws/tooling/testing-utils /aws/capabilities/testing-utils 301 -/aws/tooling/testing-utils/ /aws/capabilities/testing-utils 301 -/aws/tooling/localstack-docker-extension /aws/capabilities/localstack-docker-extension 301 -/aws/tooling/localstack-docker-extension/ /aws/capabilities/localstack-docker-extension 301 -/aws/tooling/localsurf /aws/capabilities/localsurf 301 -/aws/tooling/localsurf/ /aws/capabilities/localsurf 301 +/aws/tooling/dns-server /aws/configuration/networking/dns-server 301 +/aws/tooling/dns-server/ /aws/configuration/networking/dns-server 301 +/aws/tooling/testing-utils /aws/integrations/localstack-sdks/testing-utils 301 +/aws/tooling/testing-utils/ /aws/integrations/localstack-sdks/testing-utils 301 +/aws/tooling/localstack-docker-extension /aws/advanced-installation/localstack-docker-extension 301 +/aws/tooling/localstack-docker-extension/ /aws/advanced-installation/localstack-docker-extension 301 +/aws/tooling/localsurf /aws/configuration/networking/localsurf 301 +/aws/tooling/localsurf/ /aws/configuration/networking/localsurf 301 /aws/tooling /aws/developer-tools 301 /aws/tooling/ /aws/developer-tools/ 301 + +# --- DPX-493: Configuration / Integrations / Team Workspaces restructure --- +# Configuration (capabilities -> configuration) +/aws/capabilities/networking/* /aws/configuration/networking/:splat 301 +/aws/capabilities/networking /aws/configuration/networking 301 +/aws/capabilities/config/configuration /aws/configuration/configuration-options 301 +/aws/capabilities/config/logging /aws/configuration/logging 301 +/aws/capabilities/config/arm64-support /aws/configuration/advanced/arm64-support 301 +/aws/capabilities/config/cross-account-access /aws/configuration/advanced/cross-account-access 301 +/aws/capabilities/config/multi-account-setups /aws/configuration/advanced/multi-account-setups 301 +/aws/capabilities/config/filesystem /aws/configuration/advanced/filesystem 301 +/aws/capabilities/config/initialization-hooks /aws/configuration/advanced/initialization-hooks 301 +/aws/capabilities/config/regions-coverage /aws/configuration/advanced/regions-coverage 301 +/aws/capabilities/config/usage-tracking /aws/configuration/advanced/usage-tracking 301 +/aws/capabilities/config/internal-endpoints /aws/configuration/networking/internal-endpoints 301 +/aws/capabilities/config/credentials /aws/connecting/credentials 301 +/aws/capabilities/config/docker-images /aws/advanced-installation/docker-images 301 +/aws/capabilities/config/podman /aws/advanced-installation/podman 301 +/aws/capabilities/config /aws/configuration 301 +/aws/capabilities/dns-server /aws/configuration/networking/dns-server 301 +/aws/capabilities/localsurf /aws/configuration/networking/localsurf 301 +# Integrations moves +/aws/capabilities/testing-utils /aws/integrations/localstack-sdks/testing-utils 301 +/aws/capabilities/localstack-docker-extension /aws/advanced-installation/localstack-docker-extension 301 +/aws/capabilities/localstack-sdks/* /aws/integrations/localstack-sdks/:splat 301 +/aws/capabilities/localstack-sdks /aws/integrations/localstack-sdks 301 +/aws/capabilities/extensions/* /aws/integrations/extensions/:splat 301 +/aws/capabilities/extensions /aws/integrations/extensions 301 +/aws/integrations/containers/openshift /aws/advanced-installation/kubernetes/openshift 301 +/aws/integrations/containers/eksctl /aws/advanced-installation/kubernetes/eksctl 301 +/aws/integrations/containers/rancher-desktop /aws/advanced-installation/rancher-desktop 301 +/aws/integrations/containers/devcontainers /aws/advanced-installation/devcontainers 301 +/aws/integrations/containers /aws/advanced-installation 301 +/aws/integrations/messaging/selfmanaged-kafka-cluster /aws/integrations/app-frameworks/selfmanaged-kafka-cluster 301 +/aws/integrations/messaging /aws/integrations/app-frameworks 301 +# Team Workspaces (web-app -> team-workspaces) + other page moves +/aws/capabilities/web-app/accounts /aws/team-workspaces/accounts 301 +/aws/capabilities/web-app/workspaces /aws/team-workspaces/workspaces 301 +/aws/capabilities/web-app/managing-users-licenses /aws/team-workspaces/managing-users-licenses 301 +/aws/capabilities/web-app/stack-insights /aws/team-workspaces/stack-insights 301 +/aws/capabilities/web-app/instance-management /aws/connecting/console/instance-management 301 +/aws/capabilities/web-app/localstack-desktop /aws/developer-tools/running-localstack/localstack-desktop 301 +/aws/capabilities/web-app /aws/team-workspaces 301 +/aws/capabilities /aws/configuration 301 +# Enterprise (section removed) +/aws/enterprise/enterprise-image /aws/advanced-installation/enterprise-image 301 +/aws/enterprise/kubernetes/* /aws/advanced-installation/kubernetes/:splat 301 +/aws/enterprise/kubernetes /aws/advanced-installation/kubernetes 301 +/aws/enterprise/sso/* /aws/team-workspaces/sso/:splat 301 +/aws/enterprise/sso /aws/team-workspaces/sso 301 +/aws/enterprise /aws/advanced-installation 301 + +# DPX-493 (rev): Continuous Integration -> top-level CI Pipelines +/aws/integrations/continuous-integration/* /aws/ci-pipelines/:splat 301 +/aws/integrations/continuous-integration /aws/ci-pipelines 301 diff --git a/public/js/icon-loader.js b/public/js/icon-loader.js index 835a97294..a603088c4 100644 --- a/public/js/icon-loader.js +++ b/public/js/icon-loader.js @@ -15,7 +15,10 @@ Capabilities: 'starburst-icon', Configuration: 'starburst-icon', Tooling: 'wrench-icon', + 'CI Pipelines': 'change-icon', + 'Advanced Installation': 'cube-icon', Integrations: 'connections-icon', + 'Team Workspaces': 'users-icon', Enterprise: 'buildings-icon', Tutorials: 'book-icon', Changelog: 'change-icon', diff --git a/src/assets/images/users.svg b/src/assets/images/users.svg new file mode 100644 index 000000000..a8025466f --- /dev/null +++ b/src/assets/images/users.svg @@ -0,0 +1,6 @@ + + + + + + diff --git a/src/content/docs/aws/integrations/containers/devcontainers.mdx b/src/content/docs/aws/advanced-installation/devcontainers.mdx similarity index 99% rename from src/content/docs/aws/integrations/containers/devcontainers.mdx rename to src/content/docs/aws/advanced-installation/devcontainers.mdx index 150ea794e..df02ab3c4 100644 --- a/src/content/docs/aws/integrations/containers/devcontainers.mdx +++ b/src/content/docs/aws/advanced-installation/devcontainers.mdx @@ -110,7 +110,7 @@ To get started with LocalStack and DevContainers in VS Code, follow these steps: * Filter by typing "localstack" in the search bar and select the **LocalStack Docker-in-Docker** template. - [Select official LocalStack Template (DinD)](/aws/integrations/containers/devcontainers/#localstack-templates) + [Select official LocalStack Template (DinD)](/aws/advanced-installation/devcontainers/#localstack-templates) * Proceed through the configuration by selecting or entering values. Pressing **Enter** through the options will apply default settings, which include: diff --git a/src/content/docs/aws/capabilities/config/docker-images.md b/src/content/docs/aws/advanced-installation/docker-images.md similarity index 100% rename from src/content/docs/aws/capabilities/config/docker-images.md rename to src/content/docs/aws/advanced-installation/docker-images.md diff --git a/src/content/docs/aws/enterprise/enterprise-image.md b/src/content/docs/aws/advanced-installation/enterprise-image.md similarity index 94% rename from src/content/docs/aws/enterprise/enterprise-image.md rename to src/content/docs/aws/advanced-installation/enterprise-image.md index d197cfbbe..e7467a2f5 100644 --- a/src/content/docs/aws/enterprise/enterprise-image.md +++ b/src/content/docs/aws/advanced-installation/enterprise-image.md @@ -34,7 +34,7 @@ This offline functionality is enabled by: ## "Online" vs "Offline" image -This section compares the standard [LocalStack for AWS Docker image](/aws/capabilities/config/docker-images) ("online") with the customer-specific Enterprise image ("offline"). +This section compares the standard [LocalStack for AWS Docker image](/aws/advanced-installation/docker-images) ("online") with the customer-specific Enterprise image ("offline"). ### Key differences @@ -45,7 +45,7 @@ This section compares the standard [LocalStack for AWS Docker image](/aws/capabi | Service dependencies | Some services may download dependencies on demand during runtime. | Service dependencies are pre-baked into the image for offline usage. | | Cloud Pods | Platform remote integration can sync state with your LocalStack account. | LocalStack Platform remotes are typically unavailable in fully air-gapped setups. Use self-managed remotes (for example S3 or ORAS) when available in your environment. | | Ephemeral instances | Available via Web App/CLI as cloud-hosted LocalStack runtimes. | Not available in air-gapped/offline deployments because they run on LocalStack Cloud infrastructure. | -| Telemetry | Can send usage events for features such as [Stack Insights](/aws/capabilities/web-app/stack-insights). | Keep event reporting disabled (`DISABLE_EVENTS=1`) for strict offline setups. | +| Telemetry | Can send usage events for features such as [Stack Insights](/aws/team-workspaces/stack-insights). | Keep event reporting disabled (`DISABLE_EVENTS=1`) for strict offline setups. | ### What communicates with LocalStack Cloud? diff --git a/src/content/docs/aws/advanced-installation/index.md b/src/content/docs/aws/advanced-installation/index.md new file mode 100644 index 000000000..dd71e7b55 --- /dev/null +++ b/src/content/docs/aws/advanced-installation/index.md @@ -0,0 +1,18 @@ +--- +title: Overview +description: Run LocalStack in non-default container environments, from alternative images and runtimes to Kubernetes. +template: doc +editUrl: false +sidebar: + order: 1 +--- + +The quick start guide installs LocalStack using Docker Desktop, but many teams prefer not to use that approach. This section covers alternative installation methods — different images, container runtimes, and orchestration platforms — so you can run LocalStack in the environment that best fits your setup, including the all-important Kubernetes. + +- [Docker Images](/aws/advanced-installation/docker-images) — the available LocalStack Docker images and how to choose between them. +- [Enterprise Image](/aws/advanced-installation/enterprise-image) — the image for air-gapped and secured Enterprise setups. +- [Podman](/aws/advanced-installation/podman) — run LocalStack with Podman instead of Docker. +- [Rancher Desktop](/aws/advanced-installation/rancher-desktop) — run LocalStack on Rancher Desktop. +- [Kubernetes](/aws/advanced-installation/kubernetes) — deploy LocalStack into Kubernetes, including the Operator, Executor, OpenShift, and eksctl. +- [DevContainers](/aws/advanced-installation/devcontainers) — use LocalStack inside a development container. +- [LocalStack Docker Extension](/aws/advanced-installation/localstack-docker-extension) — manage LocalStack from Docker Desktop. diff --git a/src/content/docs/aws/enterprise/kubernetes/concepts.md b/src/content/docs/aws/advanced-installation/kubernetes/concepts.md similarity index 95% rename from src/content/docs/aws/enterprise/kubernetes/concepts.md rename to src/content/docs/aws/advanced-installation/kubernetes/concepts.md index 977b1b6a2..bb0a0180a 100644 --- a/src/content/docs/aws/enterprise/kubernetes/concepts.md +++ b/src/content/docs/aws/advanced-installation/kubernetes/concepts.md @@ -93,9 +93,9 @@ This enables applications running in Kubernetes to interact with LocalStack usin ## Storage -LocalStack can store data that persists across sessions, such as data that can be used for [local persistence](https://docs.localstack.cloud/aws/developer-tools/snapshots/persistence/) or caching downloaded resources between sessions. See the [LocalStack volume](/aws/capabilities/config/filesystem/#localstack-volume) page for more information. +LocalStack can store data that persists across sessions, such as data that can be used for [local persistence](https://docs.localstack.cloud/aws/developer-tools/snapshots/persistence/) or caching downloaded resources between sessions. See the [LocalStack volume](/aws/configuration/advanced/filesystem/#localstack-volume) page for more information. -This volume directory can be created in Kubernetes using a [Persistent Volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) and associated [Persistent Volume Claim](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims). This volume should be mounted into the pod at `/var/lib/localstack` to persist LocalStack state. See the [Operator](/aws/enterprise/kubernetes/kubernetes-operator/) and [Helm Chart](/aws/enterprise/kubernetes/deploy-helm-chart) documentation for specific details. +This volume directory can be created in Kubernetes using a [Persistent Volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) and associated [Persistent Volume Claim](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims). This volume should be mounted into the pod at `/var/lib/localstack` to persist LocalStack state. See the [Operator](/aws/advanced-installation/kubernetes/kubernetes-operator/) and [Helm Chart](/aws/advanced-installation/kubernetes/deploy-helm-chart) documentation for specific details. ## Choose execution mode diff --git a/src/content/docs/aws/enterprise/kubernetes/configuration.md b/src/content/docs/aws/advanced-installation/kubernetes/configuration.md similarity index 99% rename from src/content/docs/aws/enterprise/kubernetes/configuration.md rename to src/content/docs/aws/advanced-installation/kubernetes/configuration.md index 8ff330e0d..0b9c51b99 100644 --- a/src/content/docs/aws/enterprise/kubernetes/configuration.md +++ b/src/content/docs/aws/advanced-installation/kubernetes/configuration.md @@ -1,5 +1,5 @@ --- -title: Configuration +title: Kubernetes Configuration description: Kubernetes configuration reference for LocalStack running on Kubernetes template: doc sidebar: diff --git a/src/content/docs/aws/enterprise/kubernetes/deploy-helm-chart.md b/src/content/docs/aws/advanced-installation/kubernetes/deploy-helm-chart.md similarity index 100% rename from src/content/docs/aws/enterprise/kubernetes/deploy-helm-chart.md rename to src/content/docs/aws/advanced-installation/kubernetes/deploy-helm-chart.md diff --git a/src/content/docs/aws/integrations/containers/eksctl.mdx b/src/content/docs/aws/advanced-installation/kubernetes/eksctl.mdx similarity index 99% rename from src/content/docs/aws/integrations/containers/eksctl.mdx rename to src/content/docs/aws/advanced-installation/kubernetes/eksctl.mdx index 965ae6661..7d562d55f 100644 --- a/src/content/docs/aws/integrations/containers/eksctl.mdx +++ b/src/content/docs/aws/advanced-installation/kubernetes/eksctl.mdx @@ -3,7 +3,7 @@ title: eksctl description: Running `eksctl` on LocalStack to create EKS clusters. template: doc sidebar: - order: 5 + order: 9 --- import { Tabs, TabItem } from '@astrojs/starlight/components'; diff --git a/src/content/docs/aws/enterprise/kubernetes/faq.md b/src/content/docs/aws/advanced-installation/kubernetes/faq.md similarity index 96% rename from src/content/docs/aws/enterprise/kubernetes/faq.md rename to src/content/docs/aws/advanced-installation/kubernetes/faq.md index 1b9f8cec1..90dd0eef9 100644 --- a/src/content/docs/aws/enterprise/kubernetes/faq.md +++ b/src/content/docs/aws/advanced-installation/kubernetes/faq.md @@ -3,7 +3,7 @@ title: FAQ description: FAQ template: doc sidebar: - order: 6 + order: 11 tags: ["Enterprise"] --- @@ -171,7 +171,7 @@ Common causes for connection failure: * **Transparent Endpoint Injection** - * Review: [https://docs.localstack.cloud/aws/capabilities/networking/transparent-endpoint-injection/](https://docs.localstack.cloud/aws/capabilities/networking/transparent-endpoint-injection/) + * Review: [https://docs.localstack.cloud/aws/configuration/networking/transparent-endpoint-injection/](https://docs.localstack.cloud/aws/configuration/networking/transparent-endpoint-injection/) * **Egress restrictions** * Ensure cluster network policies allow outbound internet access. @@ -262,7 +262,7 @@ This usually means the cluster restricts which images can be pulled. * Allow the LocalStack images in your cluster * If you must use a custom image name or pull-through cache, see: - [https://docs.localstack.cloud/aws/capabilities/config/configuration/](https://docs.localstack.cloud/aws/capabilities/config/configuration/) + [https://docs.localstack.cloud/aws/configuration/configuration-options/](https://docs.localstack.cloud/aws/configuration/configuration-options/) ### Admission or security policy failures diff --git a/src/content/docs/aws/enterprise/kubernetes/index.md b/src/content/docs/aws/advanced-installation/kubernetes/index.md similarity index 100% rename from src/content/docs/aws/enterprise/kubernetes/index.md rename to src/content/docs/aws/advanced-installation/kubernetes/index.md diff --git a/src/content/docs/aws/enterprise/kubernetes/kubernetes-executor.md b/src/content/docs/aws/advanced-installation/kubernetes/kubernetes-executor.md similarity index 100% rename from src/content/docs/aws/enterprise/kubernetes/kubernetes-executor.md rename to src/content/docs/aws/advanced-installation/kubernetes/kubernetes-executor.md diff --git a/src/content/docs/aws/enterprise/kubernetes/kubernetes-operator.mdx b/src/content/docs/aws/advanced-installation/kubernetes/kubernetes-operator.mdx similarity index 97% rename from src/content/docs/aws/enterprise/kubernetes/kubernetes-operator.mdx rename to src/content/docs/aws/advanced-installation/kubernetes/kubernetes-operator.mdx index 00e104ba2..3e5cb4202 100644 --- a/src/content/docs/aws/enterprise/kubernetes/kubernetes-operator.mdx +++ b/src/content/docs/aws/advanced-installation/kubernetes/kubernetes-operator.mdx @@ -215,7 +215,7 @@ This works without additional DNS configuration in client applications. Requires Operator version 0.4.0 or later. ::: -To persist the [LocalStack volume](/aws/capabilities/config/filesystem/#localstack-volume), use the `spec.pvcName` to specify the PVC you want to mount. This automatically mounts the PVC at `/var/lib/localstack`. +To persist the [LocalStack volume](/aws/configuration/advanced/filesystem/#localstack-volume), use the `spec.pvcName` to specify the PVC you want to mount. This automatically mounts the PVC at `/var/lib/localstack`. For example: diff --git a/src/content/docs/aws/enterprise/kubernetes/limitations.md b/src/content/docs/aws/advanced-installation/kubernetes/limitations.md similarity index 98% rename from src/content/docs/aws/enterprise/kubernetes/limitations.md rename to src/content/docs/aws/advanced-installation/kubernetes/limitations.md index 3dec9bcb0..471436ad4 100644 --- a/src/content/docs/aws/enterprise/kubernetes/limitations.md +++ b/src/content/docs/aws/advanced-installation/kubernetes/limitations.md @@ -3,7 +3,7 @@ title: Limitations description: Known limitations when running LocalStack on Kubernetes template: doc sidebar: - order: 7 + order: 10 tags: ["Enterprise"] --- diff --git a/src/content/docs/aws/integrations/containers/openshift.md b/src/content/docs/aws/advanced-installation/kubernetes/openshift.md similarity index 99% rename from src/content/docs/aws/integrations/containers/openshift.md rename to src/content/docs/aws/advanced-installation/kubernetes/openshift.md index e432e67cb..be460aea5 100644 --- a/src/content/docs/aws/integrations/containers/openshift.md +++ b/src/content/docs/aws/advanced-installation/kubernetes/openshift.md @@ -3,7 +3,7 @@ title: OpenShift description: Use the OpenShift managed Kubernetes cluster to deploy LocalStack. template: doc sidebar: - order: 4 + order: 8 --- ## Introduction diff --git a/src/content/docs/aws/capabilities/localstack-docker-extension.md b/src/content/docs/aws/advanced-installation/localstack-docker-extension.md similarity index 100% rename from src/content/docs/aws/capabilities/localstack-docker-extension.md rename to src/content/docs/aws/advanced-installation/localstack-docker-extension.md diff --git a/src/content/docs/aws/capabilities/config/podman.md b/src/content/docs/aws/advanced-installation/podman.md similarity index 100% rename from src/content/docs/aws/capabilities/config/podman.md rename to src/content/docs/aws/advanced-installation/podman.md diff --git a/src/content/docs/aws/integrations/containers/rancher-desktop.mdx b/src/content/docs/aws/advanced-installation/rancher-desktop.mdx similarity index 100% rename from src/content/docs/aws/integrations/containers/rancher-desktop.mdx rename to src/content/docs/aws/advanced-installation/rancher-desktop.mdx diff --git a/src/content/docs/aws/capabilities/config/index.md b/src/content/docs/aws/capabilities/config/index.md deleted file mode 100644 index 363d4bbcd..000000000 --- a/src/content/docs/aws/capabilities/config/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Overview -description: This section describes the configuration options available for LocalStack, and how to configure them to suit your needs. -template: doc ---- - -LocalStack offers configuration options for customizing how services behave, how components interact, and how your local cloud environment is initialized. - -This section explains key configuration mechanisms (including environment variables, configuration files, and runtime hooks) along with internal features that let you adapt LocalStack to fit a variety of development and testing scenarios. - -The diagram below provides a high-level overview of what’s covered. - -![Understanding LocalStack configuration](/images/aws/understanding-localstack-overview.png) diff --git a/src/content/docs/aws/capabilities/config/internal-endpoints.md b/src/content/docs/aws/capabilities/config/internal-endpoints.md deleted file mode 100644 index 9ad73a3fe..000000000 --- a/src/content/docs/aws/capabilities/config/internal-endpoints.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Internal Endpoints -description: Overview of LocalStack and AWS specific internal endpoints for local development and testing -template: doc ---- - -LocalStack provides several internal endpoints for various local AWS services and LocalStack-specific features. -These endpoints are not part of the official AWS API and are available in the `/_localstack` and `/_aws` paths. -You can use [curl](https://curl.se/) or your favourite HTTP REST client to access endpoints. - -You can start your LocalStack instance and go to [http://localhost.localstack.cloud:4566/\_localstack/swagger](http://localhost.localstack.cloud:4566/_localstack/swagger) -to browse the Swagger UI, visualize and interact with all the API's resources implemented in LocalStack. - -### LocalStack endpoints - -The API path for the LocalStack internal resources is `/_localstack`. -Several endpoints are available under this path. -For instance, `/_localstack/health` checks the available and running AWS services in LocalStack while -`/_localstack/diagnose` (enable with the `DEBUG=1` configuration variable), reports extensive and sensitive data from -the LocalStack instance. - -:::note -You can use the `/_localstack/health` endpoint to restart or kill the services. -You can use [curl](https://curl.se/) or your HTTP REST client to access the endpoint: - -```bash -curl -v --request POST --header "Content-Type: application/json" --data '{"action":"restart"}' http://localhost.localstack.cloud:4566/_localstack/health -curl -v --request POST --header "Content-Type: application/json" --data '{"action":"kill"}' http://localhost.localstack.cloud:4566/_localstack/health -``` - -::: - -### AWS endpoints - -The API path for the AWS internal resources is `/_aws`. -These endpoints offer LocalStack-specific features in addition to the ones offered by the AWS services. -For instance, `/aws/services/sqs/messages` conveniently access all messages within a SQS queue, without deleting them. diff --git a/src/content/docs/aws/capabilities/index.mdx b/src/content/docs/aws/capabilities/index.mdx deleted file mode 100644 index 166147b2e..000000000 --- a/src/content/docs/aws/capabilities/index.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Overview -description: Configure your LocalStack installation in various ways, including configuration options, networking, SDKs, and extensions. -template: doc -editUrl: false -sidebar: - order: 5 ---- - -import SectionCards from '../../../../components/SectionCards.astro'; - -LocalStack provides a number of configuration options and supporting tools that help you set up and manage your local cloud environment. - -It brings together the configuration options that control LocalStack's behavior, networking setup for reaching your services, the LocalStack Web App, the LocalStack SDKs for programmatic access, and the extensions mechanism for adding new functionality. - -You will also find guides for several standalone tools: the [DNS Server](/aws/capabilities/dns-server), [Testing Utils](/aws/capabilities/testing-utils), the [LocalStack Docker Extension](/aws/capabilities/localstack-docker-extension), and [LocalSurf](/aws/capabilities/localsurf). - - diff --git a/src/content/docs/aws/capabilities/web-app/index.md b/src/content/docs/aws/capabilities/web-app/index.md deleted file mode 100644 index 823b15c5b..000000000 --- a/src/content/docs/aws/capabilities/web-app/index.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Overview -description: The LocalStack web app allows you to access additional features of LocalStack as well as to manage subscription and licenses, workspace members and permissions. -template: doc -sidebar: - order: 1 ---- - -The [LocalStack Web Application](https://app.localstack.cloud/) provides a visual interface for managing your LocalStack account and platform features. - -From here, you can handle subscriptions and licenses, explore your local cloud environment with the Resource Browser, enable powerful features like Cloud Pods and Extensions, view Stack Insights, and more. All in one place. diff --git a/src/content/docs/aws/integrations/continuous-integration/bitbucket.md b/src/content/docs/aws/ci-pipelines/bitbucket.md similarity index 100% rename from src/content/docs/aws/integrations/continuous-integration/bitbucket.md rename to src/content/docs/aws/ci-pipelines/bitbucket.md diff --git a/src/content/docs/aws/integrations/continuous-integration/circleci.md b/src/content/docs/aws/ci-pipelines/circleci.md similarity index 99% rename from src/content/docs/aws/integrations/continuous-integration/circleci.md rename to src/content/docs/aws/ci-pipelines/circleci.md index 941e4097d..50591c397 100644 --- a/src/content/docs/aws/integrations/continuous-integration/circleci.md +++ b/src/content/docs/aws/ci-pipelines/circleci.md @@ -92,7 +92,7 @@ workflows: To configure LocalStack use the `environment` key on the job level or a shell command, where the latter takes higher precedence. -Read more about the [configuration options](/aws/capabilities/config/configuration) of LocalStack. +Read more about the [configuration options](/aws/configuration/configuration-options) of LocalStack. #### Job level diff --git a/src/content/docs/aws/integrations/continuous-integration/codebuild.md b/src/content/docs/aws/ci-pipelines/codebuild.md similarity index 98% rename from src/content/docs/aws/integrations/continuous-integration/codebuild.md rename to src/content/docs/aws/ci-pipelines/codebuild.md index 766aa5c8c..1b71f939d 100644 --- a/src/content/docs/aws/integrations/continuous-integration/codebuild.md +++ b/src/content/docs/aws/ci-pipelines/codebuild.md @@ -56,7 +56,7 @@ phases: ### Configuration -Get know more about the LocalStack [config options](/aws/capabilities/config/configuration). +Get know more about the LocalStack [config options](/aws/configuration/configuration-options). #### Native Runner diff --git a/src/content/docs/aws/integrations/continuous-integration/github-actions.md b/src/content/docs/aws/ci-pipelines/github-actions.md similarity index 100% rename from src/content/docs/aws/integrations/continuous-integration/github-actions.md rename to src/content/docs/aws/ci-pipelines/github-actions.md diff --git a/src/content/docs/aws/integrations/continuous-integration/gitlab-ci.md b/src/content/docs/aws/ci-pipelines/gitlab-ci.md similarity index 100% rename from src/content/docs/aws/integrations/continuous-integration/gitlab-ci.md rename to src/content/docs/aws/ci-pipelines/gitlab-ci.md diff --git a/src/content/docs/aws/integrations/continuous-integration/index.md b/src/content/docs/aws/ci-pipelines/index.md similarity index 100% rename from src/content/docs/aws/integrations/continuous-integration/index.md rename to src/content/docs/aws/ci-pipelines/index.md diff --git a/src/content/docs/aws/integrations/continuous-integration/travis-ci.md b/src/content/docs/aws/ci-pipelines/travis-ci.md similarity index 100% rename from src/content/docs/aws/integrations/continuous-integration/travis-ci.md rename to src/content/docs/aws/ci-pipelines/travis-ci.md diff --git a/src/content/docs/aws/capabilities/config/arm64-support.md b/src/content/docs/aws/configuration/advanced/arm64-support.md similarity index 97% rename from src/content/docs/aws/capabilities/config/arm64-support.md rename to src/content/docs/aws/configuration/advanced/arm64-support.md index f306cc965..e25c95e61 100644 --- a/src/content/docs/aws/capabilities/config/arm64-support.md +++ b/src/content/docs/aws/configuration/advanced/arm64-support.md @@ -1,6 +1,8 @@ --- title: ARM64 Support description: Running LocalStack on ARM64 CPUs +sidebar: + order: 2 --- ## Introduction @@ -32,7 +34,7 @@ Since LocalStack 2.0, Lambda functions execute in Docker containers with th depending on the [instruction set architecture](https://docs.aws.amazon.com/lambda/latest/dg/foundation-arch.html) configured for the function (`x86_64` by default or `arm64`). This behavior can lead to errors if the host system, the Docker image, or the code/layer of the function do not support the target architecture. -If you prefer to execute Lambda functions on your native platform architecture, you can set the [Lambda configuration](https://docs.localstack.cloud/aws/capabilities/config/configuration/#lambda) variable to `LAMBDA_IGNORE_ARCHITECTURE=1`. +If you prefer to execute Lambda functions on your native platform architecture, you can set the [Lambda configuration](https://docs.localstack.cloud/aws/configuration/configuration-options/#lambda) variable to `LAMBDA_IGNORE_ARCHITECTURE=1`. Example scenario: I have an amd64 machine and want to run a an arm64 Lambda function. I know that the Lambda function runs on both architectures (i.e., no architecture specific code or dependencies). Host systems with [multi-architecture support](https://docs.docker.com/build/building/multi-platform/) can run containers for different Linux architectures using emulation. diff --git a/src/content/docs/aws/capabilities/config/cross-account-access.md b/src/content/docs/aws/configuration/advanced/cross-account-access.md similarity index 97% rename from src/content/docs/aws/capabilities/config/cross-account-access.md rename to src/content/docs/aws/configuration/advanced/cross-account-access.md index 1e3040527..6bc3eef4b 100644 --- a/src/content/docs/aws/capabilities/config/cross-account-access.md +++ b/src/content/docs/aws/configuration/advanced/cross-account-access.md @@ -1,6 +1,8 @@ --- title: 'Cross-Account and Cross-Region Access' description: Accessing resources in another account or region +sidebar: + order: 3 --- ## Introduction @@ -59,7 +61,7 @@ The full list of resources and operations that allow cross-account access are li :::tip LocalStack does not enforce IAM for cross-account access by default. -Use the `ENFORCE_IAM` [configuration](/aws/capabilities/config/configuration#iam) option to enable it. +Use the `ENFORCE_IAM` [configuration](/aws/configuration/configuration-options#iam) option to enable it. ::: ### EC2 Peering diff --git a/src/content/docs/aws/capabilities/config/filesystem.mdx b/src/content/docs/aws/configuration/advanced/filesystem.mdx similarity index 97% rename from src/content/docs/aws/capabilities/config/filesystem.mdx rename to src/content/docs/aws/configuration/advanced/filesystem.mdx index e10312d39..c61973a49 100644 --- a/src/content/docs/aws/capabilities/config/filesystem.mdx +++ b/src/content/docs/aws/configuration/advanced/filesystem.mdx @@ -2,6 +2,8 @@ title: Filesystem Layout description: Overview of runtime directory structure template: doc +sidebar: + order: 5 --- import { FileTree } from '@astrojs/starlight/components'; @@ -46,7 +48,7 @@ LocalStack uses following directory layout when running within a container. ### Configuration - `/etc/localstack`: configuration directory -- `/etc/localstack/init`: root directory for [initialization hooks](/aws/capabilities/config/initialization-hooks) +- `/etc/localstack/init`: root directory for [initialization hooks](/aws/configuration/advanced/initialization-hooks) ### Static libraries diff --git a/src/content/docs/aws/configuration/advanced/index.md b/src/content/docs/aws/configuration/advanced/index.md new file mode 100644 index 000000000..e711e0e87 --- /dev/null +++ b/src/content/docs/aws/configuration/advanced/index.md @@ -0,0 +1,18 @@ +--- +title: Overview +description: Advanced, power-user configuration topics for tailoring LocalStack to complex setups. +template: doc +editUrl: false +sidebar: + order: 1 +--- + +This section collects the more advanced, power-user configuration topics. Most users will not need to change these settings, but they are useful when you have complex requirements or are integrating LocalStack into a larger system. + +- [ARM64 Support](/aws/configuration/advanced/arm64-support) — run LocalStack on ARM64 CPUs. +- [Cross-Account and Cross-Region Access](/aws/configuration/advanced/cross-account-access) — access resources across accounts and regions. +- [Multi-Account Setups](/aws/configuration/advanced/multi-account-setups) — use LocalStack in multi-tenant setups. +- [Filesystem Layout](/aws/configuration/advanced/filesystem) — understand the runtime directory structure. +- [Initialization Hooks](/aws/configuration/advanced/initialization-hooks) — run shell or Python scripts to customize your instance. +- [Regions Coverage](/aws/configuration/advanced/regions-coverage) — the AWS regions LocalStack emulates. +- [Usage Tracking](/aws/configuration/advanced/usage-tracking) — what data LocalStack collects, and how to opt out. diff --git a/src/content/docs/aws/capabilities/config/initialization-hooks.mdx b/src/content/docs/aws/configuration/advanced/initialization-hooks.mdx similarity index 97% rename from src/content/docs/aws/capabilities/config/initialization-hooks.mdx rename to src/content/docs/aws/configuration/advanced/initialization-hooks.mdx index 263006501..0b40bb920 100644 --- a/src/content/docs/aws/capabilities/config/initialization-hooks.mdx +++ b/src/content/docs/aws/configuration/advanced/initialization-hooks.mdx @@ -3,6 +3,8 @@ title: Initialization Hooks description: Writing shell or Python scripts to customize or initialize your LocalStack instance. template: doc tags: ["Hobby"] +sidebar: + order: 6 --- import { Tabs, TabItem, FileTree } from '@astrojs/starlight/components'; @@ -34,7 +36,7 @@ All except `boot.d` will be run in the same Python interpreter as LocalStack, wh You can also use subdirectories to organize your init scripts. Currently, known script extensions are `.sh` and `.py`. -Additionally, with the installation of the `localstack-extension-terraform-init` [extension](/aws/capabilities/extensions/), `.tf` files can also be supported. +Additionally, with the installation of the `localstack-extension-terraform-init` [extension](/aws/integrations/extensions/), `.tf` files can also be supported. Shell scripts have to be executable, and have to have a [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) (usually `#!/bin/bash`). A script can be in one of four states: `UNKNOWN`, `RUNNING`, `SUCCESSFUL`, `ERROR`. @@ -165,7 +167,7 @@ Another use for init hooks can be seen when [adding custom TLS certificates to L ### Terraform Files as Init Hooks Running Terraform configuration files as init hooks requires the installation of a special extension. -For more information on how to manage [LocalStack extensions](/aws/capabilities/extensions/), please refer to the dedicated documentation page, +For more information on how to manage [LocalStack extensions](/aws/integrations/extensions/), please refer to the dedicated documentation page, and for more details on running init hooks in development mode, you can check out the [extension repository description](https://github.com/localstack/localstack-extensions/tree/main/terraform-init). Start LocalStack with **`EXTENSION_AUTO_INSTALL="localstack-extension-terraform-init"`**. @@ -258,4 +260,4 @@ If you are having issues with your initialization hooks not being executed, plea * If your script does not show up in the list of discovered init scripts, please check your Docker volume mount. Most likely the scripts are not properly mounted into the Docker container. * Are resources not being created? - * Ensure that AWS [credentials](/aws/capabilities/config/credentials) are set, e.g. through `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables. + * Ensure that AWS [credentials](/aws/connecting/credentials) are set, e.g. through `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables. diff --git a/src/content/docs/aws/capabilities/config/multi-account-setups.md b/src/content/docs/aws/configuration/advanced/multi-account-setups.md similarity index 95% rename from src/content/docs/aws/capabilities/config/multi-account-setups.md rename to src/content/docs/aws/configuration/advanced/multi-account-setups.md index 2086572d3..edecce812 100644 --- a/src/content/docs/aws/capabilities/config/multi-account-setups.md +++ b/src/content/docs/aws/configuration/advanced/multi-account-setups.md @@ -2,6 +2,8 @@ title: Multi-Account Setups description: Using LocalStack in multi-tenant setups template: doc +sidebar: + order: 4 --- :::note @@ -12,7 +14,7 @@ Please open a [GitHub Discussion](https://github.com/orgs/localstack/discussions LocalStack ships with multi-account support which allows namespacing based on AWS account ID. LocalStack uses the value in the AWS Access Key ID field for the purpose of namespacing over account ID. -For more information, see [Credentials](/aws/capabilities/config/credentials). +For more information, see [Credentials](/aws/connecting/credentials). The Access Key ID field can be configured in the AWS CLI in multiple ways: please refer to [AWS CLI documentation](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-precedence). diff --git a/src/content/docs/aws/capabilities/config/regions-coverage.md b/src/content/docs/aws/configuration/advanced/regions-coverage.md similarity index 99% rename from src/content/docs/aws/capabilities/config/regions-coverage.md rename to src/content/docs/aws/configuration/advanced/regions-coverage.md index 87d55411f..fb88fe31c 100644 --- a/src/content/docs/aws/capabilities/config/regions-coverage.md +++ b/src/content/docs/aws/configuration/advanced/regions-coverage.md @@ -1,6 +1,8 @@ --- title: "Regions Coverage" description: "This page lists the AWS Region Coverage for LocalStack's emulation of AWS services." +sidebar: + order: 7 --- ## Introduction diff --git a/src/content/docs/aws/capabilities/config/usage-tracking.md b/src/content/docs/aws/configuration/advanced/usage-tracking.md similarity index 97% rename from src/content/docs/aws/capabilities/config/usage-tracking.md rename to src/content/docs/aws/configuration/advanced/usage-tracking.md index 862ad7bea..24d71ed0c 100644 --- a/src/content/docs/aws/capabilities/config/usage-tracking.md +++ b/src/content/docs/aws/configuration/advanced/usage-tracking.md @@ -2,6 +2,8 @@ title: Usage Tracking description: Understand what data LocalStack collects and how you can opt out of usage tracking template: doc +sidebar: + order: 8 --- ## Overview @@ -12,7 +14,7 @@ It is tracked regardless of whether the user disables event tracking since we co ## LocalStack usage statistics -For Pro users, most of the information is collected to populate the [Stack Insights](/aws/capabilities/web-app/stack-insights) dashboard. +For Pro users, most of the information is collected to populate the [Stack Insights](/aws/team-workspaces/stack-insights) dashboard. Collecting basic anonymized usage of AWS services helps us better direct engineering efforts to services that are used the most or cause the most issues. ### Session information diff --git a/src/content/docs/aws/capabilities/config/configuration.md b/src/content/docs/aws/configuration/configuration-options.md similarity index 96% rename from src/content/docs/aws/capabilities/config/configuration.md rename to src/content/docs/aws/configuration/configuration-options.md index bf27084d4..5ff4585c1 100644 --- a/src/content/docs/aws/capabilities/config/configuration.md +++ b/src/content/docs/aws/configuration/configuration-options.md @@ -31,16 +31,16 @@ Options that affect the core LocalStack system. | `LOCALSTACK_HOST`| `localhost.localstack.cloud:4566` (default) | This is interpolated into URLs and addresses that are returned by LocalStack. It has the form `:`. | | `GATEWAY_LISTEN` | `0.0.0.0:4566` (default in Docker mode), `127.0.0.1:4566` (default in host mode) | Configures the bind addresses of LocalStack. It has the form `:(,:)*`. LocalStack for AWS adds port `443`. | | `USE_SSL` | `0` (default) | Whether to return URLs using HTTP (`0`) or HTTPS (`1`). Changed with 3.0.0. In earlier versions this was toggling SSL support on or off. | -| `PERSISTENCE` | `0` (default) | Enable persistence. See [Persistence Mechanism](/aws/developer-tools/snapshots/persistence) and [Filesystem Layout](/aws/capabilities/config/filesystem). | +| `PERSISTENCE` | `0` (default) | Enable persistence. See [Persistence Mechanism](/aws/developer-tools/snapshots/persistence) and [Filesystem Layout](/aws/configuration/advanced/filesystem). | | `MAIN_CONTAINER_NAME` | `localstack-main` (default) | Specify the main docker container name | | `LS_LOG` | `trace`, `trace-internal`, `debug`, `info`, `warn`, `error`, `warning`| Specify the log level. Currently overrides the `DEBUG` configuration. `trace` for detailed request/response, `trace-internal` for internal calls, too. | -| `EXTERNAL_SERVICE_PORTS_START` | `4510` (default) | Start of the [External Service Port Range](/aws/capabilities/networking/external-port-range) (inclusive). | -| `EXTERNAL_SERVICE_PORTS_END` | `4560` (default) | End of the [External Service Port Range](/aws/capabilities/networking/external-port-range) (exclusive). | +| `EXTERNAL_SERVICE_PORTS_START` | `4510` (default) | Start of the [External Service Port Range](/aws/configuration/networking/external-port-range) (inclusive). | +| `EXTERNAL_SERVICE_PORTS_END` | `4560` (default) | End of the [External Service Port Range](/aws/configuration/networking/external-port-range) (exclusive). | | `EAGER_SERVICE_LOADING` | `0` (default) \|`1` | Boolean that toggles lazy loading of services. If eager loading is enabled, services are started at LocalStack startup rather than their first use. Be aware that eager loading increases the LocalStack startup time. | -| `SERVICES`| `s3,sqs` | A comma-delimited string of services. Check the [internal health endpoint](/aws/capabilities/networking/internal-endpoints#localstack-endpoints) `/_localstack/health` for valid service names. If `SERVICES` is set LocalStack will only load the listed services. All other services will be disabled and cannot be used. | +| `SERVICES`| `s3,sqs` | A comma-delimited string of services. Check the [internal health endpoint](/aws/configuration/networking/internal-endpoints#localstack-endpoints) `/_localstack/health` for valid service names. If `SERVICES` is set LocalStack will only load the listed services. All other services will be disabled and cannot be used. | | `ALLOW_NONSTANDARD_REGIONS` | `0` (default) | Allows the use of non-standard AWS regions. By default, LocalStack only accepts [standard AWS regions](https://docs.aws.amazon.com/general/latest/gr/rande.html). | | `PARITY_AWS_ACCESS_KEY_ID` | `0` (default) | Enables the use production-like access key IDs. By default, LocalStack issues keys with `LSIA...` and `LKIA...` prefix, and will reject keys that start with `ASIA...` or `AKIA...`. | -| `LOCALSTACK_RESPONSE_HEADER_ENABLED` | `1` (default) \| `0` | Whether LocalStack adds the [`x-localstack` response header](/aws/capabilities/networking/internal-endpoints#x-localstack-response-header) to every AWS API response. The header value is the LocalStack version and lets client tools detect LocalStack and its version. | +| `LOCALSTACK_RESPONSE_HEADER_ENABLED` | `1` (default) \| `0` | Whether LocalStack adds the [`x-localstack` response header](/aws/configuration/networking/internal-endpoints#x-localstack-response-header) to every AWS API response. The header value is the LocalStack version and lets client tools detect LocalStack and its version. | ## CLI @@ -48,7 +48,7 @@ These options are applicable when using the CLI to start LocalStack. | Variable | Example Values | Description | | - | - | - | -| `LOCALSTACK_VOLUME_DIR` | `~/.cache/localstack/volume` (on Linux) | The location on the host of the LocalStack volume directory mount. See [Filesystem Layout](/aws/capabilities/config/filesystem#using-the-cli) | +| `LOCALSTACK_VOLUME_DIR` | `~/.cache/localstack/volume` (on Linux) | The location on the host of the LocalStack volume directory mount. See [Filesystem Layout](/aws/configuration/advanced/filesystem#using-the-cli) | | `CONFIG_PROFILE` | | The configuration profile to load. See [Profiles](#profiles) | | `CONFIG_DIR` | `~/.localstack` | The path where LocalStack can find configuration profiles and other CLI-specific configuration | @@ -263,8 +263,8 @@ Please consult the [migration guide](/aws/services/lambda#migrating-to-lambda-v2 | `BUCKET_MARKER_LOCAL` | `hot-reload` (default) | Magic S3 bucket name for [Hot Reloading](/aws/developer-tools/lambda-tools/hot-reloading). The S3Key points to the source code on the local file system. | | `HOSTNAME_FROM_LAMBDA` | `localstack` | Endpoint host under which APIs are accessible from Lambda containers (optional). This can be useful in docker-compose stacks to use the local container hostname if neither IP address nor container name of the main container are available (e.g., in CI). Often used in combination with `LAMBDA_DOCKER_NETWORK`.| | `LAMBDA_DISABLE_AWS_ENDPOINT_URL` | `0` (default) \| `1` | Whether to disable injecting the environment variable `AWS_ENDPOINT_URL`, which automatically configures [supported AWS SDKs](https://docs.aws.amazon.com/sdkref/latest/guide/feature-ss-endpoints.html). | -| `LAMBDA_DISABLE_JAVA_SDK_V2_CERTIFICATE_VALIDATION` | `1` (default) | Whether to disable the certificate name validation for [AWS Java SDK v2](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/home.html) calls when using [transparent endpoint injection](/aws/capabilities/networking/transparent-endpoint-injection).| -| `LAMBDA_DOCKER_DNS` | `""` (default) | Optional custom DNS server for the container running your Lambda function. Overwrites the default LocalStack [DNS Server](/aws/capabilities/dns-server). Hence, resolving `localhost.localstack.cloud` requires additional configuration. | +| `LAMBDA_DISABLE_JAVA_SDK_V2_CERTIFICATE_VALIDATION` | `1` (default) | Whether to disable the certificate name validation for [AWS Java SDK v2](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/home.html) calls when using [transparent endpoint injection](/aws/configuration/networking/transparent-endpoint-injection).| +| `LAMBDA_DOCKER_DNS` | `""` (default) | Optional custom DNS server for the container running your Lambda function. Overwrites the default LocalStack [DNS Server](/aws/configuration/networking/dns-server). Hence, resolving `localhost.localstack.cloud` requires additional configuration. | | `LAMBDA_DOCKER_FLAGS` | `-e KEY=VALUE`, `-v host:container`, `-p host:container`, `--add-host domain:ip` | Additional flags passed to Docker `run`\|`create` commands. Supports environment variables (also with `--env-file`, but the file has to be mounted into the LocalStack container), ports, volume mounts, extra hosts, networks, DNS servers, labels, ulimits, user, platform, and privileged mode. The `--env-file` argument for Docker `run` and Docker Compose have different feature sets. To provide both, we support the `--env-file` for environment files with the docker run syntax, while `--compose-env-file` supports the full docker compose features, like placeholders with `${}`, replacing quotes, etc. | | `LAMBDA_DOCKER_NETWORK` | `bridge` (Docker default) | [Docker network driver](https://docs.docker.com/network/) for the Lambda and ECS containers. Needs to be set to the network the LocalStack container is connected to. Limitation: `host` mode currently not supported. | | `LAMBDA_DOWNLOAD_AWS_LAYERS` | `1` (default, pro) | Whether to download public Lambda layers from AWS through a LocalStack proxy when creating or updating functions. | @@ -416,8 +416,8 @@ To learn more about these configuration options, see [Cloud Pods](/aws/developer | Variable | Example Values | Description | | - | - | - | -| `EXTENSION_AUTO_INSTALL` | | Install a list of extensions automatically at startup. Comma-separated list of extensions directives which will be installed automatically at startup (see [managing extensions](/aws/capabilities/extensions/managing-extensions#automating-extensions-installation))| -| `EXTENSION_DEV_MODE` | `0` (default) \| `1` | Enables development mode for extensions. Refer to the [Extensions Development Guide](/aws/capabilities/extensions/developing-extensions) for more information. | +| `EXTENSION_AUTO_INSTALL` | | Install a list of extensions automatically at startup. Comma-separated list of extensions directives which will be installed automatically at startup (see [managing extensions](/aws/integrations/extensions/managing-extensions#automating-extensions-installation))| +| `EXTENSION_DEV_MODE` | `0` (default) \| `1` | Enables development mode for extensions. Refer to the [Extensions Development Guide](/aws/integrations/extensions/developing-extensions) for more information. | ## Miscellaneous @@ -443,21 +443,21 @@ To learn more about these configuration options, see [Cloud Pods](/aws/developer ## DNS -To learn more about these configuration options, see [DNS Server](/aws/capabilities/dns-server). +To learn more about these configuration options, see [DNS Server](/aws/configuration/networking/dns-server). | Variable | Example Values | Description | | - | - | - | | `DNS_ADDRESS` | `0.0.0.0` (default) | Address the LocalStack should bind the DNS server on (port 53 tcp/udp). Value `0` to disable. | `DNS_SERVER` | Default upstream DNS or `8.8.8.8` (default) | Fallback DNS server for queries not handled by LocalStack. | `DNS_RESOLVE_IP` | `127.0.0.1` (default) | IP address the DNS server should return as A record for queries handled by LocalStack. If customized, this value will be returned in preference to the DNS server response. -| `DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM` | `([^.]+\.)*(ecr\|lambda)\.[^.]+\.amazonaws\.com` (example) | List of domain names that should *NOT* be redirected by the LocalStack DNS to the LocalStack container, but instead always forwarded to the upstream resolver. This will *NOT* redirect requests made to LocalStack due to manual endpoint configuration. Comma-separated list of Python-flavored regex patterns. See [the DNS server documentation](/aws/capabilities/dns-server#skip-localstack-dns-resolution) for more details. +| `DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM` | `([^.]+\.)*(ecr\|lambda)\.[^.]+\.amazonaws\.com` (example) | List of domain names that should *NOT* be redirected by the LocalStack DNS to the LocalStack container, but instead always forwarded to the upstream resolver. This will *NOT* redirect requests made to LocalStack due to manual endpoint configuration. Comma-separated list of Python-flavored regex patterns. See [the DNS server documentation](/aws/configuration/networking/dns-server#skip-localstack-dns-resolution) for more details. | `DNS_LOCAL_NAME_PATTERNS` | `([^.]+\.)*(ecr\|lambda)\.[^.]+\.amazonaws\.com` (example) | **Deprecated since 3.0.2** List of domain names that should *NOT* be redirected by the LocalStack DNS to the LocalStack container, but instead always forwarded to the upstream resolver. This will *NOT* redirect requests made to LocalStack due to manual endpoint configuration. Comma-separated list of Python-flavored regex patterns. **Renamed to `DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM`** ## Transparent Endpoint Injection | Variable | Example Values | Description | | - | - | - | -| `DISABLE_TRANSPARENT_ENDPOINT_INJECTION` | `0` (default in Pro) \| `1` | Whether to disable DNS resolution of AWS hostnames to the LocalStack container. Pro feature. (see [Transparent Endpoint Injection](/aws/capabilities/networking/transparent-endpoint-injection)) +| `DISABLE_TRANSPARENT_ENDPOINT_INJECTION` | `0` (default in Pro) \| `1` | Whether to disable DNS resolution of AWS hostnames to the LocalStack container. Pro feature. (see [Transparent Endpoint Injection](/aws/configuration/networking/transparent-endpoint-injection)) ## LocalStack for AWS @@ -465,7 +465,7 @@ To learn more about these configuration options, see [DNS Server](/aws/capabilit |----------------------|----------------|-------------| | `ACTIVATE_PRO` | `0` \| `1` (default) | Whether Pro should be activated or not. This is set to true by default if using the `localstack/localstack-pro` container image. If set to `1`, LocalStack will fail to start if the license key activation did not work. If set to `0`, an attempt is made to start LocalStack without Pro features. | | `LOCALSTACK_AUTH_TOKEN` | | [Auth token](/aws/getting-started/auth-token) to activate LocalStack for AWS. | -| `LOCALSTACK_API_KEY` | | **Deprecated since 3.0.0** API key to activate LocalStack for AWS.
**Use the `LOCALSTACK_AUTH_TOKEN` instead (except for [CI environments](/aws/integrations/continuous-integration/)).** | +| `LOCALSTACK_API_KEY` | | **Deprecated since 3.0.0** API key to activate LocalStack for AWS.
**Use the `LOCALSTACK_AUTH_TOKEN` instead (except for [CI environments](/aws/ci-pipelines/)).** | | `LOG_LICENSE_ISSUES` | `0` \| `1` (default) | Whether to log issues with the license activation to the console. | ## Legacy @@ -523,9 +523,9 @@ These configurations have already been removed and **won't have any effect** on | `DATA_DIR`| 2.0.0 | blank (disabled/default), `/tmp/localstack/data` | Local directory for saving persistent data. Use `PERSISTENCE` instead. | | `DISABLE_TERM_HANDLER` | 2.0.0 | `""` (default) \| `1` | Whether to disable signal passing to LocalStack when running in docker. Enabling this will prevent an orderly shutdown when running inside LS in docker. Setting this to anything else than an empty string will disable it. | `HOST_TMP_FOLDER` | 2.0.0 | `/some/path` | Temporary folder on the host that gets mounted as `$TMPDIR/localstack` into the LocalStack container. Required only for Lambda volume mounts when using `LAMBDA_REMOTE_DOCKER=false.` | -| `INIT_SCRIPTS_PATH` | 2.0.0 | `/some/path` | Before 1.0, this was used to configure the path to the initializing files with extensions `.sh` that were found in `/docker-entrypoint-initaws.d`. This has been replaced by the [init-hook system](/aws/capabilities/config/initialization-hooks/). | -| `LEGACY_DIRECTORIES` | 2.0.0 | `0` (default) | Use legacy method of managing internal filesystem layout. See [Filesystem Layout](/aws/capabilities/config/filesystem). | -| `LEGACY_INIT_DIR` | 2.0.0 | `1` \| `0`(default) | Used with `INIT_SCRIPTS_PATH`. This has been replaced by the [init-hook system](/aws/capabilities/config/initialization-hooks). | +| `INIT_SCRIPTS_PATH` | 2.0.0 | `/some/path` | Before 1.0, this was used to configure the path to the initializing files with extensions `.sh` that were found in `/docker-entrypoint-initaws.d`. This has been replaced by the [init-hook system](/aws/configuration/advanced/initialization-hooks/). | +| `LEGACY_DIRECTORIES` | 2.0.0 | `0` (default) | Use legacy method of managing internal filesystem layout. See [Filesystem Layout](/aws/configuration/advanced/filesystem). | +| `LEGACY_INIT_DIR` | 2.0.0 | `1` \| `0`(default) | Used with `INIT_SCRIPTS_PATH`. This has been replaced by the [init-hook system](/aws/configuration/advanced/initialization-hooks). | | `MULTI_ACCOUNTS` | 2.0.0 | `0` (default) | Enable multi-accounts (preview) | | `SQS_PROVIDER` | 2.0.0 | `moto` (default) and `elasticmq` | | | `SYNCHRONOUS_API_GATEWAY_EVENTS` | 2.0.0 | `1` (default) \| `0` | Whether or not to handle API Gateway Lambda event sources as synchronous invocations. | diff --git a/src/content/docs/aws/configuration/index.mdx b/src/content/docs/aws/configuration/index.mdx new file mode 100644 index 000000000..8576ae1b2 --- /dev/null +++ b/src/content/docs/aws/configuration/index.mdx @@ -0,0 +1,25 @@ +--- +title: Overview +description: Configure how the LocalStack emulator behaves, including configuration options, logging, networking, and advanced features. +template: doc +editUrl: false +--- + +import SectionCards from '../../../../components/SectionCards.astro'; + +LocalStack provides a wide range of options for configuring how the emulator behaves. Most users are well served by the defaults, but as your needs grow you can fine-tune everything from logging verbosity to networking and low-level runtime behavior. + +This section brings together the settings that control LocalStack itself: + +- **[Configuration Options](/aws/configuration/configuration-options)** — the complete reference of environment variables and flags that change how LocalStack starts and runs. +- **[Logging](/aws/configuration/logging)** — control log output and debugging verbosity. +- **Networking** — how LocalStack exposes endpoints, resolves DNS, and integrates with your local network. +- **Advanced Features** — power-user topics such as multi-account setups, initialization hooks, and filesystem layout. + + diff --git a/src/content/docs/aws/capabilities/config/logging.md b/src/content/docs/aws/configuration/logging.md similarity index 94% rename from src/content/docs/aws/capabilities/config/logging.md rename to src/content/docs/aws/configuration/logging.md index 3cc2a8b49..6f76e70ea 100644 --- a/src/content/docs/aws/capabilities/config/logging.md +++ b/src/content/docs/aws/configuration/logging.md @@ -63,5 +63,5 @@ With Docker/Docker-Compose, you can run `docker ps` to get the container ID of t To view the logs via a user interface, you can use the following options: -- [LocalStack Desktop](/aws/capabilities/web-app/localstack-desktop/) -- [LocalStack Docker Extension](/aws/capabilities/localstack-docker-extension/) +- [LocalStack Desktop](/aws/developer-tools/running-localstack/localstack-desktop/) +- [LocalStack Docker Extension](/aws/advanced-installation/localstack-docker-extension/) diff --git a/src/content/docs/aws/capabilities/networking/accessing-endpoint-url.mdx b/src/content/docs/aws/configuration/networking/accessing-endpoint-url.mdx similarity index 97% rename from src/content/docs/aws/capabilities/networking/accessing-endpoint-url.mdx rename to src/content/docs/aws/configuration/networking/accessing-endpoint-url.mdx index 056d0d557..55d7a6ad8 100644 --- a/src/content/docs/aws/capabilities/networking/accessing-endpoint-url.mdx +++ b/src/content/docs/aws/configuration/networking/accessing-endpoint-url.mdx @@ -20,10 +20,10 @@ While the LocalStack CLI does this automatically, when running the Docker contai Check out the [getting started documentation](/aws/getting-started/installation) for more information. :::tip -If you bind a domain name to `localhost`, ensure that you are not subject to [DNS rebind protection](/aws/capabilities/dns-server#dns-rebind-protection). +If you bind a domain name to `localhost`, ensure that you are not subject to [DNS rebind protection](/aws/configuration/networking/dns-server#dns-rebind-protection). ::: -You can also use the `GATEWAY_LISTEN` [configuration variable](/aws/capabilities/config/configuration) to change the exposed port if necessary. +You can also use the `GATEWAY_LISTEN` [configuration variable](/aws/configuration/configuration-options) to change the exposed port if necessary. ## From a container LocalStack created diff --git a/src/content/docs/aws/capabilities/networking/accessing-resources-created.md b/src/content/docs/aws/configuration/networking/accessing-resources-created.md similarity index 90% rename from src/content/docs/aws/capabilities/networking/accessing-resources-created.md rename to src/content/docs/aws/configuration/networking/accessing-resources-created.md index 63fd17a70..5997c6fac 100644 --- a/src/content/docs/aws/capabilities/networking/accessing-resources-created.md +++ b/src/content/docs/aws/configuration/networking/accessing-resources-created.md @@ -9,7 +9,7 @@ sidebar: If you have created a resource using LocalStack, such as an OpenSearch cluster or RDS database, you may need to access it from your application. Typically, these resources are accessible through a URL or a hostname provided by LocalStack. By default, LocalStack returns the hostname `localhost.localstack.cloud`, which resolves to LocalStack using DNS. -For special environments (e.g., proxies), the [configuration](/aws/capabilities/config/configuration) `LOCALSTACK_HOST` customizes the URLs returned by LocalStack. +For special environments (e.g., proxies), the [configuration](/aws/configuration/configuration-options) `LOCALSTACK_HOST` customizes the URLs returned by LocalStack. This guide will explore different scenarios and provide detailed instructions on accessing resources created by LocalStack under different scenarios. ## From your host @@ -24,7 +24,7 @@ Check out the [service-specific documentation](/aws/services) for more details. ![Accessing a resource created by LocalStack from a container created by LocalStack](/images/aws/6.svg) -Check out our documentation while [using the endpoint URL](/aws/capabilities/networking/accessing-endpoint-url). +Check out our documentation while [using the endpoint URL](/aws/configuration/networking/accessing-endpoint-url).
For LocalStack versions before 2.3.0 @@ -37,7 +37,7 @@ In that case, you can set the HOSTNAME_FROM_LAMBDA environment vari ![Accessing a resource created by LocalStack from a Docker container](/images/aws/9.svg) -Check out our documentation [on using the endpoint URL](/aws/capabilities/networking/accessing-endpoint-url#from-your-container). +Check out our documentation [on using the endpoint URL](/aws/configuration/networking/accessing-endpoint-url#from-your-container). ## From a separate host diff --git a/src/content/docs/aws/capabilities/dns-server.md b/src/content/docs/aws/configuration/networking/dns-server.md similarity index 97% rename from src/content/docs/aws/capabilities/dns-server.md rename to src/content/docs/aws/configuration/networking/dns-server.md index 7c303c5f3..90875b11a 100644 --- a/src/content/docs/aws/capabilities/dns-server.md +++ b/src/content/docs/aws/configuration/networking/dns-server.md @@ -3,16 +3,18 @@ title: DNS Server description: Use LocalStack as DNS server to resolve AWS queries to LocalStack. template: doc tags: ["Hobby"] +sidebar: + order: 7 --- LocalStack includes a DNS server that enables seamless connectivity to LocalStack from different environments using `localhost.localstack.cloud`. The DNS server is available on all IPv4 addresses within the LocalStack container (i.e., listening to `0.0.0.0`) and resolves `localhost.localstack.cloud` to the LocalStack container. Therefore, containers that are configured to use the DNS server can reach LocalStack using `localhost.localstack.cloud`. This configuration happens automatically for containers created by LocalStack, including compute resources such as Lambda, ECS, and EC2. -Your container can be configured to use the DNS server as demonstrated in the [Network Troubleshooting guide](/aws/capabilities/networking/accessing-endpoint-url/#from-the-same-computer). +Your container can be configured to use the DNS server as demonstrated in the [Network Troubleshooting guide](/aws/configuration/networking/accessing-endpoint-url/#from-the-same-computer). If you wish to use the DNS server on your host system, follow the instructions under [System DNS configuration](#system-dns-configuration). -LocalStack for AWS additionally offers [Transparent Endpoint Injection](/aws/capabilities/networking/transparent-endpoint-injection/) (active by default), +LocalStack for AWS additionally offers [Transparent Endpoint Injection](/aws/configuration/networking/transparent-endpoint-injection/) (active by default), which enables seamless connectivity to LocalStack without changing your application code targeting AWS. The DNS server resolves AWS domains such as `*.amazonaws.com` including subdomains to the LocalStack container. Therefore, your application seamlessly accesses the LocalStack APIs instead of the real AWS APIs. @@ -69,7 +71,7 @@ We do not recommend disabling the DNS server since this disables resolving `loca ### LocalStack endpoints If you operate behind an enterprise proxy and wish to customize the domain name returned by LocalStack services (e.g., SQS queue URL), -check out the [Configuration](/aws/capabilities/config/configuration#core) `LOCALSTACK_HOST`. +check out the [Configuration](/aws/configuration/configuration-options#core) `LOCALSTACK_HOST`. If you wish to customize internal LocalStack DNS routing of `localhost.localstack.cloud`, refer to the instructions in the [Route53 documentation](/aws/services/route53#customizing-internal-endpoint-resolution). diff --git a/src/content/docs/aws/capabilities/networking/external-port-range.mdx b/src/content/docs/aws/configuration/networking/external-port-range.mdx similarity index 100% rename from src/content/docs/aws/capabilities/networking/external-port-range.mdx rename to src/content/docs/aws/configuration/networking/external-port-range.mdx diff --git a/src/content/docs/aws/capabilities/networking/https-tls-support.mdx b/src/content/docs/aws/configuration/networking/https-tls-support.mdx similarity index 90% rename from src/content/docs/aws/capabilities/networking/https-tls-support.mdx rename to src/content/docs/aws/configuration/networking/https-tls-support.mdx index 568bda077..92f07c404 100644 --- a/src/content/docs/aws/capabilities/networking/https-tls-support.mdx +++ b/src/content/docs/aws/configuration/networking/https-tls-support.mdx @@ -3,7 +3,7 @@ title: HTTPS/TLS Support description: Overview of TLS certificate coverage for the `localhost.localstack.cloud` domain and supported AWS regions for secure HTTPS access to LocalStack service endpoints. template: doc sidebar: - order: 7 + order: 8 --- ## Introduction @@ -15,7 +15,7 @@ https://s3.us-east-1.localhost.localstack.cloud:4566 ``` These certificates enable proper hostname validation for supported AWS regions when using HTTPS with SDKs, the AWS CLI, browsers, and other tools. -If LocalStack runs behind a corporate proxy that interferes with fetching the public certificate, you can set [`SSL_NO_VERIFY=1`](/aws/capabilities/config/configuration#miscellaneous) to disable TLS verification when downloading the certificate from `localhost.localstack.cloud`. +If LocalStack runs behind a corporate proxy that interferes with fetching the public certificate, you can set [`SSL_NO_VERIFY=1`](/aws/configuration/configuration-options#miscellaneous) to disable TLS verification when downloading the certificate from `localhost.localstack.cloud`. ### Supported Regions diff --git a/src/content/docs/aws/capabilities/networking/index.mdx b/src/content/docs/aws/configuration/networking/index.mdx similarity index 63% rename from src/content/docs/aws/capabilities/networking/index.mdx rename to src/content/docs/aws/configuration/networking/index.mdx index 5445939a0..91eed2a16 100644 --- a/src/content/docs/aws/capabilities/networking/index.mdx +++ b/src/content/docs/aws/configuration/networking/index.mdx @@ -18,86 +18,86 @@ Choose the scenario below that best describes your networking layout. Whether yo LocalStack only binds to IPv4 addresses (e.g. `127.0.0.1`). Make sure you're not trying to access LocalStack over IPv6. ::: -## [Using the endpoint URL](/aws/capabilities/networking/accessing-endpoint-url) +## [Using the endpoint URL](/aws/configuration/networking/accessing-endpoint-url) For example, setting the `endpoint_url` parameter with an [AWS SDK](/aws/connecting/aws-sdks/). :::note -TLS certificates for `localhost.localstack.cloud` support only certain AWS regions. See [TLS Certificate Coverage](/aws/capabilities/networking/https-tls-support) for details. +TLS certificates for `localhost.localstack.cloud` support only certain AWS regions. See [TLS Certificate Coverage](/aws/configuration/networking/https-tls-support) for details. ::: -## [Using transparent endpoint injection](/aws/capabilities/networking/transparent-endpoint-injection) +## [Using transparent endpoint injection](/aws/configuration/networking/transparent-endpoint-injection) For example, you have a Lambda function that needs to access LocalStack resources. -## [Accessing a resource created by LocalStack](/aws/capabilities/networking/accessing-resources-created) +## [Accessing a resource created by LocalStack](/aws/configuration/networking/accessing-resources-created) For example, you have created an OpenSearch cluster and are trying to access that resource by its URL. @@ -575,7 +575,7 @@ The process is the following: Unless explicitly specified, all Cloud Pods commands default to targeting the LocalStack Platform as the storage remote. It's important to note that the CLI must be authenticated correctly with our Platform. -Custom remote configurations are stored within the [LocalStack volume directory](/aws/capabilities/config/filesystem/#localstack-volume-directory) and are managed by the LocalStack container. +Custom remote configurations are stored within the [LocalStack volume directory](/aws/configuration/advanced/filesystem/#localstack-volume-directory) and are managed by the LocalStack container. Consequently, when sharing Cloud Pods among your team using a custom remote, each team member must define the identical remote configuration. Once added, a remote persists even after LocalStack restarts. @@ -590,7 +590,7 @@ The available strategies are: - `service-merge`: This strategy merges services at the account-region level, provided there's no overlap in resources. It prioritizes the loaded resources when merging. -The LocalStack's default merge strategy can be changed via the `MERGE_STRATEGY` [configuration variable](/aws/capabilities/config/configuration/). +The LocalStack's default merge strategy can be changed via the `MERGE_STRATEGY` [configuration variable](/aws/configuration/configuration-options/). ### LocalStack CLI @@ -750,4 +750,4 @@ If you're still unable to connect to the S3 bucket, add the bucket hostname to t DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM=ls-pods-bucket-test.s3.amazonaws.com/ ``` -For more details, see the [Skip LocalStack DNS Resolution](/aws/capabilities/dns-server/#skip-localstack-dns-resolution) section. \ No newline at end of file +For more details, see the [Skip LocalStack DNS Resolution](/aws/configuration/networking/dns-server/#skip-localstack-dns-resolution) section. \ No newline at end of file diff --git a/src/content/docs/aws/enterprise/index.mdx b/src/content/docs/aws/enterprise/index.mdx deleted file mode 100644 index 3d35d2268..000000000 --- a/src/content/docs/aws/enterprise/index.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Overview -description: LocalStack Enterprise provides the most sophisticated and secure setup we offer, with advanced features and capabilities for large organizations and teams. -template: doc -editUrl: false -sidebar: - order: 1 ---- - -import SectionCards from '../../../../components/SectionCards.astro'; - -LocalStack Enterprise provides advanced features and deployment options for teams operating at scale. This section includes guides and resources to help you get the most out of your Enterprise subscription, such as setting up air-gapped environments to integrate with Kubernetes or configuring SSO. - -Explore how to: - -- Run LocalStack in secure or offline setups with a custom Enterprise Image -- Set up Single Sign-On (SSO) across identity providers -- Deploy LocalStack into Kubernetes with the Kubernetes Operator and Executor -- Access tailored support options as an Enterprise customer - - diff --git a/src/content/docs/aws/getting-started/auth-token.mdx b/src/content/docs/aws/getting-started/auth-token.mdx index b71c45a14..f21fc167d 100644 --- a/src/content/docs/aws/getting-started/auth-token.mdx +++ b/src/content/docs/aws/getting-started/auth-token.mdx @@ -106,7 +106,7 @@ You have the option to run your LocalStack container in the background by append The `localstack` CLI automatically detects the Auth Token and appropriately conveys it to the LocalStack container. :::note -If you are using LocalStack with an Auth Token, it's necessary to download the [LocalStack for AWS image](/aws/capabilities/config/docker-images#localstack-for-aws-image), which includes Pro services and several advanced features. +If you are using LocalStack with an Auth Token, it's necessary to download the [LocalStack for AWS image](/aws/advanced-installation/docker-images#localstack-for-aws-image), which includes Pro services and several advanced features. ::: ### Docker @@ -143,7 +143,7 @@ Developer Auth Tokens cannot be used in CI. CI Auth Tokens are available on the [Auth Tokens page](https://app.localstack.cloud/workspace/auth-tokens) and are configured similarly to Developer Auth Tokens. To set the CI Auth Token, add the Auth Token value in the `LOCALSTACK_AUTH_TOKEN` environment variable of your CI provider, and refer to it when starting LocalStack in your CI workflow. -You can find detailed examples in our [LocalStack in CI documentation](/aws/integrations/continuous-integration/). +You can find detailed examples in our [LocalStack in CI documentation](/aws/ci-pipelines/). ## Rotating the Auth Token @@ -159,7 +159,7 @@ To rotate your Auth Token, go to the [Auth Token page](https://app.localstack.cl ## Licensing configuration & activation checkup To avoid logging any licensing-related error messages, set `LOG_LICENSE_ISSUES=0` in your environment. -Refer to our [configuration guide](/aws/capabilities/config/configuration/#localstack-for-aws) for more information. +Refer to our [configuration guide](/aws/configuration/configuration-options/#localstack-for-aws) for more information. The simplest method to verify if LocalStack is active is by querying the health endpoint for a list of running services: diff --git a/src/content/docs/aws/getting-started/faq.mdx b/src/content/docs/aws/getting-started/faq.mdx index f8ee9d831..4dd2c7ce3 100644 --- a/src/content/docs/aws/getting-started/faq.mdx +++ b/src/content/docs/aws/getting-started/faq.mdx @@ -19,7 +19,7 @@ To resolve the issue follow the steps: This can be done by deleting the cached certificate file. For example, on Linux systems, you can locate and remove the file at `~/.cache/localstack/volume/cache/server.test.pem`. The exact path may differ depending on your operating system and how you've started LocalStack. - Please refer to our [documentation](/aws/capabilities/config/filesystem/#localstack-volume-directory) for specific instructions. + Please refer to our [documentation](/aws/configuration/advanced/filesystem/#localstack-volume-directory) for specific instructions. **Workarounds for older (<v3.7.0) LocalStack versions:** @@ -184,7 +184,7 @@ If the container can reach the internet generally but not LocalStack endpoints s Using LocalStack inside a Docker network with multiple other containers can lead to connectivity issues from/to those containers. For example, a container which attempts to deploy a stack and interact with the services directly, from within the same Docker network. -Refer to our [network troubleshooting guide](/aws/capabilities/networking/) covering several scenarios. +Refer to our [network troubleshooting guide](/aws/configuration/networking/) covering several scenarios. ### How to resolve the pull rate limit issue for LocalStack's Docker image? @@ -315,7 +315,7 @@ The CLI also supports a `--debug` flag that prints host-side debug output (host localstack --debug start ``` -See the [Logging reference](/aws/capabilities/config/logging/) for the full list of log-related options. +See the [Logging reference](/aws/configuration/logging/) for the full list of log-related options. ### How do I capture and share LocalStack container logs for troubleshooting? @@ -390,7 +390,7 @@ Common causes: ``` 3. **The billing system has not yet activated your renewal.** Check the subscription status at [app.localstack.cloud/account/subscriptions](https://app.localstack.cloud/account/subscriptions). If the subscription is paid but still shows `EXPIRED`, open a support ticket with your workspace name and the last four characters of the auth token. -4. **Wrong license type assigned.** Sometimes a user is on an expired Trial or Hobby license. Unassign the old license and assign a paid one — see [Managing users and licenses](/aws/capabilities/web-app/managing-users-licenses/#managing-licenses). +4. **Wrong license type assigned.** Sometimes a user is on an expired Trial or Hobby license. Unassign the old license and assign a paid one — see [Managing users and licenses](/aws/team-workspaces/managing-users-licenses/#managing-licenses). ### Why does my license show as SUSPENDED? @@ -708,7 +708,7 @@ Open a ticket by emailing `support@localstack.cloud`. | `SSL_NO_VERIFY` | `1` to disable outbound TLS verification (debug only) | | `ACTIVATE_PRO` | `0` to start LocalStack without Pro features (lets the container boot even if license activation fails) | -For the full configuration reference, see the [Configuration reference](/aws/capabilities/config/configuration/) and the broader [Networking documentation](/aws/capabilities/networking/). +For the full configuration reference, see the [Configuration reference](/aws/configuration/configuration-options/) and the broader [Networking documentation](/aws/configuration/networking/). ## LocalStack Platform FAQs diff --git a/src/content/docs/aws/getting-started/installation.mdx b/src/content/docs/aws/getting-started/installation.mdx index 92808c2c6..2bf847c7b 100644 --- a/src/content/docs/aws/getting-started/installation.mdx +++ b/src/content/docs/aws/getting-started/installation.mdx @@ -264,16 +264,16 @@ LocalStack runs inside a Docker container, and the above options are different w The LocalStack emulator is available on Docker Hub (`localstack/localstack-pro`). -For a comprehensive overview of the LocalStack images, check out our [Docker images documentation](/aws/capabilities/config/docker-images). +For a comprehensive overview of the LocalStack images, check out our [Docker images documentation](/aws/advanced-installation/docker-images). ### LocalStack Desktop -Learn more about our desktop client at [LocalStack Desktop](/aws/capabilities/web-app/localstack-desktop) and download it [here](https://app.localstack.cloud/download). +Learn more about our desktop client at [LocalStack Desktop](/aws/developer-tools/running-localstack/localstack-desktop) and download it [here](https://app.localstack.cloud/download). ### LocalStack Docker Extension Install our [official Docker Desktop extension](https://hub.docker.com/extensions/localstack/localstack-docker-desktop) to manage LocalStack. -See [LocalStack Docker Extension](/aws/capabilities/localstack-docker-extension) for more information. +See [LocalStack Docker Extension](/aws/advanced-installation/localstack-docker-extension) for more information. ### Docker-Compose @@ -385,7 +385,7 @@ docker run \ - Mounting the Docker socket `/var/run/docker.sock` as a volume is required for some services that use Docker to provide the emulation, such as AWS Lambda. Check out the [Lambda providers](/aws/services/lambda) documentation for more information. -- When using Docker to manually start LocalStack, you will have to configure the container on your own (see [docker-compose-pro.yml](https://github.com/localstack/localstack/blob/main/docker-compose-pro.yml) and [Configuration](/aws/capabilities/config/configuration). +- When using Docker to manually start LocalStack, you will have to configure the container on your own (see [docker-compose-pro.yml](https://github.com/localstack/localstack/blob/main/docker-compose-pro.yml) and [Configuration](/aws/configuration/configuration-options). This could be seen as the "expert mode" of starting LocalStack. If you are looking for a simpler method of starting LocalStack, please use the [LocalStack CLI](#localstack-cli). @@ -424,10 +424,10 @@ Now that you have LocalStack up and running, the following resources might be us - Use `awslocal` to use the AWS CLI against your local cloud! - Use the Serverless Framework with LocalStack! - And many more! -- [Find out how to configure LocalStack](/aws/capabilities/config/configuration) such that it perfectly fits your need. -- [Use LocalStack in your CI environment](/aws/integrations/continuous-integration/) to increase your code quality. +- [Find out how to configure LocalStack](/aws/configuration/configuration-options) such that it perfectly fits your need. +- [Use LocalStack in your CI environment](/aws/ci-pipelines/) to increase your code quality. - [Checkout LocalStack's Cloud Developer Tools](/aws/developer-tools/) to further increase your development efficiency with LocalStack. -- Find out about the ways you can [configure LocalStack](/aws/capabilities/config/configuration). +- Find out about the ways you can [configure LocalStack](/aws/configuration/configuration-options). ## Troubleshooting @@ -448,7 +448,7 @@ python3 -m localstack.cli.main If you are using the `localstack` CLI to start LocalStack, but the container is not starting, please check the following: -- Uncheck the **Use kernel networking for UDP** option in Docker Desktop (**Settings** → **Resources** → **Network**) or follow the steps in our [documentation](/aws/capabilities/dns-server#system-dns-configuration) to disable it. +- Uncheck the **Use kernel networking for UDP** option in Docker Desktop (**Settings** → **Resources** → **Network**) or follow the steps in our [documentation](/aws/configuration/networking/dns-server#system-dns-configuration) to disable it. - Start LocalStack with a specific DNS address: ```bash @@ -496,6 +496,6 @@ After running the task, run the diagnostic endpoint and share the archive file w #### My application cannot reach LocalStack over the network -We have extensive network troubleshooting documentation available [here](/aws/capabilities/networking/). +We have extensive network troubleshooting documentation available [here](/aws/configuration/networking/). If this does not solve your problem then please [reach out to LocalStack Support](/aws/help-support/get-help/). diff --git a/src/content/docs/aws/getting-started/quickstart.mdx b/src/content/docs/aws/getting-started/quickstart.mdx index 6210bf8db..643de4ac5 100644 --- a/src/content/docs/aws/getting-started/quickstart.mdx +++ b/src/content/docs/aws/getting-started/quickstart.mdx @@ -356,6 +356,6 @@ To expand your LocalStack capabilities, explore the following based on your expe - [Tutorials](/aws/tutorials): Check out our tutorials to learn how to use LocalStack across various AWS services and application stacks. - [Supported Services](/aws/services): Explore LocalStack's emulated AWS services. -- [Capabilities](/aws/capabilities/): Learn about LocalStack's capabilities including features like IAM policy stream, state management, and more. +- [Capabilities](/aws/configuration/): Learn about LocalStack's capabilities including features like IAM policy stream, state management, and more. - [Tooling](/aws/developer-tools/): Get details on LocalStack's tooling and integrations. - [Blog](https://blog.localstack.cloud): Read our blog posts about LocalStack and the latest enhancements for a better local development and testing experience. diff --git a/src/content/docs/aws/index.mdx b/src/content/docs/aws/index.mdx index dac96d9ff..a0bf6edb4 100644 --- a/src/content/docs/aws/index.mdx +++ b/src/content/docs/aws/index.mdx @@ -25,7 +25,7 @@ import starburstIcon from '../../../assets/images/Capabilities_Color.svg'; }, { title: "Test Your AWS Apps", - href: "/aws/capabilities" + href: "/aws/configuration" } ]} client:load @@ -56,7 +56,7 @@ import starburstIcon from '../../../assets/images/Capabilities_Color.svg'; { title: "Configuration", description: "Learn how to configure LocalStack and use its capabilities to accelerate your development workflow.", - href: "/aws/capabilities", + href: "/aws/configuration", icon: starburstIcon.src }, { @@ -68,7 +68,7 @@ import starburstIcon from '../../../assets/images/Capabilities_Color.svg'; { title: "Enterprise", description: "Learn how LocalStack Enterprise provides additional security, flexibility, compliance & support.", - href: "/aws/enterprise", + href: "/aws/advanced-installation", icon: buildingsIcon.src } ]} diff --git a/src/content/docs/aws/integrations/messaging/docker-compose.yml b/src/content/docs/aws/integrations/app-frameworks/docker-compose.yml similarity index 100% rename from src/content/docs/aws/integrations/messaging/docker-compose.yml rename to src/content/docs/aws/integrations/app-frameworks/docker-compose.yml diff --git a/src/content/docs/aws/integrations/messaging/selfmanaged-kafka-cluster.md b/src/content/docs/aws/integrations/app-frameworks/selfmanaged-kafka-cluster.md similarity index 93% rename from src/content/docs/aws/integrations/messaging/selfmanaged-kafka-cluster.md rename to src/content/docs/aws/integrations/app-frameworks/selfmanaged-kafka-cluster.md index fb209fc4d..82c19d21f 100644 --- a/src/content/docs/aws/integrations/messaging/selfmanaged-kafka-cluster.md +++ b/src/content/docs/aws/integrations/app-frameworks/selfmanaged-kafka-cluster.md @@ -3,7 +3,7 @@ title: Self-managed Kafka cluster description: Using LocalStack Lambda with a self-managed Kafka cluster. template: doc sidebar: - order: 1 + order: 6 --- LocalStack for AWS supports [AWS Managed Streaming for Kafka (MSK)](/aws/services/kafka) and you can create Kafka clusters directly through the MSK API that will run in LocalStack. @@ -11,7 +11,7 @@ In some cases, you may want to run your own self-managed Kafka cluster and integ ## Running self-managed Kafka -You can find the [example Docker Compose](https://github.com/localstack/localstack-docs/blob/master/src/content/docs/aws/integrations/messaging/docker-compose.yml) file which contains a single-noded ZooKeeper and a Kafka cluster and a simple LocalStack setup as well as [Kowl](https://github.com/cloudhut/kowl), an Apache Kafka Web UI. +You can find the [example Docker Compose](https://github.com/localstack/localstack-docs/blob/master/src/content/docs/aws/integrations/app-frameworks/docker-compose.yml) file which contains a single-noded ZooKeeper and a Kafka cluster and a simple LocalStack setup as well as [Kowl](https://github.com/cloudhut/kowl), an Apache Kafka Web UI. 1. Run Docker Compose: diff --git a/src/content/docs/aws/integrations/containers/index.md b/src/content/docs/aws/integrations/containers/index.md deleted file mode 100644 index 4093911f6..000000000 --- a/src/content/docs/aws/integrations/containers/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Overview -description: Use LocalStack with container-based development tools to manage and test your infrastructure locally. -template: doc -sidebar: - order: 1 ---- - -LocalStack integrates with a variety of container-based tools and platforms to support modern development workflows. This section shows you how to run LocalStack smoothly in containerized setups. - -This section covers how to use LocalStack with: - -- DevContainers -- Kubernetes -- OpenShift -- eksctl -- Rancher Desktop - -These integrations make it easy to use LocalStack in reproducible and portable environments, from local machines to container orchestration systems. \ No newline at end of file diff --git a/src/content/docs/aws/capabilities/extensions/developing-extensions.mdx b/src/content/docs/aws/integrations/extensions/developing-extensions.mdx similarity index 100% rename from src/content/docs/aws/capabilities/extensions/developing-extensions.mdx rename to src/content/docs/aws/integrations/extensions/developing-extensions.mdx diff --git a/src/content/docs/aws/capabilities/extensions/extensions-library.md b/src/content/docs/aws/integrations/extensions/extensions-library.md similarity index 100% rename from src/content/docs/aws/capabilities/extensions/extensions-library.md rename to src/content/docs/aws/integrations/extensions/extensions-library.md diff --git a/src/content/docs/aws/capabilities/extensions/index.md b/src/content/docs/aws/integrations/extensions/index.md similarity index 96% rename from src/content/docs/aws/capabilities/extensions/index.md rename to src/content/docs/aws/integrations/extensions/index.md index 20d90d43b..497a5bb8f 100644 --- a/src/content/docs/aws/capabilities/extensions/index.md +++ b/src/content/docs/aws/integrations/extensions/index.md @@ -25,7 +25,7 @@ Officially supported extensions are available in our [Official Extensions Librar :::tip Want to try out a common LocalStack extension? -Our [MailHog tutorial](/aws/capabilities/extensions/mailhog) teaches you how to install and use the official MailHog extension. It’s a quick way to explore how extensions work in LocalStack. +Our [MailHog tutorial](/aws/integrations/extensions/mailhog) teaches you how to install and use the official MailHog extension. It’s a quick way to explore how extensions work in LocalStack. ::: :::note diff --git a/src/content/docs/aws/capabilities/extensions/mailhog.md b/src/content/docs/aws/integrations/extensions/mailhog.md similarity index 93% rename from src/content/docs/aws/capabilities/extensions/mailhog.md rename to src/content/docs/aws/integrations/extensions/mailhog.md index 2a99c1657..fd34eb11d 100644 --- a/src/content/docs/aws/capabilities/extensions/mailhog.md +++ b/src/content/docs/aws/integrations/extensions/mailhog.md @@ -76,6 +76,6 @@ You should see the email you sent in the MailHog UI. - Explore our collection of official extensions, along with a growing ecosystem of third-party extensions, in our [Extensions Library](https://app.localstack.cloud/extensions/library). - Learn about the various methods for extension management and automating their installation when using LocalStack in a CI environment. - Get detailed insights from our [Managing Extensions](/aws/capabilities/extensions/managing-extensions) guide. + Get detailed insights from our [Managing Extensions](/aws/integrations/extensions/managing-extensions) guide. - Want to create your own extensions? - Dive into our guide on [Developing Extensions](/aws/capabilities/extensions/developing-extensions) for step-by-step instructions. + Dive into our guide on [Developing Extensions](/aws/integrations/extensions/developing-extensions) for step-by-step instructions. diff --git a/src/content/docs/aws/capabilities/extensions/managing-extensions.mdx b/src/content/docs/aws/integrations/extensions/managing-extensions.mdx similarity index 98% rename from src/content/docs/aws/capabilities/extensions/managing-extensions.mdx rename to src/content/docs/aws/integrations/extensions/managing-extensions.mdx index 58dc5d52e..a3e6ed969 100644 --- a/src/content/docs/aws/capabilities/extensions/managing-extensions.mdx +++ b/src/content/docs/aws/integrations/extensions/managing-extensions.mdx @@ -11,7 +11,7 @@ import { FileTree } from '@astrojs/starlight/components'; You have different options to install and manage your LocalStack extensions depending on your environment and work style. -Extensions are managed through the LocalStack container, but stored in the [LocalStack volume](/aws/capabilities/config/filesystem) on your host. +Extensions are managed through the LocalStack container, but stored in the [LocalStack volume](/aws/configuration/advanced/filesystem) on your host. The next time you start up LocalStack, your extensions will still be there! ## Using the extensions manager in our App @@ -165,7 +165,7 @@ When LocalStack starts up, you should see it tries to install the extensions and ## Extension Management within LocalStack -Extensions in LocalStack are Python distributions that operate within their dedicated virtual environment, residing in the [LocalStack Volume](/aws/capabilities/config/filesystem). +Extensions in LocalStack are Python distributions that operate within their dedicated virtual environment, residing in the [LocalStack Volume](/aws/configuration/advanced/filesystem). This involves the creation of a"variable packages folder `/var/lib/localstack/lib`," where the volume management system establishes both an `extensions` folder and a virtual environment named `python_venv`. Within this environment, all extensions and their dependencies are managed. LocalStack integrates its virtual environment, ensuring the resolution of all transitive dependencies associated with extensions. diff --git a/src/content/docs/aws/integrations/index.mdx b/src/content/docs/aws/integrations/index.mdx index de4e34e61..41cc44d2a 100644 --- a/src/content/docs/aws/integrations/index.mdx +++ b/src/content/docs/aws/integrations/index.mdx @@ -1,37 +1,32 @@ --- title: Overview -description: Use your favorite cloud development Integrations with LocalStack. +description: Integrate LocalStack with third-party software and extend it with your own extensions and SDKs. template: doc editUrl: false --- import SectionCards from '../../../../components/SectionCards.astro'; -LocalStack supports a wide range of integrations from the cloud development ecosystem. These integrations make it easy to run your existing AWS workflows locally, without modifying your tooling. +LocalStack integrates with a wide range of third-party software from the cloud development ecosystem, and can be extended to fit your own tooling. This section is mostly useful to platform teams who need to wire LocalStack into existing development and testing workflows. ## The Cloud Development Ecosystem -Cloud development spans a broad set of tools and practices. Whether you’re provisioning Infrastructure-as-Code (IaC) with tools like Terraform or CloudFormation, or building applications with AWS SDKs like `boto3` or `aws-sdk-js`, LocalStack helps you bring the entire workflow to your local machine. Get ready to speed up your feedback loops and reduce your cloud dependencies. +Whether you’re adding an extension, driving LocalStack from the Java or Python SDKs, wiring it into an application framework, or running it under a testing tool, this section shows you how to fit LocalStack into the tools you already use. ![Sample of supported integrations](/images/aws/integrations-overview.png) ## Integrations -We strive to make the integration of LocalStack into your workflow as seamless as possible. -Sometimes it's as easy as calling one of our wrapper tools, like `awslocal`, a drop-in replacement for the `aws` CLI. Other times, there's a bit of configuration involved. +We strive to make the integration of LocalStack into your workflow as seamless as possible. -Here is a list of tool integrations we support, and documentation on how to integrate LocalStack. +Here is a list of the integrations we support, and documentation on how to set each one up. diff --git a/src/content/docs/aws/capabilities/localstack-sdks/index.md b/src/content/docs/aws/integrations/localstack-sdks/index.md similarity index 100% rename from src/content/docs/aws/capabilities/localstack-sdks/index.md rename to src/content/docs/aws/integrations/localstack-sdks/index.md diff --git a/src/content/docs/aws/capabilities/localstack-sdks/java-sdk.md b/src/content/docs/aws/integrations/localstack-sdks/java-sdk.md similarity index 100% rename from src/content/docs/aws/capabilities/localstack-sdks/java-sdk.md rename to src/content/docs/aws/integrations/localstack-sdks/java-sdk.md diff --git a/src/content/docs/aws/capabilities/localstack-sdks/python-sdk.md b/src/content/docs/aws/integrations/localstack-sdks/python-sdk.md similarity index 100% rename from src/content/docs/aws/capabilities/localstack-sdks/python-sdk.md rename to src/content/docs/aws/integrations/localstack-sdks/python-sdk.md diff --git a/src/content/docs/aws/capabilities/testing-utils.md b/src/content/docs/aws/integrations/localstack-sdks/testing-utils.md similarity index 100% rename from src/content/docs/aws/capabilities/testing-utils.md rename to src/content/docs/aws/integrations/localstack-sdks/testing-utils.md diff --git a/src/content/docs/aws/integrations/messaging/index.md b/src/content/docs/aws/integrations/messaging/index.md deleted file mode 100644 index 30cda01ce..000000000 --- a/src/content/docs/aws/integrations/messaging/index.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Overview -description: Use LocalStack with messaging tools, such as Kafka, to test your messaging infrastructure locally. -template: doc -sidebar: - order: 1 ---- - -LocalStack supports messaging and event-driven architectures by integrating with services like Amazon MSK (Managed Streaming for Apache Kafka). This section explains how to connect LocalStack with a self-managed Kafka cluster for local development and testing of stream-based applications. - -Use this setup to simulate production-like messaging flows, without relying on managed cloud infrastructure. \ No newline at end of file diff --git a/src/content/docs/aws/services/cloudformation.mdx b/src/content/docs/aws/services/cloudformation.mdx index 46415862a..5a13025ab 100644 --- a/src/content/docs/aws/services/cloudformation.mdx +++ b/src/content/docs/aws/services/cloudformation.mdx @@ -201,7 +201,7 @@ Using [pseudo parameters](#pseudo-parameters) and [intrinsic functions](#intrins Hardcoding `amazonaws.com` (or conversely `localhost.localstack.cloud`) when building service URLs is one of the most common causes of templates that deploy on AWS but fail on LocalStack, or vice versa. This typically shows up in API Gateway invoke URLs, Step Functions API integration targets, and other places where a template constructs a fully qualified endpoint. -The `AWS::URLSuffix` pseudo parameter resolves to `amazonaws.com` on AWS (or `amazonaws.com.cn` in China Regions) and to the configured [`LOCALSTACK_HOST`](/aws/capabilities/config/configuration/) on LocalStack, which defaults to `localhost.localstack.cloud`. +The `AWS::URLSuffix` pseudo parameter resolves to `amazonaws.com` on AWS (or `amazonaws.com.cn` in China Regions) and to the configured [`LOCALSTACK_HOST`](/aws/configuration/configuration-options/) on LocalStack, which defaults to `localhost.localstack.cloud`. Referencing it lets the same template produce a valid URL in either environment. The following snippet shows the anti-pattern to avoid, where `amazonaws.com` is hardcoded into the output URL. @@ -325,7 +325,7 @@ LocalStack resolves each pseudo parameter to the equivalent value for the local | `AWS::Region` | Yes | The Region of the encompassing resource | Same | | `AWS::StackId` | Yes | The ARN of the stack | Same | | `AWS::StackName` | Yes | The name of the stack | Same | -| `AWS::URLSuffix` | Yes | The configured [`LOCALSTACK_HOST`](/aws/capabilities/config/configuration/) (default: `localhost.localstack.cloud`) | `amazonaws.com`, or `amazonaws.com.cn` in China Regions | +| `AWS::URLSuffix` | Yes | The configured [`LOCALSTACK_HOST`](/aws/configuration/configuration-options/) (default: `localhost.localstack.cloud`) | `amazonaws.com`, or `amazonaws.com.cn` in China Regions | :::tip Reach for `AWS::URLSuffix` and `AWS::Partition` instead of hardcoding `amazonaws.com` or `arn:aws:...` in templates. diff --git a/src/content/docs/aws/services/cloudfront.mdx b/src/content/docs/aws/services/cloudfront.mdx index e668362d5..26ae86ce3 100644 --- a/src/content/docs/aws/services/cloudfront.mdx +++ b/src/content/docs/aws/services/cloudfront.mdx @@ -48,7 +48,7 @@ curl -k https://$domain/hello.txt :::tip If you wish to use CloudFront on system host, ensure your local DNS setup is correctly configured. -Refer to the section on [System DNS configuration](/aws/capabilities/dns-server#system-dns-configuration) for details. +Refer to the section on [System DNS configuration](/aws/configuration/networking/dns-server#system-dns-configuration) for details. ::: In the example provided above, be aware that the final command (`curl https://$domain/hello.txt`) might encounter a temporary failure accompanied by a warning message `Could not resolve host`. diff --git a/src/content/docs/aws/services/cognito-idp.mdx b/src/content/docs/aws/services/cognito-idp.mdx index 84f4ea51e..22a366189 100644 --- a/src/content/docs/aws/services/cognito-idp.mdx +++ b/src/content/docs/aws/services/cognito-idp.mdx @@ -143,7 +143,7 @@ awslocal cognito-idp sign-up \ Once the user is successfully created, a confirmation code will be generated. This code can be found in the LocalStack container logs (as shown below). -Additionally, if you have [SMTP configured](/aws/capabilities/config/configuration/#emails), the confirmation code can be optionally sent via email for enhanced convenience and user experience. +Additionally, if you have [SMTP configured](/aws/configuration/configuration-options/#emails), the confirmation code can be optionally sent via email for enhanced convenience and user experience. ```bash INFO:localstack_ext.services.cognito.cognito_idp_api: Confirmation code for Cognito user example_user: 125796 @@ -357,7 +357,7 @@ The client credentials grant allows for scope-based authorization from a non-int Your app can directly request client credentials from the token endpoint to receive an access token. To request the token from the LocalStack URL, use the following endpoint: `://cognito-idp.localhost.localstack.cloud:4566/_aws/cognito-idp/oauth2/token`. -For additional information on our endpoints, refer to our [Internal Endpoints](/aws/capabilities/networking/internal-endpoints/) documentation. +For additional information on our endpoints, refer to our [Internal Endpoints](/aws/configuration/networking/internal-endpoints/) documentation. If there are multiple user pools, LocalStack identifies the appropriate one by examining the `clientid` of the request. @@ -491,7 +491,7 @@ The following code snippets and sample applications provide practical examples o By default, LocalStack's Cognito does not send actual email messages. However, if you wish to enable this feature, you will need to provide an email address and configure the corresponding SMTP settings. -The instructions on configuring the connection parameters of your SMTP server can be found in the [Configuration](/aws/capabilities/config/configuration/#emails) guide to allow your local Cognito environment to send email notifications. +The instructions on configuring the connection parameters of your SMTP server can be found in the [Configuration](/aws/configuration/configuration-options/#emails) guide to allow your local Cognito environment to send email notifications. ## API Coverage (Cognito Identity Pools) diff --git a/src/content/docs/aws/services/docdb.mdx b/src/content/docs/aws/services/docdb.mdx index 1321bd188..ab4c9476b 100644 --- a/src/content/docs/aws/services/docdb.mdx +++ b/src/content/docs/aws/services/docdb.mdx @@ -212,7 +212,7 @@ the [MongoDB documentation](https://www.mongodb.com/docs/). You need to set `DOCDB_PROXY_CONTAINER=1` when starting LocalStack to be able to use the returned `Endpoint`, which will be correctly resolved automatically. The flag `DOCDB_PROXY_CONTAINER=1` changes the default behavior and the container will be started as proxied container. -Meaning a port from the [pre-defined port](/aws/capabilities/networking/external-port-range/) range will be chosen, and when using lambda, you can use `localhost.localstack.cloud` to connect to the instance. +Meaning a port from the [pre-defined port](/aws/configuration/networking/external-port-range/) range will be chosen, and when using lambda, you can use `localhost.localstack.cloud` to connect to the instance. ::: In this sample we will use a Node.js lambda function to connect to a DocumentDB. diff --git a/src/content/docs/aws/services/ec2.mdx b/src/content/docs/aws/services/ec2.mdx index 8550c2273..4ff32ec65 100644 --- a/src/content/docs/aws/services/ec2.mdx +++ b/src/content/docs/aws/services/ec2.mdx @@ -206,7 +206,7 @@ LocalStack EC2 supports multiple methods to simulate the EC2 service. All tiers support the mock/CRUD capability. For advanced setups, LocalStack for AWS comes with emulation capability for certain resource types so that they behave more closely like AWS. -The underlying method for this can be controlled using the [`EC2_VM_MANAGER`](/aws/capabilities/config/configuration#ec2) configuration option. +The underlying method for this can be controlled using the [`EC2_VM_MANAGER`](/aws/configuration/configuration-options#ec2) configuration option. You may choose between plain mocked resources, containerized or virtualized. ## Mock VM Manager @@ -214,7 +214,7 @@ You may choose between plain mocked resources, containerized or virtualized. With the Mock VM manager, all resources are stored as in-memory representation. This only offers the CRUD capability. -To use this VM manager in LocalStack for AWS, set [`EC2_VM_MANAGER`](/aws/capabilities/config/configuration#ec2) to `mock`. +To use this VM manager in LocalStack for AWS, set [`EC2_VM_MANAGER`](/aws/configuration/configuration-options#ec2) to `mock`. This serves as the fallback manager if an operation is not implemented in other VM managers. @@ -224,7 +224,7 @@ LocalStack for AWS supports the Docker VM manager which uses the [Docker Engine] This VM manager requires the Docker socket from the host machine to be mounted inside the LocalStack container at `/var/run/docker.sock`. This is the default VM manager in LocalStack for AWS. -You may set [`EC2_VM_MANAGER`](/aws/capabilities/config/configuration#ec2) to `docker` to explicitly use this VM manager. +You may set [`EC2_VM_MANAGER`](/aws/configuration/configuration-options#ec2) to `docker` to explicitly use this VM manager. All launched EC2 instances have the Docker socket mounted inside them at `/var/run/docker.sock` to make Docker-in-Docker usecases possible. @@ -339,7 +339,7 @@ This section illustrates how this functionality can be achieved with EC2 Docker :::note This feature is disabled by default. -Please set the [`EC2_MOUNT_BLOCK_DEVICES`](/aws/capabilities/config/configuration#ec2) configuration option to enable it. +Please set the [`EC2_MOUNT_BLOCK_DEVICES`](/aws/configuration/configuration-options#ec2) configuration option to enable it. ::: First, we create a user data script `init.sh` which creates an ext3 file system on the block device `/ebs-dev/sda1` and mounts it under `/ebs-mounted`: @@ -365,7 +365,7 @@ awslocal ec2 run-instances --image-id ami-ff0fea8310f3 --count 1 --instance-type ``` Please note that, whereas real AWS uses GiB for volume sizes, LocalStack uses MiB as the unit for `VolumeSize` in the command above (to avoid creating huge files locally). -Also, by default block device images are limited to 1 GiB in size, but this can be customized by setting the [`EC2_EBS_MAX_VOLUME_SIZE`](/aws/capabilities/config/configuration#ec2) config variable (defaults to `1000`). +Also, by default block device images are limited to 1 GiB in size, but this can be customized by setting the [`EC2_EBS_MAX_VOLUME_SIZE`](/aws/configuration/configuration-options#ec2) config variable (defaults to `1000`). Once the instance is successfully started and initialized, we can first determine the container ID via `docker ps`, and then list the contents of the mounted filesystem `/ebs-mounted`, which should contain our test file named `my-test-file`: @@ -430,7 +430,7 @@ If you would like support for more metadata categories, please make a feature re ### Configuration -You can use the [`EC2_DOCKER_FLAGS`](/aws/capabilities/config/configuration#ec2) LocalStack configuration variable to pass supplementary flags to Docker during the initiation of containerized instances. +You can use the [`EC2_DOCKER_FLAGS`](/aws/configuration/configuration-options#ec2) LocalStack configuration variable to pass supplementary flags to Docker during the initiation of containerized instances. This allows for fine-tuned behaviours, for example, running containers in privileged mode using `--privileged` or specifying an alternate CPU platform with `--platform`. Keep in mind that this will apply to all instances that are launched in the LocalStack session. @@ -500,7 +500,7 @@ If you are using [Docker CLI](/aws/getting-started/installation#docker), include -v /var/run/libvirt/libvirt-sock:/var/run/libvirt/libvirt-sock ``` -If you are using a remote Libvirt hypervisor, you can set the [`EC2_HYPERVISOR_URI`](/aws/capabilities/config/configuration#ec2) config option with a connection URI. +If you are using a remote Libvirt hypervisor, you can set the [`EC2_HYPERVISOR_URI`](/aws/configuration/configuration-options#ec2) config option with a connection URI. :::tip If you encounter an error like `failed to connect to the hypervisor: Permission denied`, you may need to perform additional setup on the hypervisor host. @@ -541,7 +541,7 @@ LocalStack does not come preloaded with any AMIs. Compatible qcow2 images must be placed in the Libvirt storage pool on the host machine. By default, this is located at `/var/lib/libvirt/images`. -If you use a different storage pool, configure it using the [`EC2_LIBVIRT_POOL`](/aws/capabilities/config/configuration#ec2) option. +If you use a different storage pool, configure it using the [`EC2_LIBVIRT_POOL`](/aws/configuration/configuration-options#ec2) option. Images must be named with the prefix `ami-` followed by at least 8 hexadecimal characters without an extension, e.g. `ami-1234abcd`. You may need run the following command to make sure the image is registered with Libvirt (replace `default` with your storage pool name if different): @@ -615,7 +615,7 @@ The Libvirt VM manager supports several configuration options to customize its b By default, LocalStack creates VMs using a generic Libvirt domain configuration. However, certain hypervisor setups may require specialized configurations that LocalStack cannot automatically detect. -You can use the [`EC2_REFERENCE_DOMAIN`](/aws/capabilities/config/configuration#ec2) configuration option to specify a pre-configured Libvirt domain that LocalStack will use as a template for all new instances. +You can use the [`EC2_REFERENCE_DOMAIN`](/aws/configuration/configuration-options#ec2) configuration option to specify a pre-configured Libvirt domain that LocalStack will use as a template for all new instances. LocalStack clones the domain configuration, updating elements like UUID, MAC addresses, and boot volumes as needed. To use domain cloning: @@ -631,8 +631,8 @@ If the specified domain does not exist or is not in shut-off state, LocalStack f By default, LocalStack uses the Libvirt storage pool and network named `default`. If your Libvirt setup uses different names, you can configure them using: -- [`EC2_LIBVIRT_POOL`](/aws/capabilities/config/configuration#ec2): Name of the Libvirt storage pool for images (defaults to `default`). -- [`EC2_LIBVIRT_NETWORK`](/aws/capabilities/config/configuration#ec2): Name of the Libvirt network for instances (defaults to `default`). +- [`EC2_LIBVIRT_POOL`](/aws/configuration/configuration-options#ec2): Name of the Libvirt storage pool for images (defaults to `default`). +- [`EC2_LIBVIRT_NETWORK`](/aws/configuration/configuration-options#ec2): Name of the Libvirt network for instances (defaults to `default`). ### Networking diff --git a/src/content/docs/aws/services/ecs.mdx b/src/content/docs/aws/services/ecs.mdx index cf8211749..5c10fee23 100644 --- a/src/content/docs/aws/services/ecs.mdx +++ b/src/content/docs/aws/services/ecs.mdx @@ -251,7 +251,7 @@ If your ECS containers depend on LocalStack services, your ECS task network shou If you are running LocalStack through a `docker run` command, do not forget to enable the communication from the container to the Docker Engine API. You can provide the access by adding the following option `-v /var/run/docker.sock:/var/run/docker.sock`. -For more information regarding the configuration of LocalStack, please check the [LocalStack configuration](/aws/capabilities/config/configuration) section. +For more information regarding the configuration of LocalStack, please check the [LocalStack configuration](/aws/configuration/configuration-options) section. ## Remote debugging diff --git a/src/content/docs/aws/services/eks.mdx b/src/content/docs/aws/services/eks.mdx index 3bc78b58e..aa0662956 100644 --- a/src/content/docs/aws/services/eks.mdx +++ b/src/content/docs/aws/services/eks.mdx @@ -226,12 +226,12 @@ You can now use ECR (Elastic Container Registry) images within your EKS environm #### Initial configuration -To modify the return value of resource URIs for most services, including ECR, you can utilize the `LOCALSTACK_HOST` variable in the [configuration](/aws/capabilities/config/configuration). +To modify the return value of resource URIs for most services, including ECR, you can utilize the `LOCALSTACK_HOST` variable in the [configuration](/aws/configuration/configuration-options). By default, ECR returns a `repositoryUri` starting with `localhost.localstack.cloud`, such as: `localhost.localstack.cloud:/`. :::note In this section, we assume that `localhost.localstack.cloud` resolves in your environment, and LocalStack is connected to a non-default bridge network. -For more information, refer to the article about [DNS rebind protection](/aws/capabilities/dns-server#dns-rebind-protection). +For more information, refer to the article about [DNS rebind protection](/aws/configuration/networking/dns-server#dns-rebind-protection). If the domain `localhost.localstack.cloud` does not resolve on your host, you can still proceed by setting `LOCALSTACK_HOST=localhost` (not recommended). @@ -347,7 +347,7 @@ In the events, we can see that the pull from ECR was successful: ``` :::tip -Public Docker images from `registry.k8s.io` can be pulled without additional configuration from EKS nodes, but if you pull images from any other locations that resolve to S3 you can configure `DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM=\.s3.*\.amazonaws\.com` in your [configuration](/aws/capabilities/config/configuration). +Public Docker images from `registry.k8s.io` can be pulled without additional configuration from EKS nodes, but if you pull images from any other locations that resolve to S3 you can configure `DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM=\.s3.*\.amazonaws\.com` in your [configuration](/aws/configuration/configuration-options). ::: ### Configuring an Ingress for your services diff --git a/src/content/docs/aws/services/elasticache.mdx b/src/content/docs/aws/services/elasticache.mdx index 63d707ab3..c9048ee91 100644 --- a/src/content/docs/aws/services/elasticache.mdx +++ b/src/content/docs/aws/services/elasticache.mdx @@ -49,7 +49,7 @@ awslocal elasticache describe-cache-clusters --show-cache-node-info --query "Cac } ``` -The cache cluster uses a random port of the [external service port range](/aws/capabilities/networking/external-port-range/). +The cache cluster uses a random port of the [external service port range](/aws/configuration/networking/external-port-range/). Use this port number to connect to the Redis instance like so: ```bash diff --git a/src/content/docs/aws/services/emr.mdx b/src/content/docs/aws/services/emr.mdx index 962e17457..40e065f92 100644 --- a/src/content/docs/aws/services/emr.mdx +++ b/src/content/docs/aws/services/emr.mdx @@ -21,7 +21,7 @@ The supported APIs are available on the API coverage section for [EMR](#api-cove :::note To utilize the EMR API, certain additional dependencies need to be downloaded from the network (including Hadoop, Hive, Spark, etc). These dependencies are fetched automatically during service startup, hence it is important to ensure a reliable internet connection when retrieving the dependencies for the first time. -Alternatively, you can use one of our `*-bigdata` Docker image tags which already ship with the required libraries baked in and may provide better stability (see [here](/aws/capabilities/config/docker-images/) for more details). +Alternatively, you can use one of our `*-bigdata` Docker image tags which already ship with the required libraries baked in and may provide better stability (see [here](/aws/advanced-installation/docker-images/) for more details). ::: ## Getting started diff --git a/src/content/docs/aws/services/es.mdx b/src/content/docs/aws/services/es.mdx index de040bf75..e82e9f8d4 100644 --- a/src/content/docs/aws/services/es.mdx +++ b/src/content/docs/aws/services/es.mdx @@ -149,7 +149,7 @@ There are three configurable strategies that govern how domain endpoints are cre | - | - | - | | `domain` | `..es.localhost.localstack.cloud:4566` | This is the default strategy that uses the `localhost.localstack.cloud` domain to route to your localhost | | `path` | `localhost:4566/es//` | An alternative that can be useful if you cannot resolve LocalStack's localhost domain | -| `port` | `localhost:` | Exposes the cluster(s) directly with ports from the [external service port range](/aws/capabilities/networking/external-port-range/)| +| `port` | `localhost:` | Exposes the cluster(s) directly with ports from the [external service port range](/aws/configuration/networking/external-port-range/)| | `off` | | *Deprecated*. This value now reverts to the `port` setting, using a port from the given range instead of `4571` | Regardless of the service from which the clusters were created, the domain of the cluster always corresponds to the engine type (OpenSearch or Elasticsearch) of the cluster. diff --git a/src/content/docs/aws/services/lambda.mdx b/src/content/docs/aws/services/lambda.mdx index 1e1a08846..b5877dce9 100644 --- a/src/content/docs/aws/services/lambda.mdx +++ b/src/content/docs/aws/services/lambda.mdx @@ -526,7 +526,7 @@ This init binary is used as the entry point for every Lambda container. Our custom implementation offers additional configuration options, but these configurations are primarily intended for LocalStack developers and could change in the future. -The LocalStack [configuration](/aws/capabilities/config/configuration) `LAMBDA_DOCKER_FLAGS` can be used to configure all Lambda containers, +The LocalStack [configuration](/aws/configuration/configuration-options) `LAMBDA_DOCKER_FLAGS` can be used to configure all Lambda containers, for example `LAMBDA_DOCKER_FLAGS=-e LOCALSTACK_INIT_LOG_LEVEL=debug`. Some noteworthy configurations include: - `LOCALSTACK_INIT_LOG_LEVEL` defines the log level of the Golang binary. @@ -602,7 +602,7 @@ With the new implementation, the following changes have been introduced: The ARM containers for compatible runtimes are based on Amazon Linux 2, and ARM-compatible hosts can create functions with the `arm64` architecture. - Lambda functions in LocalStack resolve AWS domains, such as `s3.amazonaws.com`, to the LocalStack container. This domain resolution is DNS-based and can be disabled by setting `DNS_ADDRESS=0`. - For more information, refer to [Transparent Endpoint Injection](/aws/capabilities/networking/transparent-endpoint-injection). + For more information, refer to [Transparent Endpoint Injection](/aws/configuration/networking/transparent-endpoint-injection). Previously, LocalStack provided patched AWS SDKs to redirect AWS API calls transparently to LocalStack. - The new provider may generate more exceptions due to invalid input. For instance, while the old provider accepted arbitrary strings (such as `r1`) as Lambda roles when creating a function, the new provider validates role ARNs using a regular expression that requires them to be in the format `arn:aws:iam::000000000000:role/lambda-role`. @@ -613,7 +613,7 @@ With the new implementation, the following changes have been introduced: The configuration `LAMBDA_SYNCHRONOUS_CREATE=1` can force synchronous function creation, but it is not recommended. - LocalStack's Lambda implementation, allows you to customize the Lambda execution environment using the [Lambda Extensions API](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-extensions-api.html). This API allows for advanced monitoring, observability, or developer tooling, providing greater control and flexibility over your Lambda functions. - Lambda functions can also be run on hosts with [multi-architecture support](/aws/capabilities/config/arm64-support/), allowing you to leverage LocalStack's Lambda API to develop and test Lambda functions with high parity. + Lambda functions can also be run on hosts with [multi-architecture support](/aws/configuration/advanced/arm64-support/), allowing you to leverage LocalStack's Lambda API to develop and test Lambda functions with high parity. The following configuration options from the old provider are discontinued in the new provider: diff --git a/src/content/docs/aws/services/memorydb.mdx b/src/content/docs/aws/services/memorydb.mdx index 93913b07c..8be90ee9b 100644 --- a/src/content/docs/aws/services/memorydb.mdx +++ b/src/content/docs/aws/services/memorydb.mdx @@ -48,7 +48,7 @@ awslocal memorydb describe-clusters --query "Clusters[0].ClusterEndpoint" } ``` -The cache cluster uses a random port of the [external service port range](/aws/capabilities/networking/external-port-range/) in regular execution and a port between 36739 and 46738 in container mode. +The cache cluster uses a random port of the [external service port range](/aws/configuration/networking/external-port-range/) in regular execution and a port between 36739 and 46738 in container mode. Use this port number to connect to the Redis instance using the `redis-cli` command line tool: ```bash diff --git a/src/content/docs/aws/services/mwaa.mdx b/src/content/docs/aws/services/mwaa.mdx index 56e8fa55e..57ce4d1bb 100644 --- a/src/content/docs/aws/services/mwaa.mdx +++ b/src/content/docs/aws/services/mwaa.mdx @@ -101,7 +101,7 @@ awslocal s3 cp sample_dag.py s3://my-mwaa-bucket/dags ``` LocalStack syncs new and changed objects in the S3 bucket to the Airflow container every 30 seconds. -The polling interval can be changed using the [`MWAA_S3_POLL_INTERVAL`](/aws/capabilities/config/configuration/#mwaa) config option. +The polling interval can be changed using the [`MWAA_S3_POLL_INTERVAL`](/aws/configuration/configuration-options/#mwaa) config option. ## Installing custom plugins diff --git a/src/content/docs/aws/services/neptune.mdx b/src/content/docs/aws/services/neptune.mdx index 6dd9002cc..13fed6b10 100644 --- a/src/content/docs/aws/services/neptune.mdx +++ b/src/content/docs/aws/services/neptune.mdx @@ -223,7 +223,7 @@ awscurl "https://localhost.localstack.cloud:4510/gremlin?gremlin=g.V().count()" :::note If Gremlin Server is installed in your LocalStack environment, you must delete it and restart LocalStack. -You can find your LocalStack volume location on the [LocalStack filesystem documentation](/aws/capabilities/config/filesystem/#localstack-volume). +You can find your LocalStack volume location on the [LocalStack filesystem documentation](/aws/configuration/advanced/filesystem/#localstack-volume). ```bash rm -rf /lib/tinkerpop diff --git a/src/content/docs/aws/services/opensearch.mdx b/src/content/docs/aws/services/opensearch.mdx index 553ad8aec..2397e79e5 100644 --- a/src/content/docs/aws/services/opensearch.mdx +++ b/src/content/docs/aws/services/opensearch.mdx @@ -112,7 +112,7 @@ The strategy can be configured via the `OPENSEARCH_ENDPOINT_STRATEGY` environmen | ------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | `domain` | `...localhost.localstack.cloud:4566` | The default strategy employing the `localhost.localstack.cloud` domain for routing to localhost. | | `path` | `localhost:4566///` | An alternative strategy useful if resolving LocalStack's localhost domain poses difficulties. | -| `port` | `localhost:` | Directly exposes cluster(s) via ports from [the external service port range](/aws/capabilities/networking/external-port-range/). | +| `port` | `localhost:` | Directly exposes cluster(s) via ports from [the external service port range](/aws/configuration/networking/external-port-range/). | Irrespective of the originating service for the clusters, the domain of each cluster consistently aligns with its engine type, be it OpenSearch or Elasticsearch. Consequently, OpenSearch clusters incorporate `opensearch` within their domains (e.g., `my-domain.us-east-1.opensearch.localhost.localstack.cloud:4566`), while Elasticsearch clusters feature `es` in their domains (e.g., `my-domain.us-east-1.es.localhost.localstack.cloud:4566`). @@ -239,7 +239,7 @@ When using OpenSearch Dashboards with LocalStack, you need to make sure to: - Enable the [advanced security options](#advanced-security-options) and set a username and a password. This is required by OpenSearch Dashboards. - Ensure that the OpenSearch Dashboards Docker container uses the LocalStack DNS. - You can find more information on how to connect your Docker container to Localstack in our [Network Troubleshooting guide](/aws/capabilities/networking/). + You can find more information on how to connect your Docker container to Localstack in our [Network Troubleshooting guide](/aws/configuration/networking/). First, you need to make sure to start LocalStack in a specific Docker network: @@ -394,7 +394,7 @@ The `CustomEndpointOptions` in LocalStack offers the flexibility to utilize arbi ## Troubleshooting If you encounter difficulties resolving subdomains while employing the `OPENSEARCH_ENDPOINT_STRATEGY=domain` (the default setting), it's advisable to investigate whether your DNS configuration might be obstructing rebind queries. -For further insights on addressing this issue, refer to the section on [DNS rebind protection](/aws/capabilities/dns-server#dns-rebind-protection). +For further insights on addressing this issue, refer to the section on [DNS rebind protection](/aws/configuration/networking/dns-server#dns-rebind-protection). ## API Coverage diff --git a/src/content/docs/aws/services/organizations.mdx b/src/content/docs/aws/services/organizations.mdx index a3e39d316..8f9e5fda4 100644 --- a/src/content/docs/aws/services/organizations.mdx +++ b/src/content/docs/aws/services/organizations.mdx @@ -12,7 +12,7 @@ Amazon Web Services Organizations is an account management service that allows y It allows you to manage different accounts in a single organization and consolidate billing. With Organizations, you can also attach different policies to your organizational units (OUs) or individual accounts in your organization. -Organizations is available over LocalStack for AWS and the supported APIs are available over our [configuration page](/aws/capabilities/config/configuration). +Organizations is available over LocalStack for AWS and the supported APIs are available over our [configuration page](/aws/configuration/configuration-options). ## Getting started diff --git a/src/content/docs/aws/services/route53.mdx b/src/content/docs/aws/services/route53.mdx index fa9813ed6..c8be06c03 100644 --- a/src/content/docs/aws/services/route53.mdx +++ b/src/content/docs/aws/services/route53.mdx @@ -198,10 +198,10 @@ For ELB alias records: ## DNS resolution -LocalStack for AWS supports the ability to respond to DNS queries for your Route53 domain names, with our [integrated DNS server](/aws/capabilities/dns-server). +LocalStack for AWS supports the ability to respond to DNS queries for your Route53 domain names, with our [integrated DNS server](/aws/configuration/networking/dns-server). :::note -To follow the example below you must [configure your system DNS to use the LocalStack DNS server](/aws/capabilities/dns-server#system-dns-configuration). +To follow the example below you must [configure your system DNS to use the LocalStack DNS server](/aws/configuration/networking/dns-server#system-dns-configuration). ::: ### Query a DNS record @@ -224,7 +224,7 @@ test.example.com. 300 IN A 1.2.3.4 The DNS name `localhost.localstack.cloud`, along with its subdomains like `mybucket.s3.localhost.localstack.cloud`, serves an internal routing purpose within LocalStack. It facilitates communication between a LocalStack compute environment (such as a Lambda function) and the LocalStack APIs, as well as your containerised applications with the LocalStack APIs. -For example configurations, see the [Network Troubleshooting guide](/aws/capabilities/networking/). +For example configurations, see the [Network Troubleshooting guide](/aws/configuration/networking/). For most use-cases, the default configuration of the internal LocalStack DNS name requires no modification. It functions seamlessly in typical scenarios. diff --git a/src/content/docs/aws/services/s3.mdx b/src/content/docs/aws/services/s3.mdx index 7ca4a47d7..0ce504f80 100644 --- a/src/content/docs/aws/services/s3.mdx +++ b/src/content/docs/aws/services/s3.mdx @@ -143,7 +143,7 @@ By default, most SDKs will try to use **Virtual-Hosted style** requests and prep However, if the endpoint is not prefixed by `s3.`, LocalStack will not be able to understand the request and it will most likely result in an error. You can either change the endpoint to an S3-specific one, or configure your SDK to use **Path style** requests instead. -Check out our [SDK documentation](/aws/capabilities/localstack-sdks/) to learn how you can configure AWS SDKs to access LocalStack and S3. +Check out our [SDK documentation](/aws/integrations/localstack-sdks/) to learn how you can configure AWS SDKs to access LocalStack and S3. :::tip While using [AWS SDKs](https://aws.amazon.com/developer/tools/#SDKs), you would need to configure the `ForcePathStyle` parameter to `true` in the S3 client configuration to use **Path style** requests. diff --git a/src/content/docs/aws/services/ses.mdx b/src/content/docs/aws/services/ses.mdx index 58d5d0e2e..d2d6ad5fe 100644 --- a/src/content/docs/aws/services/ses.mdx +++ b/src/content/docs/aws/services/ses.mdx @@ -110,14 +110,14 @@ Sent messages can be retrieved in following ways: ```bash curl -X DELETE localhost.localstack.cloud:4566/_aws/ses?id=dqxhhgoutkmylpbc-ffuqlkjs-ljld-fckp-hcph-wcsrkmxhhldk-pvadjc ``` -- **Filesystem:** All messages are saved to the state directory (see [filesystem layout](/aws/capabilities/config/filesystem)). +- **Filesystem:** All messages are saved to the state directory (see [filesystem layout](/aws/configuration/advanced/filesystem)). The files are saved as JSON in the `ses/` subdirectory and named by the message ID. ## SMTP Integration LocalStack for AWS supports sending emails via an SMTP server. To enable this, set the connections parameters and access credentials for the server in the configuration. -Refer to the [Configuration](/aws/capabilities/config/configuration/#emails) guide for details. +Refer to the [Configuration](/aws/configuration/configuration-options/#emails) guide for details. :::tip If you do not have access to a live SMTP server, you can use tools like [MailDev](https://github.com/maildev/maildev) or [smtp4dev](https://github.com/rnwood/smtp4dev). diff --git a/src/content/docs/aws/services/sqs.mdx b/src/content/docs/aws/services/sqs.mdx index 5c0939466..126432221 100644 --- a/src/content/docs/aws/services/sqs.mdx +++ b/src/content/docs/aws/services/sqs.mdx @@ -373,7 +373,7 @@ Our Lambda implementation automatically resolves these URLs to the LocalStack co When your code run within different containers like ECS tasks or your custom ones, it's advisable to establish your Docker network setup. You can follow these steps: -1. Override the `LOCALSTACK_HOST` variable as outlined in our [network troubleshooting guide](/aws/capabilities/networking/). +1. Override the `LOCALSTACK_HOST` variable as outlined in our [network troubleshooting guide](/aws/configuration/networking/). 2. Ensure that your containers can resolve `LOCALSTACK_HOST` to the LocalStack container within the Docker network. 3. We recommend employing `SQS_ENDPOINT_STRATEGY=path`, which generates queue URLs in the format `http:///queue/...`. diff --git a/src/content/docs/aws/services/transcribe.mdx b/src/content/docs/aws/services/transcribe.mdx index 14ca39d08..651a98016 100644 --- a/src/content/docs/aws/services/transcribe.mdx +++ b/src/content/docs/aws/services/transcribe.mdx @@ -18,7 +18,7 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w LocalStack Transcribe uses an offline speech-to-text library called [Vosk](https://alphacephei.com/vosk/). It requires an active internet connection to download the language model. Once the language model is downloaded, subsequent transcriptions for the same language can be performed offline. -Language models typically have a size of around 50 MiB and are saved in the cache directory (see [Filesystem Layout](/aws/capabilities/config/filesystem)). +Language models typically have a size of around 50 MiB and are saved in the cache directory (see [Filesystem Layout](/aws/configuration/advanced/filesystem)). ## Getting Started diff --git a/src/content/docs/aws/capabilities/web-app/accounts.md b/src/content/docs/aws/team-workspaces/accounts.md similarity index 100% rename from src/content/docs/aws/capabilities/web-app/accounts.md rename to src/content/docs/aws/team-workspaces/accounts.md diff --git a/src/content/docs/aws/team-workspaces/index.md b/src/content/docs/aws/team-workspaces/index.md new file mode 100644 index 000000000..dadbf1c1a --- /dev/null +++ b/src/content/docs/aws/team-workspaces/index.md @@ -0,0 +1,18 @@ +--- +title: Overview +description: Manage your LocalStack accounts, workspaces, users, licenses, and single sign-on through the LocalStack Web Application. +template: doc +editUrl: false +sidebar: + order: 1 +--- + +Team Workspaces covers the administrative side of LocalStack: managing your account, organizing your workspace, and provisioning users, licenses, and permissions through the [LocalStack Web Application](https://app.localstack.cloud/). + +These are generally one-time setup tasks performed by an IT administrator (or by an individual setting up their own account), rather than day-to-day development work. + +- [Accounts](/aws/team-workspaces/accounts) — manage your LocalStack account. +- [Workspace](/aws/team-workspaces/workspaces) — organize and configure your workspace. +- [Users and Licenses](/aws/team-workspaces/managing-users-licenses) — invite users and assign licenses. +- [Single Sign-On](/aws/team-workspaces/sso) — configure SSO and SCIM user provisioning. +- [Stack Insights](/aws/team-workspaces/stack-insights) — view usage and activity across your workspace. diff --git a/src/content/docs/aws/capabilities/web-app/managing-users-licenses.md b/src/content/docs/aws/team-workspaces/managing-users-licenses.md similarity index 100% rename from src/content/docs/aws/capabilities/web-app/managing-users-licenses.md rename to src/content/docs/aws/team-workspaces/managing-users-licenses.md diff --git a/src/content/docs/aws/enterprise/sso/azure-ad.md b/src/content/docs/aws/team-workspaces/sso/azure-ad.md similarity index 98% rename from src/content/docs/aws/enterprise/sso/azure-ad.md rename to src/content/docs/aws/team-workspaces/sso/azure-ad.md index 2efc9210e..48ed06610 100644 --- a/src/content/docs/aws/enterprise/sso/azure-ad.md +++ b/src/content/docs/aws/team-workspaces/sso/azure-ad.md @@ -2,6 +2,8 @@ title: "SSO for Azure AD" description: Configuring Azure AD for Single Sign-on in LocalStack Enterprise tags: ["Enterprise"] +sidebar: + order: 2 --- To configure SSO with an Azure AD Enterprise application, we provide a simple step-by-step solution below: diff --git a/src/content/docs/aws/enterprise/sso/index.md b/src/content/docs/aws/team-workspaces/sso/index.md similarity index 99% rename from src/content/docs/aws/enterprise/sso/index.md rename to src/content/docs/aws/team-workspaces/sso/index.md index 4999df97a..225dc618b 100644 --- a/src/content/docs/aws/enterprise/sso/index.md +++ b/src/content/docs/aws/team-workspaces/sso/index.md @@ -3,6 +3,8 @@ title: Single-Sign On description: Configuring Custom Single-Sign On (SSO) Providers in LocalStack Web Application. template: doc tags: ["Enterprise"] +sidebar: + order: 1 --- Custom Single-Sign On (SSO) Identity providers, can be enabled to facilitate the process of quickly onboarding team members from your organization. diff --git a/src/content/docs/aws/enterprise/sso/scim.mdx b/src/content/docs/aws/team-workspaces/sso/scim.mdx similarity index 99% rename from src/content/docs/aws/enterprise/sso/scim.mdx rename to src/content/docs/aws/team-workspaces/sso/scim.mdx index 87308b66d..4b47b51aa 100644 --- a/src/content/docs/aws/enterprise/sso/scim.mdx +++ b/src/content/docs/aws/team-workspaces/sso/scim.mdx @@ -3,11 +3,13 @@ title: SCIM User Provisioning description: Automating user and license provisioning in LocalStack using SCIM (System for Cross-domain Identity Management). template: doc tags: ['Enterprise'] +sidebar: + order: 3 --- SCIM (System for Cross-domain Identity Management) allows you to automate user provisioning, deprovisioning, and license assignment in LocalStack through your identity provider (IdP). LocalStack's SCIM implementation follows the SCIM v2.0 specification and has been developed and tested with the Okta SCIM client. -SCIM is a sub-feature of SSO and requires an active SSO configuration with at least one Identity Provider already set up. See the [Single Sign-On](/aws/enterprise/sso/) documentation before proceeding. +SCIM is a sub-feature of SSO and requires an active SSO configuration with at least one Identity Provider already set up. See the [Single Sign-On](/aws/team-workspaces/sso/) documentation before proceeding. All integration details — including the SCIM Base Connector URL, Bearer Auth Token, and group names per subscription — are available in the LocalStack web app under **Settings → [Single Sign-On](https://app.localstack.cloud/settings/sso)**. diff --git a/src/content/docs/aws/capabilities/web-app/stack-insights.md b/src/content/docs/aws/team-workspaces/stack-insights.md similarity index 100% rename from src/content/docs/aws/capabilities/web-app/stack-insights.md rename to src/content/docs/aws/team-workspaces/stack-insights.md diff --git a/src/content/docs/aws/capabilities/web-app/workspaces.md b/src/content/docs/aws/team-workspaces/workspaces.md similarity index 100% rename from src/content/docs/aws/capabilities/web-app/workspaces.md rename to src/content/docs/aws/team-workspaces/workspaces.md diff --git a/src/content/docs/aws/tutorials/lambda-ecr-container-images.mdx b/src/content/docs/aws/tutorials/lambda-ecr-container-images.mdx index 1220de90c..1410df4c0 100644 --- a/src/content/docs/aws/tutorials/lambda-ecr-container-images.mdx +++ b/src/content/docs/aws/tutorials/lambda-ecr-container-images.mdx @@ -189,7 +189,7 @@ Run the following command to create the function: :::note Before creating the lambda function, please double check under which architecture you have built your image. If your image is built as arm64, you need to specify the lambda architecture when deploying or set `LAMBDA_IGNORE_ARCHITECTURE=1` when starting LocalStack. -More information can be found [in our documentation regarding ARM support.](/aws/capabilities/config/arm64-support) +More information can be found [in our documentation regarding ARM support.](/aws/configuration/advanced/arm64-support) ::: ```bash diff --git a/src/content/docs/aws/tutorials/route-53-failover.mdx b/src/content/docs/aws/tutorials/route-53-failover.mdx index 926c6f31b..72f237a53 100644 --- a/src/content/docs/aws/tutorials/route-53-failover.mdx +++ b/src/content/docs/aws/tutorials/route-53-failover.mdx @@ -62,7 +62,7 @@ The following diagram shows the architecture that this application builds and de ### Creating the resources To begin, deploy the same services in both `us-west-1` and `us-east-1` regions. -The resources specified in the `init-resources.sh` file will be created when the LocalStack container starts, using [Initialization Hooks](/aws/capabilities/config/initialization-hooks) and the `awslocal` CLI tool. +The resources specified in the `init-resources.sh` file will be created when the LocalStack container starts, using [Initialization Hooks](/aws/configuration/advanced/initialization-hooks) and the `awslocal` CLI tool. The objective is to have a backup system in case of a regional outage in the primary availability zone (`us-west-1`). We'll focus on this region to examine the existing resilience mechanisms. diff --git a/src/content/docs/aws/tutorials/using-terraform-with-testcontainers-and-localstack.mdx b/src/content/docs/aws/tutorials/using-terraform-with-testcontainers-and-localstack.mdx index 98bb639c7..13f5647bc 100644 --- a/src/content/docs/aws/tutorials/using-terraform-with-testcontainers-and-localstack.mdx +++ b/src/content/docs/aws/tutorials/using-terraform-with-testcontainers-and-localstack.mdx @@ -22,7 +22,7 @@ leadimage: "terraform-init-hooks.png" LocalStack is a robust tool that emulates a local AWS cloud stack, allowing engineers to test and develop apps using AWS services directly on their local environments. This tool is essential for enhancing developer experience, reducing development costs and increasing efficiency. -In LocalStack, [**initialization hooks**](/aws/capabilities/config/initialization-hooks) are scripts that customize or initialize your LocalStack instance at different stages of its lifecycle. +In LocalStack, [**initialization hooks**](/aws/configuration/advanced/initialization-hooks) are scripts that customize or initialize your LocalStack instance at different stages of its lifecycle. Up until now, the supported hooks could be shell or Python scripts executed at predefined lifecycle phases — BOOT, START, READY, and SHUTDOWN. By placing scripts in the respective directories (`/etc/localstack/init/{stage}.d`), developers can automate tasks like setting up initial states, configuring services, or performing clean-up activities. @@ -80,7 +80,7 @@ localstack start -e EXTENSION_AUTO_INSTALL=localstack-extension-terraform-init \ ``` This is the easiest way to quickly spin up the desired services at startup. -The command starts LocalStack with the configuration to automatically install the **`localstack-extension-terraform-init`** [extension](/aws/capabilities/extensions/) and +The command starts LocalStack with the configuration to automatically install the **`localstack-extension-terraform-init`** [extension](/aws/integrations/extensions/) and mount the necessary files into the container: the Terraform configuration file and the Lambda JAR file. The extension will install both `terraform` and `tflocal` into your LocalStack container, and enable the init hook runners to detect Terraform files. You can also organize your Terraform files into subdirectories if you want. @@ -121,7 +121,7 @@ services: Environment Variables: - **LOCALSTACK_AUTH_TOKEN**: Required for using LocalStack for AWS. - **DEBUG**: Set to 1 to enable verbose logging of the container. -- **EXTENSION_AUTO_INSTALL**: Automatically installs specified LocalStack [extensions](/aws/capabilities/extensions/), in this case, `localstack-extension-terraform-init` which allows Terraform files to be directly used as init hooks. +- **EXTENSION_AUTO_INSTALL**: Automatically installs specified LocalStack [extensions](/aws/integrations/extensions/), in this case, `localstack-extension-terraform-init` which allows Terraform files to be directly used as init hooks. Volumes: - Docker Socket: Mounts the Docker socket `/var/run/docker.sock` from the host into the container. diff --git a/src/styles/custom.css b/src/styles/custom.css index a6b460d4f..b3de3cd9b 100644 --- a/src/styles/custom.css +++ b/src/styles/custom.css @@ -102,6 +102,19 @@ vertical-align: middle; } +.users-icon::before { + content: ""; + display: inline-block; + width: 16px; + height: 16px; + background-image: url('/src/assets/images/users.svg'); + background-size: contain; + background-repeat: no-repeat; + background-position: center; + margin-right: 6px; + vertical-align: middle; +} + .book-icon::before { content: ""; display: inline-block;