AWS eks documentation change
Summary
Fixed two markdown link syntax errors: corrected broken URL formatting for inter-AZ data transfer charges and Envoy upstream clusters documentation.
Security assessment
The changes only fix URL formatting and markdown syntax. No security vulnerabilities, configurations, or features are mentioned or modified. The content remains focused on networking cost optimization without security implications.
Diff
diff --git a/eks/latest/best-practices/cost-opt-networking.md b/eks/latest/best-practices/cost-opt-networking.md index cac6362d8..525795a19 100644 --- a//eks/latest/best-practices/cost-opt-networking.md +++ b//eks/latest/best-practices/cost-opt-networking.md @@ -344 +344 @@ _There are no hourly or data transfer costs associated with Gateway VPC Endpoint -VPC Endpoints have an [hourly charge](https://aws.amazon.com/privatelink/pricing/) and have an additional charge associated with data processing via the underlying ENI. Note that inter-AZ data transfer is [not charged]([https://aws.amazon.com/about-aws/whats-new/2022/04/aws-data-transfer-price-reduction-privatelink-transit-gateway-client-vpn-services/](https://aws.amazon.com/about-aws/whats-new/2022/04/aws-data-transfer-price-reduction-privatelink-transit-gateway-client-vpn-services/)). +VPC Endpoints have an [hourly charge](https://aws.amazon.com/privatelink/pricing/) and have an additional charge associated with data processing via the underlying ENI. Note that inter-AZ data transfer is [not charged](https://aws.amazon.com/about-aws/whats-new/2022/04/aws-data-transfer-price-reduction-privatelink-transit-gateway-client-vpn-services/). @@ -475 +475 @@ The screenshots below are captured from a live example of this approach. The fir -With Istio, you can verify and export the statistics of any [upstream clusters]([https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology)) and endpoints that your proxies are aware of. This can help provide a picture of the network flow as well as the share of distribution among the services of a workload. Continuing with the same example, the `orders` endpoints that the `graphql` proxy is aware of can be obtained using the following command: +With Istio, you can verify and export the statistics of any [upstream clusters](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology) and endpoints that your proxies are aware of. This can help provide a picture of the network flow as well as the share of distribution among the services of a workload. Continuing with the same example, the `orders` endpoints that the `graphql` proxy is aware of can be obtained using the following command: