AWS S3 integration

Data forwarding

The AWS S3 integration lets you forward data to an S3 bucket further analysis. This lets you leverage HUMAN data alongside your existing logs and metrics within your AWS instance. You can use the AWS S3 integration to create a data export or trigger it with a data export action.

Prerequisites

• If you’re using the Access Key method, the S3 bucket access key ID and secret access key.
• Appropriate role permissions to create and manage integrations

Integrate with AWS S3

1. Navigate to Platform Settings > Integrations and click the AWS S3 integration.
2. Click Add Integration.
3. Provide an Integration name.
4. Select an Access method and complete the fields that appear. Click the appropriate option below for more information on their fields.

   Access Key

   With this method, you provide HUMAN your S3 bucket’s access key ID and secret access key.

   • Integration name: How the integration will appear in your HUMAN account.
   • Bucket: The name of the S3 bucket to send data to.
   • Region: The AWS region the bucket resides at.
   • SSE: Select a bucket encryption method.
   • Access Key ID: The S3 bucket access key ID.
   • Secret Access Key: The S3 bucket secret access key.
   • Path pattern: The file’s path. This does not affect the file name. See supported path patterns for details.

   ARN Role

   With this method, you update your bucket’s policy with HUMAN’s AWS IAM ARN information.

   • Bucket: The name of the S3 bucket to send data to.
   • Region: The AWS region the bucket resides at.
   • SSE: Select a bucket encryption method.
   • Path pattern: The file’s path. This does not affect the file name. See supported path patterns for details.
5. If you chose the ARN Role method, follow AWS’ instructions to edit your bucket’s policy with the following. Otherwise, skip to Step 6.
   • "Sid": "AllowHSDataExportRole"
   • "AWS": "arn:aws:iam::442426886265:role/HSDataExport"
   • Replace YOUR_BUCKET_NAME with the same bucket name you provided in Step 4.

   Full bucket policy example

   1
   {
   2
     "Version": "2012-10-17",
   3
     "Statement": [
   4
       {
   5
         "Sid": "AllowHSDataExportRole", // HUMAN value
   6
         "Effect": "Allow",
   7
         "Action": "s3:*",
   8
         "Principal": {
   9
           "AWS": "arn:aws:iam::442426886265:role/HSDataExport" // HUMAN ID and role
   10
         },
   11
         "Action": [
   12
           "s3:GetObject",
   13
           "s3:PutObject",
   14
           "s3:ListBucket",
   15
         ],
   16
         "Resource": [
   17
           "arn:aws:s3:::YOUR_BUCKET_NAME", // Same bucket name as you provided in the HUMAN console
   18
           "arn:aws:s3:::YOUR_BUCKET_NAME/*" // Same bucket name as you provided in the HUMAN console
   19
         ]
   20
       }
   21
     ]
   22
   }
6. Click Test Connection.
7. Once the test succeeds, click Save changes.

You have successfully configured an AWS S3 integration. Make sure to use the integration to create a data export or trigger it with a data export action.

Supported path patterns

Path patterns allow the following characters:

• a-z
• A-Z
• 0-9
• -, /, !, \, _, ., \, *, ', ()

For example, for the date February 2, 2022, the path pattern would resolve to: 2022/02/16/production/PX12AB34CD.

File name patterns

File names generated by HUMAN follow the following pattern: {guid}_{appId}_{startTimestamp}_{endTimestamp}.

For example, for a file name of 7bd6079a-b5e4-4788-93c5-b939549ce5be_PX3tHq532g_1645014120000000000_1645014180000000000**, the values would be:

• GUID: 7bd6079a-b5e4-4788-93c5-b939549ce5be
• App ID: PX3tHq532g
• Start timestamp (UNIX epoch): 1645014120000000000
• End timestamp (UNIX epoch): 1645014180000000000