# Cloud Networking

Cloud networking is the use of cloud-based services and virtual network components to connect organizational employees, resources, and applications, with networks defined and managed as software.

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

## What's next for Azure networking?

DevFeed: [What's next for Azure networking?](<https://devfeed.tech/articles/what-s-next-for-azure-networking-146430.md>)

Original publisher: [Read original article](<https://www.networkworld.com/article/4251523/whats-next-for-azure-networking.html>)

Author: Sean Michael Kerner

Published: 2026-11-20T16:48:53Z

Content type: news

Language: en

Sources: [Network World](<https://devfeed.tech/sources/network-world.md>)

Topics: [AI Networking](<https://devfeed.tech/topics/ai-networking.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Azure Kubernetes Service](<https://devfeed.tech/topics/azure-kubernetes-service.md>), [Azure](<https://devfeed.tech/topics/azure.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [aks](<https://devfeed.tech/tags/aks.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [apis](<https://devfeed.tech/tags/apis.md>), [at-t](<https://devfeed.tech/tags/at-t.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [cloud-computing-networking](<https://devfeed.tech/tags/cloud-computing-networking.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [data-centers](<https://devfeed.tech/tags/data-centers.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [fabric](<https://devfeed.tech/tags/fabric.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [networking](<https://devfeed.tech/tags/networking.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>)

### AI overview

AI workloads increase east-west traffic and shift demand across locations, so Microsoft is flattening its data center fabric, extending connectivity, and adding network controls. Its two-tier fabric cuts a five-hop path to three and is reported to be over 20% more power efficient; hollow core fiber is said to reduce latency by about one-third. For customers, Azure Multicloud Interconnect provisions cloud cross-connects through APIs (AWS generally available; GCP and Lumen offerings in preview, AT&T coming soon). AKS Fleet Manager peers clusters with failover and shared policy, while Route Server route maps filter, summarize, and influence routes. Agent Grid applies identity-based controls without changing agent code; Azure Firewall Premium's AI add-on uses two inline small language models to detect malware and exploit requests. Adaptive Virtual Patching applies mitigations until patches arrive. The excerpt also describes Microsoft's use of over 100 network agents, which handled more than 30,000 cases and reduced backlog by about three quarters over the past year.

### Source excerpt

AI workloads change how traffic moves inside a data center. GPUs exchange data with other GPUs, servers, and storage, which shifts traffic from north-south to east-west. AI agents add another layer. They span compute, GPUs, the network, and data centers, and demand can move from one place to another overnight. At its Ignite conference this week, Microsoft detailed Azure networking updates for this shift, including new services for enterprises as well as how Microsoft itself is using agentic AI for networking. (It also previewed Windows Server 2028, its largest platform update since Windows Server 2025.) Networking-related announcements made at Ignite include: Azure Multicloud Interconnect: Provisions cross-connects between Azure and other clouds through APIs. Amazon Web Services (AWS) is generally available. Google Cloud Platform (GCP) is in preview, as is Azure Last Mile Interconnect with Lumen. AT&T is coming soon. Cross-cluster networking for Azure Kubernetes Service (AKS): Peers clusters through Azure Kubernetes Fleet Manager with failover and one network policy. Azure Route Server route maps: Filter and summarize routes and apply autonomous system (AS) path prepending. Agent Grid: Enforces identity-based microsegmentation, isolation, and traffic policies for AI agents on the network. Azure Firewall AI add-on: Runs two inline small language models on Azure Firewall Premium to detect malware and exploit requests. Azure Adaptive Virtual Patching: Maps published vulnerabilities to workloads on virtual machines and applies inline mitigations until the actual patch arrives. Microsoft points to the shifts in traffic, location, and security that AI creates. "So, with all of these shifts, the network is no longer about connectivity. It is really becoming the intelligent control for the agentic world," said Igor Sakhnov, corporate vice president and general manager of Azure Networking, in a session at Microsoft Ignite. Azure flattens its fabric and adds hollow core fiber

## Netgate Releases pfSense Plus 26.07.2 and pfSense CE 2.9.2: Two Releases in Three Days

DevFeed: [Netgate Releases pfSense Plus 26.07.2 and pfSense CE 2.9.2: Two Releases in Three Days](<https://devfeed.tech/articles/netgate-releases-pfsense-plus-26-07-2-and-pfsense-ce-2-9-2-two-releases-in-three-days-145273.md>)

Original publisher: [Read original article](<https://www.netgate.com/blog/netgate-releases-pfsense-plus-26.07.2-and-pfsense-ce-2.9.2>)

Author: Netgate

Published: 2026-11-19T21:56:23Z

Content type: release

Language: en

Sources: [Netgate](<https://devfeed.tech/sources/blog-3.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>)

Tags: [bugs](<https://devfeed.tech/tags/bugs.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-networking](<https://devfeed.tech/tags/cloud-networking.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [netgate](<https://devfeed.tech/tags/netgate.md>), [network-edge](<https://devfeed.tech/tags/network-edge.md>), [patch](<https://devfeed.tech/tags/patch.md>), [pfsense](<https://devfeed.tech/tags/pfsense.md>), [plus](<https://devfeed.tech/tags/plus.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>), [router](<https://devfeed.tech/tags/router.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [software](<https://devfeed.tech/tags/software.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Netgate released pfSense Plus 26.07.2 and pfSense CE 2.9.2, bundling 18 FreeBSD security advisories and errata plus PHP 8.5.13 and nginx 1.30.7 updates. Both releases also disable the acpi_spmc driver, which could cause kernel panics on some hardware and provides no pfSense functionality. They include the fixes from 26.07.1 and 2.9.1, so users can upgrade directly without installing the earlier patches first. Netgate recommends backing up configuration, then using System > Update and selecting Current (26.07.2) for Plus or Current (2.9.2) for CE. The releases are described as production-ready; the article points users to upgrade troubleshooting documentation and support channels if issues arise.

### Source excerpt

pfSense® Plus and pfSense CE software, the world's leading firewall, router, and VPN solution, deliver secure network edge and cloud networking capabilities for millions of deployments worldwide. Today, Netgate® is releasing pfSense Plus software version 26.07.2 and pfSense CE software version 2.9.2. This is the second patch release in three days. On Tuesday, we released pfSense Plus 26.07.1 and pfSense CE 2.9.1 to fix several security vulnerabilities and bugs. As new advisories and errata continued to arrive, we moved quickly to deliver another update. We strongly encourage all pfSense Plus and pfSense CE users to upgrade to the latest versions.

## 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 [...]

## 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.

## StarlingX 13.0 updates the network stack for distributed edge deployments

DevFeed: [StarlingX 13.0 updates the network stack for distributed edge deployments](<https://devfeed.tech/articles/starlingx-13-0-updates-the-network-stack-for-distributed-edge-deployments-143897.md>)

Original publisher: [Read original article](<https://www.networkworld.com/article/4250526/starlingx-13-0-updates-the-network-stack-for-distributed-edge-deployments.html>)

Author: Sean Michael Kerner

Published: 2026-11-19T17:27:34Z

Content type: news

Language: en

Sources: [Network World](<https://devfeed.tech/sources/network-world.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [backup](<https://devfeed.tech/tags/backup.md>), [certificate-authority](<https://devfeed.tech/tags/certificate-authority.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [data-center-edge-computing-linux-networking](<https://devfeed.tech/tags/data-center-edge-computing-linux-networking.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [edge](<https://devfeed.tech/tags/edge.md>), [edge-computing](<https://devfeed.tech/tags/edge-computing.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [gateway-api](<https://devfeed.tech/tags/gateway-api.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [linux](<https://devfeed.tech/tags/linux.md>), [network](<https://devfeed.tech/tags/network.md>), [network-stack](<https://devfeed.tech/tags/network-stack.md>), [networking](<https://devfeed.tech/tags/networking.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [openstack](<https://devfeed.tech/tags/openstack.md>), [restore](<https://devfeed.tech/tags/restore.md>), [router](<https://devfeed.tech/tags/router.md>), [starlingx](<https://devfeed.tech/tags/starlingx.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

StarlingX 13.0 adds optional Layer 2 switching for edge servers without a nearby site router: its Kubernetes-managed Open vSwitch application can bridge SR-IOV interfaces and forward traffic to aggregation routers. The release also adds EJBCA as an optional CA for hosted application certificates; platform certificates remain managed as before. Hosted applications can use Calico-based Gateway API, while platform services and existing Ingress resources remain on NGINX Ingress, with no automatic conversion in this release. Subcloud backups can restore onto a factory-installed, bootstrapped node without reinstalling the OS. Operators can also upgrade from two releases back with one reboot per host.

### Source excerpt

Edge sites do not always come with the network gear that a data center takes for granted. That's a challenge the open-source StarlingX project from the OpenInfra Foundation is now tackling in its 13.0 update. StarlingX is an open-source distributed cloud platform that combines Linux, Kubernetes, OpenStack, and Ceph. The OpenInfra Foundation hosts the project, and operators including Verizon, Vodafone, T-Systems and KDDI use it for 5G and Open Radio Access Network (O-RAN) infrastructure. Earlier this year, the StarlingX 12.0 update added precision timing capabilities to help networking stay on time. The 13.0 update tackles a different set of issues. Key features include: Gateway API support. Calico-based support is available to hosted applications, while platform services still use Ingress NGINX Optional certificate authority. The Enterprise Java Beans Certificate Authority (EJBCA) runs on the platform and serves certificates to hosted applications. Subcloud restore. A backup restores directly onto a factory-installed node at a subcloud, a remote edge site, with no operating system reinstall. Direct upgrades. Operators can upgrade from two releases back with a single reboot per host. Layer 2 switching. A new Open vSwitch application lets servers at sites with no router next to them bridge traffic and connect directly to aggregation routers. "The OpenvSwitch application adds Layer 2 switching to the K8S platform," Greg Waines, a senior member of technical staff at Wind River and a StarlingX Technical Steering Committee member, told Network World. "A server can bridge traffic between its SR-IOV network interfaces and other servers, and it can forward traffic to the site routers." Open vSwitch works where no site router exists to the server Open vSwitch is a virtual switch that has long been enabled in OpenStack. The StarlingX 13.0 update adds an optional application that manages it through Kubernetes. "It targets edge and telco deployments where there is no site router

## 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.

## AWS PrivateLink Tunnel Endpoints Open a Whole CIDR Range to Another Account

DevFeed: [AWS PrivateLink Tunnel Endpoints Open a Whole CIDR Range to Another Account](<https://devfeed.tech/articles/aws-privatelink-tunnel-endpoints-open-a-whole-cidr-range-to-another-account-140159.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/aws-privatelink-tunnel-endpoints/>)

Author: Steef-Jan Wiggers

Published: 2026-11-18T09:29:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Resource Access Manager (RAM)](<https://devfeed.tech/topics/resource-access-manager-ram.md>)

Tags: [access-manager](<https://devfeed.tech/tags/access-manager.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-privatelink](<https://devfeed.tech/tags/aws-privatelink.md>), [aws-privatelink-tunnel-endpoints](<https://devfeed.tech/tags/aws-privatelink-tunnel-endpoints.md>), [client](<https://devfeed.tech/tags/client.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [dns](<https://devfeed.tech/tags/dns.md>), [haproxy](<https://devfeed.tech/tags/haproxy.md>), [http](<https://devfeed.tech/tags/http.md>), [logs](<https://devfeed.tech/tags/logs.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [news](<https://devfeed.tech/tags/news.md>), [resource](<https://devfeed.tech/tags/resource.md>), [space](<https://devfeed.tech/tags/space.md>), [tcp](<https://devfeed.tech/tags/tcp.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [tunnel](<https://devfeed.tech/tags/tunnel.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 all addresses in a shared CIDR range in another account, including resources added later. The provider shares a CIDR resource configuration through AWS Resource Access Manager; the consumer connects through a tunnel endpoint. Unlike VPC peering, this exposes a selected range in one direction, permits overlapping CIDRs, and allows connections only from the consumer. Consumer traffic must be wrapped in GENEVE over UDP port 6081, with endpoint and resource gateway subnets in matching Availability Zones. Inner traffic supports TCP and DNS only; ICMP, fragments, and private DNS names are unsupported. Logs identify the consumer endpoint but not the workload behind it. Sharing broad ranges such as 0.0.0.0/0 can expose routed networks beyond the provider VPC, so the excerpt recommends narrow ranges. A reported overlapping-CIDR setup required per-destination routes or an added relay/proxy hop. Charges include endpoint hours and processed data, with provider-side data billed through VPC Lattice.

### Source excerpt

AWS has detailed tunnel endpoints, a PrivateLink endpoint type that gives a consumer VPC access to an entire network segment in another account rather than one resource at a time, over an overlapping address space and with consumer-initiated connections only. The consumer must wrap traffic in GENEVE; only TCP and DNS pass, and access logs cannot attribute traffic to a workload behind the endpoint. By Steef-Jan Wiggers

## Distribute Amazon RDS traffic between read replicas using Network Load Balancer

DevFeed: [Distribute Amazon RDS traffic between read replicas using Network Load Balancer](<https://devfeed.tech/articles/distribute-amazon-rds-traffic-between-read-replicas-using-network-load-balancer-138652.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/distribute-amazon-rds-traffic-between-read-replicas-using-network-load-balancer/>)

Author: Vijay Chakraborty

Published: 2026-11-17T15:51:53Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [read-replica](<https://devfeed.tech/topics/read-replica.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [connection draining](<https://devfeed.tech/topics/connection-draining.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [affinity](<https://devfeed.tech/tags/affinity.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [amazon-elastic-kubernetes-service-amazon-eks](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service-amazon-eks.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.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>), [elastic-load-balancing](<https://devfeed.tech/tags/elastic-load-balancing.md>), [health](<https://devfeed.tech/tags/health.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [read-replicas](<https://devfeed.tech/tags/read-replicas.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

An NLB can provide one stable endpoint for distributing connections across Amazon RDS read replicas, with health checks and Availability Zone affinity. An EventBridge rule invokes a Lambda function every minute to resolve replica DNS names and synchronize their IPs into the NLB target group; S3 JSON state and retry logic help avoid premature deregistration during transient DNS failures. With zonal DNS affinity enabled and cross-zone load balancing disabled, traffic can remain AZ-local in steady state, reducing inter-AZ transfer. The endpoint also supports hybrid access over Direct Connect or Site-to-Site VPN without PrivateLink or Route 53 Resolver endpoints when a custom domain is unnecessary. The approach works with RDS engines that support read replicas, but the NLB balances connections rather than queries, so long-lived connections can limit redistribution. In EKS, CoreDNS placement can undermine zonal affinity; NodeLocal DNSCache is suggested. Deregistration delay allows existing connections to drain.

### Source excerpt

Learn how to put Amazon RDS read replicas behind a Network Load Balancer with health-aware, Availability Zone affinity routing. An AWS Lambda function keeps the load balancer target group in sync with replica IP addresses, giving clients a single stable endpoint over Direct Connect or Site-to-Site VPN without AWS PrivateLink overhead.

## Virtual Private Clouds in VMware vSphere Kubernetes Service: The Recommended Network Stack

DevFeed: [Virtual Private Clouds in VMware vSphere Kubernetes Service: The Recommended Network Stack](<https://devfeed.tech/articles/virtual-private-clouds-in-vmware-vsphere-kubernetes-service-the-recommended-network-stack-138605.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/11/17/virtual-private-clouds-in-vmware-vsphere-kubernetes-service-the-recommended-network-stack/>)

Author: vmwareblogs

Published: 2026-11-17T14:00:00Z

Content type: article

Language: en

Sources: [VMware](<https://devfeed.tech/sources/vmware-blogs.md>)

Topics: [vcf networking](<https://devfeed.tech/topics/vcf-networking.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [container-networking](<https://devfeed.tech/topics/container-networking.md>), [private cloud](<https://devfeed.tech/topics/private-cloud.md>), [vcf automation](<https://devfeed.tech/topics/vcf-automation.md>), [self-service](<https://devfeed.tech/topics/self-service.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [home-page](<https://devfeed.tech/tags/home-page.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-nodes](<https://devfeed.tech/tags/kubernetes-nodes.md>), [kubevm](<https://devfeed.tech/tags/kubevm.md>), [network](<https://devfeed.tech/tags/network.md>), [network-stack](<https://devfeed.tech/tags/network-stack.md>), [networking](<https://devfeed.tech/tags/networking.md>), [nsx](<https://devfeed.tech/tags/nsx.md>), [private](<https://devfeed.tech/tags/private.md>), [private-cloud](<https://devfeed.tech/tags/private-cloud.md>), [recommended](<https://devfeed.tech/tags/recommended.md>), [service](<https://devfeed.tech/tags/service.md>), [supervisor](<https://devfeed.tech/tags/supervisor.md>), [switch](<https://devfeed.tech/tags/switch.md>), [vcf](<https://devfeed.tech/tags/vcf.md>), [vcf-9-1](<https://devfeed.tech/tags/vcf-9-1.md>), [vcf-networking](<https://devfeed.tech/tags/vcf-networking.md>), [vks](<https://devfeed.tech/tags/vks.md>), [vks-vsphere-kubernetes-service](<https://devfeed.tech/tags/vks-vsphere-kubernetes-service.md>), [vmware-cloud-foundation](<https://devfeed.tech/tags/vmware-cloud-foundation.md>), [vmware-vsphere-kubernetes-service](<https://devfeed.tech/tags/vmware-vsphere-kubernetes-service.md>), [vpc](<https://devfeed.tech/tags/vpc.md>), [vsphere](<https://devfeed.tech/tags/vsphere.md>)

### AI overview

VCF Networking with VPC is the recommended VCF 9.1 stack for production VKS deployments and the required stack for VCF Automation environments. It places cluster nodes on private subnets and exposes needed endpoints through load balancing, with outbound NAT; its Virtual Network Appliance cluster scales to ten active/active nodes. The vSphere Distributed Switch option connects nodes to an existing VLAN and routes VIPs through one active/standby Foundation Load Balancer pair. VPC setup can start with one VLAN and grow to centralized Edge connectivity or Cisco and Arista EVPN/VXLAN integration. It also provides vCenter-based networking and Traceflow, multi-tenancy and self-service automation, and integrations including Infoblox and vDefend. A VLAN-backed VPC option in VCF 9.1.1 preserves the VPC workflow but removes private-network creation. The article says the Distributed Switch remains suited to VMware vSphere Foundation and smaller or lab environments.

### Source excerpt

Enabling the vSphere Supervisor in VMware Cloud Foundation (VCF) involves choosing a network stack for workloads running on vSphere Kubernetes Service (VKS), KubeVM Service, or Container Service - VCF Networking with Virtual Private Cloud (VPC), or the vSphere Distributed Switch. VCF Networking with VPC is the recommended, default option. It keeps Kubernetes nodes off the ... Continued The post Virtual Private Clouds in VMware vSphere Kubernetes Service: The Recommended Network Stack appeared first on VMware Blogs.

## Operation ShadowCloud: cloud service-based backdoors targeting government networks in Asia and Africa. Part 2

DevFeed: [Operation ShadowCloud: cloud service-based backdoors targeting government networks in Asia and Africa. Part 2](<https://devfeed.tech/articles/operation-shadowcloud-cloud-service-based-backdoors-targeting-government-networks-in-asia-and-africa-part-2-137169.md>)

Original publisher: [Read original article](<https://securelist.com/operation-shadowcloud-graphdoor/122005/>)

Author: Saurabh Sharma, Noushin Shabab

Published: 2026-11-17T08:00:43Z

Content type: article

Language: en

Sources: [Securelist](<https://devfeed.tech/sources/securelist.md>)

Topics: [Government Cybersecurity](<https://devfeed.tech/topics/government-cybersecurity.md>), [Infrastructure as a Service (IaaS)](<https://devfeed.tech/topics/infrastructure-as-a-service-iaas.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>)

Tags: [adapter](<https://devfeed.tech/tags/adapter.md>), [aes](<https://devfeed.tech/tags/aes.md>), [agent](<https://devfeed.tech/tags/agent.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [antivirus](<https://devfeed.tech/tags/antivirus.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [apt](<https://devfeed.tech/tags/apt.md>), [apt-reports](<https://devfeed.tech/tags/apt-reports.md>), [array](<https://devfeed.tech/tags/array.md>), [attribution](<https://devfeed.tech/tags/attribution.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [avast](<https://devfeed.tech/tags/avast.md>), [backdoor](<https://devfeed.tech/tags/backdoor.md>), [backdoors](<https://devfeed.tech/tags/backdoors.md>), [base64](<https://devfeed.tech/tags/base64.md>), [beacon](<https://devfeed.tech/tags/beacon.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [coff](<https://devfeed.tech/tags/coff.md>), [full](<https://devfeed.tech/tags/full.md>), [graphdoor](<https://devfeed.tech/tags/graphdoor.md>), [great-research](<https://devfeed.tech/tags/great-research.md>), [large](<https://devfeed.tech/tags/large.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-descriptions](<https://devfeed.tech/tags/malware-descriptions.md>), [malware-technologies](<https://devfeed.tech/tags/malware-technologies.md>), [medium](<https://devfeed.tech/tags/medium.md>), [microsoft-sharepoint](<https://devfeed.tech/tags/microsoft-sharepoint.md>), [operation-shadowcloud](<https://devfeed.tech/tags/operation-shadowcloud.md>), [thumbnail](<https://devfeed.tech/tags/thumbnail.md>), [windows-malware](<https://devfeed.tech/tags/windows-malware.md>)

### AI overview

GraphDoor uses Microsoft Graph and SharePoint as command and control: it authenticates a malicious application to obtain an access token, uploads encrypted victim data under a disguised source-map filename, fetches plug-ins and victim-specific command files, and executes commands with extensions from an allowed list. Its plug-ins include a keylogger, process lister, screenshot capture, file relocation, and proxy channels using Erfrp, Ably messaging, or Ably's Pusher-compatible WebSocket service. The loader runs COFF plug-ins from memory; the proxy components use shared memory for configuration. Attribution remains uncertain: shared staging directories and deployment timing overlap with activity associated with FamousSparrow and CopperTurtle, while an RC4 key in one side-loaded payload was previously associated with FamousSparrow. The report says the backdoor does not embed a fixed C2 domain; it obtains host and port through proxy or Ably channels. Its conclusion notes that legitimate cloud services can make malicious traffic blend with normal use, while advising that MeshCentral Agent deployment in an environment be treated as suspicious despite legitimate uses.

### Source excerpt

In part 2 of our analysis of the recently uncovered Operation ShadowCloud, we discuss the GraphDoor backdoor, additional plug-ins, and technical attribution.

## A Survey on Cloud-Edge-Terminal Collaborative Intelligence in AIoT Networks

DevFeed: [A Survey on Cloud-Edge-Terminal Collaborative Intelligence in AIoT Networks](<https://devfeed.tech/articles/a-survey-on-cloud-edge-terminal-collaborative-intelligence-in-aiot-networks-137008.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2508.18803>)

Author: Jiaqi Wu, Jing Liu, Yang Liu, Lixu Wang, Zehua Wang, Wei Chen, Zijian Tian, Richard Yu, Victor C. M. Leung

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Internet of things](<https://devfeed.tech/topics/iot.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [AI Research](<https://devfeed.tech/topics/ai-research.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [aiot](<https://devfeed.tech/tags/aiot.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [communication](<https://devfeed.tech/tags/communication.md>), [computing](<https://devfeed.tech/tags/computing.md>), [container-orchestration](<https://devfeed.tech/tags/container-orchestration.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [deep-learning](<https://devfeed.tech/tags/deep-learning.md>), [digital-twin](<https://devfeed.tech/tags/digital-twin.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-computing](<https://devfeed.tech/tags/distributed-computing.md>), [edge](<https://devfeed.tech/tags/edge.md>), [edge-cloud](<https://devfeed.tech/tags/edge-cloud.md>), [edge-computing](<https://devfeed.tech/tags/edge-computing.md>), [federated-learning](<https://devfeed.tech/tags/federated-learning.md>), [networks](<https://devfeed.tech/tags/networks.md>), [survey](<https://devfeed.tech/tags/survey.md>)

### AI overview

The survey presents cloud-edge-terminal collaborative intelligence (CETCI) as a way to build deployable collaborative AIoT systems by coordinating computing and communication across cloud, edge, and terminal layers. It reviews enabling infrastructure such as network virtualization, container orchestration, and software-defined networking; collaboration approaches for task offloading, resource allocation, and optimization across heterogeneous systems; and learning frameworks including federated and distributed deep learning, edge-cloud model evolution, and reinforcement learning. It identifies scalability, heterogeneity, and interoperability as challenges, and points to 6G+, agents, quantum computing, and digital twins as future directions. This overview is based on the supplied abstract.

### Source excerpt

arXiv:2508.18803v2 Announce Type: replace Abstract: The proliferation of Internet of things (IoT) devices in smart cities, transportation, healthcare, and industrial applications, coupled with the explosive growth of AI-driven services, has increased demands for efficient distributed computing architectures and networks, driving cloud-edge-terminal collaborative intelligence (CETCI) as a fundamental paradigm within the artificial intelligence of things (AIoT) community. With advancements in deep learning, large language models (LLMs), and edge computing, CETCI has made significant progress with emerging AIoT applications, moving beyond isolated layer optimization to deployable collaborative intelligence systems for AIoT (CISAIOT), a practical research focus in AI, distributed computing, and communications. This survey describes foundational architectures, enabling technologies, and scenarios of CETCI paradigms, offering a tutorial-style review for CISAIOT beginners. We systematically analyze architectural components spanning cloud, edge, and terminal layers, examining core technologies including network virtualization, container orchestration, and software-defined networking, while presenting categorizations of collaboration paradigms that cover task offloading, resource allocation, and optimization across heterogeneous infrastructures. Furthermore, we explain intelligent collaboration learning frameworks by reviewing advances in federated learning, distributed deep learning, edge-cloud model evolution, and reinforcement learning-based methods. Finally, we discuss challenges (e.g., scalability, heterogeneity, interoperability) and future trends (e.g., 6G+, agents, quantum computing, digital twin), highlighting how integration of distributed computing and communication can address open issues and guide development of robust, efficient, and secure collaborative AIoT systems.

## 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.

## How Red Hat OpenShift console connects virtual machines to the networks they use

DevFeed: [How Red Hat OpenShift console connects virtual machines to the networks they use](<https://devfeed.tech/articles/how-red-hat-openshift-console-connects-virtual-machines-to-the-networks-they-use-135989.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/how-red-hat-openshift-console-connects-virtual-machines-networks-they-use>)

Author: Allison Wolfe; Kevin Hatchoua

Published: 2026-11-16T00:00:00Z

Content type: article

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [backend](<https://devfeed.tech/tags/backend.md>), [console](<https://devfeed.tech/tags/console.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-networking](<https://devfeed.tech/tags/kubernetes-networking.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [networks](<https://devfeed.tech/tags/networks.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openshift-virtualization](<https://devfeed.tech/tags/openshift-virtualization.md>), [red-hat-openshift-virtualization](<https://devfeed.tech/tags/red-hat-openshift-virtualization.md>), [virtual-machines](<https://devfeed.tech/tags/virtual-machines.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>), [vm](<https://devfeed.tech/tags/vm.md>), [web](<https://devfeed.tech/tags/web.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

OpenShift Virtualization 5 and later adds console navigation for tracing VM network connections and checking service and route health. From a VM's Configuration -> Network tab or Overview interface list, secondary network links open the NAD, UDN, or CUDN details; those pages' Virtual Machines tab lists attached VMs, their namespace, status, and interface, and supports attaching or detaching them without deleting the VM. The Services -> Create Service page offers guided Form view fields for service type, ports, and matching pods, alongside YAML view for manual edits or API fields absent from the form. Services and Routes lists show ready endpoints over total. The article illustrates using health and selectors to investigate missing service backends, or network attachment pages to check whether another VM shares a secondary network. These console features build on the 4.21 networking workflows and require version 5 or later.

### Source excerpt

In Red Hat OpenShift Virtualization 4.21, we shipped networking workflows that simplify how you create and connect virtual machine (VM) networks. In OpenShift Virtualization 5, the web console builds on those workflows--the same Kubernetes networking model, with clickable paths on pages you already use.Which network is this VM on? Which VMs use this network? These new features answer those questions on the pages you already live in when something breaks at 2 AM.Building on the OpenShift Virtualization 4.21 foundationThis post builds on the VM networking workflows introduced in OpenShift Virtu

## 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.

## One Stack, Full VCF: Deploying VMware Cloud Foundation 9 on Amazon EVS with the EVS Deployment Orchestrator

DevFeed: [One Stack, Full VCF: Deploying VMware Cloud Foundation 9 on Amazon EVS with the EVS Deployment Orchestrator](<https://devfeed.tech/articles/one-stack-full-vcf-deploying-vmware-cloud-foundation-9-on-amazon-evs-with-the-evs-deployment-orchestrator-133510.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/migration-and-modernization/one-stack-full-vcf-deploying-vmware-cloud-foundation-9-on-amazon-evs-with-the-evs-deployment-orchestrator/>)

Author: David Piet, Ph.D.

Published: 2026-11-13T16:25:51Z

Content type: tutorial

Language: en

Sources: [Migration & Modernization](<https://devfeed.tech/sources/migration-modernization.md>)

Topics: [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>)

Tags: [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-elastic-vmware-service-amazon-evs](<https://devfeed.tech/tags/amazon-elastic-vmware-service-amazon-evs.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws-for-vmware](<https://devfeed.tech/tags/aws-for-vmware.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [compute](<https://devfeed.tech/tags/compute.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [evs](<https://devfeed.tech/tags/evs.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [full](<https://devfeed.tech/tags/full.md>), [one](<https://devfeed.tech/tags/one.md>), [orchestrator](<https://devfeed.tech/tags/orchestrator.md>), [repository](<https://devfeed.tech/tags/repository.md>), [service](<https://devfeed.tech/tags/service.md>), [solutions](<https://devfeed.tech/tags/solutions.md>), [stack](<https://devfeed.tech/tags/stack.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [this](<https://devfeed.tech/tags/this.md>), [thought-leadership](<https://devfeed.tech/tags/thought-leadership.md>), [vcf](<https://devfeed.tech/tags/vcf.md>), [vmware](<https://devfeed.tech/tags/vmware.md>), [vmware-cloud-foundation](<https://devfeed.tech/tags/vmware-cloud-foundation.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The open source EVS Deployment Orchestrator (EDO) uses AWS CloudFormation to automate VCF 9.x deployment on Amazon EVS from a YAML blueprint. It provisions networking, EVS bare-metal ESXi hosts, VCF appliances, and an NSX edge cluster; runs unattended in about 4-7 hours, with hosts typically online and billing starting around 50 minutes in. Before launch, users need an AWS account with Business or Enterprise Support, a Broadcom depot token, a matching VCF SDDC Manager OVA, VMware ovftool, and Git; CLI users also need AWS CLI v2 and Python 3.9 or later. The blueprint controls sizing and options: simple mode uses single NSX Manager and VCF Operations nodes, while HA mode requires at least four hosts and larger Operations appliance sizing. EDO validates configuration and quotas, checkpoints nine stages for resume, and stores appliance credentials in Secrets Manager. Optional settings enable HCX with a public /28 and three Elastic IPs, or a Windows jumpbox for private UI access. A quota preflight is recommended; teardown can remove only the environment or also its supporting infrastructure.

### Source excerpt

Earlier this year we walked through deploying VCF 9 on Amazon Elastic VMware Service (Amazon EVS) using a phased automation workflow. Since then, we've improved and streamlined that automation into the EVS Deployment Orchestrator (EDO), now available in the solutions-for-amazon-evs repository. EDO is a tool that automates an end-to-end VMware Cloud Foundation (VCF) 9.x deployment [...]

## Build composable, interoperable multi-agent systems with A2A on AWS

DevFeed: [Build composable, interoperable multi-agent systems with A2A on AWS](<https://devfeed.tech/articles/build-composable-interoperable-multi-agent-systems-with-a2a-on-aws-130561.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/build-composable-interoperable-multi-agent-systems-with-a2a-on-aws/>)

Author: Amit Chaudhary

Published: 2026-11-12T15:42:21Z

Content type: article

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [A2A protocol](<https://devfeed.tech/topics/a2a-protocol.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [supervisor agent pattern](<https://devfeed.tech/topics/supervisor-agent-pattern.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>)

Tags: [a2a](<https://devfeed.tech/tags/a2a.md>), [a2a-protocol](<https://devfeed.tech/tags/a2a-protocol.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [bedrock-agentcore](<https://devfeed.tech/tags/bedrock-agentcore.md>), [build](<https://devfeed.tech/tags/build.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [framework](<https://devfeed.tech/tags/framework.md>), [langchain](<https://devfeed.tech/tags/langchain.md>), [multi-agent](<https://devfeed.tech/tags/multi-agent.md>), [multi-agent-system](<https://devfeed.tech/tags/multi-agent-system.md>), [multi-agent-systems](<https://devfeed.tech/tags/multi-agent-systems.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [systems](<https://devfeed.tech/tags/systems.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The reference architecture shows cross-organization agents collaborating through A2A without sharing secrets or depending on each other's framework: a LangChain orchestrator on ECS calls a Strands compliance agent on Bedrock AgentCore, which calls back to an enterprise context agent for account metadata. Agent Cards expose curated skills for discovery and routing; OAuth JWTs from separate Cognito user pools authenticate calls in both directions. The deployment uses three Jupyter notebooks across two AWS accounts, with synthetic compliance findings, an end-to-end test, and token rejection checks. The sample requires specified AWS accounts, model access and Jupyter setup, incurs resource charges, and is intended for sandbox use; production adaptations are outlined, including stronger client authentication and private connectivity.

### Source excerpt

Build a composable, interoperable multi-agent system on AWS with the Agent-to-Agent (A2A) protocol. A LangChain orchestrator on Amazon ECS communicates with a Strands agent on Amazon Bedrock AgentCore across organizational boundaries, using bidirectional, OAuth-authenticated calls, with neither side depending on the other's framework or SDK.

## A Single Branch No Longer Operates in A Single Place

DevFeed: [A Single Branch No Longer Operates in A Single Place](<https://devfeed.tech/articles/a-single-branch-no-longer-operates-in-a-single-place-130890.md>)

Original publisher: [Read original article](<https://blog.checkpoint.com/security/a-single-branch-no-longer-operates-in-a-single-place/>)

Author: raphaelge@checkpoint.com

Published: 2026-11-12T13:00:26Z

Content type: article

Language: en

Sources: [Check Point Blog](<https://devfeed.tech/sources/check-point-blog.md>)

Topics: [Endpoint security](<https://devfeed.tech/topics/endpoint-security.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [security service edge](<https://devfeed.tech/topics/security-service-edge.md>), [smartdevices](<https://devfeed.tech/topics/smartdevices.md>), [Internet](<https://devfeed.tech/topics/internet.md>), [The Three Main Cloud Service Models](<https://devfeed.tech/topics/the-three-main-cloud-service-models.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [applications](<https://devfeed.tech/tags/applications.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [branch](<https://devfeed.tech/tags/branch.md>), [branch-security](<https://devfeed.tech/tags/branch-security.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [complex](<https://devfeed.tech/tags/complex.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [data-centers](<https://devfeed.tech/tags/data-centers.md>), [devices](<https://devfeed.tech/tags/devices.md>), [employees](<https://devfeed.tech/tags/employees.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [has](<https://devfeed.tech/tags/has.md>), [hybrid-mesh](<https://devfeed.tech/tags/hybrid-mesh.md>), [hybrid-mesh-network-security](<https://devfeed.tech/tags/hybrid-mesh-network-security.md>), [internet](<https://devfeed.tech/tags/internet.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [saas](<https://devfeed.tech/tags/saas.md>), [sd-wan](<https://devfeed.tech/tags/sd-wan.md>), [security](<https://devfeed.tech/tags/security.md>), [threat-prevention](<https://devfeed.tech/tags/threat-prevention.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

Modern branches connect directly to SaaS, cloud, data centers, the internet, and other sites, while supporting demanding applications and connected devices--often without on-site security staff. The text says SD-WAN can steer traffic by application, policy, and real-time network conditions, and move it to a healthier link when a connection degrades or fails; firewall clustering and hardware redundancy address additional failure points. Local inspection and protection are needed as direct internet access and IoT devices broaden the attack surface. The article also calls for visibility and policy controls over employee AI use, including preventing sensitive data from being shared in prompts. Centralized policy, zero-touch provisioning, health monitoring, and unified visibility can simplify management across many branches. Check Point presents its firewall and SD-WAN, AI controls, centralized management, and SASE integration as an approach; hybrid SASE can combine cloud security for remote users with on-premises SD-WAN and firewall protection for office users.

### Source excerpt

Branch Traffic Has Changed. Security Has to Follow. A traditional branch was simple in nature: a location that connects back to headquarters where applications, data, and security controls were housed. Today the landscape is wildly different. A branch may connect directly to SaaS apps, clouds, data centers, the open internet, and other locations within the enterprise. And while all those connections are being made, often many at one time, employees expect video calls and cloud applications to perform just as well in the office as they do at home. The branch itself has become more complex, too. Connected devices can [...] The post A Single Branch No Longer Operates in A Single Place appeared first on Check Point Blog.

## A Risk in the Clouds: NetClaw on GCP

DevFeed: [A Risk in the Clouds: NetClaw on GCP](<https://devfeed.tech/articles/a-risk-in-the-clouds-netclaw-on-gcp-131812.md>)

Original publisher: [Read original article](<https://automateyournetwork.com/netclaw/netclaw-on-gcp/>)

Author: John Capobianco

Published: 2026-11-12T12:00:00Z

Content type: article

Language: en

Sources: [Automate Your Network](<https://devfeed.tech/sources/automate-your-network.md>)

Topics: [experience report](<https://devfeed.tech/topics/experience-report.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Ollama](<https://devfeed.tech/topics/ollama.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [1-3](<https://devfeed.tech/tags/1-3.md>), [17](<https://devfeed.tech/tags/17.md>), [2](<https://devfeed.tech/tags/2.md>), [22](<https://devfeed.tech/tags/22.md>), [3](<https://devfeed.tech/tags/3.md>), [ai](<https://devfeed.tech/tags/ai.md>), [article](<https://devfeed.tech/tags/article.md>), [border](<https://devfeed.tech/tags/border.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [full](<https://devfeed.tech/tags/full.md>), [gcp](<https://devfeed.tech/tags/gcp.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [ha](<https://devfeed.tech/tags/ha.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [live](<https://devfeed.tech/tags/live.md>), [members](<https://devfeed.tech/tags/members.md>), [netclaw](<https://devfeed.tech/tags/netclaw.md>), [network-automation](<https://devfeed.tech/tags/network-automation.md>), [one](<https://devfeed.tech/tags/one.md>), [openshell](<https://devfeed.tech/tags/openshell.md>), [region](<https://devfeed.tech/tags/region.md>), [risk](<https://devfeed.tech/tags/risk.md>), [teardown](<https://devfeed.tech/tags/teardown.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The article reports that NetClaw Borders and Members ran in GCP, on-premises, hybrid setups, and a live three-region Risk, but warns the system is not production-ready because Border URLs have no authentication: anyone with one can use the HUD and Chat and spend the model API key. In the tested design, Members dial out to Borders; multiple Borders share one execution authority, and loss of quorum blocks new protected work rather than authorizing duplicate execution. Multi-region tests exposed latency-sensitive admission windows, slow failover, and a distant two-region quorum that could not admit work. OpenShell with DefenseClaw added audited blocking and sandbox isolation, with measured overhead below half a percent of the 4,500 ms admission window, though one leadership timing issue remained unexplained. The tested workloads were read-only. The article recommends experimenting in a throwaway GCP project, setting budget alerts (which do not cap spending), keeping Border URLs private, and fully deleting resources afterward. Users, SSO, and RBAC are roadmap work, not current features.

### Source excerpt

From one Border to a three-region Risk: the full NetClaw on GCP story, R01-R09C, with cloud and hybrid Members, HA, OpenShell, DefenseClaw, live evidence and lessons from teardown.

## Refresh a single tenant across accounts with Aurora MySQL and Amazon S3

DevFeed: [Refresh a single tenant across accounts with Aurora MySQL and Amazon S3](<https://devfeed.tech/articles/refresh-a-single-tenant-across-accounts-with-aurora-mysql-and-amazon-s3-129589.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/refresh-a-single-tenant-across-accounts-with-aurora-mysql-and-amazon-s3/>)

Author: Mansi Panchal

Published: 2026-11-11T22:08:37Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [etl](<https://devfeed.tech/topics/etl.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Resource Access Manager (RAM)](<https://devfeed.tech/topics/resource-access-manager-ram.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [data](<https://devfeed.tech/tags/data.md>), [encrypted](<https://devfeed.tech/tags/encrypted.md>), [load](<https://devfeed.tech/tags/load.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [network](<https://devfeed.tech/tags/network.md>), [refresh](<https://devfeed.tech/tags/refresh.md>), [route](<https://devfeed.tech/tags/route.md>), [s3](<https://devfeed.tech/tags/s3.md>), [select](<https://devfeed.tech/tags/select.md>), [separate](<https://devfeed.tech/tags/separate.md>), [staging](<https://devfeed.tech/tags/staging.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [using](<https://devfeed.tech/tags/using.md>)

### AI overview

The article describes refreshing one tenant in an existing non-production Aurora MySQL cluster without a network route between AWS accounts. A production-side copy-on-write clone exports tenant-scoped table data to a shared, encrypted S3 staging bucket; the non-production cluster imports the per-table manifests through its own S3 gateway endpoint. Cross-account access relies on IAM and bucket policies plus a production-account customer-managed KMS key, with no database connection between clusters. The workflow requires matching destination schemas, tenant-ID indexes, careful classification of tenant-scoped, tenant-derived, and shared tables, and tenant-only deletion before import. Per-table parallelism and retries limit the impact of failures, but exports are uncompressed and do not parallelize within a table, so the largest table can determine refresh time. The excerpt also notes key-collision risks, production-data handling requirements, and that this pattern is for a single tenant rather than a whole-cluster copy.

### Source excerpt

Move a single tenant's data between Amazon Aurora MySQL clusters in two separate AWS accounts with no network route between them, using Aurora cloning, SELECT INTO OUTFILE S3, and LOAD DATA FROM S3. The clusters never connect, and one encrypted Amazon S3 staging bucket is their only shared touchpoint.

## Build a multi-team AI and analytics environment on Amazon SageMaker Unified Studio with Terraform

DevFeed: [Build a multi-team AI and analytics environment on Amazon SageMaker Unified Studio with Terraform](<https://devfeed.tech/articles/build-a-multi-team-ai-and-analytics-environment-on-amazon-sagemaker-unified-studio-with-terraform-129559.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/build-a-multi-team-ai-and-analytics-environment-on-amazon-sagemaker-unified-studio-with-terraform/>)

Author: Harshi Surampalli

Published: 2026-11-11T19:58:49Z

Content type: article

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-sagemaker](<https://devfeed.tech/tags/amazon-sagemaker.md>), [amazon-sagemaker-unified-studio](<https://devfeed.tech/tags/amazon-sagemaker-unified-studio.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [apply](<https://devfeed.tech/tags/apply.md>), [blueprints](<https://devfeed.tech/tags/blueprints.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [data](<https://devfeed.tech/tags/data.md>), [data-analytics](<https://devfeed.tech/tags/data-analytics.md>), [domains](<https://devfeed.tech/tags/domains.md>), [environment](<https://devfeed.tech/tags/environment.md>), [generative](<https://devfeed.tech/tags/generative.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [governance](<https://devfeed.tech/tags/governance.md>), [studio](<https://devfeed.tech/tags/studio.md>), [team](<https://devfeed.tech/tags/team.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The Terraform module provisions a shared, governed Amazon SageMaker Unified Studio domain with team-specific project profiles for analytics, machine learning, and generative AI. It combines AWS and AWS Cloud Control providers, enables selected blueprints, and can create least-privilege service roles or use supplied roles; network settings can default to discovery of the default VPC and subnets. The walkthrough requires Terraform 1.7 or later, AWS credentials with resource-management permissions, and Unified Studio in the target Region; IAM Identity Center is needed only for SSO membership. One apply creates the domain, profiles, and an initial project, while further team projects require additional project module blocks or portal creation. Membership supports SSO users and groups plus same-account IAM users and roles. IAM principals need SageMakerStudioUserIAMConsolePolicy or equivalent, which the module does not attach; cross-account role access may be limited and should be verified for the Region. Costs mainly arise from using Redshift Serverless, EMR Serverless, Bedrock, and S3.

### Source excerpt

Learn how to use the Amazon SageMaker Unified Studio Terraform module to provision a multi-team AI and analytics platform (domains, blueprints, project profiles, and projects) for data analytics, machine learning, and generative AI teams in a single terraform apply, with shared governance and least-privilege security defined entirely as code.

## Using mathematics to validate network configurations

DevFeed: [Using mathematics to validate network configurations](<https://devfeed.tech/articles/using-mathematics-to-validate-network-configurations-129658.md>)

Original publisher: [Read original article](<https://www.amazon.science/blog/using-mathematics-to-validate-network-configurations>)

Author: Dan DaCosta

Published: 2026-11-11T17:02:01Z

Content type: article

Language: en

Sources: [Amazon Science homepage](<https://devfeed.tech/sources/amazon-science-homepage.md>)

Topics: [Network Segmentation](<https://devfeed.tech/topics/network-segmentation.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [network security](<https://devfeed.tech/topics/network-security.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>)

Tags: [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [automated-reasoning](<https://devfeed.tech/tags/automated-reasoning.md>), [aws-cloud-wan](<https://devfeed.tech/tags/aws-cloud-wan.md>), [data](<https://devfeed.tech/tags/data.md>), [data-leaks](<https://devfeed.tech/tags/data-leaks.md>), [formal-methods](<https://devfeed.tech/tags/formal-methods.md>), [global](<https://devfeed.tech/tags/global.md>), [mathematics](<https://devfeed.tech/tags/mathematics.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [networks](<https://devfeed.tech/tags/networks.md>), [partitions](<https://devfeed.tech/tags/partitions.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [risk](<https://devfeed.tech/tags/risk.md>), [scale](<https://devfeed.tech/tags/scale.md>), [security](<https://devfeed.tech/tags/security.md>), [sensitive-data](<https://devfeed.tech/tags/sensitive-data.md>), [static](<https://devfeed.tech/tags/static.md>), [static-analysis](<https://devfeed.tech/tags/static-analysis.md>)

### AI overview

Tiros validates AWS Cloud WAN segmentation by converting route tables, attachments, and policy documents into logical propositions, then checking modeled reachability across all paths rather than sampling packet traffic. It tests whether paths exist between attachments and destination IPs that policy says should be isolated; mismatches alert an operator. The method can be run as frequently as hourly and checks the modeled topology against isolation specifications. In the example, it verifies that production and development VPCs remain separate even when they share an address space. This is static analysis of the supplied configuration, and its assurance is about whether that model matches policy. The text distinguishes this from AWS reachability services, which determine whether a valid request path exists between resources; Tiros also uses reachability analysis to establish when paths are absent.

### Source excerpt

Static analysis of deployed networks helps reduce the risk that sensitive data leaks across partitions, supporting the security and reliability of global-scale networking.

## Digital sovereignty at re:Invent 2026: Sessions you won't want to miss

DevFeed: [Digital sovereignty at re:Invent 2026: Sessions you won't want to miss](<https://devfeed.tech/articles/digital-sovereignty-at-re-invent-2026-sessions-you-won-t-want-to-miss-127776.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/digital-sovereignty-at-reinvent-2026-sessions-you-wont-want-to-miss/>)

Author: Baqir Naqvi

Published: 2026-11-10T18:10:41Z

Content type: article

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Developer Events](<https://devfeed.tech/topics/developer-events.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [AWS Outposts](<https://devfeed.tech/topics/aws-outposts.md>), [AWS Local Zones](<https://devfeed.tech/topics/aws-local-zones.md>), [cloud-migration](<https://devfeed.tech/topics/cloud-migration.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [AWS Trainium](<https://devfeed.tech/topics/aws-trainium.md>), [3D](<https://devfeed.tech/topics/3d.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-digital-sovereignty-pledge](<https://devfeed.tech/tags/aws-digital-sovereignty-pledge.md>), [aws-re-invent](<https://devfeed.tech/tags/aws-re-invent.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [customers](<https://devfeed.tech/tags/customers.md>), [digital](<https://devfeed.tech/tags/digital.md>), [digital-sovereignty](<https://devfeed.tech/tags/digital-sovereignty.md>), [eu-data-protection](<https://devfeed.tech/tags/eu-data-protection.md>), [europe](<https://devfeed.tech/tags/europe.md>), [european-union](<https://devfeed.tech/tags/european-union.md>), [events](<https://devfeed.tech/tags/events.md>), [experts](<https://devfeed.tech/tags/experts.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [over](<https://devfeed.tech/tags/over.md>), [partners](<https://devfeed.tech/tags/partners.md>), [re-invent](<https://devfeed.tech/tags/re-invent.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [sovereignty](<https://devfeed.tech/tags/sovereignty.md>), [want](<https://devfeed.tech/tags/want.md>)

### AI overview

The guide groups re:Invent 2026 digital sovereignty sessions into five themes: AWS European Sovereign Cloud controls and operational autonomy; AI placement under data residency and latency needs; hybrid infrastructure choices and migration; disaster recovery and cross-partition connectivity; and industry use cases. Described options include AWS AI Factories for on-premises AI infrastructure, Local Zones and Outposts for hybrid or edge workloads, and Regions or Dedicated Local Zones. Sessions cover governance controls, detecting unauthorized data flows, recovery patterns, migration lessons, and connectivity across AWS partitions. A telecom session offers a workload-placement framework based on latency, data gravity, sovereignty, and token economics; other examples include government GenAI tokenization and in-country seismic processing. Attendees are advised to reserve seats, check alternate session times if full, allow travel time between venues, and verify schedule changes in the catalog. The text is a session guide, not a comparative evaluation of the offerings.

### Source excerpt

AWS re:Invent returns to Las Vegas for cloud and AI's biggest week from November 30-December 4, 2026. This year we have over 2,200 sessions, 70 percent of which are interactive, led by experts from Amazon Web Services (AWS), our customers, and our partners. With that much to choose from, we've pulled together the sessions built [...]

## The next era of hybrid cloud: Introducing Red Hat OpenShift 5

DevFeed: [The next era of hybrid cloud: Introducing Red Hat OpenShift 5](<https://devfeed.tech/articles/the-next-era-of-hybrid-cloud-introducing-red-hat-openshift-5-126518.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/next-era-hybrid-cloud-introducing-red-hat-openshift-5>)

Author: Mike Barrett

Published: 2026-11-10T00:00:00Z

Content type: release

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [redhat](<https://devfeed.tech/topics/redhat.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [it modernization](<https://devfeed.tech/topics/it-modernization.md>), [rhel](<https://devfeed.tech/topics/rhel.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application-platform](<https://devfeed.tech/tags/application-platform.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [community](<https://devfeed.tech/tags/community.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [customers](<https://devfeed.tech/tags/customers.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [hybrid-cloud](<https://devfeed.tech/tags/hybrid-cloud.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openshift-5](<https://devfeed.tech/tags/openshift-5.md>), [operational](<https://devfeed.tech/tags/operational.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [red-hat-openshift-5](<https://devfeed.tech/tags/red-hat-openshift-5.md>), [virtual-machines](<https://devfeed.tech/tags/virtual-machines.md>)

### AI overview

Red Hat presents OpenShift 5 as a hybrid workload platform for VMs, containers, and AI, with features aimed at operations, security, and lifecycle predictability. Optional AI experiences include chat-generated dashboards, event-based remediation suggestions, cluster-specific upgrade plans, and CVE remediation through an Advanced Cluster Security MCP server; administrators can review or modify upgrade plans. Red Hat says these features can connect to on-premises or SaaS model endpoints. Security additions include post-quantum controls for control-plane communications, SPIFFE/SPIRE workload identity, and network isolation options for multi-tenant environments. Standard support expands from 18 months to two years, with yearly Extended Lifecycle releases offering up to five years total support for minor releases. Red Hat says OpenShift 4-to-5 upgrades use in-place updates, preserve major APIs, and can mix RHEL CoreOS 9 and 10 nodes during transition; pre-flight checks and AI suggestions support later 5.x updates, with human review in remediation.

### Source excerpt

Yesterday at OpenShift Commons in Salt Lake City, I announced a major milestone for our community: the next evolution of our application platform with Red Hat OpenShift 5.If you go back to Red Hat Summit earlier this year, I talked about how IT teams face accelerating operational complexity. Over the past year, I've spent time with our customers, open source contributors, and technology partners discussing how they see platform technologies changing to meet those operational complexities. I've heard directly from platform engineers working with thousands of legacy virtual machines (VMs), c

[Next page](<https://devfeed.tech/topics/cloud-networking.md?cursor=WyIyMDI2LTExLTEwVDAwOjAwOjAwKzAwOjAwIiwgIjExYWJlNjk5LWZjNjctNDkyYy05YjZkLWMwNTI4MGU3YzY4MyJd>)