<?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>Vasu&#39;s Va-super&#39;s Blog</title>
    <link>https://vasuper.vasu3797.workers.dev/</link>
    <description>Recent content 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>Wed, 03 Sep 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vasuper.vasu3797.workers.dev/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixing a hyprland shared library issue in omarchy</title>
      <link>https://vasuper.vasu3797.workers.dev/posts/omarchy-fix/</link>
      <pubDate>Wed, 03 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/posts/omarchy-fix/</guid>
      <description>A short story of fixing a shared library hyprland issue on omarchy</description>
    </item>
    <item>
      <title>My Tutorial for Securing AWS Greengrass with TPM2 is live!</title>
      <link>https://vasuper.vasu3797.workers.dev/posts/secure-gg-with-tpm/</link>
      <pubDate>Wed, 09 Jul 2025 00:00:00 +0000</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/posts/secure-gg-with-tpm/</guid>
      <description>x509 certs secured with through the TPM2 chip so that no-one can steal it.</description>
    </item>
    <item>
      <title>Resume</title>
      <link>https://vasuper.vasu3797.workers.dev/resume/</link>
      <pubDate>Mon, 28 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/resume/</guid>
      <description>&lt;h1 id=&#34;vasudevan-perumal&#34;&gt;&lt;strong&gt;Vasudevan Perumal&lt;/strong&gt;&lt;/h1&gt;
&lt;p&gt;&lt;a href=&#34;mailto:vasu3797@gmail.com&#34;&gt;vasu3797@gmail.com&lt;/a&gt; | &lt;a href=&#34;http://www.linkedin.com/in/vasuper&#34;&gt;www.linkedin.com/in/vasuper&lt;/a&gt; | 773-707-1927 | &lt;a href=&#34;https://vasuper.vasu3797.workers.dev/&#34;&gt;vasuper.vasu3797.workers.dev&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;experience&#34;&gt;&lt;strong&gt;Experience&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;System Development Engineer II | Amazon OpsTech &amp;amp; Robotics | Austin, TX | &lt;em&gt;Dec 2023 - Present (1 yr 5 mos)&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Led the development of the OS Bakery, a CI mechanism for OS builds, and a toolchain of dev-tools for local builds. Fully automating git merge to build, and publish of OS artifacts to device deployment.&lt;/li&gt;
&lt;li&gt;Designed a framework of abstractions for OS customization in the Amazon context, making OS customization accessible to cloud-native engineers, reducing time to prototype for teams, from days to a couple of hours.&lt;/li&gt;
&lt;li&gt;Spearheaded development of AmazonEdgeOS, first ever custom Linux distribution at Amazon Robotics. Security and reliability as core tenets, we implemented A/B Updates, TPM2 full disk encryption, etc.&lt;/li&gt;
&lt;li&gt;Designed a virtual OS testing service enabling developers and integration testing frameworks, to spin up test instances, run tests, and teardown instances on-demand, built with libvirt, vagrant, and pytest.&lt;/li&gt;
&lt;li&gt;Developed abstractions, for teams to leverage TPM2 root of trust for Cloud service and  Wifi EAP registration.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;System Development Engineer I | Amazon OpsTech &amp;amp; Robotics | Austin, TX |  &lt;em&gt;Jul 2021 - Dec 2023 (2 yrs 6 mos)&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <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>Curated List of FOSDEM 2025 Talks for Linux Distribution Builders</title>
      <link>https://vasuper.vasu3797.workers.dev/posts/fosdem-2025/</link>
      <pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/posts/fosdem-2025/</guid>
      <description>&lt;p&gt;FOSDEM is a free and non-commercial event organised by the community for the community. The full form is Free and Open Source Developers European Meeting, you can learn more about it&amp;rsquo;s history &lt;a href=&#34;https://fosdem.org/2025/about/&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;My day to day involves working with Linux, and maintaining a Linux &lt;a href=&#34;https://en.wikipedia.org/wiki/Linux_distribution&#34;&gt;Distribution&lt;/a&gt; for my company and building new features for the distribution. FOSDEM is great conference for Linux builders and even users to learn about the latest greatest happening in the community.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Leveraging Container Registry APIs for your benefit.</title>
      <link>https://vasuper.vasu3797.workers.dev/posts/container_registry_api/</link>
      <pubDate>Wed, 27 Nov 2024 00:00:00 +0000</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/posts/container_registry_api/</guid>
      <description>&lt;p&gt;If you have ever run &lt;code&gt;docker pull&lt;/code&gt; or pulled a container using the favorite container runtime tool of your choice, you&amp;rsquo;ve probably interacted with a container registry.&lt;/p&gt;
&lt;p&gt;A container registry does not only provide mechanisms to store and distribute container images, it also exposes APIs that clients can use to perform other actions like fetching the container&amp;rsquo;s metadata without pulling the entire container.&lt;/p&gt;
&lt;p&gt;At work, I had a problem to solve, which is when I thought why not leverage these APIs to solve my problem. In this post we&amp;rsquo;ll see how I leveraged the Container Registry APIs for my benefit and possibly how you the reader can use it as well.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using UV to manage a python project</title>
      <link>https://vasuper.vasu3797.workers.dev/posts/using_uv/</link>
      <pubDate>Fri, 18 Oct 2024 00:00:00 +0000</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/posts/using_uv/</guid>
      <description>&lt;h2 id=&#34;1-motivation&#34;&gt;1. Motivation&lt;/h2&gt;
&lt;p&gt;I wanted to put up a small snippet of code I did at work as a public github project, as it seemed like a common usage pattern that other folks can use of the shelf or copy from.&lt;/p&gt;
&lt;p&gt;Within Amazon, we have our own python project management and dependency management tooling that automates away a lot of the boilerplate setup in defining and distributing a Python project.&lt;/p&gt;
&lt;p&gt;They abstract away the setup and usage for tools and configurations like pyproject.toml, venv, mypy, black, pytest, etc. They essentially run these tools under the hood, but we as developers don&amp;rsquo;t need to care about setting these up every time we start a new project.&lt;/p&gt;</description>
    </item>
    <item>
      <title>My notes on the Trusted Platform Modules</title>
      <link>https://vasuper.vasu3797.workers.dev/posts/intro-to-tpm/</link>
      <pubDate>Mon, 10 Jun 2024 03:25:52 +0000</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/posts/intro-to-tpm/</guid>
      <description>Notes on the basic concepts of trusted compute, the TPM architecture and features</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>
    <item>
      <title>About me</title>
      <link>https://vasuper.vasu3797.workers.dev/about/</link>
      <pubDate>Sun, 09 Jun 2024 00:00:00 +0000</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/about/</guid>
      <description>&lt;p&gt;Hello,
My name is Vasudevan Perumal.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m an computer systems generalist, with a some battle scars(aka experience) in Linux distribution engineering, and building systems to provision and manage devices at scale using cloud-native technologies. Right now, I build cloud-native endpoints for robotics systems at Amazon. What is a cloud-native endpoint you might ask?&lt;/p&gt;
&lt;p&gt;Cloud-native endpoints are devices that can be deployed from anywhere. They receive their applications and configurations dynamically from the cloud, and can easily be reset or restored. These systems don&amp;rsquo;t generally require a direct connection to any on-premises resources for usability or management.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Build your own Customized Live Debian Distro using Debootstrap</title>
      <link>https://vasuper.vasu3797.workers.dev/posts/debian-image-debootstrap/</link>
      <pubDate>Mon, 02 Jan 2023 08:23:29 -0600</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/posts/debian-image-debootstrap/</guid>
      <description>&lt;p&gt;In this guide, we&amp;rsquo;ll be going over the steps involved to build a LiveCD Debian distribution using debootstrap with both legacy BIOS and UEFI boot support using GRUB2. Why build your own distribution, you ask?
There are scenarios and use cases that necessitate packages, certificates or other artifacts are already installed in the OS Image that&amp;rsquo;s distributed in the machines that are shipped, this guide will go over the steps involved to build that image.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building Yocto Based Linux Image for AMD Ryzen Embedded v1000 Series SoCs with AWS Agents installed.</title>
      <link>https://vasuper.vasu3797.workers.dev/posts/amd-yocto-post/</link>
      <pubDate>Sun, 30 Oct 2022 17:25:08 -0500</pubDate>
      <guid>https://vasuper.vasu3797.workers.dev/posts/amd-yocto-post/</guid>
      <description>&lt;p&gt;This guide outlines the steps involved to build a linux distribution using Yocto for AMD Ryzen Embedded v1000 Series SoCs with AWS SDKs, services, and software from the &lt;a href=&#34;https://github.com/aws4embeddedlinux/meta-aws&#34;&gt;meta-aws&lt;/a&gt; layer.&lt;/p&gt;
&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites:&lt;/h2&gt;
&lt;p&gt;To follow the steps image build section, you will need:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A Supported Linux Distribution&lt;/strong&gt;: You should have a reasonably current Linux-based host system. You will have the best results with a recent release of Fedora, openSUSE, Debian, Ubuntu, or CentOS as these releases are frequently tested against the Yocto Project® and officially supported. I’ve tried building this with both Ubuntu 20.04 and Pop_OS! 22.04.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
