Skip to main content

Ripple - When an AWS Payer Account Migration Takes Place

How Ripple handles billing data when migrating your AWS Payer Account.

Written by Yo Fukuda
Updated today

Overview

This guide walks you through how Ripple handles billing data when an AWS Payer Account migration takes place. Ripple will automatically detect the new Payer Account once the migration is completed.


How Ripple Handles the Migration

For Linked Accounts that have changed Payer Accounts, the total cost — before and after the transfer — will be recorded under the new Payer Account, regardless of the timing of the transfer.

Example: If the Payer Account is migrated from Account A to Account B on October 15:

  • AWS: Costs from October 1–15 are recorded under Payer Account A, and costs from October 15 onwards are recorded under Payer Account B

  • Ripple: The total usage cost for October is recorded under the new Payer Account B


Need a Different Cost Allocation Method?

If you require a different cost allocation method — for example, separate cost breakdowns for before and after the migration rather than a combined total — please contact us and we will be happy to discuss how we can accommodate your needs.


Need More Help?

If any errors occur during the process or if you have any questions, please reach out to us:

Did this answer your question?