Amazon Web Services
Private pilot
AWS runs in a private pilot with narrower account and resource coverage. Confirm the supported scope and eligibility before connecting.
Amazon Web Services
Private pilot
- Included AWS accounts
- Read-only IAM role and External ID
- Cost Explorer cost and usage
- Permitted resource inventory
- AWS Price List catalog
Included scope, permitted reads, evidence and limitations
Read-only customer-cloud accessWhat your team reviews
- Account-native cost history
- Supported pilot review conditions
- Explicit missing evidence and scope
Define the AWS accounts for your pilot.
Agree the account, regions and resource types to include before creating the read-only role. Cost Explorer and inventory have separate collection requirements.
- Cost history for connected accounts
- A core set of checks: idle and stopped instances, unattached EBS volumes, unused Elastic IPs and similar leftovers
- Commitment coverage checks
These are supported review areas, not a promise that every resource has complete evidence. Permission-limited, unavailable, stale and partial scope remain explicit.
Connect, validate and review the available evidence.
- Confirm account scope
- Create the IAM role
- Validate the evidence
- Run a pilot audit
- Document the limits
Pilot coverage is narrower than Azure. Confirm account, region and evidence support; a plan does not grant pilot availability automatically.
Prepare for the first result
Confirm the scope for your early-access review.
Contact Costframe to confirm current availability, permissions and the evidence covered.