Migrating SAP HANA on AWS to an EC2 HMI

The course is part of this learning path

Start course

This course discusses EC2 instances for SAP workloads on AWS.

Learning Objectives

Our learning objectives for this course are to:

  • Get an understanding of what EC2 instances are recommended for SAP HANA workloads
  • Learn the ways we can scale out these instances
  • And finally talk about how to migrate to high memory instances

Intended Audience

I would recommend this course for anyone attempting to create an SAP based architecture.


You should have a decent understanding of cloud computing and cloud architectures, specifically with Amazon Web Services. You should also have some background knowledge related to SAP HANA.


Migrating SAP HANA on AWS to an EC2 High Memory instance. At some point in your SAP HANA journey you will probably need to migrate to a High Memory EC2 instance. There are a number of ways that this can be accomplished. So, let's take a few minutes to go over the basics of each of them. The first option I want to explore is how to resize your instances that are running with host or dedicated tendency. The big advantage of this type of migration is that you get to keep your IP addresses, your host name, and your EBS volumes. 

These items will all remain the same after the migration helping to reduce administrative burdens. In general, the migration is very simple but if you want detailed instructions, please take a look at the AWS docs here. The first step is just confirmation that you are running a supported operating system version. If you are not, you will have to upgrade to a supported version before resizing. Since, High Memory EC2 instances are based on the Nitro System, EBS volumes will be presented as NVMe block devices.

This means if you have any amount point entries within etc/fstab with references to block devices like dev/xvd, these will need to be labeled and mounted by label before migrating. Make sure your instance does not exceed the maximum supported EBS volumes of the new instance that you might be migrating to. Next, you want to create a backup of your source system, then you'll want to stop the source instance. If your instance is running with dedicated tenancy, you'll need to modify the instance placement to host tendency. 

Now, you can modify the instance placement of your source instance to the target High Memory dedicated host. Next, you will change your instance type to the actual desired High Memory instance type and then you can start up your instance. You may need to increase the memory of your storage sizes for the SAP HANA data, log, shared, and backup volumes. And now, you can start up your SAP HANA database and validate. And finally, you will need to complete any  SAP HANA specific post migration activities, AWS post migration activities, and configure SAP HANA systems for high availability.


About the Author

William Meadows is a passionately curious human currently living in the Bay Area in California. His career has included working with lasers, teaching teenagers how to code, and creating classes about cloud technology that are taught all over the world. His dedication to completing goals and helping others is what brings meaning to his life. In his free time, he enjoys reading Reddit, playing video games, and writing books.