---
category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Custom Integrations & Apps]
keyword: [Orchestration Builder, AWS]
nav: wcp_docs
parent_url: /wcp_docs/
title: Create AWS Signature v4 Credentials
layout: subsection
---

### Prerequisites

Create an app containing an orchestration.

To use AWS Signature v4, use the <b>Create AWS Access Key CredStore</b> task on your tenant to create an AWS CredStore that you can refer to from the orchestration's Settings.

On a development or implementation tenant you can also use temporary credentials. You first need to acquire an Access Key ID, a Secret Access Key, and a Session Token from the AWS Admin Console.

### Context

You can use AWS Signature v4 in Workday Orchestrate to securely authenticate <b>Send HTTP Request</b> steps against services like AWS Lambda, S3, and DynamoDB.

### Steps

1.  On your orchestration's <b>Settings</b> page, click <b>AWSv4</b>.
2.  Provide a <b>Name</b> for the credential.
3.  From the <b>Type</b> drop-down menu, select <b>CredStore Reference</b> or <b>Temporary Security Token</b>. The latter is available for use with development tenants only.
4.  If you selected <b>CredStore Reference</b>, use Expression Builder in the <b>Reference</b> field to provide the Access Key ID you stored in the tenant AWS Credstore for your application ID.

    If you selected <b>Temporary Security Token</b>, provide the <b>Access Key ID</b>, <b>Secret Access Key</b>, and <b>Session Token</b> you obtained from the Amazon Security Token Service.

5.  Specify the <b>AWS Region</b> where the service you want to access resides. Example: us-west-2.
6.  Specify the <b>AWS Service</b> you want to interact with. Example: S3.


### Result

Your AWS Signature v4 credentials are now available for use with the <b>Send HTTP Request</b> component with any orchestration.

