Amazon Secrets Manager · Arazzo Workflow

Amazon Secrets Manager Put New Version and Verify

Version 1.0.0

Store a new encrypted version of a secret with PutSecretValue, then read the current value to confirm the update.

1 workflow 1 source API 1 provider
View Spec View on GitHub ConfigurationCredentialsRotationSecretsSecurityArazzoWorkflows

Provider

amazon-secrets-manager

Workflows

put-version-and-verify
Attach a new secret version and verify it becomes the current value.
Calls PutSecretValue to create a new version of an existing secret, then calls GetSecretValue to confirm the new SecretString is served as the current value.
2 steps inputs: SecretId, SecretString outputs: currentSecretString, currentVersionId, newVersionId, secretArn
1
putSecretValue
Create a new encrypted version of the secret holding the supplied SecretString value.
2
getSecretValue
Read the secret value back to confirm the newly stored version is the one served by default.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon Secrets Manager Put New Version and Verify
  summary: Store a new encrypted version of a secret with PutSecretValue, then read the current value to confirm the update.
  description: >-
    The credential update pattern. When an application's password or API key
    changes, this workflow attaches a brand new encrypted version to an existing
    secret with PutSecretValue and stages it as AWSCURRENT, then reads the
    secret back to confirm the new version is the one served by default. Every
    step inlines the AWS JSON 1.1 X-Amz-Target header and request payload so the
    flow is self-describing.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-620.20
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-620.20
      capability_name: Identity & Access Management
      spec: amazon-secrets-manager-secrets-api-openapi.yml
      confidence: 0.8
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: secretsApi
  url: ../openapi/amazon-secrets-manager-secrets-api-openapi.yml
  type: openapi
workflows:
- workflowId: put-version-and-verify
  summary: Attach a new secret version and verify it becomes the current value.
  description: >-
    Calls PutSecretValue to create a new version of an existing secret, then
    calls GetSecretValue to confirm the new SecretString is served as the
    current value.
  inputs:
    type: object
    required:
    - SecretId
    - SecretString
    properties:
      SecretId:
        type: string
        description: The ARN or name of the secret to update.
      SecretString:
        type: string
        description: The new text data to encrypt and store as the latest version.
  steps:
  - stepId: putSecretValue
    description: >-
      Create a new encrypted version of the secret holding the supplied
      SecretString value.
    operationId: PutSecretValue
    parameters:
    - name: X-Amz-Target
      in: header
      value: secretsmanager.PutSecretValue
    requestBody:
      contentType: application/x-amz-json-1.1
      payload:
        SecretId: $inputs.SecretId
        SecretString: $inputs.SecretString
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      secretArn: $response.body#/ARN
      newVersionId: $response.body#/VersionId
      versionStages: $response.body#/VersionStages
  - stepId: getSecretValue
    description: >-
      Read the secret value back to confirm the newly stored version is the one
      served by default.
    operationId: GetSecretValue
    parameters:
    - name: X-Amz-Target
      in: header
      value: secretsmanager.GetSecretValue
    requestBody:
      contentType: application/x-amz-json-1.1
      payload:
        SecretId: $steps.putSecretValue.outputs.secretArn
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      currentVersionId: $response.body#/VersionId
      currentSecretString: $response.body#/SecretString
  outputs:
    secretArn: $steps.putSecretValue.outputs.secretArn
    newVersionId: $steps.putSecretValue.outputs.newVersionId
    currentVersionId: $steps.getSecretValue.outputs.currentVersionId
    currentSecretString: $steps.getSecretValue.outputs.currentSecretString

Work with this as data

Every workflow 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 arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow 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 workflow
curl "https://apis.io/api/v1/arazzo/amazon-secrets-manager-rotate-version-and-verify-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?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.