Skip to content
Cloud infrastructure/devops

amazonaws.com:accessanalyzer

Access Analyzer sandbox and mock API

<p>Identity and Access Management Access Analyzer helps identify potential resource-access risks by enabling you to identify any policies that grant access to an external principal. It does this by using logic-based reasoning to analyze resource-based policies in your Amazon Web Services environment. An external principal can be another Amazon Web Services account, a root user, an IAM user or role Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
28
Collections
-
Event types
-
Start this simulation
example request
curl https://your-amazonaws-accessanalyzer.slurry.io/analyzer \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2019-11-01.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 28.

  • PUT/archive-rule
  • GET/policy/generation/{jobId}
  • PUT/policy/generation/{jobId}
  • PUT/access-preview
  • GET/analyzer
  • PUT/analyzer
  • GET/analyzer/{analyzerName}/archive-rule
  • PUT/analyzer/{analyzerName}/archive-rule
  • GET/analyzer/{analyzerName}
  • DELETE/analyzer/{analyzerName}
  • GET/analyzer/{analyzerName}/archive-rule/{ruleName}
  • PUT/analyzer/{analyzerName}/archive-rule/{ruleName}