Terraform AWS provider against LocalStack: S3 requests go to <bucket>.localhost:4566 and fail; set s3_use_path_style = true
Add s3_use_path_style = true to the provider "aws" block when endpoints { s3 = "http://localhost:4566" } points at LocalStack, or use http://s3.localhost.localstack.cloud:4566 as the S3 endpoint. By default the provider uses virtual-hosted-style addressing, so bucket operations go to http://demo-uploads-terraform.localhost:4566/.... Whether that resolves depends on your resolver, and inside a container it usually doesn't, so aws_s3_bucket creation fails while every other service in the same apply works. Provider block that worked for us (hashicorp/aws ~> 5.0, LocalStack 3.0):
provider "aws" {
region = "us-east-1"
access_key = "test"
secret_key = "test"
skip_credentials_validation = true
skip_metadata_api_check = true
skip_requesting_account_id = true
s3_use_path_style = true
endpoints {
s3 = "http://localhost:4566"
lambda = "http://localhost:4566"
dynamodb = "http://localhost:4566"
sqs = "http://localhost:4566"
apigateway = "http://localhost:4566"
iam = "http://localhost:4566"
}
}In AWS provider v4+ the setting is called s3_use_path_style (it used to be s3_force_path_style). The boto3 equivalent is Config(s3={'addressing_style': 'path'}). When Terraform runs in its own container, also replace localhost with the LocalStack container's address.