# Sign into the AWS console
To start, we need to sign into the AWS console. Amazon cloud computing resources are hosted in multiple locations worldwide. These locations are composed of AWS Regions and Availability Zones. In this workshop, make sure your region is set to US West (Oregon). This region is also known as
If you are in a classroom setting, we will provide a credit code for you to use. To redeem, follow the instructions on the card you receive.
The credit codes provided will cover the cost of today's workshop. You must clean up these resources at the end of the workshop, otherwise you will incur additional charges.
# Set up your infrastructure with AWS CloudFormation
There are two primary components to the system you'll build today. The first component is a collection of AWS resources that process the commands you give your robot, and allow you to simulate the robot in a virtual environment. The second is part of the Alexa Skills Kit, and takes care of letting you interact with your robot via an Alexa-enabled device.
The resources in the first component include a Virtual Private Cloud, IAM roles and security groups to control access, and an Amazon S3 bucket to store artifacts.
To setup these resources, you will run a CloudFormation script to take care of the heavy lifting for you. The diagram below details the infrastructure that you'll launch:
The script creates a Virtual Private Cloud (VPC) and two subnets to isolate your resources. It also creates
- an IoT policy communication to/from the IoT service for your robot.
- an S3 bucket that is used to store code for your robot and simulated world.
- an execution role and policy that allows your system to generate logs and to access resources in Amazon S3 for the simulation.
Click the "Launch Stack" button below to run the script to provision the infrastructure:
Step through the settings by clicking the Next button on each page, giving your stack the name "VoiceRoboticsWorkshop." Check the box for "I acknowledge that AWS CloudFormation might create IAM resources with custom names", then click the Create Stack button.
Pay close attention to the values provided in the "Outputs" tab:
You'll need these as you continue through the steps in this guide. It may help to keep this browser window open, or to copy and paste the values of the outputs to a text editor for use later.
Wait for the CloudFormation script to complete before continuing. You should see a
CREATE_COMPLETE status in your stack after a few minutes.
# Creating a ROS Development Environment
AWS RoboMaker provides a quick and easy way to create an environment that is already configured for robot development. In just a few clicks, you can create a development environment and begin writing code.
Visit the "Development Environments" dashboard in AWS RoboMaker.
Click the Create environment button.
Update your settings with the following values, then click the Create button.
|Pre-installe ROS distribution||ROS Kinetic|
|IAM Role||leave unchanged|
|VPC||select the |
|Subnets||select either of the two subnets in the dropdown|
The development environment can take up to five minutes to deploy. You can now continue on with this guide, we'll come back to your environment later.
# Update your default security group
Next we need to open up a port in your security group so that you can test communications with your robot.
- Visit Security Groups on the AWS EC2 dashboard.
- Select the security group that was created when your AWS RoboMaker environment launched. The "Group Name" will look something like `aws-cloud9-WorkshopEnvironment".
- Click the "Inbound" tab, which shows protocols, ports, and IP ranges for inbound traffic to your RoboMaker environment (RoboMaker gave SSH access by default).
- Click Edit to add one more rule, allowing TCP traffic on port 8883, then use the Source dropdown to choose "Anywhere" ("0.0.0.0/0").
|Custom TCP Rule||TCP||8883||0.0.0.0/0||MQTT access from IoT console|
- Click the Save button to save your changes.
When you've made this change, you're ready for the next step!