Coverage — what works today
Every service surfaced by Vyomi, across AWS, GCP, and Azure, with a real-backend or simulated indicator. Numbers below are generated from the live service catalog at build time — not curated screenshots.
Service matrix
35 services across 3 clouds. Tagged real backend when actual production software (Postgres, Vault, MinIO, NATS, etc.) provides the data plane; simulated when Vyomi models the contract + lifecycle in process.
| Category | Service | AWS | GCP | Azure | Status |
|---|---|---|---|---|---|
| Compute | Virtual machines | ✓ EC2 sim | ✓ Compute Engine sim | ✓ Virtual Machines sim | Stable |
| Compute | Functions as a Service | ✓ Lambda sim | ✓ Cloud Functions sim | ✓ Function Apps sim | Stable |
| Storage | Object storage | ✓ S3 MinIO | ✓ Cloud Storage fake-gcs | ✓ Blob Storage MinIO | Stable |
| Database | Relational SQL | ✓ RDS Postgres + MySQL | ✓ Cloud SQL Postgres + MySQL | ✓ Azure SQL Postgres + MySQL | Stable |
| Database | NoSQL / document | ✓ DynamoDB DDB Local | ✓ Firestore gcloud emu | ✓ Cosmos DB sim | Stable |
| Messaging | Message queue | ✓ SQS ElasticMQ | — (via Pub/Sub) | ✓ Service Bus REST only | Stable |
| Messaging | Publish/subscribe | — (via EventBridge) | ✓ Pub/Sub gcloud emu | — (via Service Bus) | Stable |
| Eventing | Event bus / routing | ✓ EventBridge NATS | ✓ Eventarc NATS | ✓ Event Grid NATS | Stable |
| Networking | Virtual network (VPC) | ✓ VPC sim | ✓ VPC Network sim | ✓ VNet + NSG sim | Stable |
| API | API gateway / management | ✓ API Gateway sim | ✓ API Gateway sim | ✓ APIM sim | Stable |
| Identity | IAM / RBAC policy | ✓ IAM Cedar | ✓ IAM Cedar | ✓ Entra/RBAC Cedar | Stable |
| Security | Secret manager | ✓ Secrets Manager Vault | ✓ Secret Manager Vault | ✓ Key Vault Vault | Stable |
| Security | Key management (KMS) | ✓ KMS Vault Transit | ✓ Cloud KMS Vault Transit | ✓ Key Vault Keys Vault Transit | Stable |
SDK · CLI · IaC compatibility
Vyomi serves the wire protocol of each cloud's official APIs,
so standard SDKs and CLIs work natively against it — point the
endpoint URL at http://localhost:9000
and the rest is the same code you'd write for production.
| Tool | AWS | GCP | Azure |
|---|---|---|---|
| CLI | ✓ aws CLI v2 | ✓ gcloud + gsutil + bq | ✓ az CLI |
| Python SDK | ✓ boto3 | ✓ google-cloud-* | ✓ azure-sdk-for-python |
| Java SDK | ✓ aws-sdk-java v2 | ✓ google-cloud-java | ✓ azure-sdk-for-java |
| Go SDK | ✓ aws-sdk-go-v2 | ✓ google-cloud-go | ✓ azure-sdk-for-go |
| Terraform provider | ✓ hashicorp/aws | ✓ hashicorp/google | ✓ hashicorp/azurerm |
| Terraform export | ✓ state → real cloud | ✓ state → real cloud | ✓ state → real cloud |
Known fidelity gaps
Where Vyomi deliberately diverges from production cloud behavior. These are the items the conformance suite flags as acknowledged deviations — not silent bugs.
-
AWS S3 aws-chunked encoding: aws-sdk-java v2 sends
PUTs with chunked transfer encoding + embedded signatures. The
simulator's S3 doesn't de-chunk yet. SDK workaround:
.chunkedEncodingEnabled(false). Tracked. - KMS encrypt/decrypt roundtrip: 2 warnings in the conformance suite — exact key-blob format differs from real KMS for some algorithms. Most code paths pass.
- MinIO read-through cache: 1 known failure under rapid PUT-then-GET patterns. MinIO's eventual-consistency window is not 1:1 with S3.
- Azure Service Bus AMQP: only REST is supported today; AMQP 1.0 is on the roadmap. Use HTTP endpoints in SDK client config until then.
- Azure SDK partial: Java + Go target services (Compute, Storage, SQL, Service Bus, Cosmos) work end-to-end; smaller services may have client-shape gaps.
Want to see how these get measured? → Conformance Report · Architecture & Real Backends · Back to API Reference