Easily leverage AWS Rest API calls with the Send HTTP request Step using the AWS Signature Version 4 (SigV4) protocol. You can securely and quickly integrate with AWS to easily automate all your AWS cloud needs.
Save AWS access keys as Torq custom secrets
Create AWS access keys
Open AWS IAM: Sign in to the AWS Management Console and go to IAM.
Select the user: Go to Users and select the relevant user.
Create an access key: Click the Security credentials tab and then Create access key.
Select a use case for your access key and review the suggested alternatives.
Click Next.
(Optional) Add a descriptive tag.
Click Create access key.
Finalize: Copy the access key ID and secret access key to save them for laterâyou will need them when creating the Custom Secrets integration in Torq.
Store AWS access keys in Torq
Storing AWS access keys in Torq requires creating two separate custom secrets: one for the access key ID and the other for the secret access key.
Navigate to the integration: Go to Build > Integrations > Custom Secrets and click Add Instance.
Create the AWS access key ID secret:
Enter a meaningful name for the secret, such as
AWS SigV4 Access Key ID.Paste the access key ID you copied from AWS earlier.
Click Add.
Add another secret: Click Add Instance again to add another secret.
Create the AWS secret access key:
Enter a meaningful name for the secret, such as
AWS SigV4 Access Key Secret.Paste the secret access key you copied from AWS earlier.
Click Add.
Authorize calls with AWS SigV4
Open the Workflow: Navigate to Build > Workflows and select the relevant Workflow.
Add the Send an HTTP request Step: Drag and drop the Send an HTTP request Step into the Workflow.
Configure the Step:
Paste the call request URL.
Select the appropriate call method.
Select AWS SigV4 as the authorization.
For the AWS access key ID parameter, enter
$.secretsand select the access key ID custom secret you created earlier.For the AWS secret access parameter, enter
$.secretsand select the secret access key custom secret you created earlier.For the AWS service parameter, select the relevant AWS service from the dropdown menu or from the Workflow context.
For the AWS region parameter, select the relevant AWS region from the dropdown menu or from the Workflow context.
Some regions need to be included in both the endpoint URL and the selection (e.g.
https://s3.amazonaws.com/works forus-east-1but fails formx-central-1, unless the endpoint is updated tohttps://s3.mx-central-1.amazonaws.com/).
Execute the Step: Click Execute to test the Step, and then check the Execution Log to confirm everything is running as expected.
