<?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 Biku Shah on Medium]]></title>
        <description><![CDATA[Stories by Biku Shah on Medium]]></description>
        <link>https://medium.com/@bikulinuxer?source=rss-a1d1b3089041------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ExagVf4e-m07TLkFPktZrQ.jpeg</url>
            <title>Stories by Biku Shah on Medium</title>
            <link>https://medium.com/@bikulinuxer?source=rss-a1d1b3089041------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:12:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bikulinuxer/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[Effortless EC2 Management : Unleashing Automation with AWS SSM Resource Scheduler]]></title>
            <link>https://medium.com/@bikulinuxer/effortless-ec2-management-unleashing-automation-with-aws-ssm-resource-scheduler-9f27b089222a?source=rss-a1d1b3089041------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f27b089222a</guid>
            <category><![CDATA[aws-eventbridge]]></category>
            <category><![CDATA[lambda]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[ec2]]></category>
            <category><![CDATA[aws-ssm]]></category>
            <dc:creator><![CDATA[Biku Shah]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 00:00:35 GMT</pubDate>
            <atom:updated>2024-08-28T06:27:43.621Z</atom:updated>
            <content:encoded><![CDATA[<h3>Effortless EC2 &amp; RDS Management : Unleashing Automation with AWS SSM Resource Scheduler &amp; Instance Scheduler</h3><p>My current role as<strong> Cloud DevOps Engineer </strong>requires managing infrastructure for multiple clients, many of whom still run their workloads on EC2 instances &amp; RDS. A significant portion of my job involves optimizing these resources to ensure efficiency and cost-effectiveness. One common task is the start/stop management of EC2 instances &amp; RDS, which is crucial for reducing costs, especially for instances that aren’t needed 24/7.</p><p>Previously, automating start/stop actions of servers required complex setups with <strong>Lambda</strong>, <strong>EventBridge</strong>, and <strong>Boto3</strong>. However, <strong>AWS Systems Manager Resource Scheduler</strong> &amp; Ihas revolutionized the process, providing a simple and streamlined way to manage instances across multiple AWS Regions and accounts, saving time and resources.</p><blockquote><strong>The Challenges of Traditional Automation</strong></blockquote><p>Previously , we used to Automate EC2 instance start/stop actions with Boto3, Eventbridge , Lambda. i.e</p><ul><li>Set up an AWS Lambda function using Boto3 in Python.</li><li>Configure Amazon EventBridge to trigger the Lambda based on a schedule.</li><li>Define the code in the Lambda to start/stop specific EC2 instances.</li><li>Automate instance management, leveraging EventBridge and Boto3.</li></ul><p>This traditional approach posed significant challenges. Setting up and maintaining automation using Lambda, EventBridge, and Boto3 required substantial configuration efforts and charges. Managing schedules across various Regions and accounts added complexity, leading to maintenance overhead and potential misconfiguration.</p><blockquote><strong>Note: </strong>We’ll be using <strong>Instance Scheduler </strong>for RDS management since<strong> Resource Scheduler </strong>only works for EC2.<br>In the coming days,I ‘ll be appending the <strong>Instance Scheduler </strong>steps in this same<strong> blog.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*josBqtgK0smOXazB3zV8bA.jpeg" /></figure><h3>AWS SSM Resource Scheduler</h3><p><strong>AWS System Manager service </strong>is the core<em> DevOps Tool</em><strong> </strong>that has multiple sub-services(features) that enable to manages and automates the resources<strong> </strong>either on the Cloud or on-premises at scale . One of its sub-service is “<strong>Resource Scheduler”</strong>. Resource Scheduler redefines instance management. It offers a user-friendly interface, simplifying the process of scheduling start/stop actions. With centralized management and tag-based targeting, Resource Scheduler streamlines automation, leaving behind the complexities of the traditional method. It leverages <strong>CloudFormation</strong> service to automates the whole process in the background.</p><h3>Steps:</h3><p>Search<strong> AWS SSM </strong>on search bar and then open it . After that click on <strong>Quick Setup .</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/989/1*FKmu7HTdeh2PkdS4Dbv1IA.png" /></figure><p>Scroll down the page, we can find the <strong>Resource Scheduler</strong> .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iTLbujFrpn884ng_gjVHSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vIIOWzRe1VR8yl8D-kBGMA.png" /></figure><p>Now, Open the <strong>EC2 Console </strong>and note down the Tags Key and Value attributes of the required instances that we’ll be using at Scheduler Configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V95wSKnJE4qyY_F5PY2JCQ.png" /></figure><p>Then , On the Scheduler page, paste the Tags key-value pair on the required section.<strong> Resource Scheduler</strong> starts/stops the instances based on the tag values.</p><p>And select the required Time zone and scheduled days where we want to perform the Schedule operation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kRJyLbE0eobDxEyHA4XPJw.png" /></figure><p>Here,Select the required times when we want to start/stop the instances and choose the required Region where this Scheduler Configuration will be applied.</p><p>Then , at the end we can see the summary of the Scheduler Configuration and click on <strong>Create . </strong>This will create our scheduler configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w6qdQPK5wxYzD68DVIpeRg.png" /></figure><p>After the creation of Scheduler, we can see the various details of the it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fs5_n2_PsI__7gNz33-Pew.png" /></figure><p>Currently , the instance is in Stopped State.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6RGHVdzjr0m_KKUqCwbrDA.png" /></figure><p>We have schedule the that will start the the instance at 11:30 AM . Here, we can see the Scheduler has started the instance at 11:30 AM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eRDd7kxsYngZ_n5niV7Gew.png" /></figure><h3>Conclusion:</h3><p>AWS Systems Manager Resource Scheduler is a powerful tool that simplifies EC2 instance management by replacing complex setups with a user-friendly interface. With just a few clicks in the AWS SSM console, you can schedule instance actions and control them across multiple AWS Regions and accounts with ease.</p><p>The simplicity and efficiency of Resource Scheduler are truly impressive. As you watch it execute actions flawlessly, you’ll see how it can help you optimize your cloud operations and save time and money.</p><p>⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f27b089222a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS VPC Endpoints service “Security to Saving”]]></title>
            <link>https://medium.com/@bikulinuxer/unlocking-security-cost-efficiency-with-aws-vpc-endpoints-8f1e86eab7bc?source=rss-a1d1b3089041------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f1e86eab7bc</guid>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[private-connectivity]]></category>
            <category><![CDATA[aws-networking]]></category>
            <category><![CDATA[vpc-endpoint]]></category>
            <category><![CDATA[aws-privatelink]]></category>
            <dc:creator><![CDATA[Biku Shah]]></dc:creator>
            <pubDate>Sun, 08 Oct 2023 00:01:40 GMT</pubDate>
            <atom:updated>2024-10-02T10:06:06.244Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>The Challenge: Costly and Constrained Data Processing &amp; Transfers via NAT Gateways:</strong></blockquote><p>Most of the companies has their workload running on EC2 instances in the private subnets that tirelessly push many hundreds GBs of data daily to Amazon S3 through a NAT gateway for the Backup and Resilient purposes. This seemingly efficient setup comes with its drawbacks-availability risks, bandwidth constraints, and hefty costs. AWS charges huge fees for data processing and egress traffic of <strong>NAT Gateway</strong> , especially burdensome for high-volume data transfers like those to Amazon S3.</p><p>“To put this into perspective, transferring <strong>10 TB</strong> of data from EC2 to S3 through a NAT Gateway per month can incur costs nearly amounting to<strong> $650</strong> per month due to data processing fees and egress traffic charges of NAT Gateway .”</p><p>Here, comes the <strong>S3 VPC Gateway Endpoint </strong>as your saviour which cost you <strong>$0</strong> for the same thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*jWABn6eaARLTznrj8lCOvg.gif" /></figure><blockquote><strong>Enter VPC Endpoints: A Paradigm Shift in AWS Connectivity</strong></blockquote><p>In a world of networking problems, <strong>AWS VPC endpoints</strong> shine bright. They are virtual devices, that are horizontally scaled, redundant, and highly available VPC components that allow communication between AWS services in the VPC without imposing availability risks or bandwidth constraints on network traffic.</p><p>In simplicity</p><p>These endpoints establish secure, private connections between your VPC and AWS services without relying and requiring on Internet gateways, NAT devices, or complex VPN configurations and Direct Connect . They eliminate the need for public IP addresses, enabling seamless communication between VPC instances and various AWS services.</p><p>In fact , Traffic between your VPC and the other service does not leave the Amazon network.(All the traffic flows within AWS Internal Infrastructure without traversing the Public Internet)</p><blockquote><strong>Understanding VPC Endpoint Variants: Interface and Gateway</strong></blockquote><ul><li><strong>Interface Endpoints:</strong> These horizontally scaled, highly available virtual devices within your Amazon VPC facilitate smooth communication with supported AWS services and its powered by the AWS PrivateLink service(“ We will learn more about<strong> AWS PrivateLink</strong> in another blog<strong>”</strong> ) and it incur charges . It’s quite advanced than Gateway endpoints and even allow you to connect your VPC to resources outside of the AWS like On-prem networks, peered VPCs or through the TG without going through the open public connectivity using Direct Connect.</li></ul><p>“Behind the scene , it utilizes elastic network interfaces (ENIs) within your AWS VPC CIDR that serve as the entry point for traffic destined to AWS services like EKS, ECS, Lambda, EC2.</p><ul><li><strong>Gateway Endpoints:</strong> Serving as routing targets, they efficiently direct traffic within your route tables to specific AWS services like Amazon S3 and Amazon DynamoDB. It don’t incur charges.</li></ul><p>Below is the Traditional Networking Architecture that displayed how the data is transferred from Ec2 to S3</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xljaS5hH3Svjyc1DCKPsOg.jpeg" /></figure><p>Fig: Traditional Networking Architecture</p><p>This is the Networking Architecture that displayed the use of VPC Endpoint and how it simplified the data transferred from Ec2 to S3</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kM3x-j4VDI1j5ZZj1WxYpQ.jpeg" /></figure><p>Fig: VPC Endpoint Networking Architecture</p><h3>Steps:</h3><p>Here, we’ll be learning step by step ways to setup <strong>S3 VPC Gateway Endpoint .</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/48/1*FViCKezfHmbD7D1JoSqOTA.png" /></figure><p>We’ve one ec2 instance running on Private Subnet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_mJTtueJs6l3uzrS8z6mw.png" /></figure><p>This is the routes details of the Private Route table. Here, we can see that all the traffic associated with this Route Table goes through the NAT Gateway and then to Internet Gateway .( <strong>Note</strong>: Here, NAT Gateway is provisioned on Public Subnet)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yjb-Y-IjE3xVWWz7ehUKdA.png" /></figure><p>Below is the routes details of the Public Route table. Here, we can see that all the traffic associated with this Route Table goes directly through the Internet Gateway .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NREeTOsSsV8Cnj84VK9KBQ.png" /></figure><p>Now, Lets create Endpoint, so that all the traffic from the Instance goes through the Endpoint instead of NAT Gateway or Internet Gateway.</p><p>Click on <strong>Endpoints</strong> under Virtual Private Cloud .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/311/1*ZFiQoNQzP9R0Dqy3ibxabw.png" /></figure><p>Then , click on <strong>Create endpoint .</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XdzwZx0EJU1XqiwwdOUYAg.png" /></figure><p>Configure the Endpoint as our requirement and launched in on Private Subnet and choose the <strong>S3 Gateway Endpoint</strong> .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R2LpYxxlnTpN5Ed6WbAK7Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*582kQ-ZfKw3PwlW1-WNu2Q.png" /></figure><p>We can setup the endpoint policy for the endpoint for the restriction and compliance purpose. And then , Click on <strong>Create endpoint ,</strong> which will finally create the<strong> S3 Gateway Endpoint.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a2RJH_sxUUHAS8mUtcKBTw.png" /></figure><p>From the endpoint console, we can see the various configuration setting assigned with it .We can change the Route table, Policy, Tags for Endpoint at any time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p8KlDNYeuS-jkP2wqSzTdQ.png" /></figure><p>Now, when we navigate to Private Route table, we can find that the S3 endpoint is automatically added on the route . This will make sure that every traffic to s3 will goes through endpoint instead of NAT Gateway or Internet Gateway.</p><p>So,Everytime we push the data from EC2 to S3, it goes through the VPC endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5ANBIxQEJOaascOwrl_0Q.png" /></figure><p>At last, make sure to attach necessary permission and role to EC2 , so that it can performed required action on S3.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/1*-RxpwwFIaDy4M1xAvvpoYQ.png" /></figure><p><strong>Note:</strong> Never hard-code credentials on the EC2 i.e. Always use short-live credentials like Roles ,instead of IAM user access keys.</p><h3>Conclusion:</h3><blockquote>AWS VPC Endpoints provide a secure and efficient way to connect your Virtual Private Cloud (VPC) with various AWS services. By establishing direct connections between your VPC and the desired service, VPC Endpoints eliminate the need for public internet access(here, <strong>all the traffic flows within the AWS Internal Infrastructure</strong>) , enhancing security and reducing potential risks.</blockquote><p>By incorporating VPC Endpoints into your AWS infrastructure, you can experience several benefits. These include enhanced security, improved performance, simplified network architecture, and potential cost savings. With VPC Endpoints, your resources can securely access AWS services without exposing them to the public internet, ensuring a highly secure and isolated environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*Zw0uNEakwbjQUt0HjN3ItA.gif" /></figure><p>For more details about the <strong>Networking Data Cost </strong>and VPC Endpoint then visit this :</p><ul><li><a href="https://docs.aws.amazon.com/whitepapers/latest/aws-privatelink/what-are-vpc-endpoints.html">What are VPC endpoints?</a></li><li><a href="https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html">What is AWS PrivateLink?</a></li><li><a href="https://catalog.us-east-1.prod.workshops.aws/workshops/25daa7f1-11a5-4c96-8923-9b0e333acc59/en-US">Workshop Studio</a></li><li><a href="https://aws.amazon.com/blogs/architecture/overview-of-data-transfer-costs-for-common-architectures/">Overview of Data Transfer Costs for Common Architectures | Amazon Web Services</a></li><li><a href="https://aws.amazon.com/blogs/architecture/reduce-cost-and-increase-security-with-amazon-vpc-endpoints/">Reduce Cost and Increase Security with Amazon VPC Endpoints | Amazon Web Services</a></li><li><a href="https://docs.aws.amazon.com/whitepapers/latest/aws-privatelink/aws-privatelink.html">Securely Access Services Over AWS PrivateLink</a></li></ul><p>⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍⁌⁍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f1e86eab7bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migration Madness: Say Goodbye to On-prem Infras and Embrace Cloud Power]]></title>
            <link>https://medium.com/@bikulinuxer/migration-madness-say-goodbye-to-on-prem-infras-and-embrace-cloud-power-aae69d943706?source=rss-a1d1b3089041------2</link>
            <guid isPermaLink="false">https://medium.com/p/aae69d943706</guid>
            <category><![CDATA[aws-mgn]]></category>
            <category><![CDATA[data-transfer]]></category>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[modernization]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <dc:creator><![CDATA[Biku Shah]]></dc:creator>
            <pubDate>Tue, 12 Sep 2023 00:11:55 GMT</pubDate>
            <atom:updated>2025-08-08T11:37:04.595Z</atom:updated>
            <content:encoded><![CDATA[<h3>Migration Madness: Say Goodbye to On-prem Infras and Adopt Cloud Power</h3><p>High costs , poor performance, vague security, zero resilient of your On-premises infrastructure are the worries of many companies and You’re not alone.</p><p>To address those issues , many businesses are turning to “Cloud provider” mainly <strong>AWS</strong>(Amazon Web Service) . AWS offers a comprehensive set of data transfer services to provide the right solution for any data migration project. The level of connectivity is a major factor in data migration, and AWS has offerings that can address your hybrid cloud storage, online data transfer, and offline data transfer needs.</p><p>Your workload will be highly resilient,optimize,high performance , secured and cost-optimized after migrating to AWS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*UT4KZ1jNqxtUAMz_Swytlw.png" /></figure><blockquote><strong>Note:</strong> “We can migrate just the data with the help of <strong>AWS DataSync</strong>, <strong>AWS</strong> <strong>Storage</strong> <strong>Gateway, AWS</strong> <strong>Transfer</strong> <strong>Family</strong>, <strong>AWS Snowfamily</strong> or the entire servers, including operating system, applications, data, configurations &amp; settings with the help of <strong>AWS Application Migration Service (AWS MGN) , AWS Elastic Disaster Recovery Service( AWS DRS ) , AWS Server Migration Service(AWS SMS)</strong>, <strong>Database Migration Service (AWS DMS), VM Import/Export”</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/1*JltMZpVjXqK4WpobhASYxw.png" /></figure><p><strong>“</strong>One more thing to consider, If a server consists of only database, ,then its recommended to use <strong>AWS Database Migration Service(AWS DMS</strong>) and if a server consists of both application and database, then its prefer and recommended to use <strong>Application Migration Service(AWS MGN).”</strong></p><p>In this blog, we’ll be discussing how to migrate(Lift and Shift) applications, servers, databases to AWS from On-premises Environment using <strong>AWS Application Migration Service(AWS MGN).</strong></p><h3><strong>Introduction:</strong></h3><p>AWS Application Migration Service (AWS MGN) is highly recommended solution to simplify and accelerate the migration of applications, servers, databases to AWS. It enables continuous block-level replication of live servers such as physical, virtual (Nutanix, VMware vSphere , Microsoft Hyper-V), or cloud-based servers ensuring minimal downtime and data loss during the migration process without necessitating any changes to the applications, their underlying architecture and the good thing is that recovered servers with Windows or Linux run natively on AWS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qFg2VGJlxPxoDOq1dYCohQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*1o_OUirQvpy4z0dG_T6nMQ.png" /></figure><h3>Steps :</h3><p>First of all we need to make sure that the On-premises Servers are running with x86 architecture processor with supported OS and have port 443 and 1500 opened on both On-premises Servers and on AWS side. Also make sure , the source server must have atleast 2GB of free root space and 300 MB of free RAM .Now , create an IAM user with all the required permission for accessing,installing and migrating the servers.</p><p>And then</p><p>•<strong>Initializing the Service:</strong></p><p>Begin by initializing the AWS Application Migration Service for the desired AWS region where you plan to execute the migration. This initialization paves the way for configuring replication settings.</p><p>Search<strong> AWS MGN</strong> on the search bar, navigate to the desired region ; and then click on <strong>Get Started</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9V_TBo8nW3D7AkBqISk_6w.png" /></figure><p>Now, Click on Set up Service button which initialize the AWS MGN service on the selected region.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*1DpUDPDA8h7YQd943g1RSA.png" /></figure><p>•<strong>Configuring Replication Templates:</strong></p><p>Using the AWS Management Console, configure the replication template settings. These settings dictate how data will be replicated from On-prem to AWS . MGN utilizes these templates to manage a staging area subnet comprising essential EC2 servers functioning as replication servers. You have the flexibility to modify this template for individual or groups of source servers at any time.Same thing , apply for Launch Setting Template too.</p><p>Under the<strong> Settings</strong>, Click on <strong>Replication Template</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/292/1*5BPYwPEOr3xxaGIi2uoxOw.png" /></figure><p>We can edit the<strong> Launch Template</strong> as our desired requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-UvKTUGQ-XWrM3scZOEdJA.png" /></figure><h4>•<strong>Installing Replication Agent:</strong></h4><p>Install the AWS MGN replication agent on your selected on-premises or cloud source servers. Execute the agent with administrative or higher privileges. During setup, provide the AWS credentials and the target AWS region. This initiates the replication process.</p><p>Now, click on<strong> Add Server </strong>on AWS MGN dashboard<strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qUhNx1onwUyLMguPb-dcpg.png" /></figure><p>Inour case, its Linux Server, so I just SSH into the server and then follow the commands showed on the picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*ERgBi-Qt7T8tTyzlgtyXug.png" /></figure><p>Now, this will start downloading and installing the AWS Replication Agent on Source server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*enocqsrjQ336cGUElFqldw.png" /></figure><p>After the successful installation of Replication Agent , it will start the sync(replication) process between the Source Server and the AWS .</p><p>•<strong>Initiating the Initial Sync and Cutover Process:</strong></p><p>Once the initial synchronization is started, we can see the status of source server .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*84DQc0skzZnVDRS2MGwyrA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LzQ9TD0MrMVdjr39zm2e8g.png" /></figure><p>We can track the progress of your migration and identify any issues while launching Test/cutover instance by looking through the various stages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z-4xNFTyZPkXLSW2m6HYbw.png" /></figure><p>After the initial sync is completed , we can configured the <strong>launch template</strong>. Every source server added to AWS MGN has launch settings that control actions performed after the server is launched in AWS. These settings are created automatically based on this default launch template, which can be modified at any time. We can also choose to modify the launch template for an individual source server.</p><p>Make sure Source server is in <strong>Healthy State </strong>as shown in the picture with Ready for<strong> testing value </strong>before launching the Test Instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dVJ6NF8VxuLnyuFqCDMJvA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TMNqpyq952kFlMuV558KLA.png" /></figure><p>Now, we can proceed with launching the cutover/test instances. These instances are crucial in validating whether they operate seamlessly with up-to-date data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ailyJAPaG3jwm8RaKDOOXg.png" /></figure><p>After, we click on <strong>Launch Test Instance,</strong> it will start launching the Test ec2 instance and also we can see the details of these job by click on the Job ID. After it finishes launching test instance, we can see the change in the Lifecycle from the<strong> Ready for testing</strong> to <strong>Test in Progress.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c7E70yQviBZa3ReIc8ly7Q.png" /></figure><p>Also, we can find the launched ec2 server in the ec2 console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D52tVqsBHdZOOY37uKEZaw.png" /></figure><p>We can also find the <strong>Conversion Server </strong>while doing the migration.It converts the disks to boot and run on AWS. Specially it makes bootloader changes, injects hypervisor drivers and installs cloud tools on Test/Recovery Instance and then get automatically terminated.</p><p>Once verified, finalize the cutover process and retire the source server by clicking on the following commands like<strong> Launch Cutover Instances</strong> and then on the <strong>Finalize Cutover .</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FerVMCtPyAMSu39tMNoRrQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*66qFYie6izcIQjJqUvPTxg.png" /></figure><p>Here, we can see the changes in the Lifecycle for every action.</p><p><strong>Note</strong>: When we launch the Cutover Instances, it will overwrite or terminate the instances provisioned during the Test Process and launch the fresh new Instances.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y0R5kmqAD9bDZpdxR6lKNA.png" /></figure><p>After cutover Instances works as expected then we can finalize the cutover process which will terminate all the resources that was created during the migration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/554/1*NAEf9zh-S7IIHn3zIqxogg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J3tz_Jw62NruSIhKpW-uZA.png" /></figure><p>Also, we can see the Lifecycle changes to <strong>Cutover Complete</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*64eLUVYmuDbYtYSfT1p71g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*76r_8LghOs__bHDfYkubYg.png" /></figure><h3>Configuring a post-launch template:</h3><p>AWS recently launched the feature for AWS MGN called <strong>Post-Launch Template</strong> .This post-launch template controls which post-launch actions will be executed when launching new instances. These settings are created automatically for each server based on the post-launch template and can be modified at any time. You can also modify the post-launch settings for any individual source server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yWrWXaAaopSPpe0ZYlJRJg.png" /></figure><h3>Conclusion:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*G9DNmQXWWP-WXrPMx-tsTg.gif" /></figure><p>The AWS Application Migration Service simplifies what could be a complicated process by offering a comprehensive suite of tools, automation, and support ensuring minimal downtime, reduced risk, and optimized performance post-migration. It’s your ally in moving your apps to the cloud with ease. Embrace it, and you’ll find your applications thriving in the AWS environment, giving you more bandwidth for innovation and less worry about the migration process.</p><p>In the next chapter, we’ll be learning about the <strong>AWS DRS (Elastic Disaster Recovery Service) </strong>, which is the extension of the AWS MGN service .</p><p>⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍ ⁌⁍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aae69d943706" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>