Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Upgrading from T2.medium to T3.medium

My instance (Amazon AMI) has two network interfaces : eth0 and eth1. I would like to upgrade from T2.Medium to T3.Medium.

But, it gives me an error saying :

Enhanced networking with the Elastic Network Adapter (ENA) is required for the 't3.medium' instance type. Ensure that your instance is enabled for ENA.

So, I found out that running the command "aws ec2 modify-instance-attribute --instance-id instance_id --ena-support" will enable ENA support.

Now, would it enable ENA support for both eth0 and eth1 ?

I have found a script https://github.com/awslabs/aws-support-tools/tree/master/EC2/C5M5InstanceChecks that checks pre-requisites.

It modified the "“/etc/fstab” to replace the device name of each partition with its UUID. Is it a safe operation ?

Do I need to install NVMe module to upgrade from T2 to T3 ?

If anything goes wrong (like I cant boot or status check failed etc), can I switch back to my backup and t2 reliably ?

Thank You.

like image 512
sudip Avatar asked Jan 18 '19 18:01

sudip


People also ask

What is the difference between t2 medium and T3 medium?

One key difference between T2 and T3 is the number of cores that each service provides. T2 offers two cores per instance, while T3 offers four cores per instance. Additionally, T3 offers faster throughput and lower latency than T2. PRO TIP: T2 and T3 are two different types of Amazon Web Services (AWS).

Is it possible to change an instance type after it has been created?

With the instance still selected, choose Actions, Instance settings, Change instance type. This option is grayed out if the instance state is not stopped . On the Change instance type page, do the following: For Instance type, select the instance type that you want.


1 Answers

I have successfully upgraded my t2.medium instance to t3.medium. I am listing the steps here so that it can help others too.

My AMI is Amazon Linux AMI (https://aws.amazon.com/amazon-linux-ami/2018.03-release-notes/). It has HVM virtualization and a EBS root volume. First step is to take a backup of the root volume (or, creating a image from the existing instance). Then I run "sudo yum update" and restarted the instance to see if everything is good.

The ami had ENA and NVMe modules already installed. "/etc/fstab" already had uuid format enabled.

To check ENA : modinfo ena
To check NVMe : modinfo nvme
To check whether ena driver is loaded on eth0 : ethtool -i eth0 and on eth1: ethtool -i eth1

Running the script https://github.com/awslabs/aws-support-tools/tree/master/EC2/C5M5InstanceChecks returned success.

After that I installed AWS CLI (https://github.com/aws/aws-cli) and configured the cli with AWS access key, secret key and region.

Then I run ec2 describe-instances --instance-ids INSTANCE_ID --query "Reservations[].Instances[].EnaSupport"

It returned a response "[]" (According to the documentation the command supposed to return false).

Then I stopped the instance and run the following command from AWS cli : ec2 modify-instance-attribute --instance-id INSTANCE_ID --ena-support

I started the server and ethtool -i eth0 and ethtool -i eth1 output showed that both my interfaces has "ena" driver now.

Then I stopped the instance and change the instance type to t3.medium.

The below link has been very helpful : https://forums.aws.amazon.com/thread.jspa?threadID=290005 (njohari-aws answer).

like image 91
sudip Avatar answered Sep 21 '22 03:09

sudip