Fork and clone this repository.

Read over all the instructions before proceeding.

Follow the steps outlined to create and gain programmatic access to an AWS S3 bucket.

• An AWS (Amazon Web Services) account
• A Credit card is required to verify your AWS account.

If you do not have an account, open AWS and click Sign In to the Console. Amazon provides a free tier, with some limitations, for twelve months after you sign-up for an AWS account.

Storing large static files is a common need for a web application. Accepting image uploads from authorized users but allowing public read access is a frequent example.

AWS provides a variety of APIs, one of which is easily used for this purpose. This guide helps ensure access to these APIs is restricted.

Why is the important?

Using any metered API has financial risks. Using many APIs may have data risks (information loss or exposure).

Using restrictive access control with AWS ensures that even if an identity is compromised, the actual risks, financial and otherwise, are limited.

1. Open the AWS Consle in your browser
2. From the AWS console open tabs for IAM (Identity and Access Management) and S3 (Simple Storage Service).

Identities are how we grant access to AWS APIs.

In the IAM tab:

1. Select Users in the left sidebar.
2. Click Add User near the top of the page.
3. Enter wdi-upload into the text box.
4. Under access type, check Programmatic Access
5. Click Next
6. Highlight Add User to Group
7. Click Next
8. Click create User Then
9. Click on your newly created user.
10. Click on the security credentials tab.
11. Click the small red x to the right of your existing access key to delete it.
12. Click Create access key
13. 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)
14. Click Download Credentials.
15. Save the file credentials.csv to this repository.
16. Click Close
17. Click on the newly created user.
18. Copy the User ARN (Amazon Resource Name) at the top of the page and save it in arn.txt.

We'll need the User ARN to grant access to an S3 bucket we'll use for uploads. We'll also need an Access Key (Access Key Id and Secret Access Key) for this IAM User to upload files via the S3 API. The Access Key is contained in credentials.csv.

Note well: credentials.csv contains secrets! Do not share them or store them in git. The .gitignore in this repository explicitly ignores this file. Altering the .gitignore file in this repository could result in your AWS credentials (credentials linked to your credit card information) being visible on Github. NEVER COMMIT SECRETS TO GIT

S3 stores files you upload in buckets. A bucket is a top-level namespace for your files.

In the S3 tab:

1. Click Create Bucket. This opens the Create a Bucket - Select a Bucket Name and Region modal.

2. Enter a name in the Bucket Name box. It must be unique among all S3 buckets and in all lowercase characters.

3. Select US Standard for the Region.

4. Click Create.

5. Highlight your bucket and select the Properties tab on the right side.

6. Open the Permissions dropdown in the right sidebar.

7. Click Add bucket policy near the bottom of the Permissions dropdown.

8. At the bottom of the Bucket Policy Editor modal, click AWS Policy Generator. This opens the AWS Policy Generator page.

9. On the AWS Policy Generator page

   1. Step 1: Select Policy Type

      1. For Select Type of Policy use S3 Bucket Policy.

   2. Step 2: Add Statement(s)

      1. Select Allow for Effect.
      2. Paste the User ARN into the Principal box.
      3. Select PutObject and PutObjectAcl for Actions.
      4. Enter arn:aws:s3:::<bucket_name>/* into the Amazon Resource Name (ARN) box.
      5. Click the Add Statement.

   3. Step 3: Generate Policy

      1. Click Generate Policy
      2. Copy the JSON from the Policy JSON Document modal.

10. Return to the S3 tab.

11. Paste the bucket policy into the Bucket Policy Editor modal.

12. Click Save.

13. Click Save in the Permissions dropdown.

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

These steps limit upload access to one bucket for the identity wdi-upload.

This is one specific and restrictive way of implementing access control. AWS provides many different mechanisms to grant and restrict access.

{
  "Version": "2012-10-17",
  "Id": "Policy1439826519004",
  "Statement": [
    {
      "Sid": "Stmt1439826516658",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::<AWS Account Id>:user/<IAM User Name>"
      },
      "Action": [
        "s3:PutObjectAcl",
        "s3:PutObject"
      ],
      "Resource": "arn:aws:s3:::<bucket_name>/*"
    }
  ]
}

• Create (or select) an AWS Identity.
• Set AWS Region to US Standard
• Create and download an access key for this identity.
• Save said access key csv inside this repo.
• Save your ARN to arn.txt in this repo.
• Create an S3 bucket.
• Create a bucket policy.
• DO NOT ALTER THE .gitignore FILE

1. All content is licensed under a CC­BY­NC­SA 4.0 license.
2. All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact [email protected].