Skip to main content
Version: 0.3.0

The console, page by page

The console is the reason Emuplane exists: every claim it makes is backed by a read the console can actually perform. A page that cannot read something says so instead of showing an empty table.

The console home page: recent services, backend health, usage and the two endpoints

Console Home is a grid of widgets, every one of them a read: the emulator's health, the account's resource counts, and the addresses to point a CLI at.

The frame​

  • Region menu (top bar) — sets the region every page acts in, and follows into the URL, so a page you can see is a page you can bookmark.
  • Navigation — services down the side. S3 is the one with purpose-built pages today; every other service opens the generic service page until its own pages land, so adding pages later changes the menu rather than the rule.
  • Account menu — the signed-in account, its access keys, its regions, and the sign-in screens.

Signing out is a real session revocation, and a wrong password is answered as a wrong password rather than as "your session expired".

Every service is browsable​

All services: every service the emulator advertises, grouped by category

The service catalogue is read from the emulator, so a service it does not answer is not in the list.

Every service the emulator advertises is browsable: the console reads what the emulator holds and groups it by kind (IAM users/roles/groups/policies, EC2 instances/security groups/key pairs, and so on), one tab per kind.

Eleven services also ship actions — s3, ec2, sqs, sns, dynamodb, iam, logs, secretsmanager, ssm, kinesis, stepfunctions. The API explorer drives those through one control route (/api/exec), with the AWS call each action maps to shown before you press it.

The SQS service page: the resource list above, the API explorer's actions below

One generic service page: what the emulator holds on top, the catalogue of actions underneath, each showing the aws command it maps to.

S3​

The buckets page: every bucket in the account, each row carrying its own region

Two pages carry the console's own shape rather than the emulator's:

PageWhat it is
BucketsEvery bucket across the account's enabled regions, each row carrying its own region.
BucketThe console's tabs: Objects, Properties, Permissions, Management, File systems, Access Points.
ObjectContent, Tags, Annotations, Object Lock — each read on its own.
Access PointsGeneral purpose, Multi-Region and Object Lambda, each tab read from the region (or the one region) that serves it.

One bucket's Objects tab: the folder listing, the selection toolbar and the folder's incomplete uploads

S3 covers what each of those does, with a screenshot of every tab; S3 coverage records which operations are reachable and which are not.

Where the console is deliberately plain​

A page never invents a control the backend cannot carry. Directory buckets, Storage Lens and S3 Metrics are absent rather than empty; Object Lambda access points are listed but not created; a failed read is an error alert, not a zero-row table.