Closed afreisinger closed 1 week ago
Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.
Hi @afreisinger,
Thanks for reaching out.
This is a known "bug" introduced by the Terraform aws
provider >5.55.0
and it seems it won't go away until >6.0.0
as it's part of their aws-go-sdk-v2 migration to fall back on a pseudo region called aws-global
.
As a temporary work around, please remove any .
form your s3 bucket names and all should behave as expected.
You can find the comment addressing the issue here: https://github.com/localstack/terraform-local/pull/57#issuecomment-2188342525
Thanks a lot @lakkeger, it worked for me ! Regards Adrian
Is there an existing issue for this?
Current Behavior
I am using tflocal with my localstack S3 instance but the console show me the follow error:
ValueError: 'aws-global' is not a valid AWS region name for s3 2024-07-07T20:50:05.506 INFO --- [et.reactor-1] localstack.request.aws : AWS s3.HeadBucket => 500 (InternalError)
Expected Behavior
No response
How are you starting LocalStack?
With the
localstack
scriptSteps To Reproduce
localstack start -d tflocal init tflocal plan tflocal apply
Environment
Anything else?
provider.tf snnipet
main.tf