# Amazon VPC Published articles for Amazon 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. ## Provision a secure Amazon DocumentDB cluster with Terraform DevFeed: [Provision a secure Amazon DocumentDB cluster with Terraform]() Original publisher: [Read original article]() Author: Sourav Kundu Published: 2026-08-31T20:24:23Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [Amazon DocumentDB](), [iac-security](), [Cryptography](), [passwords]() Tags: [advanced-300](), [amazon-cloudwatch](), [amazon-documentdb](), [amazon-vpc](), [authentication](), [encryption](), [infrastructure-as-code](), [monitoring](), [secrets](), [technical-how-to](), [terraform]() ### AI overview A walkthrough for provisioning a secure Amazon DocumentDB 8.0 cluster with Terraform. It applies infrastructure-as-code security controls including private VPC subnets, TLS, KMS encryption, secrets-managed passwords, security groups, and encrypted monitoring logs. ### Source excerpt Learn how to provision a secure Amazon DocumentDB cluster using Terraform. This post applies infrastructure-as-code best practices with encryption, AWS Secrets Manager authentication, network isolation, and encrypted monitoring. ## 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. ## Characterizing SQL\*Net latency in your application for Oracle Database@AWS migrations DevFeed: [Characterizing SQL\*Net latency in your application for Oracle Database@AWS migrations]() Original publisher: [Read original article]() Author: Sameer Malik Published: 2026-08-18T18:17:28Z Content type: article Language: en Sources: [AWS Database Blog]() Topics: [Oracle Database](), [Latency](), [migration](), [Amazon Web Services](), [Database](), [Network]() Tags: [advanced-300](), [amazon-ec2](), [amazon-elastic-container-service](), [amazon-elastic-kubernetes-service](), [amazon-vpc](), [aws](), [best-practices](), [database](), [latency](), [migration](), [network](), [oracle](), [oracle-database-aws](), [performance]() ### AI overview This article presents a methodology for assessing SQL*Net latency sensitivity before migrating Oracle workloads to Oracle Database@AWS. It focuses on identifying workloads with fast, frequent, and concentrated SQL activity, then quantifying the impact of added network round-trip latency in a multi-cloud architecture. It also discusses reducing client-server round trips through stored procedures, array fetches, and bulk processing. ### Source excerpt Oracle Database@AWS places Oracle Exadata infrastructure inside AWS data centers, so SQL*Net latency between your application and the database can change after migration. This post presents the CRET methodology, a three-phase approach using AWR, Active Session History, and SQL Trace, to identify latency-sensitive SQL and quantify the impact before you migrate. ## Normalize security logs to Google SecOps UDM with Observability Pipelines DevFeed: [Normalize security logs to Google SecOps UDM with Observability Pipelines]() Original publisher: [Read original article]() Author: Danielle Park Published: 2026-07-27T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [telemetry]() Tags: [amazon-vpc](), [google-cloud](), [google-secops](), [logs](), [mapping](), [observability-pipelines](), [security](), [telemetry](), [threat-detection](), [vpc-flow-logs]() ### AI overview The article explains how Observability Pipelines Google SecOps packs normalize security logs into the Unified Data Model before they reach Google SecOps. ### Source excerpt Learn how Observability Pipelines normalizes your telemetry to Google SecOps UDM, enabling both consistent investigations across sources and precise upstream control over your SIEM ingest. ## Securing the Connection to S3 from EC2 DevFeed: [Securing the Connection to S3 from EC2]() Original publisher: [Read original article]() Author: Guillermo Ojeda Published: 2023-09-07T15:02:09Z Content type: tutorial Language: en Sources: [Guille Ojeda]() Topics: [Amazon EC2](), [Amazon S3](), [VPC](), [Security](), [AWS CloudFormation]() Tags: [amazon-vpc](), [aws](), [cloud](), [cloudformation](), [ec2](), [s3](), [security]() ### AI overview A step-by-step tutorial for securing access from an Amazon EC2 instance to a private object in Amazon S3. It explains how to replace a public bucket setup with a restrictive bucket policy and a VPC endpoint policy. ### Source excerpt You've deployed your app on an EC2 instance, and there's a file in an S3 bucket that you need to access from the app. You created a public S3 bucket and uploaded the file, and it works! But then you read somewhere that keeping your private files in a... ## 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.