Daniel Frąk

The issue turned out to be AWS SDK proxies not supporting IP ranges: https://github.com/aws/aws-sdk-java-v2/issues/5399

I'll see if I can access the LocalStack logs on CI. Could you tell me what logs I should look for and if I should start LocalStack with any specific...

I managed to retrieve the LocalStack logs from CI and it looks like AWS SDK is actually hitting LocalStack endpoints: ``` LocalStack version: 3.2.1.dev LocalStack Docker container id: dc9c52945a79 LocalStack...

Oh, right! I haven't noticed that these are logs for SQS XD Context switching is hard. I do have SQS code in my app, although I must admit I didn't...

I ran LocalStack with `LS_LOG=trace` and the logs were a repeated variation of this: ``` 2024-03-29T07:53:44.740 DEBUG --- [et.reactor-1] rolo.gateway.wsgi : POST 172.17.0.1:32773/ 2024-03-29T07:53:44.746 DEBUG --- [et.reactor-0] rolo.gateway.wsgi : POST...

According to my logs it hangs at creating a bucket in `@BeforeEach`, then deleting a bucket in `@AfterEach` - so at least these API operations seem problematic. --- I have...

I believe the issue was with how AWS SDK deals with proxy env variables. I'm planning to close all related issues soon (here and elsewhere) but I'm waiting for a...

To give some promised context, the cause of our issue is described here: https://github.com/aws/aws-sdk-java-v2/issues/5399

Thanks for the fast response! I changed the docker-compose like this: ``` localstack: image: localstack/localstack:3.4.0 restart: unless-stopped ports: - "4566:4566" environment: - DEBUG=1 - GATEWAY_SERVER=twisted volumes: - ./localstack/localstack-script.sh:/etc/localstack/init/ready.d/script.sh # Init...

For whatever reason, using `localstack:latest` like this: ```yaml localstack: image: localstack/localstack:latest restart: unless-stopped ports: - "4566:4566" environment: - DEBUG=1 - LS_LOG=trace - GATEWAY_SERVER=twisted volumes: - ./localstack/localstack-script.sh:/etc/localstack/init/ready.d/script.sh # Init script -...