# Amazon VPC AWS cloud networking service for defining logically isolated virtual networks, including subnets, route tables, gateways, and security controls. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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. ## Building ClickHouse BYOC (Bring Your Own Cloud) on AWS DevFeed: [Building ClickHouse BYOC (Bring Your Own Cloud) on AWS]() Original publisher: [Read original article]() Author: Jianfei Hu; Yiyang Shao Published: 2025-03-12T15:09:23Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Amazon Web Services](), [cloud-infrastructure](), [Amazon VPC](), [Automation](), [Provisioning](), [Amazon Elastic Kubernetes Service](), [network security](), [Security](), [AWS IAM](), [Kubernetes]() Tags: [automation](), [aws](), [clickhouse](), [cloud](), [iam](), [infrastructure](), [kubernetes](), [network](), [network-security](), [provisioning](), [security](), [vpc]() ### AI overview This article explains how ClickHouse built a Bring Your Own Cloud (BYOC) offering on AWS. It covers deploying ClickHouse Cloud into customer-controlled VPCs and the engineering challenges of infrastructure automation, networking, security, compliance, resource management, auto-provisioning, scaling, and simplifying Kubernetes operations. ### Source excerpt Learn how we built ClickHouse BYOC (Bring Your Own Cloud) on AWS, tackling challenges like infrastructure automation, network security, and resource management to deliver a seamless, fully managed deployment within customer-controlled environments. ## Announcing General Availability of ClickHouse BYOC (Bring Your Own Cloud) on AWS DevFeed: [Announcing General Availability of ClickHouse BYOC (Bring Your Own Cloud) on AWS]() Original publisher: [Read original article]() Author: ClickHouse Published: 2025-02-20T00:00:00Z Content type: news Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Amazon VPC](), [Amazon Web Services](), [Cloud](), [Deployment](), [autoscaling](), [data-governance]() Tags: [availability](), [aws](), [byoc-deployment](), [clickhouse](), [cloud](), [cloud-native](), [compliance](), [data-governance](), [scale](), [security](), [vpc]() ### AI overview The article announces the general availability of ClickHouse BYOC on AWS, a fully managed ClickHouse Cloud service deployed in a customer's own AWS account and VPC. Customer data, compute, storage, cache, and backups remain within the customer's VPC, supporting security, compliance, governance, workload isolation, scaling, and lower infrastructure costs. ### Source excerpt Today, we announce the GA of ClickHouse BYOC on AWS. A fully managed ClickHouse Cloud service deployed in your own AWS account. Designed for large-scale deployments, with personalized support and onboarding. SOC 2 and ISO 27001 aligned. ## The Two AWS RDS Postgres Errors I Always Make DevFeed: [The Two AWS RDS Postgres Errors I Always Make]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-04-08T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Amazon RDS](), [Amazon Web Services](), [Amazon VPC](), [Databases](), [Security](), [ui]() Tags: [amazon-rds](), [aws](), [database](), [postgres](), [rds](), [security](), [user-interface](), [vpc]() ### AI overview A personal guide to three recurring mistakes when creating Amazon RDS PostgreSQL instances: failing to specify an initial database name, placing the database server in the wrong VPC, and using the wrong security group. ### Source excerpt You know that awful feeling of personal stupidity when you consistently make the same mistake time after time? Well my approach to addressing that is to document said mistakes, here, each time I make them. Sometimes I take the approach of admitting to them and sometimes I take the approach of just writing them as a blog post. There are two errors, nay three, I make almost every single time I create an RDS postgres instance and I thought "maybe it is time to write them down and (hopefully) curse less" the next time. Note: I wrote this as a text post with pictures below so that the quick answers appear first before a whole bunch of screenshots. Error 1: Not Creating the Database When you Create the Database Server When you create a "database" on RDS you are actually creating a database server on which you then create the database itself. Now the core issue here is that AWS makes it very hard, at least when you are making a Postgres database to create that database later. I'm sure there is a way but, yesterday, in a few hours of messing with this, I never found it. What I had to do was drop my database server and walk through the creation process again, finally finding it nested away in an expandable section of the user interface. When you are walking through the "Create Database" form, there is a final section called "Additional Configuration". If you expand this then the very first option is "Initial Database Name" along with the helpful message: If you do not specify a database name, Amazon RDS does not create a database. Groan. Keep in mind that this whole feature starts on a web page titled "Create Database" (but the default is to NOT create a database). Error 2: Not Putting the Database Server in the Same VPC Generally speaking most of us tend to use a single VPC (virtual private cloud) for our AWS boxes. Despite this it is not guaranteed that your database server ends up in the same VPC as your other boxes unless you explicitly specify this. Error 3: Not Putting ## 10x: Logging at Clay.io DevFeed: [10x: Logging at Clay.io]() Original publisher: [Read original article]() Author: Zoli Kahan Published: 2014-10-25T05:00:00Z Content type: article Language: en Sources: [Zolmeister]() Topics: [Logging](), [log management](), [logstash](), [elasticsearch](), [kibana](), [Amazon VPC](), [Server](), [Linux](), [Docker]() Tags: [aggregate](), [amazon](), [amazon-vpc](), [analyze](), [apply](), [architecture](), [complex](), [docker](), [elasticsearch](), [kibana](), [linux](), [logging](), [logs](), [logstash](), [network](), [series](), [server](), [servers](), [ssh]() ### AI overview This article describes how Clay.io used Logstash to aggregate logs from more than 20 servers, with Elasticsearch and Kibana for analysis. It also discusses log rotation, securing Elasticsearch through Amazon VPC, and open-sourced Docker containers for deploying a distributed logging system. ### Source excerpt 10x: Logging at Clay.io Managing 20+ servers as a small team is no easy task, and when things go wrong (they always do) figuring out what happened quickly is essential. Of course we can't ssh into each machine, that would take ages, so instead we use Logstash to aggregate our logs. This is the second post in my series, and if you missed last episode: Architecture at Clay.io. Logstash overview Logstash deployments have two parts. The aggregate server (or cluster), and the client servers. ## 10x: Architecture at Clay.io DevFeed: [10x: Architecture at Clay.io]() Original publisher: [Read original article]() Author: Zoli Kahan Published: 2014-10-01T05:00:00Z Content type: opinion Language: en Sources: [Zolmeister]() Topics: [Architecture & Design](), [cloud-infrastructure](), [Amazon EC2](), [Amazon VPC](), [Dockerfile](), [MySQL](), [Amazon S3](), [Cloudflare]() Tags: [amazon-ec2](), [amazon-s3](), [architecture](), [caching](), [cloudflare](), [ddos](), [docker](), [mysql](), [ssl](), [vpc]() ### AI overview A first-person account of Clay.io's architecture for operating at scale with a small team. It describes the use of Cloudflare for DNS, caching, DDoS protection, and SSL; Amazon EC2 and VPC for servers and private networking; Amazon S3 for static content; HAProxy for traffic routing; Docker for application and staging servers; and a MySQL master-slave cluster for data. ### Source excerpt 10x: Architecture at Clay.io This is the first post in my new series , where I share my experiences and how we do things at Clay.io to develop at scale with a small team. Update: The Cloud CloudFlare CloudFlare handles all of our DNS, and acts as a distributed caching proxy with some additional DDOS protection features. It also handles SSL. Amazon EC2 + VPC + NAT server Almost all of our servers live on Amazon EC2, most are either medium or large instances.