SigV4, short for Signature Version 4, is Amazon’s request-signing scheme for AWS APIs and many S3-compatible services. A client builds a canonical version of the request, hashes it, and signs that data with a secret key. The server repeats the calculation and compares the result to verify that the request really came from an authorized caller and was not altered in transit.
In cyber security, SigV4 matters because it is often the trust boundary for object storage access. If an attacker can forge signatures, replay requests, or trick a service into accepting the wrong credentials or endpoint, they may read, write, or delete data without needing a normal password login. Defenders watch for weak proxying, bad clock handling, credential leakage, and implementation bugs in S3-compatible tooling. In exposed services, SigV4 is commonly used to secure upload, download, and administrative API calls.