调用Localstack SQS队列Peeking API时出现S3 404错误求助

问题详情 #

尝试使用LocalStack官方文档中的路径方式调用SQS队列Peeking API，却收到S3的NoSuchBucket错误，且未启用S3服务。

执行的curl命令 #

curl "http://localhost:4566/_aws/sqs/messages?QueueUrl=http://queue.localhost.localstack.cloud:4566/000000000000/queue"

返回的错误信息 #

<?xml version='1.0' encoding='utf-8'?>
<ErrorResponse><Error><Code>NoSuchBucket</Code><Message>The specified bucket does not exist</Message><Type>Sender</Type></Error><RequestId>W9WPTXP97BNLX1TFB2VU703TA8TPENLVJ3TBOQ4IS9DMWNJ4SR27</RequestId></ErrorResponse>%

Docker Compose环境变量配置 #

environment:
- AWS_DEFAULT_REGION=us-east-1
- DEFAULT_REGION=us-east-1
- EDGE_PORT=4566
- SERVICES=sns, sqs
- LS_LOG=trace
ports:
- '4566:4566'
volumes:

容器日志信息 #

GET localhost:4566/_aws/sqs/messages?QueueUrl=http://queue.localhost.localstack.cloud:4566/000000000000/queue
2023-01-26T17:52:02.045  INFO --- [   asgi_gw_0] localstack.request.aws     : AWS s3.GetObject => 404 (NoSuchBucket); GetObjectRequest({'Bucket': '_aws', 'IfMatch': None, 'IfModifiedSince': None, 'IfNoneMatch': None, 'IfUnmodifiedSince': None, 'Key': 'sqs/messages', 'Range': None, 'ResponseCacheControl': None, 'ResponseContentDisposition': None, 'ResponseContentEncoding': None, 'ResponseContentLanguage': None, 'ResponseContentType': None, 'ResponseExpires': None, 'VersionId': None, 'SSECustomerAlgorithm': None, 'SSECustomerKey': None, 'SSECustomerKeyMD5': None, 'RequestPayer': None, 'PartNumber': None, 'ExpectedBucketOwner': None, 'ChecksumMode': None}, headers={'Host': 'localhost:4566', 'User-Agent': 'curl/7.77.0', 'Accept': '*/*', 'x-localstack-tgt-api': 's3', 'Authorization': 'AWS4-HMAC-SHA256 Credential=000000000000/20160623/us-east-1/s3/aws4_request, SignedHeaders=content-type;host;x-amz-date;x-amz-target, Signature=1234', 'x-localstack-edge': 'http://localhost:4566', 'X-Forwarded-For': '127.0.0.1, localhost:4566', 'Connection': 'close'}); NoSuchBucket(The specified bucket does not exist, headers={'Content-Type': 'text/xml', 'Content-Length': '258', 'x-amz-request-id': 'Z45RC1D5WHI9WLFRZXV7ARWF3VRVL1V26XCUFDVV946B5XRMA1JN', 'Access-Control-Allow-Origin': '*', 'Access-Control-Allow-Methods': 'HEAD,GET,PUT,POST,DELETE,OPTIONS,PATCH', 'Access-Control-Allow-Headers': 'authorization,cache-control,content-length,content-md5,content-type,etag,location,x-amz-acl,x-amz-content-sha256,x-amz-date,x-amz-request-id,x-amz-security-token,x-amz-tagging,x-amz-target,x-amz-user-agent,x-amz-version-id,x-amzn-requestid,x-localstack-target,amz-sdk-invocation-id,amz-sdk-request', 'Access-Control-Expose-Headers': 'etag,x-amz-version-id'})

问题原因 #

从日志可见，LocalStack将请求错误解析为S3的GetObject操作：把路径/_aws/sqs/messages中的_aws识别为S3存储桶名称，sqs/messages识别为对象Key，而当前未启用S3服务，因此返回NoSuchBucket错误。

解决方法 #

1. 使用AWS CLI替代curl调用
   采用LocalStack兼容的AWS CLI命令查看队列消息，这是更稳定的方式：

   aws --endpoint-url=http://localhost:4566 sqs receive-message --queue-url http://queue.localhost.localstack.cloud:4566/000000000000/queue
   

2. 指定请求目标为SQS
   若坚持使用curl，需在请求头中添加x-localstack-target: sqs，明确告诉LocalStack将请求路由到SQS服务：

   curl -H "x-localstack-target: sqs" "http://localhost:4566/_aws/sqs/messages?QueueUrl=http://queue.localhost.localstack.cloud:4566/000000000000/queue"
   

3. 升级LocalStack版本
   该问题可能是特定版本的路由逻辑bug，尝试升级到最新稳定版本，修复已知的路由解析问题。

内容的提问来源于stack exchange，提问作者Rui Chen