agentsclimarketplace

Using localstack

Skill SpillwaveSolutions/using-localstack-plugin/plugins/using-localstack-plugin/skills/using-localstack

Plugin for using localstack and awslocal.

Install
npx -y skills add SpillwaveSolutions/using-localstack-plugin --skill using-localstack

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build, test, and debug AWS-native systems locally with LocalStack (Community/Pro) using awslocal, IaC toolchains, event-driven pipelines, and observability; includes setup, deployment, management, monitoring, and sharp-edge guidance.

SKILL.md

6.2 KB, as published. Nobody here has run it

Mastering LocalStack Pro — Practitioner Skill

Operations-first playbook to emulate AWS locally with high fidelity. Focuses on production-parity workflows (event-driven, streaming, containers, IaC), fast debugging, and deterministic CI.

Audience & Outcomes

  • For senior backend/platform/DevOps/AI-data engineers needing production-parity local AWS for event-driven, streaming, and data/agentic workloads
  • Assumes AWS fluency; focuses on emulator fidelity vs AWS deltas
  • Outcomes: spin up complex stacks locally (EKS/MSK/Aurora/Step Functions), debug IAM/networking/event flows, run deterministic CI/CD

When to Use

  • Stand up AWS stacks locally (S3, Lambda, DynamoDB, API Gateway, EventBridge, MSK, EKS, RDS/Aurora, Step Functions)
  • Build deterministic CI/CD without hitting real AWS
  • Debug IAM, networking, events, or data flows offline before deploying to AWS

When Not to Use

  • Production deployments (LocalStack is for dev/test only)
  • Multi-region/global table testing (single-region emulation)
  • Performance/scale validation (no multi-AZ, different latency profile)
  • Managed service edge cases (simplified IAM enforcement, custom resources may differ)

Community vs Pro

  • Community: core services (S3, basic Dynamo, Lambda, API GW) for simple serverless
  • Pro: advanced services and fidelity (MSK/Kinesis+Pipes, EKS/ECS/Fargate, Aurora/RDS, Step Functions with mocking/visualization, EventBridge schema/pipes, IAM enforcement/Policy Stream, Cloud Pods, offline bundles)

Use Pro when avoiding deploy-to-test cycles outweighs license cost.

Quick Start

  1. Install: pipx install localstack (recommended: isolated Python env, cross-platform) OR brew install localstack/tap/localstack-cli (macOS-only, simpler on M1/M2)

  2. Start:

    • Community: localstack start -d
    • Pro: LOCALSTACK_AUTH_TOKEN=<token> localstack start -d --version x.y.z

  3. Health check: curl http://localhost:4566/_localstack/health | jq
    Verify: All needed services show "available" or "running"

  4. CLI: Use awslocal <service> ... (wrapper for AWS CLI with endpoint preset to localhost:4566)
    Verify: awslocal sts get-caller-identity (should return any identity without error)

  5. S3 smoke: awslocal s3 mb s3://demo && awslocal s3 ls
    Verify: Output includes demo bucket; if not, check logs: docker logs localstack | grep -i s3

  6. DynamoDB smoke: awslocal dynamodb create-table --table-name test --attribute-definitions AttributeName=id,AttributeType=S --key-schema AttributeName=id,KeyType=HASH --billing-mode PAY_PER_REQUEST
    Verify: awslocal dynamodb describe-table --table-name test | jq .Table.TableStatus returns "ACTIVE"
    Debug: If fails, check service health: curl http://localhost:4566/_localstack/health | jq .services.dynamodb

  7. Lambda smoke: Package code, awslocal lambda create-function ..., then invoke
    Verify: Check invocation result and CloudWatch logs: awslocal logs tail /aws/lambda/<function-name>

  8. Events: Create SQS queue/SNS topic/EventBridge rule; wire S3/Lambda triggers; push test event
    See Service Workflows for detailed event-driven patterns

  9. IaC: Use tflocal/cdklocal/CloudFormation against LocalStack
    See IaC Deployment for toolchain setup and patterns

  10. Observe: docker logs localstack, LS_LOG=trace for deep traces
    See Debugging & Observability for troubleshooting

Architecture Concepts

  • Single edge port (4566) routes all service APIs; use *.localhost.localstack.cloud for service hostnames
  • Providers execute actual service logic (SNS→SQS fan-out, S3 event triggers) not stubs; scale/latency differs from AWS
  • Event-first bus: cross-service notifications emitted internally; ideal for testing async S3/SNS/SQS/EventBridge/Lambda flows
  • Hermetic by default: prefer endpoint injection/DNS over hardcoding localhost:4566; treat persistence as optional

Detailed Guides

Examples & Scripts

Official References

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.