Permalink
Browse files

Merge branch 'lm01/master'

  • Loading branch information...
Jeffrey Horn
Jeffrey Horn committed May 9, 2017
2 parents a26bd63 + 9597d65 commit 90eb69c6e7a58c939c4eba59bd7d394c0984f2c8
Showing with 54 additions and 13 deletions.
  1. +44 −0 .gitignore
  2. +10 −13 README.md
@@ -1,3 +1,47 @@
# Secrets not to be shared
.env
accessKeys.csv

# Created by https://www.gitignore.io/api/macos,linux

### macOS ###
*.DS_Store
.AppleDouble
.LSOverride

# Icon must end with two \r
Icon
# Thumbnails
._*
# Files that might appear in the root of a volume
.DocumentRevisions-V100
.fseventsd
.Spotlight-V100
.TemporaryItems
.Trashes
.VolumeIcon.icns
.com.apple.timemachine.donotpresent
# Directories potentially created on remote AFP share
.AppleDB
.AppleDesktop
Network Trash Folder
Temporary Items
.apdisk


### Linux ###
*~

# temporary files which can be created if a process still has a handle open of a deleted file
.fuse_hidden*

# KDE directory preferences
.directory

# Linux trash folder which might appear on any partition or disk
.Trash-*

# .nfs files are created when an open file is removed but is still being accessed
.nfs*

# End of https://www.gitignore.io/api/macos,linux
@@ -17,7 +17,7 @@ Follow the steps outlined to create and gain programmatic access to an AWS S3
- A Credit card is required to verify your AWS account.

If you do not have an account, open [AWS](https://aws.amazon.com/) and click
`Sign In to the Console`.
`Create a Free Account`.
Amazon provides a [free tier](http://aws.amazon.com/free/),
with some limitations, for twelve months after you sign-up for an AWS account.

@@ -40,9 +40,9 @@ Using restrictive access control with AWS ensures that even if an identity is

## AWS S3 access control

1. Open the [AWS Consle](https://console.aws.amazon.com/console/) in your
1. Open the [AWS Console](https://console.aws.amazon.com/console/) in your
browser
1. From the `AWS` console open tabs for
1. From the `AWS` console, select `All Services`, and open tabs for
`IAM` _(Identity and Access Management)_ and `S3` _(Simple Storage Service)_.

### Identity and Access Management (IAM)
@@ -63,13 +63,11 @@ In the [IAM](https://console.aws.amazon.com/iam) tab:
_Then_
1. Click on your newly created user.
1. Click on the security credentials tab.
1. Click the small red `x` to the right of your existing access key to delete it.
1. 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
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 `Download Credentials`.
1. Save the file `credentials.csv` to this repository.
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).
@@ -95,13 +93,12 @@ In the [S3](https://console.aws.amazon.com/s3) tab:
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 Standard` for the `Region`.
1. Select `US East (N. Virginia)` for the `Region`.
1. Click `Create`.
1. Highlight your bucket and select the `Properties` tab on the right side.
1. Open the `Permissions` dropdown in the right sidebar.
1. Click `Add bucket policy` near the bottom of the `Permissions` dropdown.
1. At the bottom of the `Bucket Policy Editor` modal,
click `AWS Policy Generator`. This opens the AWS Policy Generator page.
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

1. Step 1: Select Policy Type
@@ -123,7 +120,7 @@ In the [S3](https://console.aws.amazon.com/s3) tab:
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` modal.
1. Paste the bucket policy into the `Bucket Policy Editor` field.
1. Click `Save`.
1. Click `Save` in the `Permissions` dropdown.

0 comments on commit 90eb69c

Please sign in to comment.