<?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 Rajeev Ranjan on Medium]]></title>
        <description><![CDATA[Stories by Rajeev Ranjan on Medium]]></description>
        <link>https://medium.com/@mtvwhydzx?source=rss-11ef0133b053------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*syJw6UmsT6h1V18Wo1ba-g.jpeg</url>
            <title>Stories by Rajeev Ranjan on Medium</title>
            <link>https://medium.com/@mtvwhydzx?source=rss-11ef0133b053------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:40:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mtvwhydzx/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[Amazon EC2 Basics — Instance Types]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Article 2&#xA0;: This is in continuation of my Article 1 ( https://medium.com/@mtvwhydzx/amazon-ec2-ami-basics-7195607407d7 ). In this&#xA0;, I will&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@mtvwhydzx/amazon-ec2-basics-instance-types-d312c3f41577?source=rss-11ef0133b053------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@mtvwhydzx/amazon-ec2-basics-instance-types-d312c3f41577?source=rss-11ef0133b053------2</link>
            <guid isPermaLink="false">https://medium.com/p/d312c3f41577</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws-ec2]]></category>
            <category><![CDATA[cloud-services]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Rajeev Ranjan]]></dc:creator>
            <pubDate>Tue, 03 Sep 2024 09:01:57 GMT</pubDate>
            <atom:updated>2024-09-03T09:01:57.091Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Amazon EC2 — AMI Basics]]></title>
            <link>https://medium.com/@mtvwhydzx/amazon-ec2-ami-basics-7195607407d7?source=rss-11ef0133b053------2</link>
            <guid isPermaLink="false">https://medium.com/p/7195607407d7</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[amazon-ec2]]></category>
            <category><![CDATA[cloud-services]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Rajeev Ranjan]]></dc:creator>
            <pubDate>Sat, 31 Aug 2024 12:43:39 GMT</pubDate>
            <atom:updated>2024-08-31T12:43:39.193Z</atom:updated>
            <content:encoded><![CDATA[<h3>Amazon EC2 — AMI Basics</h3><p><strong>Article 1 — This is part of the series of article I am going to publish about Amazon EC2:Elastic Compute Cloud</strong></p><p>The EC2 service can be broken down into the following components:</p><blockquote>Amazon Machine Images, or AMIs</blockquote><blockquote>Instance types,</blockquote><blockquote>Instance purchasing options</blockquote><blockquote>Tenancy</blockquote><blockquote>User Data</blockquote><blockquote>Storage options, and</blockquote><blockquote>Security</blockquote><p>In this article we will be looking into AMIs, Amazon Machine Images.</p><p>AMIs are essentially templates of pre-configured EC2 instances which allow us to quickly launch a new EC2 instance based on the configuration defined within the AMI.This prevents us from needing to install an operating system ( Amazon Linux, macOS, Ubuntu, and MS Windows, among others )or any other common applications that we might need to install on a number of other EC2 instances.</p><p>AMIs can be categorized in 4 ways —</p><blockquote>AWS-managed AMIs</blockquote><blockquote>Custom-managed AMIs</blockquote><blockquote>AMIs from AWS Marketplace</blockquote><blockquote>Community AMIs ( public AMIs)</blockquote><p>As mentioned earlier , AWS provides a large number of AMIs covering different operating systems ( known as AWS-managed AMIs).In addition to this we can also create our own AMIs to speed up the deployment process.</p><p>For example, we would start by selecting and AWS AMI, perhaps Amazon Linux.And. then, once it is up and running, we may need to install a number of our own custom applications and make other specific configuration changes.Now let’s say we need a second server to perform the same functionality.In this case we have two options. First option would be to go through the same process of selecting the Amazon Linux AMI, and again manually installing the applications and making our configuration changes. Or, second option would be to once we have made those changes on the first instance, we would then simply create a brand new AMI or template of that instance with all our applications installed and configuration changes already made.Then, if we need another instance of the same configuration, all we need to do is select our custom AMI as the base image for a new instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vvGx-xG_YsMhfoXPsibgAw.png" /><figcaption>AWS-Managed AMI vs Custom-Managed AMI</figcaption></figure><p>As we see in the above example the approach adopted in option 2 has many benefits and especially comes in handy when implementing auto-scaling, where multiple instances of our baseline configuration may need to be spun up quickly to meet increasing levels of demand.</p><p>Now in addition to both AWS-managed and our own custom-managed AMIs, we could also select an AMI from the AWS Marketplace.The AWS Marketplace is essentially an online store that allows us to purchase AMIs from trusted vendors like Cisco Systems, F5, Palo Alto Networks, and others.These vendor AMIs have specific applications and configurations already made, such as instances that are optimized with built-in security and monitoring tools.</p><p>We can also choose from Community AMIs, which are public AMIs that can be created and shared by anyone.</p><p>We will continue with further beginner concepts in Article 2……..</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7195607407d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS : Security Control Policies]]></title>
            <link>https://medium.com/@mtvwhydzx/aws-security-control-policies-486ba5efdf7f?source=rss-11ef0133b053------2</link>
            <guid isPermaLink="false">https://medium.com/p/486ba5efdf7f</guid>
            <category><![CDATA[aws-security-specialty]]></category>
            <category><![CDATA[aws-organizations]]></category>
            <category><![CDATA[aws-scp]]></category>
            <category><![CDATA[aws-security]]></category>
            <category><![CDATA[cloud-security]]></category>
            <dc:creator><![CDATA[Rajeev Ranjan]]></dc:creator>
            <pubDate>Thu, 14 Mar 2024 09:38:45 GMT</pubDate>
            <atom:updated>2024-03-14T09:38:45.187Z</atom:updated>
            <content:encoded><![CDATA[<h3>AWS : Security Control Policies</h3><p>Service Control Policies are feature of AWS Organisations ( AWS Organisation is a product to manage multiple AWS accounts in cost effective way, with little to no management overhead) which can be used to restrict AWS acccounts.</p><p>Note : Understanding of AWS Organizations is important to go through the contents of this article — <a href="https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html">https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html</a></p><p>SCP is POLICY DOCUMENT ( Json document) which can be attached as a whole by attaching them to the Root Container or to one or more Organization Units ( OUs).It can also be attached to individual AWS Accounts.One thing to note is that on whatever entity it is attached to , the underlying entities will also get impacted. For example , if a SCP is attached to the Root Container within an AWS Organization then it impacts all the OUs inside that Root Container . Another example would if a SCP is attached to an Organisational Unit ( OU), then it impacts all the AWS accounts inside that OU and all other OUs under the main OU.</p><p>It is important to note that Management Account is never affected by SCP, even if Management Account is part of OU or Root Container ( to which SCp is applied).Management Account is the only account in AWS Organizations which cannot be restricted using SCPs.</p><p>SCPs can be called as Account Permission Boundaries.They limit what an AWS account ( including Root Account User) can do.</p><p>SCPs “DON’T GRANT” any permissions.They are just boundaries.They define the limit of what is and what is not allowed within the account.We still need to give “IDENTITIES” within that AWS account permission to AWS resources, but SCPs will limit the permissions that can be assigned to individual identities.</p><p>SCPs can be used in two ways : ALLOW LIST &amp; DENY LIST.</p><p>DENY LIST — In AWS by default when we enable SCP , DENY LIST is there.As soon as SCP is enabled AWS applies a default policy , which is called FULL ACCESS POLICY. This policy is applied to the organization and all OUs within that organization.This Policy means that in the default implementation, Service Control Policies have no effect since nothing is restricted.Now in this default we need to add services which we want to deny ( explicit deny).One of its benefits is low admin overhead — with ever changing and enhancement of services in AWS world, we don’t to keep track os all the services, we just need to take care of what we don’t want identities/accounts to access and add those services in deny.</p><p>ALLOW LIST — This is implemented in two part architecture.One part is to remove the AWS FULL ACCESS POLICY ( which means only Implicit Default Deny is active).Then we need to add any services which we want to allow into a new SCP policy.It is more secure compared to Deny List as in this it is explicitly mentioned which services can be allowed access for users in those accounts.One of the cons is it has got much more Admin Overhead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*qkiM40cegRgIutzNKxYR4A.png" /><figcaption>Depiction — What is actually allowed after implementation of Identity based policy and SCP</figcaption></figure><p>Links for SCP —</p><p><a href="https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html#">https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html#</a></p><p><a href="https://learn.cantrill.io/p/aws-certified-security-specialty">https://learn.cantrill.io/p/aws-certified-security-specialty</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=486ba5efdf7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>