Ben Simon Hartung

Hello! I believe this issue was resolved in the community Slack by @simonrw. The solution was to use `localhost:4566` in the `--endpoint-url` of the command, as the init scripts are...

Hello @Dragas and thanks for your report! I'll work on it shortly. This is an interesting bug, because it seems the AWS Java SDK v1 rely on the order of...

Hello @MrZoidberg and @a26-beep, and thanks for your report! This issue should now be fixed by using the following config flag: `PROVIDER_OVERRIDE_APIGATEWAY=next_gen`, starting with LocalStack 3.8. You can read more...

Thanks for the feedback @MrZoidberg! Sorry it took so long 😅 I'll close the issue then. Thanks again for the report 🙏

Hello @PascalArdex and thanks for your report! I'm currently unable to reproduce the issue that you're mentioning. Regarding the issue with the Web Application, this is because you're configuring your...

Hi! I believe adding the default permissions is only done when modifying/setting your CORS rules from the web application, to not "cut you off" directly from using it. If using...

Hello @daniel-frak, It would be nice to be sure that the request is actually hitting LocalStack here, following the change in the AWS SDK. Do you have access to the...

So the S3 client doesn't seem to hit LocalStack though? No requests look like S3 here. But SQS can... Also, from the other issues you've opened, you can safely remove...

Maybe it's something related to the endpoint configuration of S3? Maybe with debug logs of your Java app, we could try to see exactly what endpoint and the host you're...

Hello @nicumaxian and thanks for the report! We have a page in the documentation about S3 addressing style: https://docs.localstack.cloud/user-guide/aws/s3/#path-style-and-virtual-hosted-style-requests In order for LocalStack to be able to understand `Virtual-hosted style`...