This is an automated email from the ASF dual-hosted git repository. bridgetb pushed a commit to branch gh-pages in repository https://gitbox.apache.org/repos/asf/drill.git
commit 11dfe910c35cca6ee34cbaa79dc8cb16b6bfeeff Author: Nitin S <[email protected]> AuthorDate: Wed Sep 19 22:48:47 2018 -0700 Indentation Changes to S3 config for IAM roles Indentation Changes to S3 config for IAM roles --- _docs/connect-a-data-source/plugins/110-s3-storage-plugin.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) 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 4b00d55..e2b6e29 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 @@ -53,12 +53,12 @@ To configure the access keys in Drill's core-site.xml file, navigate to the `$DR 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> + <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.
