LocalStack Connector

The LocalStack connector provides the same functionality as the AWS connector, but proxied to a LocalStack instance for local development and testing. All AWS tools work identically, targeting your local LocalStack environment instead of production AWS.

Authentication

The connector points to a LocalStack endpoint. Credentials can be any non-empty string since LocalStack does not validate them by default.

{
  "name": "LocalStack Dev",
  "source_type": "localstack",
  "config": {
    "endpoint_url": "http://localhost:4566",
    "access_key_id": "test",
    "secret_access_key": "test",
    "region": "us-east-1"
  }
}

Variable	Required	Description
endpoint_url	Yes	LocalStack endpoint URL (e.g., http://localhost:4566)
access_key_id	No	AWS access key ID (any value works with default LocalStack)
secret_access_key	No	AWS secret access key (any value works with default LocalStack)
region	No	AWS region (default: us-east-1)

TIP

If you run LocalStack with ENFORCE_IAM=1, you will need valid IAM credentials. Otherwise, any non-empty string works for access_key_id and secret_access_key.

Live Tools

The LocalStack connector exposes the same 8 tools as the AWS connector, all proxied to your LocalStack instance:

Tool	Description	Arguments
list_ec2_instances	List EC2 instances	filters?, instance_ids?
describe_ec2_instance	Get details of an EC2 instance	instance_id
list_s3_buckets	List S3 buckets	prefix?
list_s3_objects	List objects in an S3 bucket	bucket, prefix?, max_keys?
list_lambda_functions	List Lambda functions	region?
describe_lambda	Get Lambda function details	function_name
list_iam_users	List IAM users	path_prefix?
list_iam_roles	List IAM roles	path_prefix?

Example: Agent Using LocalStack Tools

User: "List all S3 buckets in my local environment"

Agent: Let me check your LocalStack S3.
→ Calls list_s3_buckets()
→ Returns: "Found 3 buckets in LocalStack:
  - test-uploads (created: 2026-03-15)
  - dev-assets (created: 2026-03-10)
  - lambda-artifacts (created: 2026-03-01)"

User: "What Lambda functions are deployed locally?"

Agent: I'll check LocalStack Lambda.
→ Calls list_lambda_functions()
→ Returns: "2 Lambda functions deployed:
  - process-orders (Python 3.12, 256MB)
  - send-notifications (Node.js 20, 128MB)"

ETL Ingestion

This connector does not support ETL ingestion. Use it for live exploration and testing of local AWS resources. For graph ingestion, use the AWS connector with production credentials.

Configuration Reference

{
  "name": "LocalStack Dev",
  "source_type": "localstack",
  "config": {
    "endpoint_url": "http://localhost:4566",
    "access_key_id": "test",
    "secret_access_key": "test",
    "region": "us-east-1"
  }
}

Field	Type	Default	Description
endpoint_url	string	required	LocalStack endpoint URL
access_key_id	string	test	AWS access key ID
secret_access_key	string	test	AWS secret access key
region	string	us-east-1	AWS region

Troubleshooting

Error	Cause	Fix
Connection refused	LocalStack is not running	Start LocalStack with localstack start or docker compose up
Service not available	Requested AWS service not enabled in LocalStack	Check that the service is supported in your LocalStack edition (Community vs Pro)
InvalidClientTokenId	IAM enforcement is enabled	Set valid credentials or disable ENFORCE_IAM in LocalStack
Resource not found	Resource does not exist in the local environment	Create the resource first using awslocal CLI or the AWS SDK
Endpoint URL mismatch	Wrong port or hostname	Default LocalStack port is 4566; verify with localstack status