Amazon Data Pipeline · API Governance Rules

Amazon Data Pipeline API Rules

Spectral linting rules defining API design standards and conventions for Amazon Data Pipeline.

26 Rules error 13 warn 8 info 5
Generated by API Evangelist Written by API Evangelist tooling for Amazon Data Pipeline's APIs. It is a starting point, not a ruleset Amazon Data Pipeline publishes or enforces.
View Rules File View on GitHub

Rule Categories

action all error info no openapi operation pipeline request response schema security servers tags validation

Rules

warn
info-title-prefix
API title must start with "AWS Data Pipeline"
$.info.title
error
info-description-required
Info object must have a description
$.info
error
info-version-required
Info object must have a version
$.info
error
openapi-version-3x
Must use OpenAPI 3.x
$
error
servers-defined
Servers array must be defined
$
error
servers-https-only
All server URLs must use HTTPS
$.servers[*].url
info
action-based-paths
AWS Data Pipeline uses Action-based path conventions with ?Action= query parameter
$.paths[*]~
info
all-operations-use-post
AWS Data Pipeline uses POST for all operations
$.paths[*][get,put,patch,delete]
error
operation-summary-required
All operations must have a summary
$.paths[*][post]
error
operation-description-required
All operations must have a description
$.paths[*][post]
error
operation-id-required
All operations must have an operationId
$.paths[*][post]
warn
operation-id-camel-case
OperationId must use camelCase
$.paths[*][post].operationId
error
operation-tags-required
All operations must have tags
$.paths[*][post]
warn
request-body-json-content
All POST operations should support application/json
$.paths[*].post.requestBody.content
warn
tags-defined
Tags array should be defined globally
$
error
response-success-required
All operations must have a 200 response
$.paths[*][post].responses
error
response-description-required
All responses must have a description
$.paths[*][*].responses[*]
warn
schema-description-required
Top-level schemas should have a description
$.components.schemas[*]
error
security-schemes-defined
Security schemes must be defined
$.components
error
no-empty-descriptions
Descriptions must not be empty strings
$..description
info
pipeline-id-in-operations
Pipeline operations should reference pipelineId in request body
$.components.schemas[?(@ =~ /Request/)].properties
info
validation-output-has-errored
Validation operation responses should include errored field
$.components.schemas.PutPipelineDefinitionOutput.properties
warn
servers-expected-domain
Server URLs should be on the amazonaws.com domain.
$.servers[*].url
warn
schema-names-casing
Component schema names should be PascalCase (the dominant convention in this API).
$.components.schemas
info
schema-properties-casing
Schema properties should be camelCase (the dominant convention in this API).
$.components.schemas[*].properties
warn
error-schema-defined
A shared error schema (ValidationError) should be defined for error payloads.
$.components.schemas

Spectral Ruleset

Raw ↑
# authorship: generated by API Evangelist tooling. Stamped 2026-08-18
# on the file's own generator header (roadmap#64). An unmarked file is
# NOT assumed to be ours -- absence of evidence was never stamped.
x-method: generated
# amazon-data-pipeline — Spectral ruleset (strengthened)
# Plain Spectral. Existing hand-authored rules preserved; measured rules added
# from this provider's own OpenAPI conventions by strengthen_ruleset.py,
# then self-validated against the spec.
#
# Provenance:
#   - servers-https-only: 100% of servers already https (error)
#   - servers-expected-domain: 1/1 servers on amazonaws.com
#   - operationid-casing: camel @ 100% (n=13)
#   - schema-names-casing: pascal @ 100% (n=34)
#   - schema-properties-casing: camel @ 53% (n=75)
#   - security: global (root) — NOT emitting operation-security-required
#   - error-schema-defined: ValidationError
#   - merge: kept 22 existing, added 4 measured, upgraded 0
#   - added: servers-expected-domain, schema-names-casing, schema-properties-casing, error-schema-defined
extends:
  - spectral:oas
rules:
  info-title-prefix:
    description: API title must start with "AWS Data Pipeline"
    severity: warn
    given: $.info.title
    then:
      function: pattern
      functionOptions:
        match: ^AWS Data Pipeline
  info-description-required:
    description: Info object must have a description
    severity: error
    given: $.info
    then:
      field: description
      function: truthy
  info-version-required:
    description: Info object must have a version
    severity: error
    given: $.info
    then:
      field: version
      function: truthy
  openapi-version-3x:
    description: Must use OpenAPI 3.x
    severity: error
    given: $
    then:
      field: openapi
      function: pattern
      functionOptions:
        match: ^3\.
  servers-defined:
    description: Servers array must be defined
    severity: error
    given: $
    then:
      field: servers
      function: truthy
  servers-https-only:
    description: All server URLs must use HTTPS
    severity: error
    given: $.servers[*].url
    then:
      function: pattern
      functionOptions:
        match: ^https://
  action-based-paths:
    description: AWS Data Pipeline uses Action-based path conventions with ?Action= query parameter
    severity: info
    given: $.paths[*]~
    then:
      function: pattern
      functionOptions:
        match: ^/\?Action=
  all-operations-use-post:
    description: AWS Data Pipeline uses POST for all operations
    severity: info
    given: $.paths[*][get,put,patch,delete]
    then:
      function: falsy
  operation-summary-required:
    description: All operations must have a summary
    severity: error
    given: $.paths[*][post]
    then:
      field: summary
      function: truthy
  operation-description-required:
    description: All operations must have a description
    severity: error
    given: $.paths[*][post]
    then:
      field: description
      function: truthy
  operation-id-required:
    description: All operations must have an operationId
    severity: error
    given: $.paths[*][post]
    then:
      field: operationId
      function: truthy
  operation-id-camel-case:
    description: OperationId must use camelCase
    severity: warn
    given: $.paths[*][post].operationId
    then:
      function: pattern
      functionOptions:
        match: ^[a-z][a-zA-Z0-9]+$
  operation-tags-required:
    description: All operations must have tags
    severity: error
    given: $.paths[*][post]
    then:
      field: tags
      function: truthy
  request-body-json-content:
    description: All POST operations should support application/json
    severity: warn
    given: $.paths[*].post.requestBody.content
    then:
      field: application/json
      function: truthy
  tags-defined:
    description: Tags array should be defined globally
    severity: warn
    given: $
    then:
      field: tags
      function: truthy
  response-success-required:
    description: All operations must have a 200 response
    severity: error
    given: $.paths[*][post].responses
    then:
      function: schema
      functionOptions:
        schema:
          required:
          - '200'
  response-description-required:
    description: All responses must have a description
    severity: error
    given: $.paths[*][*].responses[*]
    then:
      field: description
      function: truthy
  schema-description-required:
    description: Top-level schemas should have a description
    severity: warn
    given: $.components.schemas[*]
    then:
      field: description
      function: truthy
  security-schemes-defined:
    description: Security schemes must be defined
    severity: error
    given: $.components
    then:
      field: securitySchemes
      function: truthy
  no-empty-descriptions:
    description: Descriptions must not be empty strings
    severity: error
    given: $..description
    then:
      function: pattern
      functionOptions:
        match: .+
  pipeline-id-in-operations:
    description: Pipeline operations should reference pipelineId in request body
    severity: info
    given: $.components.schemas[?(@ =~ /Request/)].properties
    then:
      field: pipelineId
      function: truthy
  validation-output-has-errored:
    description: Validation operation responses should include errored field
    severity: info
    given: $.components.schemas.PutPipelineDefinitionOutput.properties
    then:
      field: errored
      function: truthy
  servers-expected-domain:
    description: Server URLs should be on the amazonaws.com domain.
    severity: warn
    given: $.servers[*].url
    then:
      function: pattern
      functionOptions:
        match: amazonaws\.com
  schema-names-casing:
    description: Component schema names should be PascalCase (the dominant convention in this API).
    severity: warn
    given: $.components.schemas
    then:
      field: '@key'
      function: casing
      functionOptions:
        type: pascal
  schema-properties-casing:
    description: Schema properties should be camelCase (the dominant convention in this API).
    severity: info
    given: $.components.schemas[*].properties
    then:
      field: '@key'
      function: casing
      functionOptions:
        type: camel
  error-schema-defined:
    description: A shared error schema (ValidationError) should be defined for error payloads.
    severity: warn
    given: $.components.schemas
    then:
      field: ValidationError
      function: truthy

Work with this as data

Every ruleset 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 spectral rules

4 MCP tools reach this
  • find_rulesBrowse and filter every ruleset 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 ruleset
curl "https://apis.io/api/v1/rules/amazon-data-pipeline-spectral-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?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.