Log ownership relationships of traffic analysis modules
Global traffic analysis logs
Ownership relationship: Global traffic analysis logs belong to the account that enables traffic analysis for the VPC.
Built-in authoritative (regular zone & acceleration zone) traffic analysis logs
Ownership relationship: Built-in authoritative traffic analysis logs belong to the account where the user domain (Zone) is created.
Cache traffic analysis logs
Ownership relationship: Cache traffic analysis logs belong to the account that enables traffic analysis for the VPC.
Forward traffic analysis logs
Ownership relationship: Forward traffic analysis logs belong to the account where the forwarding domain (Zone) is created.
Recursion traffic analysis logs
Ownership relationship: Recursion traffic analysis logs belong to the account that enables traffic analysis for the VPC.
Billing logic
The system traverses user accounts (UIDs) that have enabled traffic analysis and calculates the total traffic analysis logs for each module under these accounts.
Cross-account VPC association scenarios for built-in authoritative and forward modules
For example:
User A's domain (Zone1) is associated with User B's VPC1 across accounts.
User C's domain (Zone2) is associated with User B's VPC1 across accounts.
User A has enabled the traffic analysis feature, User B has enabled the traffic analysis feature, and User C has not enabled the traffic analysis feature.
Traffic analysis data situation
User A can view the built-in authoritative traffic analysis data for domain (Zone1) in User B's VPC1.
User B cannot view the built-in authoritative traffic analysis data for domain (Zone1) in VPC1 (built-in authoritative traffic analysis logs belong to User A).
User C cannot view the built-in authoritative traffic analysis data for domain (Zone2) in User B's VPC1 (User C has not enabled the traffic analysis feature).
Traffic analysis billing situation
User A's domain (Zone1) is associated with User B's VPC1 across accounts, and User A is billed.
User C's domain (Zone2) is associated with User B's VPC1 across accounts, and no billing occurs (User C has not enabled the traffic analysis feature).
Global, cache, and recursion traffic analysis cross-account VPC association scenarios
For example:
User A has added cross-account associations with User B's VPC1 and User C's VPC2.
User A has enabled the traffic analysis feature, User B has enabled the traffic analysis feature, and User C has not enabled the traffic analysis feature.
Traffic analysis data situation
User A can view User B's global, cache, and recursion traffic analysis data.
User A cannot view User C's traffic analysis data (User C has not enabled the traffic analysis feature).
User B can view User B's global, cache, and recursion traffic analysis data.
Traffic analysis billing situation
Traffic analysis enabled for User A's VPC is billed to User A.
Traffic analysis enabled for User B's VPC is billed to User B.