Release intelligence
The daily digest classifies official AWS, Azure, Google Cloud, and OCI feeds locally. It adds lifecycle stage and review priority without sending feed data to an external AI API.
- Stage: preview, GA, security, deprecation, or retirement.
- Design: which scope, identity, network, data, or failure-domain assumption changed?
- Operations: what changes in inventory, defaults, quotas, metrics, pricing, runbooks, or rollback?
- Cross-cloud: compare implementations that satisfy the same business outcome, including operator responsibility.
Primary sources: AWS RSS / Azure RSS / Google Cloud Atom / OCI RSS. This is triage, not a claim of feature equivalence or production impact.
Four cloud design philosophies
Start with the isolation and governance model before looking for an equivalent product name. These are design tendencies derived from official landing-zone and well-architected guidance, not a ranking.
AWS — COMPOSABLE PRIMITIVES
Compose small service primitives across account and Region boundaries. Establish multi-account governance, central logging, SCPs, and network boundaries early.
- Primary isolation: account / OU
- Ask: which account, Region, and service responsibility boundary?
- Watch both identity and resource policies.
AZURE — ENTERPRISE CONTROL PLANE
Govern the enterprise through Entra, ARM, Management Groups, and Policy. A subscription is a policy, quota, billing, and operating boundary.
- Primary isolation: subscription / Management Group
- Ask: which tenant and inherited policy?
- Entra directory roles and Azure RBAC are separate.
GOOGLE CLOUD — GLOBAL PLATFORM & SRE
Bring project boundaries, global infrastructure, managed data, and SRE into the design. Confirm whether each resource is zonal, regional, or global.
- Primary isolation: project / folder
- Ask: what is the user SLO and resource scope?
- A project also scopes APIs, quotas, billing, and IAM.
OCI — COMPARTMENTS & DATABASE
Use nested compartments to segment IAM, quotas, and operations, with explicit database-centered enterprise architecture.
- Primary isolation: compartment
- Ask: which compartment, AD/FD, and database topology?
- Read both policy verbs and resource types.
Five checks for an “equivalent” service
| Dimension | Verify | Name-matching failure |
|---|---|---|
| Resource scope | Global, regional, or zonal | Two “load balancers” or “databases” can have different failure domains. |
| Isolation boundary | Account, subscription, project, or compartment | Treating all resource containers as the same control boundary. |
| Policy inheritance | Parent denies, exceptions, and data-plane policy | Mapping IAM role names while missing evaluation semantics. |
| Failure behavior | Existing data-plane behavior during control-plane failure | Comparing only SLA percentages. |
| Operator responsibility | Patching, backup, scaling, and failover | Assuming “managed” means the same responsibility split. |
Purpose-based service search
Search by workload outcome, then compare service boundaries and official documentation across all four providers.
Comparable public-price baselines
These are normalized list-price baselines, not bills or performance benchmarks. Confirm discounts, taxes, storage, networking, support, and the exact production SKU in official calculators.
Network boundaries
| Concept | AWS | Azure | Google Cloud | OCI |
|---|---|---|---|---|
| Virtual network | VPC is regional; subnets are zonal. | VNet and subnets are regional. | VPC is global; subnets are regional. | VCN and subnets are regional; subnets can be regional. |
| Private PaaS access | PrivateLink / VPC endpoints | Private Link / private endpoints | Private Service Connect | Service Gateway / private endpoints by service |
| Hybrid dedicated link | Direct Connect | ExpressRoute | Cloud Interconnect | FastConnect |
| DNS responsibility | Route 53 Resolver and private hosted zones | Private DNS zones and resolver | Cloud DNS policies and zones | Private DNS / resolver endpoints |
IAM evaluation questions
BOUNDARY FIRST
- Which organization, tenant, account, subscription, project, or compartment owns the resource?
- Which parent policies can deny the request?
- Is authorization evaluated on the control plane, data plane, or both?
WORKLOAD IDENTITY
- Prefer short-lived workload identity over static access keys.
- Separate human administration, deployment automation, and runtime identity.
- Test the effective policy and audit trail, not only the assigned role name.
Operations comparison
Normalize the operating model around user signals and ownership. Provider-native products differ, but the questions about SLOs, telemetry, alert actionability, cost allocation, and rollback remain comparable.
| Practice | Cross-cloud decision | Evidence to retain |
|---|---|---|
| SLO and availability | Define a user-visible SLI before mapping provider metrics. Document zonal, regional, and global dependencies. | SLO, error budget, dependency map, tested failover RTO/RPO. |
| Telemetry | Choose collection, retention, cardinality, and export boundaries explicitly. | Metric/log/trace inventory, retention policy, sampling and cost model. |
| Alerts | Page only for actionable user impact; route capacity and hygiene signals separately. | Owner, runbook, escalation, suppression, and post-incident follow-up. |
| Change safety | Track release stage, defaults, quota, data-plane behavior, and rollback. | Inventory query, canary, validation gate, rollback trigger. |
| FinOps | Allocate by business owner and environment; separate commitments from architecture. | Tags/labels, budgets, anomaly alerts, unit economics, commitment coverage. |
Certification and learning
Use certification material as a structured map of provider decisions. Return from wrong answers to the decision rule, instead of replaying every course.
Google Cloud PDE
- Record only wrong answers, lucky guesses, and questions narrowed to two choices.
- Write the missed requirement word, the wrong decision, and one rule for next time. Do not copy exam questions.
- Recall the rule after one, three, and seven days; retire it after three successful explanations.