­AWS Signature Authentication

AWS Signature authentication is the process of verifying the authenticity of requests made to Amazon Web Services (AWS) using the AWS Signature method.

This authentication process involves calculating a digital signature for each request using the requester’s access key and secret access key, along with details about the request being made. AWS verifies the signature against the user’s access credentials and grants access to the requested resources if the signature is valid.

The AWS Signature authentication method ensures that requests are securely transmitted and that only authorized users can access AWS resources.

AWS Signature Authentication in Astera API Management

Astera API Management lets the user configure an API Connection with AWS Signature as an authentication type.

1. Drag and drop an API Connection object from the toolbox onto a dataflow.

2. Right-Click on the object and select Properties from the context menu.

This will open a new window,

Base URL: Here, you can specify the base URL of the API which will prepend as a common path to all API endpoints sharing this connection. A Base URL usually consists of the scheme hostname and port of the API web address.

Timeout (msec): Specify the duration, in milliseconds, to wait for the API server to respond before giving a timeout error.

Include Client SSL Certificate: Selecting this option is going to include any Client SSL certificate that is needed for authentication.

Enable Authentication Logs: Selecting this checkbox will allow the client to generate authentication logs when the API connection has been configured.

3. Define the Base URL and select AWS Signature from the security type.

4. Selecting it will make the following options available.

Access Key: The unique access key provided to the AWS user for authentication.

Secret Key: The corresponding unique key provided to the AWS user for authentication

AWS Region: The region from where the API connection is being made, set by the admin.

Service Name: The name of the AWS service being used in the API Connection.

Note: While the Access Key and Secret Key are unique to each user, the AWS Region and Service Name are common among a group of users.

5. Once the fields have been filled, click OK and the API Connection will be configured.

This API Connection can then be used in an API Client object to make API Calls to the resource.

6. Drag and drop an API Client object and configure it with the API Connection.

7. Preview the output of the API Client object.

As you can see, the response has returned a ‘200 OK’ status.

This concludes the configuration and testing of the AWS Signature Authentication in Astera API Management.