Amazon Secrets Manager · Authentication Profile

Amazon Secrets Manager Authentication

Authentication

Amazon Secrets Manager secures its APIs with aws-sigv4 across 1 declared security scheme, as derived from its OpenAPI definitions.

ConfigurationCredentialsRotationSecretsSecurity
Methods: aws-sigv4 Schemes: 1 OAuth flows: API key in:

Security Schemes

aws-sigv4 sigv4

Source

Authentication Profile

Raw ↑
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

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/amazon-secrets-manager-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.