If you are running this at an AWS hosted event (such as re:Invent, Kubecon, Immersion Day, Dev Day, etc), the IAM role has been created for you so the IAM role you are attaching in this step will be different, e.g. mod-*****, than if you were to create your own IAM role, e.g. tigera-workshop-admin
.
Follow this deep link to find your Cloud9 EC2 instance
Note: If no instances are found, click the gear icon in the top right corner and verify that “Use regular expression matching” is enabled.
Select the instance, then choose Actions / Security / Modify IAM Role
Choose tigera-workshop-admin from the IAM Role drop down, and select Apply
Update IAM settings for your workspace.
Cloud9 normally manages IAM credentials dynamically. This isn’t currently compatible with some AWS services authentication, so we will disable it and rely on the IAM role instead.
Close the Preferences tab