About storage

Amperity stores the following outputs in Amazon S3 storage or Azure Blob Storage, depending on the cloud platform in which your Amperity tenant is provisioned. These outputs include:

  • Data that was ingested to Amperity, and then loaded to domain tables

  • Tables that are maintained by Stitch

  • Stitch reports

  • Validation reports

  • Database tables

  • File uploads

  • SQL results, including Spark SQL checkpoints

  • Orchestration and campaign results

  • User audit logs

  • Conversations with Amp AI

Warning

This topic applies only to new Amperity tenants that are provisioned for Amazon S3.

Choose storage location

The location in which Amperity stores outputs is configurable. The first step for a new tenant allows your brand to choose one of the following storage locations:

  • An Amazon S3 storage location that is owned and managed by your brand

  • An Amazon S3 storage location that is only used by your tenant that is provisioned automatically by Amperity (default)

Configure storage location

To configure Amperity to use an Amazon S3 storage location that is owned and managed by your brand do the following:

Step 1.

Choose a storage location

  1. Log in to the Amazon AWS console as a user with credentials that allow storage to be configured for your brand from within AWS CloudFormation , such as an administrator.

    Important

    When Amperity opens AWS CloudFormation during the storage setup process the IAM roles that are used for operations and role assumption within AWS CloudFormation will be inherited from the IAM role that is assigned to the logged-in user.

  2. Log in to your tenant.

    Note

    If your brand has chosen Amperity-managed storage the following setup workflow steps are skipped.

  3. The Storage Setup page appears.

    The Storage Setup page.

    Each of the four steps must be completed before you can start using Amperity.
Step 2.

Specify regions

Specify the regions in which your brand wants to configure primary and backup storage, and then click Continue.

Regions for configured storage should be the same regions in which Amperity is located.
Step 3.

Create backup storage

Backup storage is provisioned using AWS CloudFormation.

  1. Click Provision CloudFormation stack. This opens the Quick create stack page in AWS CloudFormation.

  2. Provide the stack name.

    Note

    The value for stack name is pre-populated by Amperity in the form of

    amperity-<tenant>-<infracode>-backup

    It is recommended to keep the pre-populated stack name.

  3. Optional. Configure the IAM role for AWS CloudFormation to use for all operations performed on this stack.

    Note

    AWS CloudFormation will automatically use the credentials assigned to the user who is configuring the storage location.

  4. Review the parameters and configure the number of days for backups to be locked and retained.

    Important

    The values for InfraCode and Tenant should not be changed.

  5. Optional. Configure the IAM role for AWS CloudFormation to assume when performing operations on this stack.

    Note

    AWS CloudFormation will automatically use the credentials assigned to the user who is configuring the storage location.

  6. When finished, click Create stack.

    AWS CloudFormation will begin provisioning backup storage. This may take a few minutes.

    After provisioning for backup storage is complete return to the Create backup storage page in the storage setup workflow.

  7. On the Create backup storage page click Continue.
Step 4.

Create primary storage

Primary storage is provisioned using AWS CloudFormation.

Important

The values for primary storage are prepopulated using the information that was provided for backup storage. You may change these values in AWS CloudFormation, if necessary.

  1. The steps for configuring primary storage are nearly identical to backup storage. Click Provision CloudFormation stack, which opens the Quick create stack page in AWS CloudFormation. Provide a stack name, review IAM credentials and parameters, and then provision primary storage.

    Note

    The value for stack name is pre-populated by Amperity in the form of

    amperity-<tenant>-<infracode>-storage

    It is recommended to keep the pre-populated stack name.

    Important

    You must allow AWS CloudFormation to create IAM resources. Select the checkbox under “The following resource(s) require capabilities [AWS::IAM::Role]”.

  2. When finished, click Create stack.

    AWS CloudFormation will begin provisioning primary storage. This may take a few minutes.

    After provisioning for primary storage is complete return to the Create primary storage page in the storage setup workflow.

  3. On the Create primary storage page click Continue.
Step 4.

Bind storage

After backup storage and primary storage are provisioned test the connection between Amperity and provisioned storage.

  1. Copy the value for the AccessRole for primary storage. Add the value to the Access Role ARN field in the Bind storage page. Click Test connection.

    Tip

    The value for the access role ARN is found on the Outputs tab for the configured primary storage.

    Copy the access role ARN for primary storage and provide it to Amperity.

  2. If the connection is successful click Finish to bind your Amperity tenant to the configured backup and primary storage.

After the storage setup workflow is finished you are redirected to your tenant and can configure identity resolution.