Services Matrix

Which cloud services DevCloud serves, and how deeply.

Counts live in coverage.md: it is the primary page that publishes official counts, and CI validates that its figures match the binary. This page describes the architectural shape of supported services.

Looking Up a Service

Per-operation depth is declared by the generated fidelity manifest. You can query it directly using the Admin API (requires admin.enabled: true):

curl -s 'localhost:4747/devcloud/api/fidelity?service=s3'
TierWhat it means
hand-verifiedThe service provider explicitly implements and dispatches the operation.
auto-crudServed by the generic CRUD engine: store-backed and plausible responses.
unimplementedRefused with an authentic cloud error format. Never returns a fabricated success.

Depth by Group

AWS

GroupServicesDepth
CoreS3, SQS, DynamoDB, Lambda, IAM, STSHand-written throughout; deepest SDK coverage
IntegrationSNS, EventBridge, CloudWatch, CloudWatch Logs, KMS, Secrets Manager, SSM, ECR, CloudFormationHand-written common operations plus cross-service event routing
ExtendedEC2, ECS, EKS, Route53, ACM, RDS, Kinesis, Firehose, Step Functions, Bedrock, and long-tail servicesCommon operations hand-written; long tail is engine-served or declines cleanly

The tier1 / tier2 / tier3 tokens accepted by DEVCLOUD_SERVICES represent startup convenience sets, not depth tiers. See configuration.md for details.

Azure

ServiceIdentifierProtocolDepth
Blob StorageblobREST-XMLHand-written container and block blob lifecycle, chunked blocks, conditional requests
Queue StorageazurequeueREST-XMLHand-written queue management, FIFO messages, visibility timeouts, pop receipts
Table StorageazuretableREST-JSON (OData)SQLite-backed OData table and entity operations, composite key lookups
Cosmos DBcosmosdbREST-JSONSQLite-backed NoSQL document store, collections, partition keys, system attributes
Key VaultazurekeyvaultREST-JSONHand-written secret versioning, payload retrieval, RSA software-backed keys
App ConfigurationazureappconfigREST-JSONHand-written key-values, ETag tracking, tag management, label filtering

GCP

ServiceIdentifierProtocolDepth
Cloud StoragegcsREST-JSONHand-written bucket/object CRUD, media/resumable uploads, downloads, CRC32c checksums
Secret ManagergcpsecretsREST-JSONHand-written secret lifecycle, version management, payload access, and destruction
Cloud Pub/SubgcppubsubREST-JSONHand-written topic/subscription lifecycle, batch publishing, message pull/ack delivery

Cross-Service Integrations

These integrations execute real workflows locally:

IntegrationImplementation
CloudFormation -> Resource Typescloudformation/engine.go: topological sort and intrinsic functions
DynamoDB -> DynamoDB StreamsWrite paths publish stream change records
DynamoDB Streams -> Lambdalambda/eventsource.go polls stream shards
SQS -> LambdaEvent source polling worker
S3 -> Lambdas3/notifications.go on PUT events
EventBridge -> SQS / SNS / LambdaRule matching and target dispatch
SNS -> SQSTopic publish triggers queue delivery

Protocols

ProtocolContent typeExample services
JSON 1.0application/x-amz-json-1.0DynamoDB, DynamoDB Streams, Kinesis
JSON 1.1application/x-amz-json-1.1ECS, Lambda, Batch, CloudWatch Logs, Step Functions
REST-JSONapplication/jsonACM, API Gateway, GCS, GCP Secrets, Azure Key Vault, App Config
REST-XMLapplication/xmlS3, Route53, CloudFront, Azure Blob, Azure Queue
Queryapplication/x-www-form-urlencodedIAM, STS, SQS, SNS, RDS, EC2, AutoScaling
EC2 Queryapplication/x-www-form-urlencodedEC2 (EC2-compliant XML with <requestId>)
RPC-v2 CBORapplication/cborPartner Central Revenue Measurement

SQS supports both Query and JSON protocols, auto-detected per request.

Verification

make test          # Go unit tests
make test-compat   # Multi-cloud compatibility test suites
make stats         # Registered services and hand-written operations inventory

The compatibility test suite runs in CI on every commit. A failing test fails the build.