Using aws cmdlets with s3 compatible storage has a 15 second delay before communicating with the endpointurl

[nocentino]

Describe the bug

Using Get-S3Object and conjunction with the -endpointurl parameter the cmdlet attempts to retrieve instance metadata. Since this execution is not on an EC2 instance there is a delay which the attempt to get instance metadata times out. This is approximately 15 seconds. Once it times out the connection to s3 compatible storage works fine. If you specify a -Region parameter with any value the cmdlet works properly, in a timely fashion.

Expected Behavior

When using the endpointurl parameter I would expect the ability to disable the instance metadata check.

Current Behavior

There is a 15 second delay due to connection retry attempts on retrieving instance metadata

Reproduction Steps

Get-S3Object -BucketName sql-dumps -SecretKey $SecretKey -AccessKey $AccessKey -endpointurl https://PRIVATEENDPOINTURL

Possible Solution

Allow a -Region parameter value of None to be set to bypass the instance metadata check

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

AWSPowerShell 4.1.348

Targeted .NET Platform

.NET Core

Operating System and version

Windows Server 2016

[nocentino]

Apologies, wrong repo. Opened on proper repo at aws/aws-tools-for-powershell#330

[ashishdhingra]

Duplicate of aws/aws-tools-for-powershell#330

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.