bbevens closed pull request #1471: Docs for configuring Drill to S3 Instance
Profiles - DRILL-6748
URL: https://github.com/apache/drill/pull/1471
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/_docs/connect-a-data-source/plugins/110-s3-storage-plugin.md
b/_docs/connect-a-data-source/plugins/110-s3-storage-plugin.md
index b758e80c091..e2b6e29c004 100644
--- a/_docs/connect-a-data-source/plugins/110-s3-storage-plugin.md
+++ b/_docs/connect-a-data-source/plugins/110-s3-storage-plugin.md
@@ -47,7 +47,18 @@ To configure the access keys in Drill's core-site.xml file,
navigate to the `$DR
<name>fs.s3a.endpoint</name>
<value>s3.REGION.amazonaws.com</value>
</property>
- </configuration>
+ </configuration>
+
+### Configuring Drill to use AWS IAM Roles for Accessing S3
+
+If you use IAM roles/Instance profiles, to access data in s3, use the
following settings in your core-site.xml. Do not specify the secret key or
access key properties. As an example:
+
+ <configuration>
+ <property>
+ <name>fs.s3a.aws.credentials.provider</name>
+
<value>com.amazonaws.auth.InstanceProfileCredentialsProvider</value>
+ </property>
+ </configuration>
**Note:** When you rename the file, Hadoop support breaks if `$HADOOP_HOME`
was in the path because Drill pulls in the Drill core-site.xml file instead of
the Hadoop core-site.xml file. In this situation, make the changes in the
Hadoop core-site.xml file. Do not create a core-site.xml file for Drill.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
