HANA Database experience.
Terraform template that will launch either
a) 2 CM platform EC2 instances using IP overlay failover or
b) single instance with AMI replacement, whichever of the two solutions will create a HA CM platform layer.
This configuration will also require the control system that will force the switch from the active node to the passive node.
a. Operational runbooks to force failover, how to replace a failed instance, patching strategy (not patching, but how to put cluster into maintenance mode and target individual instances)
Terraform template to create two EC2 Hana instances with pacemaker installed and ready to configure AWS control plane actions for high availability (this will be used for the CC Hana layer, and the CM Hana layer) - Separate HANA Databases for CC & CM
a. Operational runbooks to force failover, how to replace failed instance, patching strategy
Architect/Design/Implement CM/CC & HANA Database DR scenarios (Async) - target would be a new region. Operational runbook for lighting up Hana from backup.
Terraform template to create EC2 instance layer (this will be used for
a) CC rater/bulk uploader layer,
b) CC updater/guider layer,
c) CM engine layer - this does not need elasticity, we can manually control ASG size.
Also the expectation is that these would attach to ALB, but not go into healthy state until manual application install occurs.
Terraform template to deploy 2 EC2 instances for CC core (HA will be covered by SAP clustering mechanisms)
EFS template w/ userdata scripts to mount to EC2 instances automatically
Please reach me at