Deploy the Infrastructure and Application

1. Go to https://dashboard.eventengine.run/login

2. Enter the 16 character hashcode you were provided and click “Proceed”

3. Sign-in using either an Amazon.com retail account or a One-Time Password (OTP) that will be emailed to you.

4. [optional] assign a name to your account (this is referred to as “Team name”)

   • click “Set Team Name”
   • Enter a name and click “Set Team Name”

5. Click “AWS Console”

6. Get and store your AWS credentials

   • IMPORTANT Copy the provided credentials and save them. You wil need these to complete the workshop

   • Copy the whole code block corresponding to the system you are using.

7. Access the AWS console

   • Click “Open AWS Console”.
   • The AWS Console will open and you can continue the lab.

• Sign in to the AWS Management Console as an IAM user who has PowerUserAccess or AdministratorAccess permissions, to ensure successful execution of this lab.
• You will need the AWS credentials, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY, of this IAM user for later use in this lab.
  • If you do not have this IAM user’s credentials or you wish to create a new IAM user with needed permissions, follow the instructions here to create them

Here you will build a state machine using AWS Step Functions and AWS Lambda that orchestrates the deployment of the multi-tier infrastructure. This is not the service infrastructure itself, but meta-infrastructure we use to build the actual infrastructure.

Learn more: After the lab see this blog post on how AWS Step Functions and AWS CodePipelines can work together to deploy your infrastructure

1. Get the CloudFormation template: Download the appropriate file (You can right-click then choose download; or you can right click and copy the link to use with wget)

   • single region: download CloudFormation template here
   • multi region: download CloudFormation template here

2. Ensure you have selected the Ohio region. This region is also known as us-east-2, which you will see referenced throughout this lab.

3. Go to the AWS CloudFormation console at https://console.aws.amazon.com/cloudformation and click Create Stack and select With new resources from the drop-down menu

4. Leave “Prepare template” setting as-is

   • 1 - For “Template source” select “Upload a template file”
   • 2 - Specify the CloudFormation template you downloaded

5. Click the “Next” button. For “Stack name” enter: DeployResiliencyWorkshop

   

6. On the same screen, for “Parameters” enter the appropriate values:

   • If you are attending an in-person workshop and were provided with an AWS account by the instructor: Leave all the parameters at their default values
   • If you are using your own AWS account: Set the first three parameters using these instructions and leave all other parameters at their default values.
   • You optionally may review the default values of this CloudFormation template here

7. Click the “Next” button.

   • On the “Configure stack options” page, click “Next” again
   • On the “Review DeployResiliencyWorkshop” page, scroll to the bottom and tick the checkbox “I acknowledge that AWS CloudFormation might create IAM resources with custome names.”
   • Click the “Create stack” button.

8. This will take you to the CloudFormation stack status page, showing the stack creation in progress.
   
   This will take approximately a minute to deploy. When it shows status CREATE_COMPLETE, then the state machine will start deploying the infrastructure and service.

9. Once the “deployment machine” starts deploying the infrastructure and service it will take approximately the following times to deploy:

   Time until you can start…	Single region	Multi region
   EC2 failure injection test	15-20 min	15-20 min
   RDS and AZ failure injection tests	20-25 min	40-45 min
   Multi-region failure injection tests	NA	50-55 min
   Total deployment time	20-25 min	50-55 min

1. Go to the AWS Step Function console at https://console.aws.amazon.com/states

2. On the Step Functions dashboard, you will see “State Machines”. Click on the one named “DeploymentMachine-random characters.” This will bring up an execution console

3. Click on the state machine execution under Executions

4. You can watch the state machine as it executes by clicking the icon to expand the visual workflow to the full screen.
   

5. You can also watch the CloudFormation stacks as they are created and transition from CREATE_IN_PROGRESS to CREATE_COMPLETE.

6. You can start the first test (EC2 failure injection testing) when the web tier has been deployed in the Ohio region. Look for the WaitForWebApp step (for single region) or WaitForWebApp1 step (for multi region) to have completed successfully. This will look something like this on the visual workflow.

   

   • Above screen shot is for single region. for multi region see this diagram instead