Ingesting Entities from an AWS S3 Bucket

1. Sign into the Amazon AWS S3 Management Console.
2. Click the Create Bucket button
3. Enter a bucket name, like sgnl-aws-s3-ingest.
4. Select the US East (Ohio) us-east-2 region.
5. Set Object Ownership to ACLs disabled (recommended).
6. Leave checkboxes for Block public access checked.
7. Set Bucket Versioning to Disable.
8. Tags are not required.
9. Leave Default encryption at defaults: Encryption key type = Amazon S3 managed keys (SSE-S3) and Bucket Key = Enable.
10. Do not change any Advanced settings.
11. Click the Create bucket button.

Complete this section to enable public web access to files in the bucket. Otherwise, skip to the next section if access must be restricted to a specific user.

1. From S3 Console, click the Buckets tab in side-bar.
2. Click on the bucket that you created, e.g. sgnl-aws-s3-ingest.
3. Click the Permissions tab.
4. Click the Edit button in the Block public access (bucket settings) section.
5. Uncheck the Block all public access checkbox and all four checkboxes underneath it.
6. Click the Save changes button.
7. Type confirm in the box that pops up, and click the Confirm button.
8. Scroll down to the Bucket policy section and click the Edit button.
9. Copy and paste the text below, replacing the bucket name if needed:
   

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "PublicReadGetObject",
               "Effect": "Allow",
               "Principal": "*",
               "Action": [
                   "s3:GetObject"
               ],
               "Resource": [
                   "arn:aws:s3:::sgnl-aws-s3-ingest/*"
               ]
           }
       ]
   }
   

10. Click the Save changes button.

Note: If you upload a file named user.csv to the bucket, then the publicly-accessible URL to an object in the bucket will look like this: https://s3.us-east-2.amazonaws.com/sgnl-aws-s3-ingest/user.csv

This permission policy will be assigned to the user created in a later step.

1. Go to the Amazon AWS IAM Management Console
2. Click Policies on the side-bar.
3. Click the Create Policy button
4. Click the JSON tab
5. Copy and paste the following into the text box, replacing the bucket name if needed:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:ListBucket"
            ],
            "Resource": [
                "arn:aws:s3:::sgnl-aws-s3-ingest"
            ]
        },
        {
            "Effect": "Allow",
            "Action": ["s3:*"],
            "Resource": "arn:aws:s3:::sgnl-aws-s3-ingest/*"
        }
    ]
}

6. Click the Next: Tags button.
7. Click the Next: Review button.
8. Enter S3SingleBucketFullAccess as the Name, or another name of your choosing.
9. Click the Create policy button.

1. Go to the Amazon AWS IAM Management Console
2. Click Users on the side-bar.
3. Click the "Create user" button.
4. Enter "sgnl-ingest" or equivalent as the Username. Click Next.
5. Under Permission options click the "Attach policies directly"
6. In the Permission polices section search for "S3SingleBucketFullAccess" and check the box to the left of it.
7. Click the "Next" button.
8. Click the "Create user" button.

1. Ensure you're in the Amazon AWS IAM Management Console and click "Users" in the left handrail under "Access management"
2. Click on the user's Username you just created. e.g. sgnl-ingest
3. Click on the "Security credentials" tab.
4. Scroll down to the "Access keys" section. Click "Create access key"
5. Under "Use case" select "Third-party service"
6. At the bottom of the page, under Confirmation click the check box next to: "I understand the above recommendation and want to proceed to create an access key."
7. Click the "Next" button.
8. Optional - add a tag with the description of the key.
9. Click the "Create access key" button
10. Copy and secure both the "Access Key" and "Secret access key". You'll use these to configure the ingest adapter inside SGNL.
11. Click the "Done" button