JMeter生成签名AWS API请求失败，寻求正确实现方案

Let's break down your two issues and walk through practical fixes step by step:

Issue 1: "Access denied" when adding raw AWS credentials to HTTP Header Manager #

First off, AWS API requests don't accept raw AccessKey/SecretKey directly in headers. Postman likely handles the AWS SigV4 signature process automatically under the hood, which is why your Postman request works. When you manually drop those keys into headers, you're skipping the critical cryptography and header formatting steps required by AWS's authentication protocol.

Key points to correct:

• You can't just paste your AccessKey into a header; instead, you need to generate a full Authorization header that follows the SigV4 format (includes credential scope, signed headers, and a cryptographically generated signature).
• If you're using temporary credentials (with a Session Token), that token belongs in a dedicated header named X-Amz-Security-Token — not a custom-named header.

Issue 2: JSR223 PreProcessor not setting the "aaauthorization" variable #

If your Debug Sampler isn't picking up the variable, there are a few common pitfalls to fix, plus a reliable implementation to generate the signature correctly:

1. Verify PreProcessor placement #

Make sure your JSR223 PreProcessor is directly attached as a child to your target HTTP Request, or positioned immediately before it in the test plan. If it runs after the request (or on a different scope), the variable won't be available when the request executes.

2. Check for code errors or null values #

Add logging to your JSR223 script to confirm it's running and generating a valid value. For example:

// After generating your auth value
log.info("Generated auth header: " + authValue);
if (authValue == null) {
    log.error("Auth value is null — check credential parameters!");
}

Open the JMeter Log Viewer (Options > Log Viewer) to see these messages. If you don't see the log entry, your script isn't running at all.

3. Fix variable naming (and spelling!) #

Double-check the variable name: you mentioned "aaauthorization" — that extra 'a' might be a typo. Stick to a clear name like authorization to avoid confusion.

4. Working SigV4 Signature Implementation #

The most reliable way to generate AWS SigV4 signatures in JMeter is to use the AWS Java SDK. Here's a complete script for your JSR223 PreProcessor:

Prerequisites:

• Download the AWS Java SDK Core JAR (and its dependencies like jackson-databind, commons-codec) and place them in JMeter's lib folder. Restart JMeter after adding the JARs.
• Define these variables in a User Defined Variables element for easy reuse:
  • AWS_ACCESS_KEY
  • AWS_SECRET_KEY
  • AWS_SESSION_TOKEN (if using temporary credentials)
  • AWS_REGION (e.g., us-east-1)
  • AWS_SERVICE_NAME (e.g., s3, lambda)
  • AWS_ENDPOINT (the full URL of your AWS API, e.g., https://lambda.us-east-1.amazonaws.com/2015-03-31/functions/my-function/invocations)

JSR223 Script:

import com.amazonaws.auth.AWSStaticCredentialsProvider;
import com.amazonaws.auth.BasicSessionCredentials;
import com.amazonaws.auth.SignerFactory;
import com.amazonaws.auth.signer.Aws4Signer;
import com.amazonaws.http.HttpMethodName;

// Fetch variables from User Defined Variables
String accessKey = vars.get("AWS_ACCESS_KEY");
String secretKey = vars.get("AWS_SECRET_KEY");
String sessionToken = vars.get("AWS_SESSION_TOKEN");
String region = vars.get("AWS_REGION");
String serviceName = vars.get("AWS_SERVICE_NAME");
String endpoint = vars.get("AWS_ENDPOINT");

// Initialize session credentials (skip sessionToken line if using permanent credentials)
BasicSessionCredentials credentials = new BasicSessionCredentials(accessKey, secretKey, sessionToken);

// Set up SigV4 signer
Aws4Signer signer = SignerFactory.createSigner("AWS4SignerType");
signer.setServiceName(serviceName);
signer.setRegionName(region);

// Build the HTTP request object
com.amazonaws.http.HttpRequest request = new com.amazonaws.http.HttpRequest(HttpMethodName.POST, new java.net.URI(endpoint));
// For POST requests, add your request body here:
// String requestBody = vars.get("REQUEST_BODY");
// request.setContent(new java.io.StringInputStream(requestBody));

// Sign the request
signer.sign(request, credentials);

// Extract signed headers
String authHeader = request.getHeaders().get("Authorization");
String securityTokenHeader = request.getHeaders().get("X-Amz-Security-Token");

// Store values in JMeter variables
vars.put("authorization", authHeader);
vars.put("x_amz_security_token", securityTokenHeader);

// Log for verification
log.info("Successfully generated Authorization header: " + authHeader);

Final Setup:

• In your HTTP Header Manager, add these headers:
  • Authorization: ${authorization}
  • X-Amz-Security-Token: ${x_amz_security_token} (only if using temporary credentials)
• Run your test and check the Debug Sampler — you should see both variables populated.

内容的提问来源于stack exchange，提问作者Thomas