Introduction

HNR to ZERO platform can support ingress of data from either a managed or unmanaged S3 location.

Managed locations are S3 buckets hosted and controlled by HNR, therefore the data lifecycle is managed by HNR and the customer is responsible for delivering the data file to the provided location securely.

Unmanaged locations are S3 buckets hosted and controlled by the customer, therefore the data lifecycle is managed by the customer who is responsible for ensuring that HNR can access the files securely.

Both managed and unmanaged ingress are file based. We support CSV format (uncompressed or gzipped), and it is possible to either use a predefined mapping configuration or to customise the mapping of fields through Receivers and Canonicalisers.

This guide specifically covers unmanaged locations, i.e. those under a customer’s control.

Steps

The customer registers an S3 location which is then periodically scanned and any new files will then be ingested in to the HNR to ZERO platform. The following steps outline the process to achieve this:

  1. Grant HNR access to customer AWS S3 Bucket
  2. Configure Basic Collector Details
  3. Configure Bucket Collection Details

Step 1: Grant HNR access to AWS S3 Bucket

In order to read objects from an AWS S3 Bucket, a policy needs to be created in your AWS Account to allow cross-account access so that HNR to ZERO can assume a role with the following permissions:

"Action": [
  "s3:GetObject",
  "s3:GetBucket",
  "s3:List"
]

As this is within the customer’s infrastructure, HNR cannot make these changes. Please discuss with your technical team accordingly.

Step 2 of [x]: Configure Basic Collector Details

  1. Title [ ]
  2. Description [ ]

Step 3 of [x]: Configure Additional Bucket Details