<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Operations on My AWS Rocks!</title><link>https://myaws.name/tags/operations/</link><description>Recent content in Operations on My AWS Rocks!</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 05 Jan 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://myaws.name/tags/operations/index.xml" rel="self" type="application/rss+xml"/><item><title>Troubleshooting with VPC Flow Logs</title><link>https://myaws.name/troubleshooting-with-vpc-flowlogs/</link><pubDate>Thu, 05 Jan 2023 00:00:00 +0000</pubDate><guid>https://myaws.name/troubleshooting-with-vpc-flowlogs/</guid><description>&lt;p&gt;So you built your secure VPC, but things are not working as expected.&lt;br&gt;Or maybe something changed on the infrastructure and now things are not working.&lt;/p&gt;
&lt;p&gt;And as any network engineer knows, every application fault is always due to the network! So how do we prove traffic is getting to our systems and it&amp;rsquo;s not the network?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The answer is VPC Flow Logs.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;There is great guidance on Flow Logs in the &lt;a href="https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html"&gt;AWS VPC documentation&lt;/a&gt; so I will try not to cover that. What I will try and do is clarify some areas and explain how we can then use them to understand what is going on in our network. Specifically how we can use the AWS CloudWatch Logs console to find out what is happening in our VPC and give us some pointers on what might be wrong.&lt;/p&gt;</description></item></channel></rss>