bug: AWS Java SDK 2 returns a 403 error about localstack HOT 3 CLOSED

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.

from localstack.

Hello @markwimpory !
It seems in your jenkins instance, there is some kind of proxy setup intercepting the requests to LocalStack, the return message is not sent by LocalStack, but some squid proxy instance. Nothing in LocalStack would return the response you were given.
These log parts you sent:

2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "Server: squid[\r][\n]"
2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "Mime-Version: 1.0[\r][\n]"
2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "Date: Fri, 26 Jan 2024 11:21:36 GMT[\r][\n]"
2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "Content-Type: text/html;charset=utf-8[\r][\n]"
2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "Content-Length: 4317[\r][\n]"
2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "X-Squid-Error: ERR_ACCESS_DENIED 0[\r][\n]"
2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "Vary: Accept-Language[\r][\n]"
2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "Content-Language: en[\r][\n]"
2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "X-Cache: MISS from ip-10-92-1-254.ops.iptho.co.uk[\r][\n]"
2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "X-Cache-Lookup: NONE from ip-10-92-1-254.ops.iptho.co.uk:8080[\r][\n]"
2024-01-26 11:21:36 DEBUG wire:73 - http-outgoing-0 << "Via: 1.1 ip-10-92-1-254.ops.iptho.co.uk (squid)[\r][\n]"

Hint toward this, also notice the X-Squid-Error header.

As a resolution, you should try to exclude the traffic to localstack from the proxying, if it is not necessary.

It is very possible that the Apache HTTP client picks up this proxy, while the urlconnection client does not, or is somehow differently configured.

I am sorry I cannot help any further, as I have no insight into your proxy setups, but hope I was able to get you closer to a solution.

from localstack.

Hello 👋! It looks like this issue hasn’t been active in longer than two weeks. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

from localstack.