Amazon EventBridge Schema Registry
Registry of OpenAPI and JSONSchema event schemas with discovery and generated code bindings.
- Provider
- aws
- Kind
- Schema registry
- Category
- Data
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| compatibility | enum | none | backward | forward | full | no | backward | ▸ none |
| crossAccountDiscovery | boolean | — | no | true | inherited |
| discoveryEnabled | boolean | — | no | false | inherited |
| enforced | boolean | — | no | false | ▸ false |
| managed | boolean | — | no | false | ▸ true |
| schemaFormat | enum | openapi3 | jsonschema-draft4 | no | openapi3 | inherited |
| versioned | boolean | — | no | true | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
No rule reads this kind yet. That is a gap, not a guarantee.
nodes:
- { id: "eventbridge-schemas", component: "aws-eventbridge-schemas" }# yaml-language-server: $schema=../../schema/component.schema.json # Amazon EventBridge Schema Registry: registries of OpenAPI 3 and JSONSchema Draft4 schemas used # to generate code bindings. "Amazon EventBridge schemas" describes no compatibility check and no # runtime validation of events, and "Inferring schemas from event bus events" shows discovery is # off until you start a discoverer, after which every changed event creates a new schema version. schemaVersion: "1" type: "component" id: "aws-eventbridge-schemas" kind: "schema-registry" provider: "aws" docs: "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-schema-registry.html" defaults: managed: true compatibility: "none" enforced: false properties: schemaFormat: type: "enum" values: ["openapi3", "jsonschema-draft4"] default: "openapi3" discoveryEnabled: type: "boolean" default: false crossAccountDiscovery: type: "boolean" default: true versioned: type: "boolean" default: true