AWS Direct Connect Announces the Support for Granular Cost Allocation and Removal of Payer ID Restriction for Direct Connect Gateway Association.

AWS Direct Connect announces support for granular cost allocation and removal of payer ID restriction for Direct Connect gateway association.

Prior to the granular cost allocation support, Data Transfer Out charges for private and transit virtual interfaces were allocated to the AWS account that owns the private/transit virtual interface(s). The new granular cost allocation feature will allocate Data Transfer Out charges to the AWS account responsible for the Data Transfer. The introduction of granular cost allocation will not change the cost per gigabyte to use AWS Direct Connect. The granular cost allocation will be effective from October 1st, 2019.

Along with the introduction of the granular cost allocation, we have removed the payer ID restriction for Direct Connect gateway association. Until now, the AWS accounts owning the Direct Connect gateway and Virtual Private Cloud(s)/AWS Transit Gateway(s) had to be under the same payer ID. Effective today, the payer ID restriction for Direct Connect gateway association is removed, so you can now associate Virtual Private Cloud(s)/AWS Transit Gateway(s) from any AWS account to a Direct Connect gateway owned by any AWS account.

For more information, please read the user guide.