How We Build / Live-AWS Integration Report
Unit tests prove logic in isolation; these prove the real data plane. Each suite provisions an actual stack -- real EC2 instances, ENIs, route tables, and load balancers -- drives traffic through it, and verifies behavior under normal and failure conditions before tearing everything down.
521+
live-AWS integration scenarios
48
end-to-end test suites
13
capability areas covered
2
deploy lanes exercised (CloudFormation + Terraform)
Capability Coverage
Every suite below runs against live infrastructure. Scenario counts are floor figures measured from the suite; deploy-lane and parameter matrices multiply the real number of stack runs. Individual test names and code are omitted by design.
| Capability area | Scenarios | Result |
|---|---|---|
| NAT egress, GWLB & port forwarding | 57 | PASS |
| High availability, failover & scaling | 97 | PASS |
| Firewall, IDS/IPS & threat prevention | 82 | PASS |
| Web security & TLS | 82 | PASS |
| Transit mesh, VPC peering & edge | 74 | PASS |
| Kubernetes & multi-account fabric | 30 | PASS |
| AI gateway: caching & inference | 38 | PASS |
| Elastic application catalog | 14 | PASS |
| Cross-account IAM provisioning | 3 | PASS |
| Deploy modes: CloudFormation, Terraform & standalone | 26 | PASS |
| Onboarding & entitlement | 10 | PASS |
| Monitoring & observability | 5 | PASS |
| Teardown & resource cleanup | 3 | PASS |
Both deploy lanes, one standard. Cloud Spectra can be deployed by CloudFormation or by a native Terraform module. The same integration suites run against both, so neither path can silently drift from the other.
Sanitized on purpose. No source code, file paths, account IDs, stack names, or internal identifiers appear here -- only aggregate counts and human-written capability labels. An automated guard fails the build if anything else slips in.
See Also
Automatically generated from the integration suite on 2026-07-16. Counts are floor figures; the live run multiplies them across deploy lanes and parameter cases.