Loading…
Open-Policy Exchange
~8 min to deploy
AWS Agent Egress & Spend Gate
Opens sandbox egress only for the exact target the grant covers, and stops a run that would blow the account budget.
For: Platform teams running agent workloads inside their own AWS account
SOC 2 CC6.1ISO 27001 A.8.20Cloud spend evidence
What it enforces
Bound-grant egress
Blocks outbound traffic to any target the issued execution grant does not name explicitly.
Single-use grant
Blocks reuse of an execution grant that has already been consumed.
Daily burn circuit breaker
Restrains automated changes that would materially increase daily burn.
aws-agent-egress-and-spend-gate.yaml
# AWS Agent Egress & Spend Gate
# Fork: set your own burn threshold; grants stay action- and target-bound.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: aws-agent-egress-and-spend-gate
surface: aws
standards: [SOC2-CC6.1, ISO27001-A.8.20]
defaults:
mode: shadow
emit_dossier: true
fail_closed: true
rules:
- name: bound_grant_egress
when: "action == 'sandbox.open_egress'"
decision: |
BLOCK IF target not in grant.bound_targets
ALLOW OTHERWISE
reason_code: egress_target_not_in_grant
- name: single_use_grant
when: "action == 'grant.consume'"
decision: |
BLOCK IF grant.consumed == true
ALLOW OTHERWISE
reason_code: grant_already_consumed
- name: daily_burn_circuit_breaker
when: "action == 'infrastructure.change'"
decision: |
RESTRAIN IF daily_burn_delta_percent > 15
ALLOW OTHERWISE
reason_code: burn_delta_over_threshold
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Follow the install path for this surface, then paste the forked YAML as your policy config.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.