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

By default, this storage is provisioned automatically and managed by Amperity.

Bring Your Own Storage (BYOS) allows your brand to store this data in an Amazon S3 bucket or Azure Blob Storage location that is owned and managed by your brand. Your data stays within your brand’s storage location, while Amperity continues to manage the control plane: the user interface, workflow orchestration, and managed connectors.

Note

BYOS and Bring Your Own Compute (BYOC) are independent – you can enable either one on its own. Brands that use both keep the storage and the processing of their data within infrastructure that they own and manage.

Warning

Configured storage applies only to new Amperity tenants that are provisioned for Amazon S3 or Microsoft Azure.

Amperity Learning Lab

Amperity stores outputs in Amazon S3 or Azure Blob Storage, depending on your cloud platform.

Open Learning Lab to learn more about configuring Amazon S3 storage and configuring Azure storage for Amperity. Registration is required.

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:

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

    or

    A Microsoft Azure Blob Storage location that is owned and managed by your brand.

  2. An Amazon S3 storage location that is only used by your tenant that is provisioned automatically by default and managed by Amperity.

    or

    A Microsoft Azure Blob Storage location that is only used by your tenant that is provisioned automatically by default and managed by Amperity.

Provision storage on Amazon AWS

Configure a new tenant to use an Amazon S3 storage location that is owned and managed by your brand.

To provision storage on Amazon AWS

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 is inherited from the IAM role that is assigned to the logged-in user.

  2. Log in to your Amperity 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 step 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.

The region for primary storage should be the same region in which Amperity is hosted.

Note

Amperity is hosted in one of the following Amazon AWS regions:

Australia, primary (Sydney)

ap-southeast-2

Australia, backup (Melbourne)

ap-southeast-4

Canada (Central)

ca-central-1

US West (Oregon)

us-west-2

Cross-region transfer costs will apply when Amazon S3 storage is configured in different region than the one in which your Amperity tenant is hosted and will increase latency.
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 resources 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 5.

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.

Provision storage on Microsoft Azure

Configure a new tenant to use a Microsoft Azure Blob Storage location that is owned and managed by your brand.

To provision storage on Microsoft Azure

Step 1.

Choose a storage location

  1. Log in to the Microsoft Azure console as a user with credentials that allow provisioning storage, IAM and user roles, and the ability to deploy resources using Azure Resource Manager .

  2. Log in to your Amperity tenant.

    Note

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

  3. The Storage Setup page appears.

    Each step must be completed before you can start using Amperity.
Step 2.

Grant admin consent

Your brand must allow Amperity as an enterprise application within your Microsoft Azure account by granting Amperity admin consent .

Important

This step must be done by a Microsoft Azure user account with one of the following administrator roles: “Privileged Role”, “Cloud Application”, or “Application”.

  1. Click Grant admin consent. This will redirect you to the Microsoft Azure console.

    Grant admin consent to Amperity.

  2. Approve Amperity as an enterprise application.

    Grant admin consent to Amperity.

    Note

    You can grant admin consent from the Microsoft Entra admin center. Navigate to the Microsoft Entra admin center.

    Under Security select Permissions. On the Permissions page click the Grant admin consent for Amperity button.

    An Entra ID is created for Amperity in your Microsoft Azure account, along with an application object , after which you are redirected back to Amperity.
Step 3.

Provision storage resources

Amperity requires the Object ID for the Microsoft Azure application to generate a deployment template.

Note

The Name of the enterprise application is shown on the Provision storage resources page and is a string. For example: az-prod-socktown-storage.

  1. Navigate to the Microsoft Entra admin center and open the list of enterprise applications .

  2. Click the enterprise application with the matching Name, and then copy the Object ID.

  3. On the Provision storage resources page in Amperity paste the Object ID into the empty field, and then click the Generate deployment template button.

    Configure the Object ID.

  4. After the Azure Resource Manager (ARM) deployment template is generated click the Deploy to Azure button.

    This will open the ARM deployment template in the Microsoft Azure console.

    Tip

    In the Microsoft Azure console click the Edit button to review the ARM deployment template generated by Amperity, including the resources and access levels for objects in the template.

  5. In the Microsoft Azure console, select the regions in which to provision primary and backup storage.

    Note

    Amperity is hosted in one of the following Microsoft Azure regions:

    US East 2

    eastus2

    North Europe

    northeurope

    Cross-region transfer costs will apply when Azure Blob Storage is configured in different region than the one in which your Amperity tenant is hosted and will increase latency.

  6. When you are finished configuring the ARM deployment template click Revew + Create. Microsoft Azure will validate the ARM deployment template, and then create resources using the ARM deployment template.

  7. When Microsoft Azure is finished creating resources, return to Amperity and click Complete step.
Step 4.

Configure storage access

The last step is to configure permission for Amperity to access your brand’s Microsoft Azure storage resources. This requires a tenant ID and a subscription ID.

Configure the Object ID.

  1. Navigate to the Microsoft Entra admin center and copy the tenant ID .

    Paste the tenant ID into the box above the Test connection butto on the Configure storage access page.

  2. Click Add credentials to register Microsoft Azure storage to your Amperity account. After storage is registered Amperity tests and validates the connection.

  3. When Amperity is finished validating the connection copy the subscription ID .

    Paste the subscription ID into the box below the Test connection button on the Configure storage access page.

  4. Click Finish to bind Microsoft Azure storage to your Amperity account.