Regression in `aws s3 cp` about aws-cli HOT 6 CLOSED

Hi @aarashy, thanks for reaching out. Could you tell me how you're configuring the CLI region? Also, since you're running it in a container, I'd recommend reading https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html, specifically the following.

In a container environment, we recommend setting the hop limit to 2.

The AWS SDKs use IMDSv2 calls by default. If the IMDSv2 call receives no response, the SDK retries the call and, if still unsuccessful, uses IMDSv1. This can result in a delay, especially in a container environment. In a container environment, if the hop limit is 1, the IMDSv2 response does not return because going to the container is considered an additional network hop. To avoid the process of falling back to IMDSv1 and the resultant delay, in a container environment we recommend that you set the hop limit to 2. For more information, see Configure the instance metadata options.

from aws-cli.

Yeah, this was in a container environment (EKS). Let me try setting that parameter for hop limit. It was strange that it works on the old version with no changes needed, and didn't give a reasonable error message though.

from aws-cli.

@aarashy are you still having this issue?

from aws-cli.

Hey @sean-smith, I haven't tried again yet, will update here when I do.

I suppose this means that in any container environment, I have to make this AWS cli command at least once first, which permanently changes the local state of the host. It's not clear to me yet if this applies to Python SDKs like boto3 as well, where I haven't seen the error.

from aws-cli.

Did adjusting the hop limit work? I'd test it before modifying the dockerfile/python code.

from aws-cli.

Greetings! It looks like this issue hasn’t been active in longer than five days. 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 aws-cli.