Overview

This page documents the AWS Signature feature of Request Man.

AWS Signature (Version 4) GET https://s3.amazonaws.com/my-bucket/file.txt AWS Signature Access Key ID AKIAIOSFODNN7EXAMPLE Secret Access Key 🔒 Secret *************************************** AWS Region us-east-1 Service Name s3 Session Token (Optional - for temporary credentials) Leave empty for permanent credentials Advanced Options ✓ Include X-Amz-Date header ✓ Include Content-SHA256 header ✓ Use environment variables for credentials
Documentation in Progress: Full documentation for this feature coming soon!

Key Features

The AWS Signature feature provides powerful capabilities for API testing and development.

🔑 SigV4 Protocol ✓ AWS Signature Version 4 ✓ HMAC-SHA256 signing ✓ Request canonicalization Signing Process: 1. Create canonical request 2. Create string to sign 3. Calculate signature 4. Add Authorization header ☁️ All AWS Services ✓ S3, EC2, Lambda, DynamoDB ✓ API Gateway, CloudWatch ✓ Any AWS API endpoint Supported Services: ☁️ S3 (Simple Storage Service) ☁️ EC2, Lambda, DynamoDB ☁️ API Gateway, CloudWatch ☁️ All AWS services with REST APIs 🔑 Credential Types ✓ IAM user credentials ✓ Temporary STS credentials ✓ Role-based access Credentials Supported: 🔑 Permanent (Access Key + Secret) ⏱️ Temporary (with Session Token) ⚙️ Environment variables 👤 Assumed role credentials

Getting Started

Access the Feature

Navigate to AWS Signature in the Request Man interface.

Configure Settings

Set up your AWS Signature preferences.

Start Using

Begin using AWS Signature in your API workflows!

Step 1: Select AWS Signature AWS Signature Step 2: Enter AWS credentials Access Key ID: AKIAIOSFODNN7EXAMPLE Secret Access Key: ************************** Region: us-east-1 Service: s3 Step 3: AWS Signature V4 Automatically Generated ✓ Canonical request created ✓ String-to-sign computed ✓ Signature calculated using HMAC-SHA256 ✓ Authorization header added to request

Examples

Here are practical examples of using AWS Signature:

Example: AWS S3 API Request with Signature V4 Request GET https://my-bucket.s3.amazonaws.com/documents/report.pdf AWS Signature V4 Configuration Access Key: AKIAIOSFODNN7EXAMPLE Secret Key: ************************** Region: us-east-1 Service: s3 Date: 20231115T120000Z AUTO-GENERATED AWS SIGNATURE V4 HEADERS: X-Amz-Date: 20231115T120000Z X-Amz-Content-Sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Authorization: AWS4-HMAC-SHA256 Credential=AKIAIOSFODNN7EXAMPLE/20231115/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=a1b2c3... Response 200 OK ✓ Successfully authenticated with AWS S3 using Signature Version 4

Tips & Best Practices

Tip 1

Learn the keyboard shortcuts for faster workflow.

Tip 2

Use variables for flexibility across environments.

Tip 3

Save and organize your work in collections.

Tip 4

Check the console for detailed logging information.