<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Aws on Vasu&#39;s Va-super&#39;s Blog</title>
    <link>https://vasuper.vasu3797.workers.dev/tags/aws/</link>
    <description>Recent content in Aws on Vasu&#39;s Va-super&#39;s Blog</description>
    <image>
      <title>Vasu&#39;s Va-super&#39;s Blog</title>
      <url>https://vasuper.vasu3797.workers.dev/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://vasuper.vasu3797.workers.dev/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.147.7</generator>
    <language>en</language>
    <lastBuildDate>Sat, 22 Feb 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vasuper.vasu3797.workers.dev/tags/aws/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Setting up Cloudwatch Cross Account Observability with CDK</title>
      <link>https://vasuper.vasu3797.workers.dev/posts/xaxr-cloudwatch/</link>
      <pubDate>Sat, 22 Feb 2025 00:00:00 +0000</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/posts/xaxr-cloudwatch/</guid>
      <description>&lt;p&gt;Cross Account Cross Region(XAXR) Cloudwatch Observability has been a feature that has been around for a while, it was introduced by AWS in &lt;a href=&#34;https://aws.amazon.com/blogs/aws/new-amazon-cloudwatch-cross-account-observability/&#34;&gt;2022&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s consider this scenario, you work in a company, that uses AWS. You are in a team that vends constructs/templates to other internal teams in your company. These internal teams are your customers. You vend your solution as an abstraction, that solves an undifferentiated problem for your customer. This let&amp;rsquo;s your customer focus on what makes their &lt;a href=&#34;https://podup.substack.com/p/jeff-bezoss-beer-tasting-analogy&#34;&gt;beer taste better&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>My Notes while learning about Greengrass</title>
      <link>https://vasuper.vasu3797.workers.dev/posts/greengrass_notes/</link>
      <pubDate>Sun, 09 Jun 2024 17:25:08 -0500</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/posts/greengrass_notes/</guid>
      <description>&lt;h1 id=&#34;greengrass-concepts-basics&#34;&gt;Greengrass Concepts Basics&lt;/h1&gt;
&lt;p&gt;GG is a edge runtime with a deployment and management mechanism for the egde runtime&lt;/p&gt;
&lt;p&gt;&lt;img alt=&#34;gg_arc&#34; loading=&#34;lazy&#34; src=&#34;https://vasuper.vasu3797.workers.dev/gg_post.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;AWS IoT thing&lt;/strong&gt;: A device or logic entity&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Greengrass core device&lt;/strong&gt;: Device running greengrass core software&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Greengrass client device&lt;/strong&gt;: A device that connects to and communicates with a greengrass core device over MQTT.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;client device&lt;/em&gt; and &lt;em&gt;core device&lt;/em&gt; could the same device or could be separated, with a sort of master slave relationship. client devices are meant for small footprint device that run embedded linux or RTOS maybe?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
