Create an Amazon Web Services (AWS) Account
In this step, you'll learn how to:
- Create an Amazon Web Services (AWS) account.
- Create a user with API access.
- Download and install the AWS Command Line Interface.
In this step, we set up your AWS account so you can utilize it for creating an AWS Lambda function and your Alexa for Business organization. AWS Lambda is an Amazon Web Services offering that runs your code only when it's needed and scales automatically, so there is no need to provision or continuously run servers.
Go to http://aws.amazon.com and create an AWS account. Check out this walkthrough for setting up an AWS account. Note: You’re required to provide a credit card number during account creation and there is an account verification process. All services and the usage of those services in this project are free of charge.
If you already have an account, sign in to the console.
Pro tip: Permissions on existing AWS accounts can prevent you from accomplishing all of the steps below. If you find yourself blocked or stopped, try creating a new account. Once signed in, click on the region next to your user name and select (US East N. Virginia).
- In the
AWS Console, type IAM in the AWS services search box at the top of the page and select IAM.
- Click Users.
- Click Add user.
- Provide a username:
- For Select AWS Access Type, select Programmatic Access.
- Click Next: Permissions.
- On the Permissions page, select Attach existing policies directly. You add two policy types:
- In the search box, enter
AWSLambdaFullAccessand then check the box next to the policy that shows up.
- Next, search for
IAMFullAccessand check the box next to that policy.
Pro tip: For this project, we use AWS managed policies, which are automatically updated as new permissions are added to these services. If you continue to develop Alexa skills using AWS, follow these AWS Identity and Access Management Best Practices to keep your resources secure.
- Click Next: Tags at the bottom right, then Next: Review.
- Verify on the Review page that your two policies,
AWSLambdaFullAccess, are showing.
- Click Create user.
- On the Add user Success page, you can download a .CSV file containing the user’s Access key ID and Secret access key, or you can copy them directly from the page. Click Show to see the secret access key. Write these down. If you lose
these keys, don’t worry. You can always generate new ones in the future if you need them.
- Click Close when you’ve saved the keys.
Installing the AWS Command Line Interface and use the links to install the appropriate package for your system.
- Make sure things are set up properly by checking that the following command works.
$ aws --version aws-cli/1.11.84 Python/3.6.2 Linux/4.4.0-59-generic botocore/1.5.47
- If the previous command didn’t work, you may need to add the path to the executable file to your PATH variable. For platform-specific instructions, see the following topics:
-Linux— Adding the AWS CLI Executable to your Command Line Path
-Windows— Adding the AWS CLI Executable to your Command Line Path
-macOS— Adding the AWS CLI Executable to your Command Line Path
- Once you have completed the installation process, run the following command, using the access key ID and secret access key you copied from the previous step.
$ aws configure AWS Access Key ID [None]: <Enter your access key ID> AWS Secret Access Key [None]: <Enter your secret access key> Default region name [None]: us-east-1 Default output format [None]: ENTER
We won’t check any of your setup. Click Verify Step to proceed to the next step in the project.