Amazon Web Services provider
Deterministic AWS contracts exist in source, but the provider is disabled and is not a customer runtime capability in v0.0.1. Current posture: Disabled in v0.0.1.
Exact release scope. This page documents the reviewed v0.0.1 source at fcc5871. Check release status before enabling a gated capability.
Release posture
Disabled in v0.0.1Deterministic AWS contracts exist in source, but the provider is disabled and is not a customer runtime capability in v0.0.1.
Implemented operation contracts
- ✓STS credential validation
- ✓Region, instance type and image discovery
- ✓VPC and subnet planning
- ✓VM lifecycle contracts
- ✓Create, scale and replace planning
Prerequisites
- ✓Least-privilege IAM identity and STS reachability
- ✓Explicit region, AMI and network metadata
- ✓Reviewed generated ingress policy
- ✓Live-provider evidence for every enabled operation
Limits and stop conditions
| Boundary | Operator rule |
|---|---|
| 01 | Disabled in v0.0.1 |
| 02 | Do not enable by configuration override |
| 03 | Provider quotas and throttling remain customer-owned |
| 04 | No hidden fallback to default VPC or image |
Evaluation workflow
- 01
Create a disposable provider boundary
Use dedicated credentials, quota/budget controls and no production workload.
- 02
Register and validate
Confirm allowed hosts, identity, region and discovery without retry loops.
- 03
Review the infrastructure plan
Inspect network, firewall, image, size, node identity and warnings.
- 04
Exercise lifecycle
Create, scale, replace, upgrade, failure/recovery and cleanup for the exact release.
- 05
Record the decision
Retain provider action IDs, OperationRuns, artifacts, residual risk and explicit approval or rejection.