Skip to main content

Welcome, what can we help you with?

Search

Crunchtime Ops Execution Data Streaming: Setup Guide

Updated: Illia Khomenko Edited:
Note: This setup requires access to your organization's AWS environment with permissions to create S3 buckets and manage bucket policies. Please coordinate with your IT/DevOps team if needed.
To receive your Crunchtime Ops Execution data files, you must configure a destination Amazon S3 bucket within your AWS environment. Crunchtime utilizes S3 Cross-Account Bucket Replication to automatically push data files to your bucket the moment they are uploaded into our production environment.

🔍 Navigate this article: 

  1. Create Your Destination Bucket
  2. Apply the Destination Bucket Policy
  3. What to Send to Crunchtime
  4. What Happens Next?

1. Create Your Destination Bucket

Please create a new AWS S3 bucket with the following specifications:

  1. Region: The bucket must be located in us-east-1 (N. Virginia).
  2. Naming Convention: To streamline internal operations, please use the following prefix:
    crunchtime-ops-execution-data-streaming-[YOUR-COMPANY]
    Example: crunchtime-ops-execution-data-streaming-rbi
  3. Bucket Versioning: You must Enable Bucket Versioning. AWS requires versioning on both the source and destination for replication to work.

2. Apply the Destination Bucket Policy

To allow the Crunchtime data replication service to write files into your bucket, you must apply the following Bucket Policy.

  1. Navigate to your bucket in the S3 Console.
  2. Select the Permissions tab and click Edit under Bucket policy.
  3. Paste the JSON below, replacing YOUR-BUCKET-NAME with the name of the bucket you created in Step 1.
 
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::309517936062:role/S3-Replication-AllCompanies-Role"
            },
            "Action": [
                "s3:ReplicateObject",
                "s3:ReplicateDelete",
                "s3:ReplicateTags",
                "s3:ObjectOwnerOverrideToBucketOwner"
            ],
            "Resource": "arn:aws:s3:::YOUR-BUCKET-NAME/*"
        }
    ]
}
Good to know: The ObjectOwnerOverrideToBucketOwner action ensures that any files Crunchtime sends to you will be owned by your AWS account, giving you full control over the data.

3. What to Send to Crunchtime

Once your bucket is ready and the policy is applied, please send the following details to your Crunchtime Representative:

  1. Your Destination Bucket Name (e.g., crunchtime-ops-execution-data-streaming-rbi)
  2. Confirmation that Versioning is enabled.
  3. Your AWS Account ID (Optional, but helpful for verification)

4. What Happens Next?

Once you provide your bucket details and confirm the policy is in place:

  1. Crunchtime will configure the replication rule on our side.
  2. You will immediately start seeing files arriving in your bucket — these are files for new submissions created after the rule is active.
  3. We will then initiate a backfill job to replicate historical files from the past into your bucket.
  4. We will notify you once the backfill replication job is complete and the entire replication process has been successfully configured.
  5. You should verify that files appear in your bucket and that your downstream systems can access them.
  6. Our team may reach out to you proactively to verify that file delivery is working as expected.

Image File Paths: Image paths in your submission data will match the following format:

company/{company_id}/forms/submissions/id/{123456}/{year}/{month}/{day}/{image_name}.png

The path will be the same in your S3 bucket after replication, with additional folders prepended to help differentiate in brand-wide implementations:

company_id/{company_id}/company/{company_id}/forms/submissions/id/{123456}/{year}/{month}/{day}/{image_name}.png

 

Was this article helpful?
0 out of 0 found this helpful
Return to top

Related articles

Comments

0 comments

Please sign in to leave a comment.