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


The following commit(s) were added to refs/heads/gh-pages by this push:
     new 9df925f  edits
9df925f is described below

commit 9df925fa7bcc8e7b9b42d6127c4535db8f1947b8
Author: Bridget Bevens <[email protected]>
AuthorDate: Wed Jan 30 15:07:21 2019 -0800

    edits
---
 _docs/connect-a-data-source/plugins/110-s3-storage-plugin.md | 8 +++-----
 1 file changed, 3 insertions(+), 5 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 73dbb5d..92fa168 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
@@ -1,6 +1,6 @@
 ---
 title: "S3 Storage Plugin"
-date: 2019-01-11
+date: 2019-01-30
 parent: "Connect a Data Source"
 ---
 Drill works with data stored in the cloud. With a few simple steps, you can 
configure the S3 storage plugin for Drill and be off to the races running 
queries. 
@@ -51,16 +51,14 @@ To configure the access keys in Drill's core-site.xml file, 
navigate to the `$DR
 
 ### 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. For example:
+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. For 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.  
+       </configuration>    
 
 ##Configuring the S3 Storage Plugin
 

Reply via email to