To run this workshop, you need an AWS account, and a user identity with access to the following services:
You can use your own account, or an account provided through Event Engine as part of an AWS organized workshop. Using an account provided by Event Engine is the easier path, as you will have full access to all AWS services, and the account will terminate automatically when the event is over.
You should also have familiarity with using the AWS CLI, including configuring the CLI for a specific account and region profile. If not, please follow the CLI setup instructions. Make sure you have a default profile set up.
If you are running this workshop as part of an Event Engine lab, please log into the console using this link and enter the hash provided to you as part of the workshop.
If you are using your own AWS account, be sure you have access to create S3 buckets, run SageMaker training jobs, create SageMaker endpoints, and create and manage EKS clusters.
After completing the workshop, remember to complete the cleanup section to remove any unnecessary AWS resources.
After you have your account identified, pick an AWS region to work in, such as
us-west-2. We'll refer to this as
REGION going forward.
Also note your AWS account number. You find this in the console or by running
aws sts get-caller-identity on the CLI. We'll refer to this as
ACCOUNT going forward.
Whichever AWS account option you use, you may prefer to use a cloud-based environment rather than installing tools like
eksctl on your own machine. In that case, you can use a Cloud 9 IDE.
In the AWS console, go to the Cloud9 service and select
Create environment. Call your new IDE
KubeIDE and click
Next Step. On the next screen, change the instance type to
m5.large and click
Next step again. On the final page, click
Create environment. Make sure that you leave the VPC settings at the default values.
Once the environment builds, you'll automatically redirect to the IDE. Take a minute to explore the interface, and note that you can change the color scheme if you like (AWS Cloud9 menu -> Preferences -> Themes).
Next, let's update the Cloud9 environment to let you run the labs from the environment.
AWS servicefor the entity and leave the service set to
AWS managed temporary credentials.
Note that this role grants a very broad set of permissions to your Cloud9 instance.
In your Cloud9 IDE, create the file
~/.aws/config with these lines, replacing
ACCOUNT with your own settings:
[default] region=REGION account=ACCOUNT