Test AWS-compatible APIs with LocalStack on Sealos. Point your SDK or CLI at the hosted gateway to develop S3, SQS, and other cloud integrations.
Launch in your Sealos workspace.
Start with the resources defined by the LocalStack template. Review CPU, memory, persistent storage, and network allocations for every service in Canvas. Capacity needs depend on your data and workload; monitor usage as they grow.
Template configuration and setupUse the application URL or connection details shown in Canvas. Follow the deployment guide for first-time account setup or client configuration, and keep generated credentials available for that step.
Sealos monthly plans include compute, memory, storage, and traffic. Size your plan for all deployed services. Software licenses and external AI or API services may have separate terms and charges. Confirm the applicable plan and optional charges in Cost Center.
Compare Sealos resource plansFor current cloud charges, refer to Sealos plan pricing. Upstream documentation may reference earlier billing models.
LocalStack is an AWS-compatible cloud emulator for development and testing. This template deploys the final legacy Community release, LocalStack 4.14.0, behind a generated Sealos HTTPS endpoint.
LocalStack provides AWS-compatible APIs for services such as S3, SQS, SNS, DynamoDB, CloudFormation, and API Gateway. Applications can point an AWS SDK or CLI at the generated endpoint and exercise cloud workflows in an isolated environment.
The template creates one LocalStack Deployment, a ClusterIP Service, and a TLS Ingress. Port 4566 serves the public gateway. Ports 4510-4559 preserve the official external-service range for cluster clients.
Community 4.14.0 starts with an empty emulator state after each Pod replacement. Recreate test fixtures through scripts, Terraform, AWS CDK, or CloudFormation. Local state persistence is available in LocalStack Base and higher plans with an account-based image and auth token.
Container-runtime-backed services such as Lambda execution require a Docker or Kubernetes executor. This template supports gateway-backed services that execute inside the LocalStack process.
The Sealos template includes the LocalStack Community runtime, internal networking, and a public HTTPS gateway.
Architecture Components:
localstack/localstack:4.14.0 with one replica and a recreate update strategy./tmp/localstack-user as a writable temporary directory for the non-root process.4566 and external service ports 4510-4559 inside the cluster./_localstack/health so the running edition, version, and service status are visible.Configuration:
LOCALSTACK_HOST and USE_SSL=1 align generated service URLs with the Sealos HTTPS endpoint.SQS_ENDPOINT_STRATEGY=path keeps queue URLs on the generated hostname and public TLS route.TEMP=/tmp/localstack-user places temporary service state in a directory owned by user 1000.DNS_ADDRESS=0 uses cluster DNS and keeps the non-root runtime on unprivileged ports./_localstack/health route.1000 with a runtime-default seccomp profile and dropped Linux capabilities.100m CPU and 256Mi memory.Release and License Information:
LocalStack 4.14.0 is the final legacy Community release and uses the Apache License 2.0. Account-based LocalStack images provide maintained releases and plans for current commercial workflows.
Sealos is a Kubernetes-based cloud operating system that manages application resources through a visual Canvas. Deploying LocalStack on Sealos provides:
100m CPU and 256Mi memory profile.The generated endpoint is publicly reachable. Use synthetic test data and remove the instance after each testing session.
Set standard AWS development credentials and direct the AWS CLI to the generated HTTPS endpoint:
export AWS_ACCESS_KEY_ID=test
export AWS_SECRET_ACCESS_KEY=test
export AWS_DEFAULT_REGION=us-east-1
export LOCALSTACK_URL=https://<generated-localstack-host>
aws --endpoint-url "$LOCALSTACK_URL" s3api create-bucket --bucket sealos-demo
aws --endpoint-url "$LOCALSTACK_URL" s3api list-buckets
aws --endpoint-url "$LOCALSTACK_URL" sqs create-queue --queue-name sealos-demo
aws --endpoint-url "$LOCALSTACK_URL" sqs list-queues
LocalStack Community accepts AWS-compatible request credentials. Development values such as test fit isolated test workloads.
Each Pod replacement creates a fresh Community emulator state. Keep fixture creation in version-controlled setup scripts or infrastructure definitions so every test environment starts consistently.
LocalStack Base and higher plans provide local state persistence. Those plans use an account-based image, an auth token, and a mounted LocalStack volume.
Use the Sealos Canvas after deployment to adjust the LocalStack workload:
SERVICES and EAGER_SERVICE_LOADING=1 when a fixed service allowlist improves startup behavior.Use the exact HTTPS URL shown by the App resource and pass its origin through the client's endpoint option. AWS CLI uses --endpoint-url, while SDKs expose an equivalent endpoint setting.
The path-style URL keeps the queue on the generated Sealos hostname. Pass the returned QueueUrl directly to SQS operations.
Lambda container execution and similar runtime-backed features require Docker or a Kubernetes executor with matching permissions. Gateway-backed services such as S3, SQS, SNS, and DynamoDB fit the default template profile.
Increase CPU and memory from the Deployment resource card. The default profile targets compact development workflows.
This Sealos template follows the license of the templates repository. LocalStack Community is available under the Apache License 2.0.
A shorter path from an app you want to an app you can run. Sealos brings deployment and ongoing operations into one place.
Start with a ready-made template. Review its configuration and launch from the Sealos console.
Run on managed infrastructure with built-in workload scheduling and recovery.
Give your application a public HTTPS endpoint with certificates managed for you.
Keep application data on persistent volumes across container restarts.
Adjust CPU, memory, and replicas from the console as your workload changes.
Sealos provisions the resources defined by your template and brings them together in your workspace.
Container workloads with configurable CPU, memory, and replicas.
An address for your app, with managed TLS certificates.
A database provisioned alongside your app when the template calls for one.
Storage for the files and data your application needs to keep.
Application settings and secrets configured in one place.
Inspect container logs and resource usage from the console.
Resources and their configuration vary by template. Review the deployment form for this app’s exact setup.
Explore more production-ready templates.
Build production-ready devops templates with Sealos.
Connect databases, APIs, and SaaS tools to a warehouse with Airbyte. Deploy its integration services, PostgreSQL, and object storage on Sealos.
Build production-ready devops templates with Sealos.
BunkerWeb is an open-source Web Application Firewall and reverse proxy that protects web services with secure-by-default NGINX-based traffic handling.
Build production-ready devops templates with Sealos.
Host Tentix on Sealos for AI-assisted support ticket workflows. Connect a knowledge base and AI provider to help staff draft replies and handle customer requests.