If you don't have fs.s3a.endpoint set and lack a region set in
env var AWS_REGION_ENV_VAR, system property aws.region or the file ~/.aws/config
then S3A FS creation fails with the message
"Unable to find a region via the region provider chain."
This is caused by the move to the AWS S3 client builder API in
This is pretty dramatic and no doubt everyone will be asking "why didn't you notice this?",
But in fact there are some reasons.
- when running in EC2, all is well. Meaning our big test runs were all happy.
- if a developer has fs.s3a.endpoint set for the test bucket, all is well.
Those of us who work with buckets in the "regions tend to do this, not least because it can save a HEAD request every time an FS is created.
- if you have a region set in ~/.aws/config then all is well
reason #3 is the real surprise and the one which has really caught us out. Even my tests against buckets in usw-2 through central didn't fail because of course I, like my colleagues, have the AWS cli client installed locally. This was sufficient to make the problem go away. It is also why this has been an intermittent problem on test clusters outside AWS infra: it really depended on the VM/docker image whether things worked or not.
If you have found this JIRA because you are encountering this problem, you can fix it in by explicitly declaring the endpoint in core-site.xml
For Apache Spark, this can be done in spark-defaults.conf
If you know the exact AWS region your data lives in, set the endpoint to be that region's endpoint, and so save an HTTPS request to s3.amazonaws.com every time an S3A Filesystem instance is created.