Update 019/master from study-template #42

merged 3 commits into from Aug 2, 2017
File filter...
Filter file types
Jump to file or symbol
Failed to load files and symbols.
+46 −8
Diff settings


Just for now

Add step-by-step imgs & more detailed instructions

Add images to help developers follow process more easily.
Add more explicit instructions for less confusion.

Close #37
Close #38
  • Loading branch information...
jcornmanhomonoff committed Aug 2, 2017
commit f6a773e503692c3ff1dd0aded9889f82ebc4c5a8
Copy path View file
@@ -51,25 +51,50 @@ Identities are how we grant access to AWS APIs.

In the [IAM](https://console.aws.amazon.com/iam) tab:

*Getting to the IAM tab:*



*Identity and Access Management (IAM)*

1. Select `Users` in the left sidebar.

1. Click `Add User` near the top of the page.

1. Enter `wdi-upload` into the text box.

1. Under access type, check `Programmatic Access`
1. Click Next

1. Click Next: Permissions

1. Highlight Add User to Group
1. Click Next

1. Click Next: Review

1. Click create User

1. Click on your newly created user.
1. Click on the security credentials tab.
1. Click the small `x` to the right of your existing access key to delete it.
- Make sure `wdi-upload` is checked.
- Click directly on `wdi-upload`
9. Click on the security credentials tab.
10. Click the small `x` to the right of your existing access key to delete it.
1. Click `Create access key`
1. When complete, click `download .csv file` and save the CSV to this repository.(this is
1. When you recieve a `Success` response, click `download .csv file` and save the CSV to this repository.(this is
the only time you'll be able to see your access key, but you can generate a new one anytime
and are encouraged to rotate them frequently)
1. Click `Close`
1. Click on the newly created user.
1. Copy the `User ARN` _(Amazon Resource Name)_ at the top of the page and save it in [arn.txt](arn.txt).

We'll need the User ARN to grant access to an S3 bucket we'll use for uploads.
@@ -88,15 +113,18 @@ S3 stores files you upload in `buckets`. A bucket is a top-level namespace
for your files.

In the [S3](https://console.aws.amazon.com/s3) tab:

1. Click `Create Bucket`.
This opens the `Create a Bucket - Select a Bucket Name and Region` modal.
1. Enter a name in the `Bucket Name` box. It must be unique among all S3
buckets and in all lowercase characters.
1. Select `US East (N. Virginia)` for the `Region`.
1. Click `Create`.
1. Highlight your bucket and select the `Permissions` tab.

1. Click `Bucket policy` near the bottom of the `Permissions` tab.
1. At the bottom of the `Bucket Policy Editor` page,
click `Policy Generator`. This opens the AWS Policy Generator page.
1. On the AWS Policy Generator page
@@ -106,16 +134,26 @@ In the [S3](https://console.aws.amazon.com/s3) tab:
1. Select `Allow` for `Effect`.
1. Paste the User ARN into the `Principal` box.
1. Select `PutObject` and `PutObjectAcl` for `Actions`.

1. Enter `arn:aws:s3:::<bucket_name>/*` into the
`Amazon Resource Name (ARN)` box.
- Make sure you add `/*` at the end of your user ARN for this step.

1. Click the `Add Statement`.
1. Step 3: Generate Policy
1. Click `Generate Policy`
1. Copy the JSON from the `Policy JSON Document` modal.
1. Return to the S3 tab.
1. Paste the bucket policy into the `Bucket Policy Editor` field.
1. Click `Save`.
1. Click `Save` in the `Permissions` dropdown.
2. Click on `Access Control List`
3. Click on your account
4. A modal will pop up.
1. Click `Save` in the modal.

You have now created and granted access to an S3 bucket.

ProTip! Use n and p to navigate between commits in a pull request.