Amazon Data Lifecycle Manager · Arazzo Workflow

Amazon Data Lifecycle Manager Untag Policy Resource

Version 1.0.0

Remove tags from a DLM resource and confirm removal by listing the resource's tags.

1 workflow 1 source API 1 provider
View Spec View on GitHub BackupEBS SnapshotsLifecycle ManagementStorageAutomationComplianceArazzoWorkflows

Provider

amazon-data-lifecycle-manager

Workflows

untag-policy-resource
Remove tags from a DLM resource and verify via a list.
Removes the provided tag keys from the resource identified by its ARN and then reads the resource's tags back to confirm they were removed.
2 steps inputs: resourceArn, tagKeys outputs: tags
1
removeTags
Remove the supplied tag keys from the resource identified by its ARN.
2
confirmRemoval
List the remaining tags on the resource so the caller can confirm the removed keys are no longer present.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon Data Lifecycle Manager Untag Policy Resource
  summary: Remove tags from a DLM resource and confirm removal by listing the resource's tags.
  description: >-
    Strips governance metadata from an Amazon Data Lifecycle Manager resource. The
    workflow removes the supplied tag keys from the resource identified by its
    ARN, then lists the tags on that same resource so the caller can confirm the
    keys are gone. Every step spells out its request inline so the flow can be
    read and executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: tagsApi
  url: ../openapi/amazon-data-lifecycle-manager-tags-api-openapi.yml
  type: openapi
workflows:
- workflowId: untag-policy-resource
  summary: Remove tags from a DLM resource and verify via a list.
  description: >-
    Removes the provided tag keys from the resource identified by its ARN and
    then reads the resource's tags back to confirm they were removed.
  inputs:
    type: object
    required:
    - resourceArn
    - tagKeys
    properties:
      resourceArn:
        type: string
        description: The ARN of the Data Lifecycle Manager resource to untag.
      tagKeys:
        type: array
        description: The list of tag keys to remove from the resource.
        items:
          type: string
  steps:
  - stepId: removeTags
    description: >-
      Remove the supplied tag keys from the resource identified by its ARN.
    operationId: untagResource
    parameters:
    - name: resourceArn
      in: path
      value: $inputs.resourceArn
    - name: tagKeys
      in: query
      value: $inputs.tagKeys
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      statusCode: $statusCode
  - stepId: confirmRemoval
    description: >-
      List the remaining tags on the resource so the caller can confirm the
      removed keys are no longer present.
    operationId: listTagsForResource
    parameters:
    - name: resourceArn
      in: path
      value: $inputs.resourceArn
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      tags: $response.body#/Tags
  outputs:
    tags: $steps.confirmRemoval.outputs.tags

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-data-lifecycle-manager-untag-policy-resource-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.