generated: '2026-06-20'
method: derived
source: openapi/amazon-compute-optimizer-openapi.yml + docs.aws.amazon.com/compute-optimizer
description: >-
  Cross-cutting / industry standard conformance for the AWS Compute Optimizer
  API, derived from the OpenAPI security schemes and request/response shapes and
  from the AWS documentation.
standards:
  - id: aws-sigv4
    conforms: true
    evidence: >-
      securitySchemes.hmac (Authorization header, x-amazon-apigateway-authtype
      awsSigv4); security requirement hmac applied globally.
  - id: oauth2
    conforms: false
    evidence: No oauth2 security scheme; authentication is AWS SigV4.
  - id: oidc
    conforms: false
  - id: rfc9457-problem-details
    conforms: false
    evidence: >-
      Errors use the AWS JSON error shape (typed exception objects with a
      message field), not application/problem+json.
  - id: json-api
    conforms: false
  - id: odata
    conforms: false
  - id: fhir-r4
    conforms: false
  - id: scim2
    conforms: false
  - id: fapi
    conforms: false
  - id: psd2
    conforms: false
  - id: pagination
    conforms: true
    evidence: >-
      Token-based pagination via nextToken request/response fields and
      maxResults on the Get*Recommendations and Describe* operations.
  - id: idempotency
    conforms: false
    evidence: No Idempotency-Key header defined; reads are naturally idempotent.
  - id: rest-json
    conforms: true
    evidence: >-
      JSON over HTTPS with X-Amz-Target operation dispatch (AWS JSON 1.0
      protocol) as modeled in the OpenAPI.