Skip to main content

aws_auth

Purpose

aws_auth re-signs an existing AWS Authorization v4 HTTP Header. The original algorithm is honored. This transform works with request tokens in the generator. This is not a transform for re-signing AWS Auth keys in the responder because it is not necessary.

This transform generates a new Authorization signature using the complete request. Make sure that this is the last transform chain to be run in sequence if you want the signature to include other changes you may have made with other transforms.

The incoming token must be a current valid AWS signature because the SignedHeaders and other information is necessary for the re-sign process. In other words, if you want to change how the signature is generated then you can modify fields in the incoming Authorization header. For instance, if you remove a header from the SignedHeaders portion of the current header than this transform will not use it during it's new calculation.

Usage

"type": "aws_auth"
KeyDescription
secretPathThe local path of a secret mounted to generator. This secret should be plain text and contain the same info that you would find in the AWS_SECRET_ACCESS_KEY environment variable. If working in Kubernetes, you can specify a secret using this format: ${{secret:secret_name/key_inside_the_secret}} and the operator will automatically mount it to the load generator.
idPathThe local path of a secret mounted to generator. This secret should be plain text and contain the same info that you would find in the AWS_ACCESS_KEY_ID environment variable. If working in Kubernetes, you can specify a secret using this format: ${{secret:secret_name/key_inside_the_secret}} and the operator will automatically mount it to the load generator.

Example

"type": "aws_auth",
"config": {
"secretPath": "${{secret:awscreds/secretkey}}",
"idPath": "${{secret:awscreds/id}}",
}