Task 01. Verify Created Resources

Check out the important resources created with SAP HANA Quick Starts.

  1. Check created SAP HANA Instance. After log in to AWS Management Console, access EC2 Console service.

  2. You can see HANA DB Primary and Secondary instances have been created. image02-01

  3. Select HANA DB Primary or Secondary instance and look at Description below to see that Secondary private ip has been created. This Secondary IP is used to communicate between two nodes (used to check if other nodes have issues). image02-02 image02-03

  4. Select HANA DB Primary or Secondary instance and look at Tags tab below to see that PaceTag(entered as an option in Quick Starts) has been created. Since hostname of EC2 Instance is automatically created, Cluster agent identifies HANA DB Instance by looking at this tag. image02-04 image02-05

  5. If you select HANA DB Primary or Secondary instance and click the Connect at the top, you can connect to the instance through Session Manager. click Connect to connect to the instance. In Lab03, we plan to conduct HA test by connecting to the instance through Session Manager. image02-06 image02-07 image02-08

  6. Check created VPC and Subnets.. After log in to AWS Management Console, access Subnets Console service.

  7. You can see that two private and two public subnets were created each. image02-09

  8. Check Route Tables menu on the left. You can check the routing for Public and Private Subnet.

  9. If you select Private subnet route table and check Routes tab below, you can see the routing entry for Overlay IP(see Task 02. Connect to Overlay IP for more information). If you click eni defined in Target, you can check that it is currently connected to Primary DB. (* Note: Private IP is different for each user.)

    • In Lab03, please check how Route Table changes after being taken over to Secondary DB. image02-10 image02-11

© 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.