# UltraInfra security

[Website page](https://ultrainfra.ai/security/)

You own the cloud, set the limits, and can stop access at any time. UltraInfra uses temporary AWS STS credentials through a revocable role; the customer retains runtime and billing ownership. No long-lived IAM user access keys are required for the supported connection model.

## Checks before change

- Explicit organization, project, account, environment, and resource scope.
- Evidence freshness, coverage, and version alignment; incomplete evidence fails closed.
- Action policy covering autonomy mode, budget, risk, maintenance windows, entitlements, and safety stops.
- Temporary credentials for the exact approved operation.
- An immutable decision ledger binding evidence, parameters, workflow, policy, and evaluation versions.
- Verification and recovery determining completion, rollback, abandonment, or escalation.

AI cannot give itself permission. Only versioned action-catalogue operations can reach the independent evaluator and workflow layer. Decisions expire or re-evaluate when bound facts or authority change. Removing or invalidating the connected role stops new AWS authority.

GCP and Azure semantics currently support observation, recommendation, and planning only; they do not add credentials, live collectors, or mutation paths.

[AWS access guide](/guides/how-ultrainfra-accesses-aws/index.md)