Merge pull request #399 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/connections/storage/catalog/aws-s3/index.md

@@ -38,9 +38,10 @@ To complete this section, you need access to your AWS dashboard.
 
 1. Create a new S3 bucket in your preferred region. For more information, see Amazon's documentation, [Create your first S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-bucket.html){:target="_blank"}. 
 2. Create a new IAM role for Segment to assume. For more information, see Amazon's documentation, [Creating a role to delegate permissions to an IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user.html){:target="_blank"}.
-    1. When prompted to enter an Account ID, enter `595280932656`. (You cannot enter an ARN in this step. In step 4, you can update the `Principal` to a specific role after you create an IAM role.)
-    2. Click the **Require External ID** checkbox.
-    3. Enter your Segment Workspace ID in the **External ID** field.
+    1. Select the **AWS account** type from the list of trusted entities. 
+    2. When prompted to enter an Account ID, enter `595280932656`. (You cannot enter an ARN in this step. In step 4, you can update the `Principal` to a specific role after you create an IAM role.)
+    3. Click the **Require External ID** checkbox.
+    4. Enter your Segment Workspace ID in the **External ID** field.
 3. Attach the following policy to the IAM role created in step 2. Replace `<YOUR_BUCKET_NAME>` with the name of the S3 bucket you created in step 1.    
     ```json 
     {
@@ -488,4 +489,4 @@ For user-property destinations, Segment sends an [identify](/docs/connections/sp
 
 When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs send updates for users whose membership has changed since the last sync.
 
-{% include content/destination-footer.md %}
+{% include content/destination-footer.md %}