AWS cur documentation change
Summary
Removed 'AWS' prefix from 'Direct Connect' references throughout the document
Security assessment
This is a branding/nomenclature change only. No security implications as it doesn't modify any security controls or data handling instructions.
Diff
diff --git a/cur/latest/userguide/cur-data-transfers-charges.md b/cur/latest/userguide/cur-data-transfers-charges.md index 8752134e6..64684ce8a 100644 --- a//cur/latest/userguide/cur-data-transfers-charges.md +++ b//cur/latest/userguide/cur-data-transfers-charges.md @@ -5 +5 @@ -Data transfer within an AWS RegionData transfer between AWS RegionsData transfer out to the internetAWS Direct Connect trafficS3 Transfer Acceleration trafficCloudFront traffic +Data transfer within an AWS RegionData transfer between AWS RegionsData transfer out to the internetDirect Connect trafficS3 Transfer Acceleration trafficCloudFront traffic @@ -59 +59 @@ Data transfer usage types that don’t have the Region prefix, such as `DataTran -## AWS Direct Connect traffic +## Direct Connect traffic @@ -61 +61 @@ Data transfer usage types that don’t have the Region prefix, such as `DataTran -AWS Direct Connect data transfer over a public virtual interface have usage types that end with `DataXfer-In` or `DataXfer-Out`. +Direct Connect data transfer over a public virtual interface have usage types that end with `DataXfer-In` or `DataXfer-Out`. @@ -63 +63 @@ AWS Direct Connect data transfer over a public virtual interface have usage type -AWS Direct Connect data transfer over a private or transit virtual interface have usage types that end with `DataXfer-In:dc.3` or `DataXfer-Out:dc.3`. +Direct Connect data transfer over a private or transit virtual interface have usage types that end with `DataXfer-In:dc.3` or `DataXfer-Out:dc.3`.