# 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-compute-optimizer — 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: 50% of servers already https (warn)
# - query-params-casing: camel @ 100% (n=10)
# - operationid-casing: pascal @ 100% (n=21)
# - schema-names-casing: pascal @ 100% (n=283)
# - schema-properties-casing: camel @ 69% (n=356)
# - security: global (root) — NOT emitting operation-security-required
# - error-schema-defined: GetRecommendationErrors
# - pagination params observed: ['maxResults', 'nextToken']
# - merge: kept 22 existing, added 4 measured, upgraded 0
# - added: query-params-casing, schema-names-casing, schema-properties-casing, error-schema-defined
extends:
- spectral:oas
rules:
info-title-required:
description: OpenAPI info must have a title.
severity: error
given: $.info
then:
field: title
function: truthy
info-description-required:
description: OpenAPI info must have a description.
severity: warn
given: $.info
then:
field: description
function: truthy
info-version-required:
description: OpenAPI info must have a version field.
severity: error
given: $.info
then:
field: version
function: truthy
openapi-version-3:
description: Specs must use OpenAPI 3.0.x.
severity: error
given: $
then:
field: openapi
function: pattern
functionOptions:
match: ^3\.0\.
servers-required:
description: At least one server must be defined.
severity: error
given: $
then:
field: servers
function: truthy
servers-https-required:
description: Server URLs should use HTTPS.
severity: warn
given: $.servers[*]
then:
field: url
function: pattern
functionOptions:
match: ^https://
operation-summary-required:
description: Every operation must have a summary.
severity: error
given: $.paths[*][get,post,put,patch,delete]
then:
field: summary
function: truthy
operation-summary-amazon-prefix:
description: Operation summaries should start with Amazon Compute Optimizer.
severity: warn
given: $.paths[*][get,post,put,patch,delete].summary
then:
function: pattern
functionOptions:
match: ^Amazon Compute Optimizer
operation-description-required:
description: Every operation must have a description.
severity: warn
given: $.paths[*][get,post,put,patch,delete]
then:
field: description
function: truthy
operation-id-required:
description: Every operation must have an operationId.
severity: error
given: $.paths[*][get,post,put,patch,delete]
then:
field: operationId
function: truthy
operation-id-pascal-case:
description: OperationIds should use PascalCase as per AWS convention.
severity: warn
given: $.paths[*][get,post,put,patch,delete].operationId
then:
function: pattern
functionOptions:
match: ^[A-Z][a-zA-Z0-9]*$
operation-tags-required:
description: Every operation must have at least one tag.
severity: warn
given: $.paths[*][get,post,put,patch,delete]
then:
field: tags
function: truthy
parameter-description-required:
description: Every parameter must have a description.
severity: warn
given: $.paths[*][get,post,put,patch,delete].parameters[*]
then:
field: description
function: truthy
request-body-json-content:
description: Request bodies should use application/json.
severity: warn
given: $.paths[*][post,put,patch].requestBody.content
then:
field: application/json
function: truthy
response-description-required:
description: Every response must have a description.
severity: warn
given: $.paths[*][get,post,put,patch,delete].responses[*]
then:
field: description
function: truthy
schema-description-recommended:
description: Top-level schemas should have a description.
severity: info
given: $.components.schemas[*]
then:
field: description
function: truthy
schema-type-defined:
description: Schema objects should have a type.
severity: warn
given: $.components.schemas[*]
then:
field: type
function: truthy
security-schemes-defined:
description: Security schemes must be defined.
severity: error
given: $.components
then:
field: securitySchemes
function: truthy
get-no-request-body:
description: GET operations should not have a request body.
severity: error
given: $.paths[*].get
then:
field: requestBody
function: falsy
compute-optimizer-resource-arn-documented:
description: ResourceArn parameters should include supported resource type documentation.
severity: info
given: $.components.schemas[*].properties.resourceArn
then:
field: description
function: truthy
no-empty-descriptions:
description: Descriptions must not be empty strings.
severity: warn
given: $..description
then:
function: truthy
microcks-operation-extension:
description: Operations should have x-microcks-operation for mock server compatibility.
severity: info
given: $.paths[*][get,post,put,patch,delete]
then:
field: x-microcks-operation
function: truthy
query-params-casing:
description: Query parameters should be camelCase (the dominant convention in this API).
severity: warn
given: $.paths[*][get,post,put,patch,delete].parameters[?(@.in=='query')]
then:
field: name
function: casing
functionOptions:
type: camel
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: pattern
functionOptions:
match: ^[A-Z][A-Za-z0-9]*$
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: pattern
functionOptions:
match: ^[a-z][A-Za-z0-9]*$
error-schema-defined:
description: A shared error schema (GetRecommendationErrors) should be defined for error payloads.
severity: warn
given: $.components.schemas
then:
field: GetRecommendationErrors
function: truthy
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.