Console

http://localhost:7644/_pogi/

The console is a web page that pogi serves itself. It works in a browser on your own machine and is built for a laptop screen.

Press ⌘K (or Ctrl+K) on any page to search services, resources and actions. A cloud picker at the top narrows every page to AWS, Google Cloud or Azure. The sidebar lists the main pages, the services that hold resources ("In use") and the tools.

HomeCopy Anchor Link

/_pogi/

Shows how many services are in use, how many resources they hold, a live feed of recent calls, and quick actions such as saving a snapshot. On the first run it shows a welcome with your endpoint.

RequestsCopy Anchor Link

/_pogi/requests

Shows every call to every service, newest first. Click a call to see its request and response. The same list is in the REST API.

FlowsCopy Anchor Link

/_pogi/flows

A flow is everything one call set off, across services and clouds: notifications, subscriptions, triggers, retries and dead-letters. Each row shows the first call, the path it took, how many steps there were and how long it all took.

Click a flow to see its steps on a timeline. Click a step for its request and response.

ServicesCopy Anchor Link

/_pogi/services

Lists all the emulated services, grouped by category. Star a service to pin it to the sidebar.

MapCopy Anchor Link

/_pogi/map

Shows how your resources are wired, and what is flowing through them right now. Click a resource for its connections. You can export the map as SVG.

ResourcesCopy Anchor Link

/_pogi/resources/{service}

Click a service under "In use" to browse its resources in tables. Create resources from a form. Every create form has a CLI mirror, which shows the matching command so you can repeat the action in a script.

Some services have their own pages:

ToolsCopy Anchor Link

The sidebar lists these under "Tools".

The console shows your calls only. Chaos rules never apply to the console itself.

IAM form postsCopy Anchor Link

/_pogi/iam/...

These are the requests behind the buttons on the IAM page. They are HTML forms, not JSON: send the fields as application/x-www-form-urlencoded. They are not part of the REST API, and they may change between releases.

Every POST answers 303 with no body. A failed action redirects to an address with err= in it, so check the Location header. These calls follow the same-origin rule.

Set the mode:

curl -si -X POST localhost:7644/_pogi/iam/mode -d mode=soft | grep -iE '^(HTTP|location)'

HTTP/1.1 303 See Other
Location: /_pogi/iam?principal=

An unknown mode redirects with an error:

HTTP/1.1 303 See Other
Location: /_pogi/iam?err=unknown+mode+%22bogus%22

Get the recorded policy for a user:

curl "localhost:7644/_pogi/iam/policy?principal=arn:aws:iam::000000000000:user/dev"

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "s3:ListAllMyBuckets",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "sqs:ListQueues",
      "Resource": "*"
    }
  ]
}

Ask for a principal that has no recorded calls and the answer is 404 with nothing recorded for <principal>.

Attach it. The redirect carries the values that undo needs:

curl -si -X POST localhost:7644/_pogi/iam/attach -d principal=arn:aws:iam::000000000000:user/dev | grep -i '^location'

Location: /_pogi/iam?principal=arn%3Aaws%3Aiam%3A%3A000000000000%3Auser%2Fdev&attached=v1&policy=pogi-dev&arn=arn%3Aaws%3Aiam%3A%3A000000000000%3Apolicy%2Fpogi-dev&prev=&linked=1

See alsoCopy Anchor Link

• Switch IAM modes
• Flows and the Map
• REST API