Overview
This article summarises the necessary steps and important notes for managing Ripple's CUR integration when using AWS Billing Transfer to migrate billing from one Payer Account to another.
Since Billing Transfer switches on a monthly basis, confirming the migration timing and CUR update status is especially important.
Terminology
Term | Description |
Payer Account | The AWS management account responsible for billing |
Transfer Source / Transfer Destination | The account billing is transferred from / to |
CUR | AWS Cost and Usage Report — detailed billing data output to S3 periodically |
S3 Bucket Path | The S3 output destination for CUR (e.g. |
Backfill | Regenerating or supplementing CUR data for a past period (may require an AWS Support request) |
How AWS Billing Transfer Works
Important Notes
Migration occurs on a monthly basis — mid-month switching is not possible.
After Transfer is activated, billing data will be retrieved from the Transfer destination Payer Account.
After migration, the previous CUR may stop updating or return errors — confirming the CUR status post-migration is mandatory.
Note: Only usage fees after the migration date will be reflected in the CUR. Usage fees from before the migration period will not be updated. If historical data is required, refer to the Historical Data section below.
CUR Configuration During Billing Transfer
Billing Transfer does not automatically consolidate all Payer Account data into a single CUR. A separate CUR must be created for each Payer Account.
For example, if Payer B and Payer C are transferred to Payer A, the following CURs are required:
Payer A's CUR (created within Payer A)
Payer B's CUR (created within Payer A)
Payer C's CUR (created within Payer A)
Recommended CUR Integration Pattern After Transfer
Recommended setup (example: Payer B transferred to Payer A)
Create a new CUR for Payer B within Payer A.
Update Ripple's integration settings to point to the new S3 output path (Payer B's CUR within Payer A).
Ripple will retrieve Payer B's CUR from the Transfer destination (Payer A) S3 bucket.
Why this is recommended: After Transfer, the Transfer source (Payer B)'s CUR may stop updating or return errors. It is safer to recreate the CUR on the Transfer destination side and update the integration accordingly.
Migration Steps
Before Migration (Required)
Record the Payer Account and S3 bucket path of the CUR currently integrated with Ripple.
Confirm the Transfer destination Payer Account ID (e.g. Payer A).
Since migration takes effect from the start of the month, complete all AWS-side configurations before the end of the month prior to the planned migration month.
At the Start of the Migration Month (Confirm)
Confirm that Billing Transfer has been activated as expected from the start of the month.
Confirm that the CUR is being updated (and that the previous CUR has not stopped).
After Migration (Ripple)
After Transfer is complete, update the CUR reference information (S3 bucket path, etc.) in Ripple to point to the new CUR.
Confirm that data is being ingested correctly and that updates are continuing.
Example: Confirm the S3 path of Payer B's CUR created within Payer A → update Ripple's integration settings accordingly.
Historical Data (Including the Migration Month)
Billing Transfer typically only reflects usage fees after the migration date in the CUR — usage fees from before the migration period cannot be retrieved automatically.
However, if the data has already been integrated with Ripple and historical data is required, it may be possible to reflect past data in Ripple. If this is needed, please contact Alphaus with the following information:
Field | Details |
Previous Payer Account ID | The Payer Account ID before migration |
Migrating Payer Account ID | The Payer Account ID being migrated |
Transfer Destination Payer Account ID | The Payer Account ID receiving the transfer |
Migration Timing | From which month's usage the migration applies |
Email template (ready to use):
Subject: Request to Reflect Past Month CUR Data Due to Billing Transfer
Previous Payer Account ID: xxxxxxxxxxxx
Migrating Payer Account ID: xxxxxxxxxxxx
Transfer Destination Payer Account ID: xxxxxxxxxxxx
Migration Timing: From YYYY/MM usage onwards
Note: Already integrated with Ripple / Requesting reflection of past months (including migration month)
Migration Checklist
Item | Timing |
Record the current CUR's Payer Account and S3 bucket path | Before migration |
Confirm the Transfer destination Payer Account ID | Before migration |
Confirm that Billing Transfer has been activated from the start of the month | Start of migration month |
Confirm the S3 bucket path within the Transfer destination (e.g. Payer A) and update Ripple's integration settings | After migration |
Confirm that the CUR is updating correctly (no update stops or errors) | After migration |
If CUR data for past months (including migration month) is missing, request a Backfill from AWS Support or contact Alphaus | As needed |
FAQ
Q1. Will Billing Transfer consolidate all Payer Account data into a single CUR?
No. A separate CUR must be created for each Payer Account. Each Payer's CUR must be created and managed within the Transfer destination Payer Account.
Q2. Are any special settings required in Ripple for Billing Transfer?
No special settings are required — the process is the same as a standard CUR integration. However, if the CUR reference path (S3 bucket path) changes, you will need to update Ripple's integration settings accordingly.
Q3. Can I continue using the CUR from before the migration?
After Transfer, the original CUR may return errors or stop updating. Confirming the CUR status after migration is mandatory. If errors occur, create a new CUR on the Transfer destination side.
Q4. Is mid-month Billing Transfer possible?
No. Billing Transfer operates on a monthly basis and mid-month switching is not possible.
Q5. What should I do if CUR data for past months is missing?
You will need to request a Backfill (regeneration/supplementation of past period data) from AWS Support. If you contact Alphaus, we can assist with raising the support case.
Reference Links
Need More Help?
If any errors occur during the process or if you have any questions, please reach out to us:
📧 Email: ripple_cs@alphaus.cloud
💬 Live Chat: Available in the bottom-right corner of your dashboard
📖 Help Center: https://help.alphaus.cloud/