Loading...
Loading...
Analyze LocalStack logs and debug issues. Use when users need to view LocalStack logs, debug AWS API errors, troubleshoot Lambda functions, identify error patterns, or enable debug mode.
npx skill4agent add localstack/skills localstack-logs# Follow logs in real-time
localstack logs -f
# View last N lines
localstack logs --tail 100
# Via Docker
docker logs localstack-main -f
docker logs localstack-main --tail 200# Filter by service
localstack logs | grep -i s3
localstack logs | grep -i lambda
localstack logs | grep -i dynamodb
# Filter errors only
localstack logs | grep -i error
localstack logs | grep -i exception
# Filter by request ID
localstack logs | grep "request-id-here"# Start with debug mode
DEBUG=1 localstack start -d
# Enable specific debug flags
LS_LOG=trace localstack start -dAWS <service>.<operation> => <status>AWS s3.CreateBucket => 200
AWS dynamodb.PutItem => 200
AWS lambda.Invoke => 200| Error | Possible Cause | Solution |
|---|---|---|
| Resource doesn't exist | Create the resource first |
| IAM policy issue | Check IAM enforcement mode |
| Invalid parameters | Verify request parameters |
| Internal error | Check LocalStack logs for details |
# Lambda function logs appear in LocalStack logs
localstack logs | grep -A 10 "Lambda"
# Or use CloudWatch Logs locally
awslocal logs describe-log-groups
awslocal logs get-log-events \
--log-group-name /aws/lambda/my-function \
--log-stream-name <stream-name>LAMBDA_DEBUG=1 localstack start -d# Check overall health
curl http://localhost:4566/_localstack/health | jq
# Check specific service
curl http://localhost:4566/_localstack/health | jq '.services.s3'localstack statusDEBUG=1