A developer is implementing AWS Signature Version 4 signed requests and has already built the canonical request, created the string to sign, and computed the signing key. Which approaches can the developer use to attach the signature to the HTTP request? (Choose two.)

AWS Signature Version 4 allows attaching the computed signature to an HTTP request in two primary ways: as an Authorization header or as query string parameters. Including the signature in an Authorization header is the most common method, where the header contains the signing algorithm, credential scope, signed headers, and the final signature. Alternatively, for GET requests or when specific services require it, the signature can be included as query string parameters, with X-Amz-Signature being the parameter holding the final signature. Placing the signature in a session cookie is not a standard or secure method for AWS SigV4. Authentication and WWW-Authenticate are standard HTTP headers but are not used for carrying the AWS SigV4 signature itself; WWW-Authenticate is typically for server challenges.