| title | description | keywords | services | ms.subservice | ms.date | ms.topic |
|---|---|---|---|---|---|---|
Authenticate Azure Automation runbooks with Amazon Web Services |
This article tells how to authenticate runbooks with Amazon Web Services. |
aws authentication, configure aws |
automation |
process-automation |
04/23/2020 |
conceptual |
Automating common tasks with resources in Amazon Web Services (AWS) can be accomplished with Automation runbooks in Azure. You can automate many tasks in AWS using Automation runbooks just like you can with resources in Azure. For authentication, you must have an Azure subscription.
To authenticate with AWS, you must obtain an AWS subscription and specify a set of AWS credentials to authenticate your runbooks running from Azure Automation. Specific credentials required are the AWS Access Key and Secret Key. See Using AWS Credentials.
You can use an existing Automation account to authenticate with AWS. Alternatively, you can dedicate an account for runbooks targeting AWS resources. In this case, create a new Automation account.
You must store the AWS credentials as assets in Azure Automation. See Managing Access Keys for your AWS Account for instructions on creating the Access Key and the Secret Key. When the keys are available, copy the Access Key ID and the Secret Key ID in a safe place. You can download your key file to store it somewhere safe.
After you have created and copied your AWS security keys, you must create a Credential asset with the Automation account. The asset allows you to securely store the AWS keys and reference them in your runbooks. See Create a new credential asset with the Azure portal. Enter the following AWS information in the fields provided:
- Name - AWScred, or an appropriate value following your naming standards
- User name - Your access ID
- Password - Name of your Secret Key
- To learn how to create runbooks to automate tasks in AWS, see Deploy an Amazon Web Services VM with a runbook.