From 5185af10f9a310e36ddf3e864bec7f2c24388406 Mon Sep 17 00:00:00 2001
From: "Jose J. Escobar" <53836904+jescobar-docker@users.noreply.github.com>
Date: Thu, 19 Sep 2019 02:42:50 -0700
Subject: [PATCH] Update s3.md (#9477)

Because in the preceding paragraphs we talk about creating a bucket and/or a user and there are also bucket and user policies, I thing it is important to make clear the example policy is a 'user' policy and not a bucket policy.

Added a link to AWS for information about creating a user policy.
---
 ee/dtr/admin/configure/external-storage/s3.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ee/dtr/admin/configure/external-storage/s3.md b/ee/dtr/admin/configure/external-storage/s3.md
index a47ebea055..5bb1380698 100644
--- a/ee/dtr/admin/configure/external-storage/s3.md
+++ b/ee/dtr/admin/configure/external-storage/s3.md
@@ -24,12 +24,12 @@ Start by
 Then, as a best practice you should
 [create a new IAM user](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html)
 just for the DTR
-integration and apply an IAM policy that ensures the user has limited permissions.
+integration and apply an [IAM policy](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) that ensures the user has limited permissions.
 
 This user only needs permissions to access the bucket that you'll use to store
 images, and be able to read, write, and delete files.
 
-Here's an example of a policy like that:
+Here's an example of a user policy:
 
 ```json
 {