# Networking & Content Delivery

Published articles for Networking & Content Delivery.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Introducing mTLS for Network Load Balancer

DevFeed: [Introducing mTLS for Network Load Balancer](<https://devfeed.tech/articles/introducing-mtls-for-network-load-balancer-144602.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-mtls-for-network-load-balancer/>)

Author: Rizwan Mushtaq

Published: 2026-11-19T22:45:08Z

Content type: release

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [elastic-load-balancing](<https://devfeed.tech/tags/elastic-load-balancing.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [mtls](<https://devfeed.tech/tags/mtls.md>), [mutual-tls](<https://devfeed.tech/tags/mutual-tls.md>), [network](<https://devfeed.tech/tags/network.md>), [spiffe](<https://devfeed.tech/tags/spiffe.md>), [store](<https://devfeed.tech/tags/store.md>), [tls](<https://devfeed.tech/tags/tls.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

Network Load Balancer (NLB) can verify client certificates at a TLS listener, so only clients that pass trust, optional identity filters, and revocation checks reach backend targets; targets receive no client certificate data. Configure verify mode with a trust store built from a CA bundle in Amazon S3, optionally add a CRL, and optionally filter on certificate CN, OU, DNS SAN, or URI SAN (including SPIFFE IDs). Filters use exact or prefix matching, are OR-combined, and apply per listener. NLB checks trust chains, certificate expiry and purpose, then filters and revocation; expired certificates can be allowed through an advanced setting. CRLs are imported when added and must be added again when updated. Access logs record authentication failures, while CloudWatch metrics cover handshakes, errors, latency, and certificate expiration. The article also describes setup prerequisites, testing, trust store sharing, limits, and configuration through console, CLI, SDKs, or CloudFormation.

### Source excerpt

Network Load Balancer now offloads mutual TLS for you. Learn how to attach a trust store, validate client certificates against your revocation lists, restrict access by CN, OU, or SPIFFE ID with client certificate filtering, and monitor connections with access logs and Amazon CloudWatch metrics.

## Introducing policy-based routing for AWS Transit Gateway

DevFeed: [Introducing policy-based routing for AWS Transit Gateway](<https://devfeed.tech/articles/introducing-policy-based-routing-for-aws-transit-gateway-144603.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-policy-based-routing-for-aws-transit-gateway/>)

Author: Arshdeep Grover

Published: 2026-11-19T21:06:11Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS Network Firewall](<https://devfeed.tech/topics/aws-network-firewall.md>), [Firewall](<https://devfeed.tech/topics/firewall.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-transit-gateway](<https://devfeed.tech/tags/aws-transit-gateway.md>), [based](<https://devfeed.tech/tags/based.md>), [cases](<https://devfeed.tech/tags/cases.md>), [class](<https://devfeed.tech/tags/class.md>), [console](<https://devfeed.tech/tags/console.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [ip](<https://devfeed.tech/tags/ip.md>), [policy](<https://devfeed.tech/tags/policy.md>), [port](<https://devfeed.tech/tags/port.md>), [post](<https://devfeed.tech/tags/post.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [reference](<https://devfeed.tech/tags/reference.md>), [reference-architecture](<https://devfeed.tech/tags/reference-architecture.md>), [route](<https://devfeed.tech/tags/route.md>), [routing](<https://devfeed.tech/tags/routing.md>), [setup](<https://devfeed.tech/tags/setup.md>), [source](<https://devfeed.tech/tags/source.md>), [transit](<https://devfeed.tech/tags/transit.md>)

### AI overview

AWS Transit Gateway policy-based routing (PBR) evaluates traffic against ordered rules matching any combination of source and destination CIDRs, protocol, and ports, then sends the first match to a target route table for normal destination-based forwarding. It supports path selection, segmentation, and selective inspection or bypass. Configure a policy table in the VPC console, add rules, and associate it with attachments; each attachment uses either a policy table or a route table. Unmatched traffic is dropped, and protocol- or port-based rules might not apply to fragmented packets. Plan matching return paths for stateful inspection. Associating a policy table with Site-to-Site VPN or Connect attachments stops BGP route advertisement; Direct Connect gateway attachments retain allowed-prefix advertisements. PBR is unavailable in AWS GovCloud (US) Regions and adds no charge beyond standard Transit Gateway pricing.

### Source excerpt

Policy-based routing (PBR) for AWS Transit Gateway matches traffic on its 5-tuple (source and destination IP, source and destination port, and protocol) and sends each class to a different route table. This post explains how PBR works and walks through a reference architecture, console setup, and three use cases.

## AWS Network Firewall proxy and native NAT Gateway integration

DevFeed: [AWS Network Firewall proxy and native NAT Gateway integration](<https://devfeed.tech/articles/aws-network-firewall-proxy-and-native-nat-gateway-integration-144599.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/aws-network-firewall-proxy-and-native-nat-gateway-integration/>)

Author: Tom Adamski

Published: 2026-11-19T20:49:47Z

Content type: release

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [AWS Network Firewall](<https://devfeed.tech/topics/aws-network-firewall.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [Firewall](<https://devfeed.tech/topics/firewall.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [secure web gateway](<https://devfeed.tech/topics/secure-web-gateway.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-network-firewall](<https://devfeed.tech/tags/aws-network-firewall.md>), [egress](<https://devfeed.tech/tags/egress.md>), [explicit-proxy](<https://devfeed.tech/tags/explicit-proxy.md>), [filter](<https://devfeed.tech/tags/filter.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [http](<https://devfeed.tech/tags/http.md>), [https](<https://devfeed.tech/tags/https.md>), [inspect](<https://devfeed.tech/tags/inspect.md>), [integration](<https://devfeed.tech/tags/integration.md>), [introduced](<https://devfeed.tech/tags/introduced.md>), [launch](<https://devfeed.tech/tags/launch.md>), [nat](<https://devfeed.tech/tags/nat.md>), [native](<https://devfeed.tech/tags/native.md>), [network](<https://devfeed.tech/tags/network.md>), [network-firewall](<https://devfeed.tech/tags/network-firewall.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

AWS Network Firewall now supports explicit HTTP/HTTPS proxying and routed firewall inspection through one firewall policy, with both traffic paths using the same egress IP addresses. For routed traffic, optional native NAT managed by Network Firewall can centralize egress from VPCs with overlapping or non-overlapping CIDRs without service chaining; without NAT, traffic returns through the endpoint as before. Proxy setup uses CONNECT requests and requires no route table changes. The source describes migration aids including custom proxy hostnames with an ACM certificate and a Squid-to-Suricata rule converter. TLS inspection can cover secondary endpoints only when they are in the firewall's account; domain-based selective TLS inspection applies to proxy traffic, not routed traffic. For domain filtering, it recommends pairing DNS rules that control proxy resolution with TLS SNI rules that check traffic inside established tunnels. Cached DNS responses honor TTLs of 5-3,600 seconds, so a new drop rule may not affect connections until the cached entry expires.

### Source excerpt

With this launch you can use your AWS Network Firewall to filter HTTP and HTTPS traffic as an explicit proxy, inspect all other traffic as a routed firewall, and centralize egress from overlapping and non-overlapping source VPC through a NAT Gateway that Network Firewall manages for you. In August 2026, we re-introduced Network Firewall proxy [...]

## Fast failover with Amazon Route 53 Private Endpoint Health Checks

DevFeed: [Fast failover with Amazon Route 53 Private Endpoint Health Checks](<https://devfeed.tech/articles/fast-failover-with-amazon-route-53-private-endpoint-health-checks-144601.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/fast-failover-with-amazon-route-53-private-endpoint-health-checks/>)

Author: Prabhakar Varadarajan

Published: 2026-11-19T20:21:15Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [health check](<https://devfeed.tech/topics/health-check.md>)

Tags: [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [dns](<https://devfeed.tech/tags/dns.md>), [failover](<https://devfeed.tech/tags/failover.md>), [fast](<https://devfeed.tech/tags/fast.md>), [health-checks](<https://devfeed.tech/tags/health-checks.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [native](<https://devfeed.tech/tags/native.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [private](<https://devfeed.tech/tags/private.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [routing](<https://devfeed.tech/tags/routing.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

Amazon Route 53 Private Endpoint Health Checks let Route 53 probe reachable private targets from a VPC and drive DNS failover in private hosted zones, avoiding a custom CloudWatch alarm and Lambda control loop that the excerpt says commonly takes minutes and adds operational burden. Create a Health Check Source, which provides VPC access through ENIs in three Availability Zones; configure a check for a private IP or domain over HTTP, HTTPS, or TCP; then attach it to the primary record in a failover routing policy. The excerpt says detection and failover are designed to complete in seconds, without public exposure or a required load balancer. Setup requires bidirectional security group and network ACL access, and short DNS TTLs help clients move to standby quickly. For VPCs spanning more than three Availability Zones, add a source to cover each target AZ. At launch, private endpoint latency measurement, public checks through a source, and calculated checks referencing private checks are unavailable.

### Source excerpt

Amazon Route 53 Private Endpoint Health Checks bring native, fast DNS failover to private endpoints inside your VPC, without a custom CloudWatch and Lambda control loop. Learn how the feature works, how to set up a private health check and failover routing step by step, and the private-only resilience patterns it unlocks.

## Introducing resource context for firewall policies with AWS Transit Gateway

DevFeed: [Introducing resource context for firewall policies with AWS Transit Gateway](<https://devfeed.tech/articles/introducing-resource-context-for-firewall-policies-with-aws-transit-gateway-144604.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-resource-context-for-firewall-policies-with-aws-transit-gateway/>)

Author: Rajat Tyagi

Published: 2026-11-19T18:41:56Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-transit-gateway](<https://devfeed.tech/tags/aws-transit-gateway.md>), [context](<https://devfeed.tech/tags/context.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [gateway-load-balancer](<https://devfeed.tech/tags/gateway-load-balancer.md>)

### AI overview

AWS Transit Gateway can attach source resource context to traffic sent to third-party firewalls through Gateway Load Balancer network function attachments. A separate AWS Network Manager context store maps the compact packet context IDs to VPCs, subnets, security groups, and attachments, letting firewalls apply resource-based policies alongside existing IP rules without waiting for IP synchronization. The walkthrough requires a transit gateway, healthy Gateway Load Balancer firewall targets, an endpoint service, static routes to the attachment, and a context store association; the firewall assumes an IAM role to read the store. The documented limits include source context only, no inspection of traffic within the same VPC, no context sharing across inter-Region peering, and omission of security groups when a resource has more than five. Routing changes during migration may interrupt active connections.

### Source excerpt

AWS Transit Gateway now shares AWS resource context (VPCs, subnets, security groups, and attachments) with third-party firewalls, so you can write firewall policies based on how resources are organized instead of IP addresses. This post shows how to create a Gateway Load Balancer network function attachment and turn on context sharing.

## New Site-to-Site VPN connections will default to recommended cryptography

DevFeed: [New Site-to-Site VPN connections will default to recommended cryptography](<https://devfeed.tech/articles/new-site-to-site-vpn-connections-will-default-to-recommended-cryptography-142037.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/new-site-to-site-vpn-connections-will-default-to-recommended-cryptography/>)

Author: Durgesh Potnis

Published: 2026-11-18T21:10:11Z

Content type: release

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Post-quantum cryptography](<https://devfeed.tech/topics/post-quantum-cryptography.md>)

Tags: [2027](<https://devfeed.tech/tags/2027.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [audit](<https://devfeed.tech/tags/audit.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-site-to-site-vpn](<https://devfeed.tech/tags/aws-site-to-site-vpn.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [diffie-hellman](<https://devfeed.tech/tags/diffie-hellman.md>), [existing](<https://devfeed.tech/tags/existing.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [ikev2](<https://devfeed.tech/tags/ikev2.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [learn](<https://devfeed.tech/tags/learn.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [recommended](<https://devfeed.tech/tags/recommended.md>), [site-to-site-vpn](<https://devfeed.tech/tags/site-to-site-vpn.md>), [vpn](<https://devfeed.tech/tags/vpn.md>)

### AI overview

Starting March 1, 2027, new AWS Site-to-Site VPN connections will default to IKEv2, AES256-GCM-16, SHA2-384, and Diffie-Hellman group 20; existing connections retain their configured algorithms. Customers whose gateway devices need other algorithms must explicitly select them when creating connections, including through CloudFormation, CDK, or Terraform, or negotiation may fail. To migrate existing tunnels, audit negotiated algorithms with GetActiveVpnTunnelStatus, update the customer gateway, validate connectivity, then remove non-recommended options on the AWS side one tunnel at a time with ModifyVpnTunnelOptions. Each tunnel update causes brief downtime. The article also provides an audit script for enabled Regions and lists its required read-only IAM permissions.

### Source excerpt

Starting March 1, 2027, new AWS Site-to-Site VPN connections will default to only the recommended cryptographic algorithms (IKEv2, AES256-GCM-16, SHA2-384, and Diffie-Hellman group 20). Existing connections are unaffected. Learn what changes, how to check whether you are affected, and how to audit and migrate your existing tunnels before the change.

## Introducing network calls in Amazon CloudFront Functions

DevFeed: [Introducing network calls in Amazon CloudFront Functions](<https://devfeed.tech/articles/introducing-network-calls-in-amazon-cloudfront-functions-141165.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-network-calls-in-amazon-cloudfront-functions/>)

Author: Babur Khan

Published: 2026-11-18T20:16:51Z

Content type: release

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Dynamic authorization rules](<https://devfeed.tech/topics/dynamic-authorization-rules.md>), [serverless monitoring](<https://devfeed.tech/topics/serverless-monitoring.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-cloudfront](<https://devfeed.tech/tags/amazon-cloudfront.md>), [amazon-cloudfront-functions](<https://devfeed.tech/tags/amazon-cloudfront-functions.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [background](<https://devfeed.tech/tags/background.md>), [beacon](<https://devfeed.tech/tags/beacon.md>), [bot](<https://devfeed.tech/tags/bot.md>), [budget](<https://devfeed.tech/tags/budget.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [cloudfront](<https://devfeed.tech/tags/cloudfront.md>), [collecting](<https://devfeed.tech/tags/collecting.md>), [edge](<https://devfeed.tech/tags/edge.md>), [lambda-edge](<https://devfeed.tech/tags/lambda-edge.md>), [latency](<https://devfeed.tech/tags/latency.md>), [launch](<https://devfeed.tech/tags/launch.md>), [network-calls](<https://devfeed.tech/tags/network-calls.md>), [networking-content-delivery](<https://devfeed.tech/tags/networking-content-delivery.md>)

### AI overview

CloudFront Functions now supports `cf.fetch()` and `cf.beacon()` for network calls to origins configured on the same distribution. `cf.fetch()` lets a viewer request function consult a live service, such as an authorization or bot detection service, and use its response to allow, block, or redirect a request; `cf.beacon()` sends background events without delaying the page response, including for cached views. The example requires the `cloudfront-js-2.0` runtime, a configured origin, and association with a Viewer Request event. The announcement reports DataDome saw 60% lower customer cost than with its Lambda@Edge implementation. Network calls cost $0.10 per million in addition to invocation charges; flat-rate plans require Pro tier or above.

### Source excerpt

Amazon CloudFront lets you securely deliver static and dynamic content with low latency and high transfer speeds. With CloudFront Functions, you can run business logic such as redirecting requests, selectively routing to alternate origin, or modifying headers at every CloudFront edge location with low latency and scale. Today, we are introducing network calls in CloudFront [...]

## Choosing the right network architecture for Amazon Bedrock AgentCore

DevFeed: [Choosing the right network architecture for Amazon Bedrock AgentCore](<https://devfeed.tech/articles/choosing-the-right-network-architecture-for-amazon-bedrock-agentcore-141163.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/choosing-the-right-network-architecture-for-amazon-bedrock-agentcore/>)

Author: Daniel Neri

Published: 2026-11-18T19:50:20Z

Content type: comparison

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Resource Access Manager (RAM)](<https://devfeed.tech/topics/resource-access-manager-ram.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [account](<https://devfeed.tech/tags/account.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agentcore-runtime](<https://devfeed.tech/tags/agentcore-runtime.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [lattice](<https://devfeed.tech/tags/lattice.md>), [network](<https://devfeed.tech/tags/network.md>), [network-architecture](<https://devfeed.tech/tags/network-architecture.md>), [networking](<https://devfeed.tech/tags/networking.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

AgentCore runtime VPC support and AgentCore Gateway with VPC Lattice are independent options for reaching private resources; either or both can be used. Runtime VPC support gives agents direct access through ENIs shared by agents with the same subnet and security group configuration. ENI and IP use therefore grow with distinct access patterns, as do security group rules on reachable resources, making this option a better fit when access patterns stay few. Gateway puts authorization and configured access policies at a central point, then routes requests through VPC Lattice resource gateways. In managed mode, AgentCore operates gateways for resources in its own account, reusing them for matching configurations; each gateway consumes one IP per subnet. Self-managed mode lets teams share a gateway across resource configurations and is required for resources in other accounts, which share configurations through AWS RAM. Gateway reduces distributed security group rule sprawl, but targets, policies, credentials, certificates, shares, and quotas still require management. Gateway targets also require publicly trusted TLS certificates, with specific endpoint setup for private API Gateway and

### Source excerpt

As enterprises move AI agents from pilot to production, networking often decides whether a deployment scales. This post compares two Amazon Bedrock AgentCore options for reaching private resources in your VPCs: AgentCore runtime VPC support and AgentCore Gateway with VPC Lattice, and shows how each scales with your access patterns and accounts.

## Introducing 1:1 NAT on AWS Transit Gateway and AWS Cloud WAN

DevFeed: [Introducing 1:1 NAT on AWS Transit Gateway and AWS Cloud WAN](<https://devfeed.tech/articles/introducing-1-1-nat-on-aws-transit-gateway-and-aws-cloud-wan-137829.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-11-nat-on-aws-transit-gateway-and-aws-cloud-wan/>)

Author: Shubham Singh

Published: 2026-11-16T20:10:05Z

Content type: release

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloud](<https://devfeed.tech/tags/aws-cloud.md>), [aws-cloud-wan](<https://devfeed.tech/tags/aws-cloud-wan.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-site-to-site-vpn](<https://devfeed.tech/tags/aws-site-to-site-vpn.md>), [aws-transit-gateway](<https://devfeed.tech/tags/aws-transit-gateway.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [connect](<https://devfeed.tech/tags/connect.md>), [csp](<https://devfeed.tech/tags/csp.md>), [dns](<https://devfeed.tech/tags/dns.md>), [ecmp](<https://devfeed.tech/tags/ecmp.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [nat](<https://devfeed.tech/tags/nat.md>), [network](<https://devfeed.tech/tags/network.md>)

### AI overview

AWS Transit Gateway and AWS Cloud WAN now support static, stateless IPv4 1:1 NAT through Regional Private NAT Gateway integration to connect networks with overlapping CIDRs. Per attachment, rules map a source CIDR to a translated CIDR of the same prefix length; the host portion and ports remain unchanged, and translation works in both directions. NAT CIDRs must come from RFC 1918 or RFC 6598 ranges. A route to each translated range is required: system-route support lets AWS create it, while disabling that setting requires the network to advertise the NAT CIDR over BGP. The article illustrates use on overlapping VPCs, a Direct Connect gateway attachment for multicloud connectivity, and Cloud WAN VPN attachments for partner networks. Update DNS records to translated addresses because NAT does not rewrite DNS. System routes rank below static and above propagated routes; with system-route support enabled, original BGP attributes such as AS path and MED are not preserved. For VPN designs using ECMP or primary/standby, the article recommends disabling system-route support and having the partner advertise the NAT CIDR and stop advertising the overlapping original range. NAT is IPv4-only,

### Source excerpt

Overlapping IP addresses keep networks from connecting. With 1:1 NAT on AWS Transit Gateway and AWS Cloud WAN, each network gets a unique range through native Regional Private NAT Gateway integration, so you don't renumber networks or deploy a separate NAT solution.

## Building a unidirectional edge layer for third-party connectivity on AWS with Amazon VPC Lattice

DevFeed: [Building a unidirectional edge layer for third-party connectivity on AWS with Amazon VPC Lattice](<https://devfeed.tech/articles/building-a-unidirectional-edge-layer-for-third-party-connectivity-on-aws-with-amazon-vpc-lattice-137828.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/building-a-unidirectional-edge-layer-for-third-party-connectivity-on-aws-with-amazon-vpc-lattice/>)

Author: Vijay Menon

Published: 2026-11-16T20:06:07Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [AWS Network Firewall](<https://devfeed.tech/topics/aws-network-firewall.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloud-wan](<https://devfeed.tech/tags/aws-cloud-wan.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-network-firewall](<https://devfeed.tech/tags/aws-network-firewall.md>), [aws-privatelink](<https://devfeed.tech/tags/aws-privatelink.md>), [aws-site-to-site-vpn](<https://devfeed.tech/tags/aws-site-to-site-vpn.md>), [aws-transit-gateway](<https://devfeed.tech/tags/aws-transit-gateway.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [edge](<https://devfeed.tech/tags/edge.md>), [egress](<https://devfeed.tech/tags/egress.md>), [ingress](<https://devfeed.tech/tags/ingress.md>), [layer](<https://devfeed.tech/tags/layer.md>), [network-connectivity](<https://devfeed.tech/tags/network-connectivity.md>), [networking-content-delivery](<https://devfeed.tech/tags/networking-content-delivery.md>), [third-party](<https://devfeed.tech/tags/third-party.md>), [thought-leadership](<https://devfeed.tech/tags/thought-leadership.md>)

### AI overview

Amazon VPC Lattice and AWS PrivateLink can provide partner ingress and egress while keeping third parties off the internal Layer 3 network. The design uses separate edge ingress and egress VPCs connected to internal workloads through Transit Gateway; expose only needed services, optionally routing traffic through AWS Network Firewall for inspection. VPC Lattice resource gateways and configurations suit TCP services and can target IP addresses or FQDNs. Use AWS PrivateLink for UDP services or when a consumer cannot allocate the required /28 per Availability Zone for a service network endpoint; providers that publish only PrivateLink services also require PrivateLink endpoints. For non-AWS providers, dedicated VPCs can use overlapping address ranges and connect by VPN or Direct Connect without creating a routed path into the broader network. Traditional peering, Transit Gateway, Cloud WAN, VPN, and Direct Connect offer broader bidirectional Layer 3 reachability, while public APIs bring internet exposure and endpoint-hardening requirements. The architecture assumes existing hybrid networking and supports optional firewall inspection.

### Source excerpt

Building a unidirectional edge layer for third-party connectivity removes a common trade-off. Enterprises need bidirectional service exchange with partners, vendors, and external platforms, without bidirectional network connectivity that broadens exposure. With Amazon VPC Lattice and AWS PrivateLink, you can exchange services for both ingress and egress, without creating a routed network path. The traditional options [...]

## Monitoring global traffic with AWS Cloud WAN Flow Logs

DevFeed: [Monitoring global traffic with AWS Cloud WAN Flow Logs](<https://devfeed.tech/articles/monitoring-global-traffic-with-aws-cloud-wan-flow-logs-134113.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/monitoring-global-traffic-with-aws-cloud-wan-flow-logs/>)

Author: Thaddeus Worsnop

Published: 2026-11-13T21:02:02Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [VPC Flow Logs](<https://devfeed.tech/topics/vpc-flow-logs.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-data-firehose](<https://devfeed.tech/tags/amazon-data-firehose.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloud-wan](<https://devfeed.tech/tags/aws-cloud-wan.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [cross](<https://devfeed.tech/tags/cross.md>), [edge](<https://devfeed.tech/tags/edge.md>), [global-network](<https://devfeed.tech/tags/global-network.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [logs](<https://devfeed.tech/tags/logs.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [query](<https://devfeed.tech/tags/query.md>), [region](<https://devfeed.tech/tags/region.md>), [s3](<https://devfeed.tech/tags/s3.md>), [scopes](<https://devfeed.tech/tags/scopes.md>)

### AI overview

AWS Cloud WAN Flow Logs provide a core-network view of traffic across VPC and hybrid attachments, including Region, segment, attachment, NAT, and packet-drop context. Logs can be created at core-network, edge, or attachment scope and delivered to CloudWatch Logs, S3, or Data Firehose; Athena and CloudWatch Logs Insights support analysis. Records capture traffic at each in-scope attachment, so a flow may appear more than once; filtering for ingress or a single attachment can avoid double counting. Setup requires the core-network owner account, IAM permissions, active traffic, and AWS CLI 2.40.1 or later. Initial core-network or edge log creation briefly locks the core network in UPDATING; first attachment logs briefly update that attachment. Logs use a fixed one-minute interval and are immutable. Drops inside an inspection VPC are not marked as Cloud WAN drops and require firewall or appliance-interface logs to investigate.

### Source excerpt

AWS Cloud WAN Flow Logs capture flow-level traffic across your global network. Learn how to create flow logs at the core network, edge, and attachment scopes, publish them to Amazon CloudWatch Logs, Amazon S3, or Amazon Data Firehose, and query them with Amazon Athena and CloudWatch Logs Insights to analyze cross-segment and cross-Region traffic and drops.

## Authenticate external gRPC clients with Amazon VPC Lattice

DevFeed: [Authenticate external gRPC clients with Amazon VPC Lattice](<https://devfeed.tech/articles/authenticate-external-grpc-clients-with-amazon-vpc-lattice-127235.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/authenticate-external-grpc-clients-with-amazon-vpc-lattice/>)

Author: Alin Scurtu

Published: 2026-11-10T01:16:39Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [gRPC](<https://devfeed.tech/topics/grpc.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [application-load-balancer](<https://devfeed.tech/tags/application-load-balancer.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [grpc](<https://devfeed.tech/tags/grpc.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [identity](<https://devfeed.tech/tags/identity.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The pattern bridges external JWT identity and VPC Lattice's SigV4 trust: an ALB validates RS256 access tokens, then an ECS proxy extracts selected claims into headers and signs requests with its task role. Lattice authorizes that workload identity through service network and per-service IAM auth policies; the translated identity headers are covered by SigV4. The native AWS SDK approach supports unary RPCs and requires application code to handle credentials, signing, and gRPC framing. Envoy moves signing into a filter pipeline and supports gRPC streaming when the Lattice target group uses protocol version GRPC; Lua claim translation must run before signing. The sample is for non-production use. The ALB needs a publicly accessible JWKS endpoint and cannot check token revocation, while the proxy must only accept ALB traffic because it does not revalidate JWTs.

### Source excerpt

External gRPC clients carry JWTs, but Amazon VPC Lattice trusts SigV4 signatures. This post shows how to build an ingress layer where an Application Load Balancer validates JWTs and an Amazon ECS proxy translates that identity into SigV4, enforcing per-service authorization with VPC Lattice auth policies while preserving gRPC over HTTP/2 end-to-end.

## Introducing device posture assessment for AWS Client VPN

DevFeed: [Introducing device posture assessment for AWS Client VPN](<https://devfeed.tech/articles/introducing-device-posture-assessment-for-aws-client-vpn-119792.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-device-posture-assessment-for-aws-client-vpn/>)

Author: Bruce Pinsky

Published: 2026-11-05T16:48:16Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [AWS Client VPN](<https://devfeed.tech/topics/aws-client-vpn.md>), [Endpoint security](<https://devfeed.tech/topics/endpoint-security.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [test](<https://devfeed.tech/topics/test.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-client-vpn](<https://devfeed.tech/tags/aws-client-vpn.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [client-vpn](<https://devfeed.tech/tags/client-vpn.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [condition](<https://devfeed.tech/tags/condition.md>), [connect](<https://devfeed.tech/tags/connect.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [crowdstrike](<https://devfeed.tech/tags/crowdstrike.md>), [device](<https://devfeed.tech/tags/device.md>), [device-management](<https://devfeed.tech/tags/device-management.md>), [device-trust](<https://devfeed.tech/tags/device-trust.md>), [devices](<https://devfeed.tech/tags/devices.md>), [endpoint-security](<https://devfeed.tech/tags/endpoint-security.md>), [health](<https://devfeed.tech/tags/health.md>), [logs](<https://devfeed.tech/tags/logs.md>), [policy](<https://devfeed.tech/tags/policy.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

AWS Client VPN can require device health as well as authenticated identity for tunnel access through a Cedar authorization policy. Administrators register device trust providers--CrowdStrike (Windows and macOS), Jamf (macOS), or JumpCloud (Windows, macOS, and Ubuntu)--and Client VPN checks signed device tokens at connection and on refreshes about every five minutes. A denial can refuse a new connection or end an active session. Provider attributes differ substantially, so policies are provider-specific; existing network authorization rules still separately govern reachable destinations. Shadow mode logs policy decisions without blocking connections, allowing administrators to review results before enforcement. Setup also requires AWS VPN Client 6.2.0 or later and an updated .ovpn file with the posture directive; other OpenVPN clients have no device attributes and will fail policies that require them. If token refresh stops, existing claims are used for up to 15 minutes, then device attributes are removed and the policy is reevaluated. The feature has no additional charge.

### Source excerpt

AWS Client VPN now offers device posture assessment: make device health a condition of tunnel access. Register a device trust provider (CrowdStrike, Jamf, or JumpCloud), write a Cedar policy, and Client VPN evaluates every connection at connect time and throughout the session. Use shadow mode and connection logs to test a policy before you enforce it.

## Introducing tunnel endpoints for private access to network segments

DevFeed: [Introducing tunnel endpoints for private access to network segments](<https://devfeed.tech/articles/introducing-tunnel-endpoints-for-private-access-to-network-segments-119793.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-tunnel-endpoints-for-private-access-to-network-segments/>)

Author: Bruce Pinsky

Published: 2026-11-05T16:48:12Z

Content type: release

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Network Segmentation](<https://devfeed.tech/topics/network-segmentation.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [Resource Access Manager (RAM)](<https://devfeed.tech/topics/resource-access-manager-ram.md>), [VXLAN](<https://devfeed.tech/topics/vxlan.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [application](<https://devfeed.tech/tags/application.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-privatelink](<https://devfeed.tech/tags/aws-privatelink.md>), [created](<https://devfeed.tech/tags/created.md>), [gives](<https://devfeed.tech/tags/gives.md>), [inside](<https://devfeed.tech/tags/inside.md>), [ip](<https://devfeed.tech/tags/ip.md>), [network](<https://devfeed.tech/tags/network.md>), [one](<https://devfeed.tech/tags/one.md>), [private](<https://devfeed.tech/tags/private.md>), [private-access](<https://devfeed.tech/tags/private-access.md>), [range](<https://devfeed.tech/tags/range.md>), [resource](<https://devfeed.tech/tags/resource.md>), [resources](<https://devfeed.tech/tags/resources.md>), [shares](<https://devfeed.tech/tags/shares.md>), [type](<https://devfeed.tech/tags/type.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

AWS PrivateLink tunnel endpoints let a consumer VPC reach an entire provider-defined CIDR range through a consumer-initiated GENEVE tunnel, so resources added later are reachable without sharing each one separately. Providers define allowed ranges, protocols, and ports in a CIDR resource configuration, attach it to an IN_VPC resource gateway, and share it through AWS RAM; traffic outside those ranges is dropped. DNS can also be resolved through the tunnel in the provider's network. Access remains subject to provider-side security controls, and logs do not reveal the consumer workload's inner source address. Setup requires overlapping Availability Zones and UDP 6081 between the consumer endpoint and compute. Application traffic must be TCP (DNS is the only supported UDP traffic); ICMP and IP fragments are not forwarded, and connections can only be initiated by the consumer.

### Source excerpt

Tunnel endpoints are a new VPC endpoint type, powered by AWS PrivateLink, that gives an application in one VPC private access to an entire range of IP addresses in another VPC. The network owner shares a CIDR block once, and every resource inside it becomes reachable, including resources created later.

## Introducing change-based throttling for Amazon Route 53 APIs

DevFeed: [Introducing change-based throttling for Amazon Route 53 APIs](<https://devfeed.tech/articles/introducing-change-based-throttling-for-amazon-route-53-apis-117599.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-change-based-throttling-for-amazon-route-53-apis/>)

Author: Bhargav Talluri

Published: 2026-11-03T23:09:04Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [apis](<https://devfeed.tech/tags/apis.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws-cdk](<https://devfeed.tech/tags/aws-cdk.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [dns](<https://devfeed.tech/tags/dns.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [limits](<https://devfeed.tech/tags/limits.md>), [throughput](<https://devfeed.tech/tags/throughput.md>)

### AI overview

Since July 30, 2026, Route 53 DNS APIs have a default account-wide request limit of 10 calls per second (50-token burst) and a separate change-throughput limit of 100 DNS record changes per second (1,500-token burst). Each ChangeResourceRecordSets call draws from both buckets; other API operations use no change-throughput tokens, and some operations have lower request limits. IaC deployments with few changes per call mainly benefit from the higher request rate, while large migrations are constrained by total changes: batching more per call does not increase sustained throughput. Spread changes evenly, use burst capacity for brief spikes, and retry only HTTP 400 responses carrying the Throttling code with exponential backoff and jitter. SDK backoff is on by default; adaptive retry is opt-in and regulates request frequency, not changes per request. Workloads needing higher limits can request an increase through AWS Support. These limits exclude Resolver, Profiles, and domain registration APIs.

### Source excerpt

Amazon Route 53 now uses change-based throttling and has doubled its default API request rate from 5 to 10 requests per second. Learn how the new per-account model works, with separate request-rate and change-throughput limits, and best practices for automating DNS management at scale.

## Use Bring Your Own ASN (BYOASN) to enforce data sovereignty on AWS Direct Connect public VIFs

DevFeed: [Use Bring Your Own ASN (BYOASN) to enforce data sovereignty on AWS Direct Connect public VIFs](<https://devfeed.tech/articles/use-bring-your-own-asn-byoasn-to-enforce-data-sovereignty-on-aws-direct-connect-public-vifs-117600.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/use-bring-your-own-asn-byoasn-to-enforce-data-sovereignty-on-aws-direct-connect-public-vifs/>)

Author: Gonzalo Escarrá

Published: 2026-11-03T19:38:28Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [Routing Security](<https://devfeed.tech/topics/routing-security.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [data-sovereignty](<https://devfeed.tech/tags/data-sovereignty.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [saas](<https://devfeed.tech/tags/saas.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

SaaS providers can use AWS VPC IPAM to associate a distinct Bring Your Own ASN (BYOASN) with each Region where they advertise Bring Your Own IP (BYOIP) prefixes over Direct Connect public VIFs. The region-specific ASN appears as the origin in BGP AS_PATH, giving customers a standard signal to accept routes only from a permitted Region without relying on provider-maintained prefix lists. The provider needs IPAM with regional public pools, qualifying RIR-registered IP ranges and ASNs, matching authorization and ROA records, and public VIF advertisements. Customers need Direct Connect public VIFs and routers that support AS_PATH filtering. On public VIFs, AWS prepends ASN 7224, so the path is `7224 <your-ASN>`. Existing advertised prefixes can switch ASN without withdrawal or downtime; switching from Amazon ASN to a customer ASN is limited to once per hour, and authorizations and ROAs require renewal and maintenance.

### Source excerpt

SaaS providers can use Bring Your Own ASN (BYOASN) on AWS Direct Connect public VIFs to assign a distinct ASN per Region, giving end customers a standard BGP AS_PATH signal to enforce data sovereignty without relying on fragile per-Region prefix lists.

## Designing geo-segmented AWS Cloud WAN with service insertion

DevFeed: [Designing geo-segmented AWS Cloud WAN with service insertion](<https://devfeed.tech/articles/designing-geo-segmented-aws-cloud-wan-with-service-insertion-106908.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/designing-geo-segmented-aws-cloud-wan-with-service-insertion/>)

Author: Abhishek Kumar

Published: 2026-10-29T16:06:16Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Network Segmentation](<https://devfeed.tech/topics/network-segmentation.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [AWS Network Firewall](<https://devfeed.tech/topics/aws-network-firewall.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloud-wan](<https://devfeed.tech/tags/aws-cloud-wan.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-network-firewall](<https://devfeed.tech/tags/aws-network-firewall.md>), [aws-transit-gateway](<https://devfeed.tech/tags/aws-transit-gateway.md>), [cloudformation](<https://devfeed.tech/tags/cloudformation.md>), [data-residency](<https://devfeed.tech/tags/data-residency.md>), [inspection](<https://devfeed.tech/tags/inspection.md>), [multi-region](<https://devfeed.tech/tags/multi-region.md>), [reference-architecture](<https://devfeed.tech/tags/reference-architecture.md>), [security](<https://devfeed.tech/tags/security.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The reference design keeps workloads in-region with geo-restricted AWS Cloud WAN segments while centralizing east-west and internet-egress inspection. Its dual-hop policy uses three `send-via` NFGs for intra-geo and cross-geo segment pairs, plus two dedicated `send-to` egress NFGs: a segment pair can use only one NFG, and an NFG used for dual-hop `send-via` cannot also handle `send-to`. Dual-hop inspects cross-Region traffic in both Regions, giving each a policy enforcement point at the cost of extra NFGs, attachment processing, and inter-Region transfer; single-hop inspects once in a deterministically selected Region and suits single-sided inspection needs. Each east-west inspection VPC needs an inspection-subnet route back to the Core Network, appliance mode for symmetric flow routing, and IPv6 enabled on its attachment in dual-stack designs. Missing routes or IPv6 support can leave traffic silently unusable despite available attachments. The article describes lab-validated flows and an accompanying deployable CloudFormation template.

### Source excerpt

Design an AWS Cloud WAN network that keeps regional traffic in-region for data residency while running centralized security inspection across geographies. This deployable four-segment, multi-Region reference architecture combines geo-restricted segments with Network Function Groups, covering dual-hop versus single-hop trade-offs and the key NFG constraints.

## Your AWS Networking and Content Delivery guide to re:Invent 2026

DevFeed: [Your AWS Networking and Content Delivery guide to re:Invent 2026](<https://devfeed.tech/articles/your-aws-networking-and-content-delivery-guide-to-re-invent-2026-101071.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/your-aws-networking-and-content-delivery-guide-to-reinvent-2026/>)

Author: Rick Armstrong

Published: 2026-10-26T19:53:05Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Nitro System](<https://devfeed.tech/topics/nitro-system.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [amazon-cloudfront](<https://devfeed.tech/tags/amazon-cloudfront.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloud-wan](<https://devfeed.tech/tags/aws-cloud-wan.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-privatelink](<https://devfeed.tech/tags/aws-privatelink.md>), [aws-shield](<https://devfeed.tech/tags/aws-shield.md>), [aws-waf](<https://devfeed.tech/tags/aws-waf.md>), [elastic-load-balancing](<https://devfeed.tech/tags/elastic-load-balancing.md>), [networking](<https://devfeed.tech/tags/networking.md>), [networking-and-content-delivery](<https://devfeed.tech/tags/networking-and-content-delivery.md>)

### AI overview

AWS re:Invent 2026 runs November 30-December 4 in Las Vegas, with networking and content delivery sessions across six formats: 60-minute breakouts, chalk talks, code talks and builders' sessions; 120-minute hands-on workshops; and 20-minute lightning talks, each featuring a recent launch. In-person lightning talks are walk-up only; other formats allow reservations through the event portal or walk-up attendance if space remains. The Expo at The Venetian features AWS experts, interactive demos, a hardware showcase and a networking kiosk with hands-on architecture building. Dates and venues may change, so check the event portal. Practical tips include picking up a badge early, using the AWS Events app for agendas and routes, and noting Caesars Palace and Caesars Forum are about 0.4 miles apart. Breakout sessions will be posted to AWS Events YouTube after the event.

### Source excerpt

The AWS Networking and Content Delivery (CDN) team invites you to join us at re:Invent from November 30 through December 4 2026. During that time, Las Vegas, Nevada becomes the ultimate destination for cloud innovation, and there is no better time to look ahead at where cloud networking is going. Across five action-packed days you [...]

## Securing autonomous fleet communications at scale with mTLS over QUIC using Network Load Balancer passthrough

DevFeed: [Securing autonomous fleet communications at scale with mTLS over QUIC using Network Load Balancer passthrough](<https://devfeed.tech/articles/securing-autonomous-fleet-communications-at-scale-with-mtls-over-quic-using-network-load-balancer-passthrough-97734.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/securing-autonomous-fleet-communications-at-scale-with-mtls-over-quic-using-network-load-balancer-passthrough/>)

Author: Priya Huddar

Published: 2026-10-23T17:15:39Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [autonomous vehicles](<https://devfeed.tech/topics/autonomous-vehicles.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-drones](<https://devfeed.tech/tags/autonomous-drones.md>), [aws](<https://devfeed.tech/tags/aws.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [communications](<https://devfeed.tech/tags/communications.md>), [controller](<https://devfeed.tech/tags/controller.md>), [device](<https://devfeed.tech/tags/device.md>), [drones](<https://devfeed.tech/tags/drones.md>), [eks](<https://devfeed.tech/tags/eks.md>), [elastic-load-balancing](<https://devfeed.tech/tags/elastic-load-balancing.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [latency](<https://devfeed.tech/tags/latency.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [mtls](<https://devfeed.tech/tags/mtls.md>), [mutual-tls](<https://devfeed.tech/tags/mutual-tls.md>), [passthrough](<https://devfeed.tech/tags/passthrough.md>), [pods](<https://devfeed.tech/tags/pods.md>), [quic](<https://devfeed.tech/tags/quic.md>), [scale](<https://devfeed.tech/tags/scale.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The article's reference setup keeps QUIC's TLS 1.3 handshake on the application pods while an AWS Network Load Balancer forwards QUIC packets and routes sessions by Server ID embedded in Connection IDs. On Amazon EKS, the AWS Load Balancer Controller provisions the QUIC-enabled NLB; quic-go pods use unique injected Server IDs and AWS Private CA certificates to verify each device with mTLS. The walkthrough covers cluster and controller setup, certificate provisioning, baseline server-only TLS verification, then requiring and testing client certificates. A valid trusted certificate succeeds; missing or untrusted certificates fail during the handshake. A critical constraint is the exact 17-byte destination Connection ID required for non-Envoy servers: incorrect length can stall mTLS handshakes when certificate data arrives in separate Handshake packets. The article also notes that the NLB uses TCP health checks and does not drain QUIC connections; target replacement can break in-flight sessions, so clients need reconnect handling.

### Source excerpt

Learn how to architect end-to-end mutual TLS (mTLS) authentication over QUIC using AWS Network Load Balancer passthrough mode. This post shows how to route QUIC traffic to quic-go server pods on Amazon EKS through the AWS Load Balancer Controller, with per-device certificate authentication for latency-sensitive fleet workloads such as autonomous drones.

## Use private domain-name targets with Amazon VPC Lattice

DevFeed: [Use private domain-name targets with Amazon VPC Lattice](<https://devfeed.tech/articles/use-private-domain-name-targets-with-amazon-vpc-lattice-90830.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/use-private-domain-name-targets-with-amazon-vpc-lattice/>)

Author: Salman Ahmed

Published: 2026-10-20T15:51:26Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Resource Access Manager (RAM)](<https://devfeed.tech/topics/resource-access-manager-ram.md>), [TTL in DNS](<https://devfeed.tech/topics/ttl-in-dns.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [dns](<https://devfeed.tech/tags/dns.md>), [domain-name](<https://devfeed.tech/tags/domain-name.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [route-53](<https://devfeed.tech/tags/route-53.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Amazon VPC Lattice can now use private DNS names as resource configuration targets. Set `ResourceConfigDnsResolution` to `IN_VPC` so the resource gateway resolves names through the DNS servers in its VPC's DHCP option set. With the default AmazonProvidedDNS, this supports Route 53 private hosted zones and Resolver rules forwarding to on-premises DNS; a matching Resolver rule takes precedence over a private hosted zone. `PUBLIC` resolution cannot read private zones or on-premises DNS. The article describes sharing these resources across accounts through AWS RAM and a service network, plus two consumer prerequisites: enable private DNS on the resource association and permit the domain in the consumer's private DNS preference. The default `VERIFIED_DOMAINS_ONLY` does not cover private names; specify them explicitly. Resolution type and the relevant association settings are immutable after creation, so choose them in advance. Both VPCs need DNS support and hostnames enabled; target connectivity, security group rules, and any hybrid DNS forwarding path must also be in place.

### Source excerpt

VPC Lattice now supports private domain-name targets, so you can point a resource configuration at a name that resolves only in a Route 53 private hosted zone or on an on-premises DNS server. This post explains how to choose a DNS resolution type and source, then walks through two deployment patterns for sharing a private service across accounts.

## How Amazon CloudFront secures and accelerates the AWS MCP Server

DevFeed: [How Amazon CloudFront secures and accelerates the AWS MCP Server](<https://devfeed.tech/articles/how-amazon-cloudfront-secures-and-accelerates-the-aws-mcp-server-90465.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/how-amazon-cloudfront-secures-and-accelerates-the-aws-mcp-server/>)

Author: Salman Ahmed

Published: 2026-10-19T20:43:15Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-cloudfront](<https://devfeed.tech/tags/amazon-cloudfront.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [aws-waf](<https://devfeed.tech/tags/aws-waf.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cloudfront](<https://devfeed.tech/tags/cloudfront.md>), [has](<https://devfeed.tech/tags/has.md>), [lambda-edge](<https://devfeed.tech/tags/lambda-edge.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model](<https://devfeed.tech/tags/model.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [networking-content-delivery](<https://devfeed.tech/tags/networking-content-delivery.md>), [production](<https://devfeed.tech/tags/production.md>)

### AI overview

The AWS MCP Server handles public and authenticated requests behind Amazon CloudFront. The article explains how CloudFront, AWS WAF, and Lambda@Edge route requests, block abuse, answer static protocol calls and OAuth challenges near callers, and reduce origin load. It also describes monitoring across edge locations and reports a limited latency comparison from one client and one PoP.

### Source excerpt

The AWS MCP Server, a managed remote server for the Model Context Protocol (MCP), runs in production behind Amazon CloudFront. Hundreds of thousands of AWS accounts call it, and it handles millions of tool calls every month. Every request enters one of CloudFront's more than 750 Points of Presence (PoPs), the edge locations nearest the [...]

## Cross-account canary routing with Amazon VPC Lattice and Amazon API Gateway

DevFeed: [Cross-account canary routing with Amazon VPC Lattice and Amazon API Gateway](<https://devfeed.tech/articles/cross-account-canary-routing-with-amazon-vpc-lattice-and-amazon-api-gateway-67031.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/cross-account-canary-routing-with-amazon-vpc-lattice-and-amazon-api-gateway/>)

Author: Mahmoud Ismail

Published: 2026-10-07T19:16:35Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>), [VPC Flow Logs](<https://devfeed.tech/topics/vpc-flow-logs.md>), [blue-green deployment](<https://devfeed.tech/topics/blue-green-deployment.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [canary](<https://devfeed.tech/tags/canary.md>), [canary-deployment](<https://devfeed.tech/tags/canary-deployment.md>), [networking-content-delivery](<https://devfeed.tech/tags/networking-content-delivery.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

The article describes a cross-account canary-routing pattern for gradually moving traffic from a monolith to microservices. Amazon API Gateway makes the per-request canary decision, while Amazon VPC Lattice provides cross-account service connectivity. A VPC-attached Lambda function forwards requests to the selected service, and separate APIs can provide independent canary settings for each extracted service.

### Source excerpt

Modernizing a monolith into microservices may require placing each new service in its own AWS account for isolation, independent scaling, and clear ownership. During that migration you hit a hard question: how do you shift a small, precise slice of live traffic from the monolith to a new service in a different account? You need [...]

## Provisioning AWS Interconnect - multicloud with the Kiro agentic IDE

DevFeed: [Provisioning AWS Interconnect - multicloud with the Kiro agentic IDE](<https://devfeed.tech/articles/provisioning-aws-interconnect-multicloud-with-the-kiro-agentic-ide-66401.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/provisioning-aws-interconnect-multicloud-with-the-kiro-agentic-ide/>)

Author: Tushar Jagdale

Published: 2026-10-06T18:49:18Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Oracle Database@AWS](<https://devfeed.tech/topics/oracle-database-aws.md>), [Azure](<https://devfeed.tech/topics/azure.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-transit-gateway](<https://devfeed.tech/tags/aws-transit-gateway.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [kiro](<https://devfeed.tech/tags/kiro.md>), [microsoft-azure](<https://devfeed.tech/tags/microsoft-azure.md>), [multicloud](<https://devfeed.tech/tags/multicloud.md>), [networking-content-delivery](<https://devfeed.tech/tags/networking-content-delivery.md>)

### AI overview

The post walks through using the Kiro agentic IDE to research, plan, provision, test, and document a private AWS-Google Cloud interconnect. It describes the cross-cloud resource sequence, approval steps for infrastructure changes, and validation results from a single 1 Gbps test deployment, while noting considerations for security, cost, and production use.

### Source excerpt

Multicloud is no longer an edge case. Workloads end up spanning AWS and Google Cloud, Microsoft Azure, or Oracle Cloud Infrastructure after an acquisition, through a footprint that predates any consolidation decision, or because a key vendor operates on the other cloud. Sooner or later a network engineer gets the task: connect two environments privately [...]

## Powering predictable costs with AWS Direct Connect flat-rate pricing

DevFeed: [Powering predictable costs with AWS Direct Connect flat-rate pricing](<https://devfeed.tech/articles/powering-predictable-costs-with-aws-direct-connect-flat-rate-pricing-65226.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/powering-predictable-costs-with-aws-direct-connect-flat-rate-pricing/>)

Author: Donald Quindardo

Published: 2026-10-05T19:56:23Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [AWS data center network architecture](<https://devfeed.tech/topics/aws-data-center-network-architecture.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>)

Tags: [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cost-explorer](<https://devfeed.tech/tags/aws-cost-explorer.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-support](<https://devfeed.tech/tags/aws-support.md>), [aws-transit-gateway](<https://devfeed.tech/tags/aws-transit-gateway.md>), [cost-optimization](<https://devfeed.tech/tags/cost-optimization.md>), [costs](<https://devfeed.tech/tags/costs.md>), [hybrid-connectivity](<https://devfeed.tech/tags/hybrid-connectivity.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [networking](<https://devfeed.tech/tags/networking.md>), [networking-content-delivery](<https://devfeed.tech/tags/networking-content-delivery.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [resiliency](<https://devfeed.tech/tags/resiliency.md>)

### AI overview

The article explains how AWS Direct Connect flat-rate pricing applies a fixed hourly charge with no per-gigabyte data transfer out charge for covered Regions. It walks through configuring connections and resiliency groups, selecting geographic tiers, converting existing connections, and evaluating costs with CloudWatch and Cost Explorer. Examples cover single-Region and multi-Region workloads, failover, and separate billing modes across accounts. It also describes limitations, including standard charges for traffic outside a subscribed tier and exclusions such as hosted connections, SiteLink, and provider fees.

### Source excerpt

In a traditional on-premises network, predictable costs have always been central to network connectivity budgets. Organizations relied on leased lines, Multiprotocol Label Switching (MPLS) links, and dedicated cross-connects. No matter how much data they moved, the bill stayed the same. As they rebuilt their architecture in the cloud, they gained the flexibility of pay-as-you-go pricing. [...]

[Next page](<https://devfeed.tech/sources/networking-content-delivery.md?cursor=WyIyMDI2LTEwLTA1VDE5OjU2OjIzKzAwOjAwIiwgIjhiMWUzZjUzLTA2NGQtNDk3OS1iMGVjLWVhOGUyZjM5MjlkNiJd>)