AWS Systems Manager Integration --> FIS SSM Start Automation Setup
The CLI commands provided to create the SSM document and export the document ARN do not run properly when copy/pasted into CloudShell as one block. The SSM document creation runs ok, but it echo's the document back in the output, requiring the user to type "q" to get back to a prompt, or press the space bar to page through. Therefore, subsequent commands (highlighted in red box) fail to run.
Recommend separating into two different copy/paste activities, or adjusting output of the SSM doc creation.
For all FIS experiment console throughout the workshop
The IAM Role option in FIS Console is no longer underneath Description and Name, as shown in Workshop. Role is after Action and Target. When setting the Role first, as the workshop shows, then going back up to work on the Action and Target, the Role gets set back to default without realizing it. This causes issues later, of course, since experiment has unintended role. Recommend updating screenshot and selecting Role AFTER working on Action and Target.
AWS Systems Manager Integration → FIS SSM Start Automation Setup → Create SSM Role
The iam-ec2-demo-policy.json and iam-ec2-demo-trust.json files already exist in CloudShell directory: ~/environment/aws-fault-injection-simulator-workshop/workshop/content/030_basic_content/040_ssm/050_direct_automation.
No need to create the file from scratch. You can just execute the CLI commands as shown to create the policy and role.
The file ssm-terminate-instances-asg-az.yaml already exists in ~/environment/aws-fault-injection-simulator-workshop/workshop/content/030_basic_content/040_ssm/050_direct_automation, no need to create a new file.
The file fis-terminate-instances-asg-az.json already exists in ~/environment/aws-fault-injection-simulator-workshop/workshop/content/030_basic_content/040_ssm/050_direct_automation, no need to create it. You will need to open and edit the file and replace values with appropriate values for your environment, as shown in the workshop
AWS Systems Manager Integration --> FIS SSM Start Automation Setup
The CLI commands provided to create the SSM document and export the document ARN do not run properly when copy/pasted into CloudShell as one block. The SSM document creation runs ok, but it echo's the document back in the output, requiring the user to type "q" to get back to a prompt, or press the space bar to page through. Therefore, subsequent commands (highlighted in red box) fail to run.
Recommend separating into two different copy/paste activities, or adjusting output of the SSM doc creation.
For all FIS experiment console throughout the workshop The IAM Role option in FIS Console is no longer underneath Description and Name, as shown in Workshop. Role is after Action and Target. When setting the Role first, as the workshop shows, then going back up to work on the Action and Target, the Role gets set back to default without realizing it. This causes issues later, of course, since experiment has unintended role. Recommend updating screenshot and selecting Role AFTER working on Action and Target.
AWS Systems Manager Integration → FIS SSM Start Automation Setup → Create SSM Role
The iam-ec2-demo-policy.json and iam-ec2-demo-trust.json files already exist in CloudShell directory: ~/environment/aws-fault-injection-simulator-workshop/workshop/content/030_basic_content/040_ssm/050_direct_automation.
No need to create the file from scratch. You can just execute the CLI commands as shown to create the policy and role.
AWS Systems Manager Integration → FIS SSM Start Automation Setup → Create SSM Document
The file ssm-terminate-instances-asg-az.yaml already exists in ~/environment/aws-fault-injection-simulator-workshop/workshop/content/030_basic_content/040_ssm/050_direct_automation, no need to create a new file.
AWS Systems Manager Integration → FIS SSM Start Automation Setup → Create FIS Experiment Template
The file fis-terminate-instances-asg-az.json already exists in ~/environment/aws-fault-injection-simulator-workshop/workshop/content/030_basic_content/040_ssm/050_direct_automation, no need to create it. You will need to open and edit the file and replace values with appropriate values for your environment, as shown in the workshop