generated: '2026-06-20' method: searched source: >- https://docs.aws.amazon.com/secretsmanager/latest/apireference/CommonParameters.html and https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html — the OpenAPI in this repo declares no securitySchemes (the AWS query protocol carries auth in signed request headers rather than OpenAPI security objects), so this profile is captured from the AWS documentation. docs: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html summary: types: [aws-sigv4] api_key_in: [] oauth2_flows: [] note: >- Amazon Secrets Manager uses AWS Signature Version 4 (SigV4) request signing, not API keys or OAuth. Authorization is enforced by AWS IAM identity-based policies and Secrets Manager resource-based (secret) policies. There is no OAuth scope surface, so no scopes/ artifact is produced for this provider. schemes: - name: aws-sigv4 type: sigv4 description: >- Every request is signed with AWS Signature Version 4 using the caller's access key ID and secret access key (plus a session token for temporary credentials). The signature is carried in the Authorization header along with X-Amz-Date; the operation is selected via the X-Amz-Target header (e.g. secretsmanager.GetSecretValue). signing_name: secretsmanager region_scoped: true docs: https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html authorization: model: AWS IAM + resource-based policies identity_based: >- IAM identity-based policies grant secretsmanager:* actions (e.g. secretsmanager:GetSecretValue, secretsmanager:CreateSecret) to users/roles. resource_based: >- Secret resource policies (PutResourcePolicy) enable cross-account and fine-grained principal access to individual secrets. kms: >- Callers also need kms:Decrypt/kms:GenerateDataKey on the customer-managed KMS key when the secret is encrypted with a non-default key. docs: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html