hosted public VIF data transfer egress billing scenario clarification

Question

Hello Networking TFC
 
I noticed this in the FAQ  for Public VIFs
For publicly addressable AWS resources (for example, Amazon S3 buckets, Classic EC2 instances, or EC2 traffic that goes through an internet gateway), if the outbound traffic is destined for public prefixes owned by the same AWS payer account and actively advertised to AWS through an AWS Direct Connect public virtual Interface, the Data Transfer Out (DTO) usage is metered toward the resource owner at AWS Direct Connect data transfer rate.

However it leaves the customer wanting to understand some scenarios, is this the same for hosted public VIF, and what if accounts are not in the same AWS organizations (different payer )
 
Example Scenario

- Account A has the DX connection, and its own public VIF
 - Account B (not in AWS organizations with account A)  was given a hosted public VIF from account A
 - Account C unrelated to Account A or B
 
Scenario billing questions – please just respond with yes or no on the billing items so we can help the customer predict billings.
 
 - Scenario 1
   - Account B S3 bucket, data transfer out to account B DX on premises. 
    - Account A S3 egress yes/no
    - Account A DX egress yes/no
    - Account B S3 egress yes/no
    - Account B DX egress yes/no

- Scenario 2
  - Account B S3 bucket, data transfer out to account A DX on premises. 
   - Account A S3 egress yes/no
   - Account A DX egress yes/no
   - Account B S3 egress yes/no
   - Account B DX egress yes/no

- Scenario 3
  - Account A S3 bucket, data transfer out to account B DX on premises. 
   - Account A S3 egress yes/no
   - Account A DX egress yes/no
   - Account B S3 egress yes/no
   - Account B DX egress yes/no

- Scenario 4
  - Account C S3 bucket, data transfer out to account B DX on premises. 
   - Account A S3 egress yes/no
   - Account A DX egress yes/no
   - Account B S3 egress yes/no
   - Account B DX egress yes/no

Thanks in advance

Accepted Answer

Short answer here is Owner of S3 bucket pays the egress charges. Now if the S3 owner is in same account family (means same payer account for both) as the DX VIF owner then the charges are reduced, it appears to be not the case in your scenario. Account A has its own public VIF and Account B has it own public VIF although Account A provided the public VIF to account B. Account C is anyone else.
 
•	Scenario 1 (S3 Owner and Public VIF owner are same account)

◦	Account B S3 bucket, data transfer out to account B DX on premises.
	◦	Account A S3 egress yes/no — NO
	◦	Account A DX egress yes/no — NO
	◦	Account B S3 egress yes/no — NO  
	◦	Account B DX egress yes/no — YES (reduced rate)

•	Scenario 2 (S3 Owner and Public VIF owner are in different accounts not in same org as well)

◦	Account B S3 bucket, data transfer out to account A DX on premises.
	◦	Account A S3 egress yes/no — NO
	◦	Account A DX egress yes/no — NO  ($0 charge)
	◦	Account B S3 egress yes/no — YES (standard internet egress charge)
	◦	Account B DX egress yes/no — NO

•	Scenario 3 (S3 Owner and Public VIF owner are in different accounts not in same org as well)

◦	Account A S3 bucket, data transfer out to account B DX on premises.
	◦	Account A S3 egress yes/no — YES (standard internet egress charge)
	◦	Account A DX egress yes/no — NO
	◦	Account B S3 egress yes/no — NO 
	◦	Account B DX egress yes/no — NO ($0 charge)

•	Scenario 4 (S3 Owner and Public VIF owner are in different accounts)

◦	Account C S3 bucket, data transfer out to account B DX on premises.
	◦	Account A S3 egress yes/no — NO 
	◦	Account A DX egress yes/no — NO
	◦	Account B S3 egress yes/no — NO
	◦	Account B DX egress yes/no — NO
	◦	Who payers here - it is the Account C! and that too at standard internet egress rate

hosted public VIF data transfer egress billing scenario clarification

Contenido relevante