The NI Cloud Toolkit for AWS has a LabVIEW based implementation for generating signatures that AWS requires on the HTTP requests. Here's a high level flow of how your AWS secret access key (not your login credentials) is used to sign each request to AWS by following the Signature Version 4 process. More details on how the signatures are generated and used can be found in Amazon's documentation. Signature Version 4 Signing Process
How Signature Version 4 works
-
Create a canonical request.
-
Use the canonical request and additional metadata to create a string for signing.
-
Derive a signing key from your AWS secret access key. Then use the signing key, and the string from the previous step, to create a signature.
-
Add the resulting signature to the HTTP request in a header or as a query string parameter.
When an AWS service receives the request, it performs the same steps that you did to calculate the signature you sent in your request. AWS then compares its calculated signature to the one you sent with the request. If the signatures match, the request is processed. If the signatures don't match, the request is denied.
Danny Funk -- Senior Group Manager -- Software R&D -- NI