After the EC2 instances are launched by AWS CloudFormation, AWS Launch Wizard for SAP orchestrates the creation and configuration of AWS resources. To configure the SAP applications, a workflow is carried out (by the scripts) on the launched EC2 instances.

The scripts are downloaded on all the instances being launched by AWS CloudFormation. They are executed based on the role and parameters of the instances and the selections made in the Launch Wizard console. In case of SAP deployments across multiple instances, baseline activities are performed on each node. The baseline activities wait for a signal from the orchestration logic to execute the dependent activities.

Below is the workflow:

1. Install Python3.
2. Install awscli.
3. Download the scripts to /root/install/scripts.
4. main.py is executed. This is the main program that orchestrates all the activities (described below) based on the info provided by the user in the Launch Wizard console, SAP workload, and deployment type.
5. Prepare parameters json file based on Launch Wizard console inputs and store in /root/install/scripts/log/inputs.json. This file is used by scripts to execute the automation.
6. If proxy information is provided, proxy server will be configured.
7. Install SSM Agent.
8. Install CloudWatch Agent.
9. Install [AWSTOE] (https://docs.aws.amazon.com/imagebuilder/latest/userguide/toe-get-started.html).
10. Once all the agents are installed, it is implied that the instances have internet access and an EgressCheckWaitHandle signal is sent to AWS CloudFormation. Timeout for this wait handle is configured to 60 mins. If the signal is not received within 60 mins, the deployment will error out.
11. Initialize workflow DynamoDb table. This table will be used to orchestrate the workflow from the master/primary HANA node.
12. [Optional] Execute pre-configuration scripts using AWSTOE.
13. OS hardening - install packages and configure OS parameters.
14. Get total host count for all nodes to take an inventory in DynamoDb.
15. Update /etc/hosts file with all the hostnames and private IP addresses.
16. Storage is built/mounted based on AWS recommended storage layout for the given SAP component.
17. [Optional] Install database on the database instances if selected.
18. [Optional] Install application on the application instances if selected.
19. [Optional] In case of HA setup, configure high availability (HA) cluster for database.
20. [Optional] In case of HA setup, configure HA cluster for application.
21. [Mandatory] Install AWS Data Provider for SAP.
22. [Optional] Execute post-configuration scripts using AWSTOE.
23. Cleanup instances. Remove /root/install/scripts folder. Copy /root/install/scripts/log/install.log and /root/install/scripts/log/inputs.json. to /tmp folder.
24. Delete the DynamoDB table created in Setup 11.
25. Success signal sent back to the AWS CloudFormation stack.
26. Deployment status updated and SNS notification sent out.