Spectro Cloud · Schema
v1.DataSinkCloudWatchConfig
Data sink cloud watch config
CompanyInfrastructureKubernetesCloud-NativeCluster ManagementEdge ComputingMulti-CloudDevOpsAI Infrastructure
Properties
| Name | Type | Description |
|---|---|---|
| payload | object | |
| spec | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/spectro-cloud/main/json-schema/spectro-cloud-v1-data-sink-cloud-watch-config-schema.json",
"title": "v1.DataSinkCloudWatchConfig",
"description": "Data sink cloud watch config",
"x-generated": "2026-10-04",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/spectro-cloud-data-sinks-api-openapi.yml#/components/schemas/v1.DataSinkCloudWatchConfig",
"properties": {
"payload": {
"$ref": "#/$defs/v1.DataSinkPayloads"
},
"spec": {
"$ref": "#/$defs/v1.CloudWatchConfig"
}
},
"type": "object",
"$defs": {
"v1.CloudWatchConfig": {
"description": "Cloud watch config entity",
"properties": {
"credentials": {
"$ref": "#/$defs/v1AwsCloudAccount"
},
"group": {
"description": "Name of the group",
"type": "string"
},
"region": {
"description": "Name of the region",
"type": "string"
},
"stream": {
"description": "Name of the stream",
"type": "string"
}
},
"type": "object"
},
"v1.DataSinkPayload": {
"additionalProperties": {
"type": "object"
},
"description": "Data sink payload entity",
"properties": {
"refUid": {
"description": "RefUid of the data sink payload",
"type": "string"
},
"timestamp": {
"$ref": "#/$defs/v1Time"
}
},
"type": "object"
},
"v1.DataSinkPayloads": {
"description": "List of data sink payload entities",
"items": {
"$ref": "#/$defs/v1.DataSinkPayload"
},
"type": "array",
"uniqueItems": true
},
"v1AwsCloudAccount": {
"description": "AWS cloud account which includes access key and secret key in case of 'secret' credentials type. It includes policyARNS, ARN and externalId in case of sts. It includes roleArn and permissionBoundaryArn in case of podIdentity. Partition is a group of AWS Region and Service objects",
"properties": {
"accessKey": {
"description": "AWS account access key",
"type": "string"
},
"credentialType": {
"$ref": "#/$defs/v1AwsCloudAccountCredentialType"
},
"partition": {
"default": "aws",
"description": "AWS accounts are scoped to a single partition. Allowed values [aws, aws-us-gov], Default values",
"enum": [
"aws",
"aws-us-gov",
"aws-iso",
"aws-iso-b"
],
"type": "string"
},
"podIdentity": {
"$ref": "#/$defs/v1AwsPodIdentityCredentials",
"description": "AWS EKS Pod Identity credentials in case of credentialType podIdentity, will be empty in case of other credential types"
},
"policyARNs": {
"description": "List of policy ARNs required in case of credentialType sts.",
"items": {
"type": "string"
},
"type": "array"
},
"secretKey": {
"description": "AWS account secret key",
"type": "string"
},
"secretSpec": {
"$ref": "#/$defs/v1AwsSecretSpec"
},
"secretToken": {
"description": "AWS account secret token; in case of aws-iso and aws-iso-b",
"type": "string"
},
"sts": {
"$ref": "#/$defs/v1AwsStsCredentials",
"description": "AWS STS credentials in case of credentialType sts, will be empty in case of credential type secret"
}
},
"type": "object"
},
"v1AwsCloudAccountCredentialType": {
"default": "secret",
"description": "Allowed Values [secret, sts, pod-identity]. STS type will be used for role assumption for sts type, accessKey/secretKey contains the source account, Arn is the target account. Pod Identity type will be used for EKS Pod Identity authentication with roleArn as the target account.",
"enum": [
"secret",
"sts",
"pod-identity"
],
"type": "string"
},
"v1AwsPodIdentityCredentials": {
"description": "AWS EKS Pod Identity credentials for role assumption",
"properties": {
"permissionBoundaryArn": {
"description": "Optional Permission Boundary ARN to limit the maximum permissions for roles created by Hubble",
"type": "string"
},
"roleArn": {
"description": "IAM Role ARN for the AWS EKS Pod Identity in cloud account",
"type": "string"
}
},
"type": "object"
},
"v1AwsSecretSpec": {
"description": "AWS cloud account which includes access key and secret key in case of 'secret' credentials type. It includes policyARNS, ARN and externalId in case of sts. Partition is a group of AWS Region and Service objects",
"properties": {
"accountName": {
"description": "AWS secret accountName; only for aws-iso-b environment",
"type": "string"
},
"agency": {
"description": "AWS secret agency",
"type": "string"
},
"isCapValidationEnabled": {
"description": "Flag to rotate the secret region credentials",
"type": "boolean"
},
"mission": {
"description": "AWS secret mission; only for aws-iso environment",
"type": "string"
},
"namePrefix": {
"description": "Policy Boundary",
"type": "string"
},
"permissionBoundary": {
"description": "Role or Policy Prefix",
"type": "string"
},
"policy": {
"description": "AWS secret policy; JSON string",
"type": "string"
},
"role": {
"description": "AWS secret role",
"type": "string"
},
"tls": {
"$ref": "#/$defs/v1AwsSecretTlsConfig",
"description": "TLS configuration for the AWS secret"
}
},
"type": "object"
},
"v1AwsSecretTlsConfig": {
"description": "TLS configuration for the AWS secret",
"properties": {
"ca": {
"description": "CA certificate",
"type": "string"
},
"cert": {
"description": "Certificate",
"type": "string"
},
"key": {
"description": "Key",
"type": "string"
}
},
"type": "object"
},
"v1AwsStsCredentials": {
"description": "Aws sts credentials",
"properties": {
"arn": {
"description": "Arn for the aws sts credentials in cloud account",
"type": "string"
},
"externalId": {
"description": "ExternalId for the aws sts credentials in cloud account",
"type": "string"
}
},
"type": "object"
},
"v1Time": {
"description": "Time is a wrapper around time.Time which supports correct marshaling to YAML and JSON. Wrappers are provided for many of the factory methods that the time package offers.",
"format": "date-time",
"type": "string"
}
}
}
Work with this as data
Every JSON Schema 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 schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema 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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/spectro-cloud-v1-data-sink-cloud-watch-config"
All schemas
curl "https://apis.io/api/v1/json-schemas?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.