Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.4.0
-
None
Description
After commented out the default region in my ~/.aws/config [default} profile, test ITestS3AConfiguration. testS3SpecificSignerOverride() fails
[ERROR] testS3SpecificSignerOverride(org.apache.hadoop.fs.s3a.ITestS3AConfiguration) Time elapsed: 0.054 s <<< ERROR!
software.amazon.awssdk.core.exception.SdkClientException: Unable to load region from any of the providers in the chain software.amazon.awssdk.regions.providers.DefaultAwsRegionProviderChain@12c626f8: [software.amazon.awssdk.regions.providers.SystemSettingsRegionProvider@ae63559: Unable to load region from system settings. Region must be specified either via environment variable (AWS_REGION) or system property (aws.region)., software.amazon.awssdk.regions.providers.AwsProfileRegionProvider@6e6cfd4c: No region provided in profile: default, software.amazon.awssdk.regions.providers.InstanceProfileRegionProvider@139147de: EC2 Metadata is disabled. Unable to retrieve region information from EC2 Metadata service.]
I'm worried the sdk update has rolled back to the 3.3.x region problems where well-configured developer setups / ec2 deployments hid problems. certainly we can see the code is checking these paths
Attachments
Issue Links
- links to