You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running localstack through docker and have enabled SQS and S3 for this test. Additionally, I am invoking my Lambda through AWS SAM local, in a docker container. The following Python code to access localstack SQS through Boto3 works perfectly:
I get the error: An error occurred (NoSuchBucket) when calling the ListBuckets operation: The specified bucket does not exist: NoSuchBucket. I've made sure that the ports are correct and that through the normal aws local CLI I can manage S3 in localstack, so I have absolutely no idea as to what would be causing this. If anyone knowledgeable with AWS SAM/localstack S3/boto3 could give me some insight I would greatly appreciate it.
The text was updated successfully, but these errors were encountered:
Thanks for reporting @zachschultz . My assumption would be that this is related to the difference between domain-style addressing and path-style addressing in S3. See also the note in the Troubleshooting section of the README.
I am running localstack through docker and have enabled SQS and S3 for this test. Additionally, I am invoking my Lambda through AWS SAM local, in a docker container. The following Python code to access localstack SQS through Boto3 works perfectly:
However, when I try to use S3 instead, like so:
I get the error:
An error occurred (NoSuchBucket) when calling the ListBuckets operation: The specified bucket does not exist: NoSuchBucket
. I've made sure that the ports are correct and that through the normal aws local CLI I can manage S3 in localstack, so I have absolutely no idea as to what would be causing this. If anyone knowledgeable with AWS SAM/localstack S3/boto3 could give me some insight I would greatly appreciate it.The text was updated successfully, but these errors were encountered: