Skip to main content

Move classic EC2 instance into VPC

  1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
  2. Click Instances in the navigation pane.
  3. On the Instances page, right-click your running instance and select Create Image.
  4. Fill in a unique image name and an optional description of the image (up to 255 characters), and click Create Image.
  5. Go to the AMIs page and view the AMI's status. While the new AMI is being created, its status is pending.
  6. It takes a few minutes for the whole process to finish.
  7. Once your new AMI's status is available, go to the Snapshots page and view the new snapshot that was created for the new AMI. Any instance you launch from the new AMI uses this snapshot for its root device volume. You could update your Auto Scaling group with the new AMI, however we will do this as part of the AWS CloudFormation step.

Important information:
  1. We have to wait 30 mins after Lauch, for Password configuration.
  2. The password is the same as for the instance from which you created the AMI, unless this setting was modified in the EC2Config service settings.
  3. You will not use Same IP Address, becuase this IP address is allocated to classic EC2 pool and new instance will require an IP of VPC pool.
  4. After migration we will get all the informations same as it was in previous instance.
why migration required?
  1. classic EC2 not supported Multiple IPs
  2. classic Ec2 in not secured as VPC EC2, as classic Ec2 instance is touch with direct environment.

 

Comments

Popular posts from this blog

IIS, There was an error when trying to connect. Do you want to retype your credentials and try again?

IIS 8 error on windows server 2012 insufficient permission There was an error when trying to connect. Do you want to retype your credentials and try again? Details: Filename: \?\C:Windows\system32\inetsrv\config\redirection.config Error: Cannot read configuration file due to insufficient permissions screenshot: Solution: Steps to short out this issue: go to C:\Windows\Microsoft.Net\Framework64\v2.0.50727\CONFIG\machine.config here you got the redirection tag like the below <configurationredirection enabled="true" password="[enc:IISCngProvider:X0ObCWwZ4+PrTHiFVPtzFeCcL8u5P6KUOYfo1/0QrgZWATA5pKWqHvD8nL2crNJKyyqr4z/rBdLPjdRcaLxAMMj4l+lvp5EXXKSXueolvyGa34F4QZfbBVCM6oVNcq3M368TOTVjJv4POVFQWvu0MDVlGgReglXB+Lw5BRI4Htw=:enc]" path="C:\Windows\System32\inetsrv\config\import\" username="Administrator"> </configurationredirection"></li"> you need to change this to <configurationRedirection /> Th...

Plesk - Upgrade the .net Framework to 4.7.2 OR 4.8

 Steps to Upgrade the .net Framework to 4.7.2 OR 4.8 1. First Download the .NET Framework from https://dotnet.microsoft.com/download/dotnet-framework   2. Install on the Server. 3. Login to the Plesk and go to "Tools & Settings" > "Server Components" and refresh the components using the refresh button 4. After update, it will reflect in "Web Script" section at the server component page. All done!!!