steveloughran commented on PR #8058: URL: https://github.com/apache/hadoop/pull/8058#issuecomment-3532453285
also, I think we may want to add an enum of fallbacks ``` fs.s3a.endpoint.region.fallback = <ec2, sdk, central> ``` this would define the policy for calculating the region of a bucket which isn't set explicitly, or inferred from the endpoint (vpce, aws, external). today's behaviour is "central", which doesn't work when the network is locked down in a VPC in a different region. if you set ec2 or sdk, then unless the region is declared (or set to those explicit region names) then the fallback will be whichever of the defaults. There's one more thing to consider here: should we always do an EC2/IAM probe before falling back to central? pro: works great in EC2 with local regions con: change in behavior when working with remote buckts. I think the fallback option has better compatibility. now, given we are doing ec2 region resolution in our own code, we have a choice of what to do when the resolution fails. so what does endopoint.region=ec2 endpoint.fallback=ec2 mean? so maybe we only need two fallbacks central: today sdk: do the chain of env vars, sysprops and iam info. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
