<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws on The Comfy Seat</title><link>https://beanbag.technicalissues.us/tags/aws/</link><description>Recent content in Aws on The Comfy Seat</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 31 May 2024 17:00:00 -0400</lastBuildDate><atom:link href="https://beanbag.technicalissues.us/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Routing Across AWS Subnets</title><link>https://beanbag.technicalissues.us/routing-across-aws-subnets/</link><pubDate>Fri, 31 May 2024 17:00:00 -0400</pubDate><guid>https://beanbag.technicalissues.us/routing-across-aws-subnets/</guid><description>&lt;p&gt;This morning at work I was presented with an interesting question: why can&amp;rsquo;t two instances in AWS seem to talk to each other on their internal / private network interfaces? To answer this, let&amp;rsquo;s back up a second and let me show you what the architecture of the environment is. First, take a moment and look at the diagram below and observe not only how many layers there are, but also that this is a pretty simple setup with one VPC containing two instances that are spread across two Availability Zones:&lt;/p&gt;</description></item></channel></rss>