<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Shibin on Medium]]></title>
        <description><![CDATA[Stories by Shibin on Medium]]></description>
        <link>https://medium.com/@shibinarayan?source=rss-2fcafd5dad00------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qQPeTdyDHYkqxiwD1JmIXw@2x.jpeg</url>
            <title>Stories by Shibin on Medium</title>
            <link>https://medium.com/@shibinarayan?source=rss-2fcafd5dad00------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:59:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shibinarayan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tips for Changing AWS Instance Types: Avoiding Issues and Ensuring a Smooth Transition]]></title>
            <link>https://medium.com/@shibinarayan/tips-for-changing-aws-instance-types-avoiding-issues-and-ensuring-a-smooth-transition-140ae20dc1a7?source=rss-2fcafd5dad00------2</link>
            <guid isPermaLink="false">https://medium.com/p/140ae20dc1a7</guid>
            <category><![CDATA[aws-ec2]]></category>
            <dc:creator><![CDATA[Shibin]]></dc:creator>
            <pubDate>Fri, 31 Mar 2023 16:43:02 GMT</pubDate>
            <atom:updated>2023-03-31T16:43:02.943Z</atom:updated>
            <content:encoded><![CDATA[<p>Changing an AWS instance type is a simple process, but it can lead to issues if not done properly. To ensure a smooth transition, there are a few things to keep in mind before making any changes.</p><p>If you are upgrading from an older generation AWS instance to a new generation Nitro instance, be aware that failure rates may be higher due to the absence of the ena and nvme modules. Additionally, incorrect entries in the fstab can cause boot-up failures after resizing. To avoid this issue, it is recommended to use the block device UUID in the fstab instead of the disk names.</p><p>To confirm that your instance has passed the necessary requirements, you can use the script found at <a href="https://github.com/awslabs/aws-support-tools/tree/master/EC2/NitroInstanceChecks">https://github.com/awslabs/aws-support-tools/tree/master/EC2/NitroInstanceChecks</a>. By following these guidelines, you can avoid potential issues and ensure a smooth instance type change on AWS.</p><p>It’s recommended to take a snapshot before making any changes!</p><p><a href="https://repost.aws/knowledge-center/boot-error-linux-nitro-instance">Resolve boot errors on Linux Nitro-based EC2 instances | AWS re:Post</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=140ae20dc1a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a CloudWatch math expression to identify Micro-bursting on AWS EBS volumes.]]></title>
            <link>https://medium.com/@shibinarayan/how-to-create-a-cloudwatch-math-expression-to-identify-micro-bursting-on-aws-ebs-volumes-fb576b87dcc1?source=rss-2fcafd5dad00------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb576b87dcc1</guid>
            <dc:creator><![CDATA[Shibin]]></dc:creator>
            <pubDate>Sat, 08 Oct 2022 13:29:05 GMT</pubDate>
            <atom:updated>2022-10-08T13:34:13.664Z</atom:updated>
            <content:encoded><![CDATA[<p>Micro-bursting occurs when you have high IO or throughput usage on the disk for significantly shorter period.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4LTfr2kTFAT22g1sU8Diw.png" /><figcaption>sample micro-burst result</figcaption></figure><p><strong>How to use CloudWatch to identify micro-bursting.</strong></p><p>To calculate average IOPS, do the following.</p><p>Form the CloudWatch service, search for the volume with volume ID and select “VolumeReadOps”, “VolumeWriteOps” and “VolumeIdleTime” as below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qLztzdR2AMAK70QFG4UG1A.png" /></figure><p>The formula to calculate average IOPS is below [1]</p><p>Actual average IOPS in Ops/s = (Sum(VolumeReadOps) + Sum(VolumeWriteOps) ) / ( Period — Sum(VolumeIdleTime) )</p><p>Now, add math expression in CloudWatch as below.</p><p><em>Statistic must be Sum and the period I selected here as 1 minute (60 seconds)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WH9QUDe7Fmpc8o7XrXiwdw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oBSBtYpJYjRhO81XAsdRZg.png" /><figcaption>math expression</figcaption></figure><p>Now, Average IOPS in Ops/s = (m1 + m2) / (60 — m3)</p><p>m1 = Sum (VolumeReadOps)</p><p>m2 = Sum (VolumewriteOps)</p><p>m3= Sum(VolumeIdleTime)</p><p>And 60 second is the period.</p><p>Now you select the Expression1 to get the result as below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kh5XFjdWN_HsefGXhZp13Q.png" /><figcaption>Average IOPS in Ops/s</figcaption></figure><p>Similarly, you can setup another expression to calculate average throughput by using below formula.</p><p>Average Throughput in Bytes/s = (Sum(VolumeReadBytes) + Sum(VolumeWriteBytes) ) / ( Period — Sum(VolumeIdleTime) )</p><p>Reference: [1] <a href="https://aws.amazon.com/premiumsupport/knowledge-center/ebs-identify-micro-bursting/">https://aws.amazon.com/premiumsupport/knowledge-center/ebs-identify-micro-bursting/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb576b87dcc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On-Demand capacity reservation on AWS (ODCR)]]></title>
            <link>https://medium.com/@shibinarayan/on-demand-capacity-reservation-on-aws-odcr-9342e45e9f07?source=rss-2fcafd5dad00------2</link>
            <guid isPermaLink="false">https://medium.com/p/9342e45e9f07</guid>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Shibin]]></dc:creator>
            <pubDate>Sat, 05 Feb 2022 10:29:38 GMT</pubDate>
            <atom:updated>2022-02-05T10:51:28.668Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the errors we are seeing during instance launch on AWS is getting Insufficient Capacity Error (ICE). It means, AWS doesn’t have sufficient capacity to launch your instance on the AZ. We can avoid this kind of situation by enabling ODCR.</p><p>You can create Capacity Reservations (CR) at any time, and the capacity is available immediately. Billing starts as soon as the capacity is provisioned, and the Capacity Reservation enters the active state.</p><p><strong>When you create CR, specify:</strong></p><blockquote>Availability zone (AZ) — Availability Zone in which to reserve the capacity.</blockquote><blockquote>Quantity- (Number of instances for which to reserve the capacity).</blockquote><blockquote>The instance attributes, including the instance type, tenancy, and platform/OS</blockquote><p><strong>Creating a CR.</strong></p><p>From the EC2 console — Capacity Reservation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0VhkEChWg02XoCPruzGN8g.png" /></figure><p><em>Platform — The operating system for your instances. <br>Availability Zone — The Availability Zone in which to reserve the capacity.<br>Tenancy — Specify whether to run on shared hardware or a dedicated instance.</em></p><p><strong>Quotas</strong></p><p>The quantity that you are allowed to reserve capacity is based on your account’s On-Demand Instance quota. You can reserve capacity for as many instances as that quota allows, minus the number of instances that are already running.</p><p>Capacity Reservations can only be used by instances that match their attributes. By default, they are automatically used by running instances that match the attributes. If you don’t have any running instances that match the attributes of the Capacity Reservation, it remains unused until you launch an instance with matching attributes. It is a completely random choice of instances. Meaning, if you have a Capacity Reservation for 1 instance and there are 2 instances already running with the same attributes, a random instance will be associated with this CR.</p><p><strong>Modify the CR</strong></p><p>You can modify the CR only to increase or decrease the quantity in the CR. You cannot modify the instance type in the CR. To do that, we need to cancel the current CR and create a new one.</p><p><strong>Billing</strong></p><p>When the Capacity Reservation enters the active state, you are charged the equivalent On-Demand rate whether you run instances in the reserved capacity or not. If you do not use the reservation, this shows up as unused reservation on your EC2 bill.</p><p><strong>Cancelling the CR</strong></p><p>If you no longer needed the CR, you can cancel the reservation any time to stop incurring charges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9342e45e9f07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Big mistakes in AWS Cloud Security.]]></title>
            <link>https://medium.com/@shibinarayan/big-mistakes-in-aws-cloud-security-8aa7275d886d?source=rss-2fcafd5dad00------2</link>
            <guid isPermaLink="false">https://medium.com/p/8aa7275d886d</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-security]]></category>
            <dc:creator><![CDATA[Shibin]]></dc:creator>
            <pubDate>Sun, 29 Aug 2021 11:40:44 GMT</pubDate>
            <atom:updated>2021-08-29T11:40:44.278Z</atom:updated>
            <content:encoded><![CDATA[<p>As you know AWS is one of the biggest cloud providers in the industry and have a highly secured track record. However, most of the security vulnerability issues reported are not really from the AWS environment itself but from the misconfigured environment deployed by the customers on AWS.</p><p>Most common security issues are:</p><p>1. Misconfigured access control on S3 buckets.</p><p>2. Vulnerabilities due to the application running on an EC2.</p><p>3. Security group and NACL hardening flaws.</p><p>4. Privilege escalation.</p><p><strong>Misconfigured access control on S3 buckets.</strong></p><p>We are using AWS S3 service to store static files or any content that needed for business purposes. By default, any resources stored on S3 are private and only the resource owner can grant access for others to the contents via access policy. Usually, when a request comes to S3 bucket, S3 evaluates all the necessary user policies, access policies and resource-based policies to decide whether to authorize the access. In this case, if you grant full access to the S3 bucket that can leads to malicious activity on the S3.</p><p>You can check unauthorized user access to a bucket via AWS CLI.</p><p>1. Try uploading a content to s3.</p><p>aws s3 cp testfile.txt s3://bucket-name/</p><p>If the upload is success from an unauthorized user, means anybody can upload a content to this s3.</p><p>Similarly, you can check the downloading or deleting or any modification on contents. All this is happening due to the wrong s3 policy configuration and an attacker can utilize this privilege for any malicious activity.</p><p><strong>Vulnerabilities due to the application running on an EC2.</strong></p><p>This can be happened due to the outdated application version or due to any security bug. We have a database called CVE (Common Vulnerabilities and Exposures) where list all the publicly disclosed security vulnerabilities. We can use Amazon Inspector to assesses the application for any exposure or any vulnerabilities.</p><p>If a particular CVE appears in a finding that is produced by an Amazon Inspector, you can search <a href="https://cve.mitre.org/">https://cve.mitre.org/</a> for the ID of the CVE. The search results can provide detailed information about this CVE, its severity, and how to mitigate it.</p><p><strong>Security group and NACL hardening flaws.</strong></p><p>Security group and NACL works as a firewall that allows to filter the traffic that crosses the network segments. Security group adds a security layer to EC2 instances that control both inbound and outbound traffic at the instance level and the NACL provides an optional layer of security to your subnets. One of the most common mistake seeing on this settings is to allow all traffic for the incoming network 0.0.0.0/0 in security group which will allow the AWS resource to access from outside world!.</p><p><strong>Privilege escalation.</strong></p><p>Privilege escalation is an attack that involves gaining illegitimate access of all rights, or privileges, beyond what is intended for a user. AWS IAM is the critical component that customers using to operate AWS services. A misconfiguration in IAM trust policies can utilize attacker to get full privilege to the AWS account and do whatever they want.</p><p>Different scenarios where we are using IAM policies are, AWS service assesses another AWS service, AWS account assesses another AWS accounts and a third party web identity needs access.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8aa7275d886d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monitoring and troubleshooting AWS network traffic.]]></title>
            <link>https://medium.com/@shibinarayan/monitoring-and-troubleshooting-aws-network-traffic-71784da80bbe?source=rss-2fcafd5dad00------2</link>
            <guid isPermaLink="false">https://medium.com/p/71784da80bbe</guid>
            <category><![CDATA[vpc]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Shibin]]></dc:creator>
            <pubDate>Sun, 22 Aug 2021 16:47:52 GMT</pubDate>
            <atom:updated>2021-08-22T16:47:52.055Z</atom:updated>
            <content:encoded><![CDATA[<p>There are multiple ways to troubleshoot an AWS network traffic issue. Here are the 4 ways I always following to troubleshoot a connectivity issue.</p><ol><li>Enable VPC Flow logs.</li><li>VPC Traffic mirroring</li><li>EC2 instance level metrics.</li><li>VPC reachability analyzer.</li></ol><p><strong>VPC Flow logs</strong>: As you know, Flow logs will capture all the traffic that is going through an EC2 instance. This can be enabled for a particular instance or all instances in a subnet or a VPC.</p><p>Captured logs can be further analyzed by using AWS cloudWatch or Athena.</p><p><strong>VPC Traffic Mirroring: </strong>AWS traffic mirroring help us to get better visibility into the payload. This is basically will send a copy actual network packets to either a network interface or a network load balancer to inspect in detail by using standard tools like Elasticsearch and Kibana (or any other similar kind of solutions).</p><p>Key elements of Traffic mirroring are:</p><p>1. Mirror source :- A network resource that exists within a VPC, and that can be used as a source of the network traffic.</p><p>2. Mirror target:- This can be either a network interface or a network load balancer that act as a destination for mirrored traffic.</p><p>3. Mirror filter :- You can apply filters to accept or reject Inbound or outbound traffic.</p><p>4. Traffic mirror session :- It’s a connection between source mirror and target that make use of a filter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*9_rLQtjBaiqZhdEm0EhTYQ.png" /><figcaption>A sample Traffic mirroring architecture</figcaption></figure><p><strong>Monitor network performance on EC2 instance</strong>:</p><p>1. CloudWatch metrics:- This is one of my favorite service to monitor and analyze the resource utilization in AWS. This allows you to check how much bytes of traffic going In or out (NetworkIn and NetworkOut) from the instance and the packets count.</p><p>2. From the OS layer.</p><p>There are multiple tools like “ethtool”, “tcpdump”, traceroute etc.. to troubleshoot from the instance level.</p><p><strong>VPC reachability Analyzer</strong>.</p><p>This is one of my favourite tool to troubleshoot a network issue on AWS because of it’s simplicity. The tool basically checks all the possible way between source and target points without sending any data to the medium and describe us where exactly the traffic is blocked!.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71784da80bbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>