<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Vinny Akkal</title>
    <description>The latest articles on DEV Community by Vinny Akkal (@vinnyakkal).</description>
    <link>https://dev.to/vinnyakkal</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F180765%2F5eaaedfe-2c13-4c24-a4ce-09ce5aaa5e62.png</url>
      <title>DEV Community: Vinny Akkal</title>
      <link>https://dev.to/vinnyakkal</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vinnyakkal"/>
    <language>en</language>
    <item>
      <title>Is there any software to generate a list of NACL rules for my AWS account?</title>
      <dc:creator>Vinny Akkal</dc:creator>
      <pubDate>Thu, 20 Jun 2019 05:41:03 +0000</pubDate>
      <link>https://dev.to/vinnyakkal/is-there-any-software-to-generate-a-list-of-nacl-rules-for-my-aws-account-3i13</link>
      <guid>https://dev.to/vinnyakkal/is-there-any-software-to-generate-a-list-of-nacl-rules-for-my-aws-account-3i13</guid>
      <description>&lt;p&gt;I am facing this issue for a long time now, our NACL rules are all messed up and this in turn hinders our resource management.&lt;br&gt;
Is there a way through which I can generate a list of NACL rules for my AWS account?&lt;br&gt;
Any input shall be appreciated.&lt;/p&gt;

</description>
      <category>aws</category>
      <category>cloud</category>
      <category>nacl</category>
      <category>cloudcost</category>
    </item>
    <item>
      <title>Automate deletion of unused AWS Workspaces</title>
      <dc:creator>Vinny Akkal</dc:creator>
      <pubDate>Wed, 19 Jun 2019 11:05:39 +0000</pubDate>
      <link>https://dev.to/vinnyakkal/automate-deletion-of-unused-aws-workspaces-dkg</link>
      <guid>https://dev.to/vinnyakkal/automate-deletion-of-unused-aws-workspaces-dkg</guid>
      <description>&lt;p&gt;Recently, we received way more than expected AWS bill; after using a cost explorer, we found that all this while we were billed for inactive Workspaces also. Practically, it is a tiresome job to keep a check on all the workspaces and terminate them before the billing period ends.&lt;br&gt;
Is there a way where I can automate the filtering and deleting of unused Workspaces?&lt;/p&gt;

</description>
      <category>aws</category>
      <category>cloud</category>
      <category>cloudcost</category>
      <category>awsworkspace</category>
    </item>
    <item>
      <title>Automate deletion of unused EBS Volumes</title>
      <dc:creator>Vinny Akkal</dc:creator>
      <pubDate>Wed, 19 Jun 2019 10:43:46 +0000</pubDate>
      <link>https://dev.to/vinnyakkal/automate-deletion-of-unused-ebs-volumes-g0b</link>
      <guid>https://dev.to/vinnyakkal/automate-deletion-of-unused-ebs-volumes-g0b</guid>
      <description>&lt;p&gt;Recently, my AWS account was heavily billed because I didn't pay attention to my unused EBS Volume.&lt;br&gt;
We have been trying to pay attention the the unused EBS Volume and delete them, but is there a way to automate it?&lt;br&gt;
Because it is practically difficult to implement the whole procedure manually periodically.&lt;br&gt;
Even if I get notified monthly, it would be of great help.&lt;br&gt;
Any input shall be appreciated.&lt;/p&gt;

</description>
      <category>aws</category>
      <category>cloud</category>
      <category>ebs</category>
      <category>cloudcost</category>
    </item>
    <item>
      <title>How to proactively monitor daily lambda cost?</title>
      <dc:creator>Vinny Akkal</dc:creator>
      <pubDate>Fri, 14 Jun 2019 16:23:01 +0000</pubDate>
      <link>https://dev.to/vinnyakkal/how-to-proactively-monitor-daily-lambda-cost-4lpk</link>
      <guid>https://dev.to/vinnyakkal/how-to-proactively-monitor-daily-lambda-cost-4lpk</guid>
      <description>&lt;p&gt;There was a bug in our code which lead to a large number of invocations in lambdas which costed us the next 6 months of budget. We are talking to the AWS Support to check if they can refund the same. However, how do you guys proactively monitor costs?&lt;/p&gt;

</description>
      <category>aws</category>
      <category>lambda</category>
      <category>cost</category>
    </item>
  </channel>
</rss>
