I’ve been using Amazon Lightsail for the past six months to host my WordPress blog site. I’m happy with Lightsail – I have full control over both my Linux instance OS and my WordPress blog site administration but I don’t have to deal with the headaches (or the price) of a full-blown EC2 instance.
A few months back I wrote a blog post listing the pros and cons of Amazon Lightsail. Why would one use Lightsail versus Amazon EC2? Within the Amazon ecosystem, Lightsail is the cheapest and easiest to use platform if the goal is to get a Linux instance and simple application up and running in AWS.
Think of Lightsail as a lightweight version of AWS EC2. There really is no learning curve to get started on Lightsail – just pick some basic options and launch the instance. The Lightsail pricing structure is straightforward and predictable. Both the pricing and ease of use make Lightsail as a hosting platform attractive for bloggers and developers to get started on Amazon and the experience is quick, cheap, and easy.
With this simplicity comes limitations. A lightweight version of an Amazon EC2 instance doesn’t have the full compliment of every EC2 feature. This makes sense – Lightsail is geared towards bloggers and developers and is kept separate from EC2. A lightweight version works fine when starting a project but what if we hit a point where the advanced networking features of a VPC are required? Or autoscaling groups? Or spot instances?
Fortunately this has changed as of AWS re:Invent 2018 – we can now convert a Lightsail instance into an EC2 instance using Lightsail instance snapshots! I’ll walk through the process in this blog and show some of the strategies and considerations needed to move a Lightsail instance out of the limited Lightsail environment into the feature-rich EC2 environment.
Why should I move my instance out of Lightsail?
Let’s face it – we aren’t going to move our instance out of Lightsail unless we have to. Lightsail is the cheapest option for running an instance in AWS. Instance monthly plans start as low as $3.50/month as long as the instance stays within the resource bounds of the pricing plan.
Adding more horsepower to a Lightsail instance is also not a reason to move to EC2. Lightsail allows upgrading an instance to use more resources (for a price) – just use an instance snapshot to clone the existing instance to a new plan with more resources (the application inside the instance will persist using instance snapshots).
But what if we want to to take our application out of the Lightsail environment and place it into more of a production environment? What if we have found limitations in Lightsail and found that our applications needs to reside in EC2 to take advantage of all the available EC2 features? What if we need web-scale features, advanced networking, and access to services that are limited in the Lightsail environment? In that use case we need to move to EC2.
AWS terminology and concepts
Before we go through the conversion process, let’s clear up some terminology and concepts that will help illustrate the task.
Instance – this is just Amazon’s fancy word for a virtual machine. The term “virtual machine” probably sounded too much like VMware so Amazon calls virtual machines “instances”. An instance is a virtual machine but runs on Amazon’s proprietary hypervisor environment.
Lightsail instance – An AWS image running in the Lightsail environment. Lightsail is separate from other AWS environments and runs on a dedicated hardware stack in selected data centers.
EC2 instance – An AWS image running in the EC2 environment. EC2 is completely separate from Lightsail and runs on its own hardware and has many more management and configuration options.
Instance snapshot – A snapshot of either a Lightsail or EC2 instance that not only includes the state of the virtual machine but also a snapshot of the attached OS disk.
Disk snapshot – Unlike an instance snapshot, a disk snapshot only tracks changes to the physical disk attached to the virtual machine. No virtual machine state is captured so this type of snapshot is only good for keeping track of block disk data, not for the virtual machine state.
CloudFormation Stack – a template that tracks AWS resources associated with an AWS service through the use of a template. CloudFormation can be used to define the configuration details of an AWS instance.
Key pair – quite simply, a .PEM file used to connect to an instance. We can’t connect to an instance remotely (SSH, Putty) without a .PEM key pair.
AMI – a preconfigured template that is also associated with an EBS snapshot and is used to launch an instance with a specified configuration
How exporting an instance snapshot works
Instance snapshots are portable. When an instance snapshot is taken of a Lightsail instance, the OS and disk state are stored to flat files and kept in some form of S3 object storage. The flat files can be shared within Lightsail to create a new instance from the same snapshot – we can even assign more CPU or RAM to an instance snapshot to upgrade the instance to something faster.
With the latest AWS Lightsail EC2 instance snapshot export feature we can now take the same Lightsail snapshot and share it with AWS EC2 infrastructure. This allows EC2 to import the Lightsail snapshot to clone our Lightsail instance and spin it up in EC2. Lightsail snapshots were always portable but the recent EC2 export feature enabled sharing of snapshots outside of Lightsail.
Behind the scenes Amazon uses CloudFormation to enable this conversion process. Which simply means we automatically get a CloudFormation stack (or template) created when we move our Lightsail instance snapshot out to EC2. But we don’t have to worry at all about CloudFormation, this is transparent to the user and doesn’t even require the user to open the CloudFormation console or interact at all with CloudFormation.
Walkthrough of moving a Lightsail instance to EC2
Exporting a Lightsail instance is very easy. First log into your AWS account and open the Lightsail console. Select your existing Lightsail instance to see the options below.
Open the snapshots tab and create an instance snapshot (if you don’t already have one). Use any name you like and click “create snapshot”. The process will most likely take a few minutes and the progress is shown in the console.
Create Instance Snapshot in Lightsail console
After the snapshot is completed it will display in the list of “recent snapshots”. We can then select this snapshot (three orange dots on the right) and select “Export to Amazon EC2”. This will move the snapshot out of Lightsail object storage over to EC2.
Recent Snapshots in Lightsail Console
An informational pop-up will appear explaining the outcome (EBS snapshot and AMI) along with a warning that EC2 billing rates will apply, click “Yes, continue”.
Export Lightsail Snapshot to EC2 in Lightsail console
One last warning will appear alerting that the existing default Lightsail key pairs (.PEM file) should be replaced with an individual key pair. Click “Acknowledged”.
Export Security Warning in Lightsail Console
The progress can be monitored using the top “gear” in the Lightsail console which will “spin” during the export process. When completed, the gear will stop “spinning” and the task will show as completed and “Exported to EC2” in the task history.
Running Snapshot export task in Lightsail Console
Completed Snapshot export in lightsail console
Using the exported EC2 Lightsail instance
Now that we have exported our Lightsail instance snapshot to EC2, what happens next? By default, nothing. Looking at the completed task screenshot (above), we can open the EC2 console to see what we have or we can use the Lightsail console to launch in EC2 instance from our exported snapshot.
Lightsail is great and I love the simplified console but we really should use the EC2 console at this point. Lightsail has all new wizard screens to manage our instance in EC2 but my feeling is that if we are going to export to EC2, we should switch over and learn to use the EC2 console.
See the screenshot below, open the EC2 console and make sure region is the same that was used for Lightsail (in my case I’m US East (Ohio)).
EC2 in the AWS Console
Open the “Elastic Block Storage” link on the left side of the EC2 console. On the top right side of the console we can see the instance snapshot that was created by Lightsail. Since this snapshot is an instance snapshot we will also find an AMI associated with this EBS snapshot.
elastic block storage snapshots in EC2 Console
EBS snapshots in ec2 console
Open the “Images” – “AMI” link in the EC2 console. We can see in the upper right frame that the Lightsail snapshot has been converted to an EC2 AMI. This was done with AWS CloudFormation but that doesn’t really matter, the AMI is ready for us to use without worrying about how it was created.
AMIs in ec2 console
AMis in ec2 console
Now the fun part, we can launch our Lightsail instance in EC2 using the AMI. Just click “launch”! A few things to consider when launching the AMI (the details are out of scope for this post):
Instance size – pick an EC2 image size for your Lightsail instance, the EC2 options have different pricing plans and different levels of CPU, RAM, GPU, storage, etc.
Security (key pair, security groups, VPC info) – design a strategy (if you don’t already have one) to secure your new image with a VPC, security group, key pair, etc.
Additional storage – additional disk storage can be attached during the EC2 launch
Tags – optionally you can tag your instance for easier AWS billing.
Pick your options and you are ready to go, your Lightsail instance is now running in EC2! Thanks for reading!