# VPC Published articles for VPC. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How AWS Lambda logs every flow across thousands of microVMs per host with eBPF and Rust DevFeed: [How AWS Lambda logs every flow across thousands of microVMs per host with eBPF and Rust]() Original publisher: [Read original article]() Author: Prashant Kumar Singh Published: 2026-09-11T12:00:00Z Content type: article Language: en Sources: [The New Stack]() Topics: [AWS Lambda](), [Architecture & Design](), [SIEM, Security, Observability](), [telemetry](), [Amazon EC2](), [Amazon S3](), [VPC]() Tags: [architecture](), [aws](), [aws-lambda](), [aws-marketplace](), [compliance](), [ebpf](), [firecracker](), [incident](), [incident-response](), [logs](), [monitoring](), [observability](), [post-contributed](), [rust](), [s3](), [scale](), [security](), [server](), [serverless](), [sponsor-aws-marketplace](), [sponsored-post-contributed](), [vpc]() ### AI overview AWS Lambda describes replacing an aging network-capture system with an eBPF and Rust pipeline that records network flows across short-lived, tenant-isolated microVMs. The system prioritizes complete, correctly attributed records with minimal overhead for security investigation, metering, audit, observability, and monitoring. ### Source excerpt On any compute platform, when a security alert fires, the question is always the same. Which workload talked to that The post How AWS Lambda logs every flow across thousands of microVMs per host with eBPF and Rust appeared first on The New Stack. ## Model-agnostic PII detection with LLMs DevFeed: [Model-agnostic PII detection with LLMs]() Original publisher: [Read original article]() Author: Christophe Dupuy Published: 2026-09-10T16:02:16Z Content type: tutorial Language: en Sources: [Artificial Intelligence]() Topics: [AI Chat]() Tags: [advanced-300](), [amazon-bedrock](), [benchmark](), [fine-tuning](), [inference](), [large-language-models-llms](), [llms](), [pii](), [security](), [technical-how-to](), [vpc]() ### AI overview A tutorial on building a configurable, model-agnostic PII detector with large language models. It explains prompt-based entity configuration, implementation, benchmarking, and running the detector on custom data. ### Source excerpt A configurable, model-agnostic detector that turns any large language model on Amazon Bedrock into a PII detector. Because the entities to detect live in a prompt rather than in code, one detector adapts to new entity types without retraining, and it outperforms an off-the-shelf tool across five public corpora and nine LLM-based detectors. ## Tailscale Kubernetes Operator 1.102: In-cluster Peer Relays, better IPv6, and optimized certificates DevFeed: [Tailscale Kubernetes Operator 1.102: In-cluster Peer Relays, better IPv6, and optimized certificates]() Original publisher: [Read original article]() Author: Mike Stefaniak Published: 2026-09-09T14:00:00Z Content type: release Language: en Sources: [Blog on Tailscale]() Topics: [Kubernetes](), [networking](), [VPC]() Tags: [kubernetes](), [networks](), [release](), [routing](), [vpc]() ### AI overview Tailscale Kubernetes Operator 1.102 adds in-cluster peer relays, improves IPv6 connectivity support, and reduces certificate-related deployment and connectivity issues. ### Source excerpt Faster cross-cluster connections, fewer IPv6 dead ends, less certificate churn. ## Extend your data perimeter to the AWS Management Console with Private Access DevFeed: [Extend your data perimeter to the AWS Management Console with Private Access]() Original publisher: [Read original article]() Author: Madhur Kulkarni Published: 2026-08-28T18:53:57Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [AWS Management Console](), [VPC](), [network security](), [Authentication](), [Amazon Web Services](), [Virtual Private Network](), [Amazon EC2](), [Amazon WorkSpaces]() Tags: [advanced-300](), [authentication](), [aws](), [aws-management-console](), [aws-organizations](), [iam](), [network](), [network-security](), [private-access](), [routing](), [security](), [security-blog](), [security-identity-compliance](), [technical-how-to](), [vpc]() ### AI overview AWS Management Console Private Access is generally available with support for VPCs without internet connectivity. Supported console traffic, including authentication flows, static assets, console-only APIs, and AWS service API calls, can route through VPC endpoints, eliminating the need for an internet gateway, NAT gateway, or public-internet route. ### Source excerpt Organizations in regulated industries such as financial services, government, defense, and healthcare restrict their sensitive workloads to isolated network environments with no access to the public internet. Until now, customers could restrict AWS Management Console access to authorized AWS accounts and corporate networks, but the console itself required internet connectivity. This was creating tension between [...] ## Encrypt Amazon ECS traffic: VPC encryption controls and Service Connect TLS DevFeed: [Encrypt Amazon ECS traffic: VPC encryption controls and Service Connect TLS]() Original publisher: [Read original article]() Author: Simone Tallevi-Diotallevi Published: 2026-08-19T20:37:56Z Content type: tutorial Language: en Sources: [Containers]() Topics: [Cryptography]() Tags: [advanced-300](), [amazon-elastic-container-service](), [amazon-vpc](), [aws](), [aws-fargate](), [containers](), [encryption](), [how-to](), [logs](), [nitro-system](), [security](), [technical-how-to](), [tls](), [vpc](), [vpc-flow-logs]() ### AI overview A hands-on guide to encrypting traffic between Amazon ECS workloads with VPC encryption controls or Service Connect TLS. It covers activation on AWS Fargate and verification through VPC Flow Logs. ### Source excerpt Learn how to encrypt traffic between Amazon ECS workloads using two native approaches: VPC encryption controls for network-layer encryption through the AWS Nitro System, and Service Connect TLS for application-layer encryption. A hands-on walkthrough shows how to activate encryption on AWS Fargate and verify it in VPC Flow Logs. ## Deploying IPv6-first EKS on AWS: What Still Doesn't Work, and What It Saves DevFeed: [Deploying IPv6-first EKS on AWS: What Still Doesn't Work, and What It Saves]() Original publisher: [Read original article]() Author: Spiro Stathakis Published: 2026-08-14T08:57:28Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Amazon Elastic Kubernetes Service](), [Amazon Web Services](), [VPC](), [networking](), [cloud-infrastructure](), [Kubernetes]() Tags: [2026](), [amazon](), [amazon-elastic-kubernetes-service](), [aws](), [cni](), [competition](), [cost](), [ip](), [ipv4](), [ipv6](), [kubernetes](), [nat](), [networking](), [networks](), [vpc]() ### AI overview A field report on deploying an IPv6-first Amazon Elastic Kubernetes Service platform on AWS. It explains how IPv6 pods, VPC networking, and an egress-only Internet gateway reduce dependence on NAT gateways and public IPv4 addresses, while legacy IPv4-only dependencies such as databases, payment APIs, and container registries still impose compatibility requirements and costs. ### Source excerpt In this field report on IPv6-first Amazon Elastic Kubernetes Service (EKS), the isp6 team shares which dependencies still drag IPv4 back in, what they learnt from /28s, and why the saving is large but not automatic. ## Best Kubernetes Infrastructure as Code Tools in 2026 DevFeed: [Best Kubernetes Infrastructure as Code Tools in 2026]() Original publisher: [Read original article]() Author: Pulumi Content Team Published: 2026-08-14T00:00:00Z Content type: comparison Language: en Sources: [Pulumi]() Topics: [Infrastructure as code](), [Kubernetes](), [Terraform](), [argo-cd](), [Helm charts](), [GitOps](), [flux](), [opentofu](), [Amazon EKS](), [AWS CloudFormation](), [VPC](), [AWS IAM]() Tags: [argo-cd](), [cloudformation](), [code](), [comparisons](), [devops](), [flux](), [general](), [gitops](), [helm](), [helm-charts](), [iam](), [infrastructure](), [infrastructure-as-code](), [kubernetes](), [opentofu](), [platform-engineering](), [terraform](), [vpc]() ### AI overview This comparison explains that Kubernetes infrastructure as code spans cluster and cloud provisioning, in-cluster workload definition, and continuous delivery and reconciliation. It presents Pulumi and Terraform or OpenTofu as general-purpose provisioning options, Helm and Kustomize for workload templating, and Argo CD and Flux for GitOps reconciliation. ### Source excerpt There is no single best Kubernetes infrastructure as code tool, because "Kubernetes IaC" actually spans three different jobs. For provisioning the cluster and its cloud dependencies, Pulumi and Terraform (or OpenTofu) are the strongest general-purpose options. For templating and packaging workloads, Helm and Kustomize dominate. For continuous reconciliation once things are running, Argo CD and Flux lead the GitOps category. The right stack usually combines one tool from each layer, not a single tool that claims to do all three. What counts as infrastructure as code for Kubernetes? Kubernetes infrastructure as code work splits into three layers that get conflated constantly, and the confusion is where most tool comparisons go wrong. The cluster and cloud layer provisions the things Kubernetes itself sits on top of: the managed control plane (EKS, GKE, AKS), node pools, the VPC and subnets, IAM roles, load balancers, and cluster add-ons. Terraform, Pulumi, and cloud-native tools like CloudFormation operate here. The in-cluster workload layer defines what runs on the cluster once it exists: Deployments, Services, ConfigMaps, CustomResourceDefinitions, and the Helm charts or Kustomize overlays that template them. This is where Helm, Kustomize, and Crossplane's custom resources live. The delivery and reconciliation layer keeps what's declared in Git in sync with what's actually running on the cluster, continuously, rather than as a one-shot apply. Argo CD and Flux own this layer, and they consume the output of the other two rather than replacing them. Most real Kubernetes platforms use tools from at least two of these layers together. A team might provision EKS with Terraform, package its application with Helm, and let Argo CD reconcile it continuously. Knowing which layer a tool actually addresses, rather than treating "Kubernetes IaC" as one shopping list, is the first decision that matters. Pulumi provisions the cluster and the workloads on it in the same language Pul ## Neon Functions: backend logic next to your data DevFeed: [Neon Functions: backend logic next to your data]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2026-08-12T12:00:00Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Back end](), [Node.js](), [Database](), [Serverless](), [WebSocket](), [Cloud]() Tags: [backend](), [database](), [hosting](), [network](), [node](), [node-js](), [product](), [serverless](), [vpc]() ### AI overview Neon Functions provide long-running Node.js 24 backend compute deployed beside a Neon Postgres branch. They automatically receive database and related Neon service credentials, reducing network hops and supporting streaming, WebSockets, SSE, and persistent connection pools. ### Source excerpt Neon Functions are Node.js 24 compute you deploy onto a Neon branch, in the same region as your Lakebase Postgres database, with DATABASE_URL injected automatically. They're long-running enough that agents can stream for minutes and WebSockets or SSE can stay open while data flows. ## A decade of mathematical certainty: Reflections on the Automated Reasoning Group DevFeed: [A decade of mathematical certainty: Reflections on the Automated Reasoning Group]() Original publisher: [Read original article]() Author: Byron Cook Published: 2026-08-11T16:22:19Z Content type: article Language: en Sources: [Amazon Science homepage]() Topics: [Automated reasoning](), [Formal verification](), [Math and Logic](), [systems](), [Amazon Web Services](), [VPC](), [network security](), [Security](), [AWS IAM](), [Amazon S3](), [Cloud](), [amazon]() Tags: [agentic-ai](), [amazon](), [amazon-web-services-aws](), [automated-reasoning](), [aws](), [compliance](), [formal-verification](), [network-security](), [security](), [security-privacy-and-abuse-prevention](), [vpc](), [vulnerabilities]() ### AI overview Amazon's Automated Reasoning Group reflects on a decade of applying mathematical logic, formal verification, and program analysis to AWS security and reliability. The article describes how research projects became production systems, including Tiros for VPC and network analysis and Zelkova for analyzing policies, S3 Block Public Access, and IAM Access Analyzer. ### Source excerpt Ten years after we founded the Automated Reasoning Group, mathematical logic has moved from academic research into production services that secure millions of customer workloads -- demonstrating that systems can be provably correct, not just probably correct. ## Migrate CloudFormation to Pulumi with Discovered Stacks DevFeed: [Migrate CloudFormation to Pulumi with Discovered Stacks]() Original publisher: [Read original article]() Author: Alejandro Cotroneo Published: 2026-07-30T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Infrastructure as code](), [AWS CloudFormation](), [migration](), [Amazon Web Services](), [VPC](), [Amazon S3](), [DynamoDB](), [AWS IAM]() Tags: [aws](), [cloudformation](), [dynamodb](), [git](), [iac](), [iam](), [import](), [insights](), [kms](), [migration](), [pulumi](), [pulumi-cloud](), [pulumi-neo](), [s3](), [tutorials](), [vpc]() ### AI overview A tutorial shows how to migrate a 61-resource AWS CloudFormation stack to Pulumi using Discovered Stacks in Pulumi Cloud. It explains how to find the stack, review migration status, start the migration, resolve unmatched resources, and verify the result with a zero-diff pulumi preview. ### Source excerpt With Discovered Stacks, Pulumi Cloud does the bookkeeping for a CloudFormation migration: every resource in the stack gets an explicit migration status, and the migration is done when the code provably matches the cloud. In this tutorial, we take one real CloudFormation stack from discovered to migrated and managed by Pulumi IaC, end to end. What we're migrating Our example is payments-api, a CloudFormation stack with 61 resources: a VPC, an Aurora ledger database behind an RDS Proxy, an assets S3 bucket, a DynamoDB ledger table, a Kinesis payment-events pipeline, and the IAM roles, KMS keys, and secrets that wire them together. The plan has five steps: Find the stack in Pulumi Cloud. Review the migration breakdown at a glance. Start the migration. Resolve the stragglers, so every resource is accounted for. Confirm the quality gate: a zero-diff pulumi preview. We'll use Pulumi Neo to do the heavy lifting, but nothing here depends on it. The same flow works with your own coding agent or entirely by hand, because migration status is derived from actual stack state -- however the work gets done, the console shows the same progress. Step 1: Find your stack in Pulumi Cloud Discovered Stacks builds on Discovery, so the only prerequisite is a scanned cloud account -- the AWS account holding your CloudFormation stacks. Once a scan has run, open the Stacks page and turn on Show Discovered Stacks. Your CloudFormation stacks appear alongside your Pulumi stacks. The project name comes from the CloudFormation stack (payments-api), and the stack name encodes the account and region it came from, so the same template deployed to two regions shows up as two distinct discovered stacks. Step 2: Plan the migration at a glance Open the discovered stack's Migration tab. It lays out all 61 resources of payments-api by status, so you can visualize the migration before touching anything: 54 Ready: mapped to a Pulumi type and confirmed to exist -- importable right now. 2 Not found: mapped, but ## Connect OpenSearch to private ML endpoints DevFeed: [Connect OpenSearch to private ML endpoints]() Original publisher: [Read original article]() Author: Nathalie Jonathan Published: 2026-07-28T15:00:41Z Content type: tutorial Language: en Sources: [OpenSearch]() Topics: [Amazon OpenSearch Service](), [network security](), [VPC](), [inference-endpoints](), [Security](), [AWS IAM](), [Latency](), [Self-hosted](), [Amazon Web Services]() Tags: [aws](), [aws-identity-and-access-management-iam](), [blog](), [firewalls](), [inference](), [infrastructure](), [opensearch](), [production](), [self-hosted](), [vpc]() ### AI overview This guide explains how to connect OpenSearch and Amazon OpenSearch Service to machine learning models hosted on private infrastructure. It covers VPC-hosted endpoints, private SageMaker endpoints, internal API gateways, and self-hosted inference servers, with configuration steps for connectors, model registration, deployment, testing, and VPC egress. ### Source excerpt Connect OpenSearch to ML models hosted on private infrastructure. Configure ML Commons connectors for VPC-hosted endpoints, private SageMaker models, and internal inference servers without exposing services to the public internet The post Connect OpenSearch to private ML endpoints appeared first on OpenSearch. ## From intent to enforcement: Lessons from operating Kubernetes controllers at scale DevFeed: [From intent to enforcement: Lessons from operating Kubernetes controllers at scale]() Original publisher: [Read original article]() Author: Sri Saran Balaji Vellore Rajakumar Published: 2026-07-17T12:00:00Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Kubernetes](), [Amazon Elastic Kubernetes Service](), [VPC]() Tags: [amazon-eks](), [aws-marketplace](), [clusters](), [controllers](), [declarative](), [kubernetes](), [networking](), [platform-engineering](), [policy-controller](), [post-contributed](), [reconciliation](), [scale](), [security](), [sponsor-aws-marketplace](), [sponsored-post-contributed](), [vpc]() ### AI overview This article explains lessons from operating Kubernetes controllers at scale in Amazon EKS. It focuses on how the Network Policy Controller and VPC Resource Controller reconcile declared intent with changing cluster state to enforce network traffic and AWS resource access policies. ### Source excerpt Kubernetes controllers are what make the platform's declarative model real. They observe the state, reconcile toward the intent, and keep The post From intent to enforcement: Lessons from operating Kubernetes controllers at scale appeared first on The New Stack. ## Introducing Autonomous Worker Agents DevFeed: [Introducing Autonomous Worker Agents]() Original publisher: [Read original article]() Author: Jyoti Bansal Rohan Gupta Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [AI Agent](), [Deployment](), [Security](), [Architecture & Design](), [Model Context Protocol]() Tags: [agents](), [ai-agent](), [governance](), [graph](), [mcp](), [release](), [safety](), [security](), [vpc]() ### AI overview Harness introduces Autonomous Worker Agents for software delivery. The agents run as pipeline steps or independently, use organizational context from the Harness Knowledge Graph and Harness MCP, and produce auditable outputs under controls such as scoped credentials, OPA policies, approval gates, and audit trails. ### Source excerpt Harness launches Autonomous Worker Agents: AI that runs as pipeline steps, with the governance enterprises need to trust agents in production | Blog ## Why infrastructure changes still take a week DevFeed: [Why infrastructure changes still take a week]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-06-10T00:00:00Z Content type: opinion Language: en Sources: [Encore Updates]() Topics: [Terraform](), [Security](), [Architecture & Design]() Tags: [iam](), [infrastructure](), [security](), [terraform](), [vpc]() ### AI overview The article examines why infrastructure changes often wait days or weeks for review while application code ships faster. It attributes the queue to a small reviewer pool, the high blast radius of infrastructure mistakes, and limited verification before Terraform changes are merged. It also discusses how AI coding tools have affected the queue and how teams can remove the bottleneck. ### Source excerpt Application code ships in hours and the infrastructure it needs waits days for review. Where the queue comes from, what AI coding tools did to it, and how teams remove it. ## Slack AI: The Path to Multi-Cloud DevFeed: [Slack AI: The Path to Multi-Cloud]() Original publisher: [Read original article]() Author: Shaurya Kethireddy Published: 2026-05-28T14:15:20Z Content type: article Language: en Sources: [Engineering at Slack]() Topics: [AI Chat]() Tags: [ai](), [amazon-bedrock](), [anthropic](), [availability](), [aws](), [backend](), [cloud](), [cloud-architecture](), [cloud-computing](), [collaboration](), [compliance](), [containers](), [engineering](), [enterprise](), [gpu](), [iam](), [infrastructure](), [innovation](), [llms](), [machine-learning](), [performance](), [security](), [slack](), [software-development](), [uncategorized](), [vpc]() ### AI overview Slack describes evolving its enterprise LLM-serving infrastructure from AWS SageMaker toward multi-cloud, multi-vendor orchestration to improve resilience, capacity management, and access to newer models. ### Source excerpt In early 2023, Slack faced a foundational challenge: serving Large Language Models (LLMs) at enterprise scale with the security, reliability, and performance our customers expect. Over three years, we evolved from basic infrastructure to orchestrating a sophisticated multi-cloud architecture. We didn't just want shiny new models; we needed a system resilient to regional outages and... ## ClickHouse expands strategic collaboration with Google Cloud, bringing deeper integration, cloud flexibility, and next-generation performance DevFeed: [ClickHouse expands strategic collaboration with Google Cloud, bringing deeper integration, cloud flexibility, and next-generation performance]() Original publisher: [Read original article]() Author: Tanya Bragin Published: 2026-04-21T00:00:00Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [Google](), [data](), [Deployment](), [migration]() Tags: [analytics](), [announcement](), [clickhouse](), [collaboration](), [data](), [deployment](), [google-cloud](), [integration](), [mcp](), [mcp-server](), [migration](), [performance](), [vpc]() ### AI overview ClickHouse announced an expanded collaboration with Google Cloud, including Lakehouse integration, BYOC availability, a planned migration to Axion processors, and an MCP server integration with Google Antigravity. ### Source excerpt ClickHouse, a leader in real-time analytics, data warehousing, observability, and AI/ML, today at Google Next 26 announced a significant expansion of its strategic collaboration with Google Cloud. ## ClickHouse BYOC on Google Cloud now Generally Available DevFeed: [ClickHouse BYOC on Google Cloud now Generally Available]() Original publisher: [Read original article]() Author: Aashish Kohli; Yiyang Shao Published: 2026-03-31T00:00:00Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [data](), [networking](), [Orchestration]() Tags: [announcement](), [availability](), [clickhouse](), [google-cloud](), [iam](), [terraform](), [vpc](), [zero-trust]() ### AI overview ClickHouse BYOC is generally available on Google Cloud, letting customers run the data plane in their own Google Cloud project while ClickHouse operates a separate managed control plane. ### Source excerpt Run ClickHouse in your own Google Cloud account : with full data sovereignty, zero-trust networking, and a managed control plane. ## Managed Databases Are Now Available in Laravel Forge DevFeed: [Managed Databases Are Now Available in Laravel Forge]() Original publisher: [Read original article]() Author: Laravel Team Published: 2026-03-17T15:48:55Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [postgresql clusters](), [Availability](), [Provisioning](), [Monitoring](), [Replication](), [Network](), [VPC]() Tags: [compute](), [databases](), [datacenter](), [high-availability](), [laravel](), [learn](), [memory](), [monitoring](), [network](), [postgres](), [replication](), [security](), [storage](), [vpc]() ### AI overview Laravel Forge now offers managed PostgreSQL clusters provisioned directly from its dashboard. The service handles patching, backups, replication, failover, and monitoring, with configurable compute, storage, region, networking, and high-availability options. ### Source excerpt Let Laravel Forge handle managed Postgres clusters for you with automated backups, PITR, high availability, and monitoring, all from your Forge dashboard. ## Deploy Smarter with AI: Introducing App Platform Skills on DigitalOcean DevFeed: [Deploy Smarter with AI: Introducing App Platform Skills on DigitalOcean]() Original publisher: [Read original article]() Author: Ritesh Mahato Published: 2026-03-16T14:00:00Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Deployment](), [Artificial Intelligence](), [Open Source](), [GitHub Actions](), [migration](), [PostgreSQL](), [VPC](), [SSL](), [Heroku]() Tags: [ai](), [deployment](), [digitalocean](), [github-actions](), [heroku](), [migration](), [open-source](), [platform](), [postgresql](), [product-updates](), [skills](), [ssl](), [vpc]() ### AI overview DigitalOcean introduces App Platform Skills, a collection of open-source playbooks that provide AI assistants with current, opinionated knowledge for designing, deploying, and troubleshooting applications on DigitalOcean App Platform. ### Source excerpt AI coding assistants have fundamentally changed how developers write software. Tools like Claude Code, Codex, GitHub Copilot, Gemini, and Cursor can scaffold an entire application in minutes. But ask any of them to deploy that application to a production cloud environment, and the experience breaks down -- not because models lack intelligence, but because they lack current, opinionated infrastructure knowledge. Cloud platforms evolve faster than training data refreshes: instance sizes change, new features ship, and battle-tested best practices emerge from customer feedback that never makes it into public documentation. Today, we're announcing App Platform Skills, a collection of open-source, AI-native playbooks that bridge this gap. Skills inject up-to-date, opinionated DigitalOcean App Platform knowledge directly into your AI assistant's context -- turning it from a generic code generator into an infrastructure-aware co-pilot that understands deployment models, networking primitives, database bindings, and operational patterns. Shell npx skills add digitalocean-labs/do-app-platform-skills That single command gives your AI assistant access to 12 specialized skills covering everything from greenfield app design to Heroku migration to production troubleshooting. Benefits -Production-Ready from the Start: Skills encode patterns from thousands of real deployments -- VPC networking by default, PostgreSQL v16 with SSL required, credentials in GitHub Secrets -- so AI-generated configuration aligns with how experienced platform engineers actually build. -Composable Skill Chaining: Skills work together. Describe a new app to the designer skill, and the planner skill decomposes deployment into staged phases while the deployment skill generates a GitHub Actions workflow to execute the rollout. -Zero Credential Exposure: The AI agent never handles sensitive credentials directly. Workflows reference GitHub Secrets by name, managed services use bindable variables like ${db.DATABASE_U ## Redpanda Cloud's BYOVPC for AWS is now Generally Available DevFeed: [Redpanda Cloud's BYOVPC for AWS is now Generally Available]() Original publisher: [Read original article]() Author: David Yu Published: 2026-03-11T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [Amazon VPC](), [Amazon Web Services](), [AWS IAM](), [Cloud](), [Firewall](), [Security](), [Platform Engineering](), [Amazon S3]() Tags: [announcement](), [aws](), [cloud](), [firewall](), [iam](), [infrastructure](), [networking](), [platform](), [platform-engineering](), [production](), [s3](), [security](), [vpc]() ### AI overview Redpanda Cloud's Bring Your Own VPC (BYOVPC) for AWS is generally available for production workloads. The deployment model gives teams control over their VPC, subnets, IAM roles, security policies, and networking while Redpanda manages the service within the customer-defined environment. ### Source excerpt BYOVPC is ready for production workloads, giving teams advanced networking control without sacrificing the managed experience you love about Redpanda Cloud. ## Supabase incident on February 12, 2026 DevFeed: [Supabase incident on February 12, 2026]() Original publisher: [Read original article]() Author: Paul Copplestone Published: 2026-02-13T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [incident](), [Supabase](), [Amazon Web Services](), [configuration](), [VPC](), [Deployment](), [networking](), [Security](), [Monitoring]() Tags: [auth](), [aws](), [database](), [incident](), [infrastructure](), [monitoring](), [network](), [networking](), [operations](), [outage](), [production](), [security](), [vpc]() ### AI overview Supabase describes a major February 12, 2026 outage affecting all services in its Ohio region for 3 hours and 42 minutes. A monitoring-service deployment inadvertently enabled AWS VPC Block Public Access regionally, blocking internet-gateway traffic across the region. Supabase restored service by rolling back the deployment and identifies insufficient infrastructure-pipeline guardrails as the underlying configuration problem. ### Source excerpt A detailed account of the February 12 outage in us-east-2, what caused it, and the steps we are taking to prevent it from happening again. ## Redpanda Terraform supports managing Redpanda Connect pipelines, private network DevFeed: [Redpanda Terraform supports managing Redpanda Connect pipelines, private network]() Original publisher: [Read original article]() Author: David Yu Published: 2026-02-05T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [Terraform](), [Redpanda-Connect](), [Provisioning](), [Cloud](), [configuration](), [Kafka](), [VPC](), [API](), [Amazon Web Services](), [Command-line interface]() Tags: [api](), [automation](), [aws](), [cloud](), [configuration](), [governance](), [infrastructure](), [pipelines](), [provisioning](), [redpanda-connect](), [terraform](), [vpc]() ### AI overview This article describes recent additions to the Redpanda Terraform provider for managing Redpanda Cloud clusters and Apache Kafka resources. It covers provisioning, configuration, and management of clusters, topics, schemas, roles, and pipelines, including BYOC and BYOVPC deployments supported on AWS and GCP. ### Source excerpt Automate Redpanda Cloud with Terraform. Manage Connect pipelines, PrivateLink, and BYOVPC to reduce operational toil and enforce enterprise governance. ## Setting up a VPC Route Server with Pulumi DevFeed: [Setting up a VPC Route Server with Pulumi]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2026-01-28T13:00:00Z Content type: tutorial Language: en Sources: [Scott's Weblog]() Topics: [VPC](), [Amazon Web Services](), [BGP](), [GitHub](), [Code]() Tags: [aws](), [bgp](), [cilium](), [cli](), [cloud](), [cni](), [code](), [containers](), [cri-o](), [devops](), [docker](), [github](), [go](), [iac](), [k8s](), [kubernetes](), [linux](), [networking](), [oci](), [security](), [tutorial](), [vpc]() ### AI overview A tutorial on using Pulumi to create and configure an AWS VPC Route Server for BGP-learned route injection. It covers creating the Route Server, associating it with a VPC, creating an endpoint for BGP peering, handling an explicit dependency between components, and propagating learned routes to a VPC route table. ### Source excerpt If you need to work with BGP in your AWS VPCs--so that BGP-learned routes can be injected into a VPC route table--then you will likely need a VPC Route Server. While you could set up a VPC Route Server manually, what's the fun in that? In this post, I will walk you through a Pulumi program that will set up a VPC Route Server. Afterward, I will discuss some ways you could check the functionality of the VPC Route Server to show that it is indeed working as expected. To make things as easy as possible, I have added a simple Pulumi program to my GitHub "learning-tools" repository in the aws/vpc-route-server directory. This program sets up a VPC Route Server and its associated components for you, and I will walk through this program in this blog post. The first step is creating the VPC Route Server itself. The VPC Route Server has no prerequisities, and the primary configuration needed is setting the ASN (Autonomous System Number) the Route Server should use: rs, err := vpc.NewRouteServer(ctx, "rs", &vpc.RouteServerArgs{ AmazonSideAsn: pulumi.Int(65534), Tags: pulumi.StringMap{ "Name": pulumi.String("rs"), "Project": pulumi.String("vpc-route-server"), }, }) Next, you will need to associate the Route Server with a VPC. This requires a VPC ID, as you might expect; this ID could come from a configuration value passed in by the user, or from a VPC created earlier in this or another Pulumi program. rsa, err := vpc.NewRouteServerVpcAssociation(ctx, "rsa", &vpc.RouteServerVpcAssociationArgs{ RouteServerId: rs.ID(), VpcId: pulumi.String(userSuppliedVpcId), }) With that association in place, the next component is a Route Server Endpoint. This endpoint is created in a subnet, and will have an IP address assigned from that subnet. This IP address is what your BGP peer will use to establish a peering relationship to exchange routes. rse, err := vpc.NewRouteServerEndpoint(ctx, "rse", &vpc.RouteServerEndpointArgs{ RouteServerId: rs.RouteServerId, SubnetId: pulumi.String(userSuppliedPriv ## Supabase PrivateLink is now available DevFeed: [Supabase PrivateLink is now available]() Original publisher: [Read original article]() Author: Miles Thomas Published: 2026-01-27T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Database](), [Amazon Web Services](), [VPC](), [Security](), [Network](), [Cloud](), [Latency](), [SSL]() Tags: [aws](), [cloud](), [compliance](), [data](), [database](), [finance](), [healthcare](), [internet](), [latency](), [network](), [public-sector](), [security](), [ssl](), [vpc]() ### AI overview Supabase PrivateLink enables connections between Supabase databases and AWS resources over private networks, avoiding public internet exposure. It supports private VPC endpoints, private DNS, direct Postgres connections, and PgBouncer, with benefits for compliance, security, and potentially lower latency. ### Source excerpt Connect to your Supabase database without touching the public internet. [Next page]()