floci-aws-ui
v0.2.0
Published
A web console for floci, the local AWS emulator. Looks and works like the AWS console.
Maintainers
Readme
Floci Console
A web console for floci, the local AWS emulator. It looks and works like the AWS console, so a team that knows AWS can use an on-prem non-prod environment without learning a new tool.
It is built with Cloudscape, the open source design system that the AWS console itself uses.
The console has no login. Anyone who can open it can change everything in floci. Run it only on a private network.
This is a community project. It is not part of floci and it is not affiliated with Amazon Web Services.
Run it with npx
You need Node 20 or newer and a running floci. Nothing to install or build.
npx floci-aws-ui serve # floci on http://localhost:4566
npx floci-aws-ui serve --floci http://your-floci-host:4566 --port 9000Then open http://localhost:8080.
The command checks that floci answers. If it does not, it prints how to start floci and keeps running.
| Option | Default | Meaning |
|--------|---------|---------|
| --floci, -f | http://localhost:4566 | Where floci listens. |
| --port, -p | 8080 | Port for the console. |
| --host, -H | 127.0.0.1 | Address to listen on. Use 0.0.0.0 to let other machines in. |
See it in 21 seconds

The same clip with sound: docs/video/floci-console.mp4. GitHub cannot play it in the page, so download it.
Screenshots
Console Home

SQS queues

S3 bucket

Parameter Store

What it covers
| Service | What you can do | |---------|-----------------| | Console Home | See resource counts, service health and the CLI profile for this environment. | | Lambda | Dashboard. List, create and delete functions. Edit code in the browser and deploy. Run test events. Read logs. Change memory, timeout, handler and environment variables. Manage layers and event source mappings. | | S3 | Create, empty and delete buckets. Browse folders. Upload, download, open, preview and delete objects. | | CloudWatch | Overview. Browse log groups and streams. Read log events with a time filter and live tail. Create and delete alarms. Graph metrics. | | EC2 | Dashboard. Launch, start, stop, reboot and terminate instances. Manage security groups, key pairs, volumes, snapshots and Elastic IPs. List AMIs. | | API Gateway | REST APIs: resources, methods (Lambda, HTTP or mock), deploy to a stage. HTTP APIs: routes, integrations, stages. Send a test request to a stage from the page. | | CloudFront | List, create, enable, disable and delete distributions. See origins and behaviors. Create invalidations. | | RDS | Create, stop, start, reboot and delete databases. Shows the connect command. Snapshots and subnet groups. | | Secrets Manager | Store, read, edit and delete secrets, as key/value pairs or plain text. | | IAM | Users, user groups, roles and policies. Attach and detach policies. Create access keys. Edit trust policies. | | Parameter Store | Create, edit and delete parameters. Version history. Show and hide SecureString values. | | SQS | Create, purge and delete queues, standard and FIFO. Send a message. Poll for messages and read them. | | SNS | Topics and subscriptions. Subscribe a queue, a function, a URL or an email address. Publish a message. | | SES | Verify email addresses and domains. Send a test email. A mailbox page shows every email the environment captured. | | ElastiCache | Create and delete Valkey, Redis OSS and Memcached caches. Shows the connect command. Replication groups. | | Load balancers | Under EC2. Load balancers, listeners, target groups and registered targets. | | KMS | Customer managed and AWS managed keys. Create, enable, disable and schedule deletion. Aliases, key policy, encrypt and decrypt. | | DynamoDB | Create and delete tables with indexes. Change capacity, TTL and streams. Scan, query, create, edit and delete items as JSON. | | Cognito | Create user pools, users, groups and app clients. Manage a user's attributes, password and groups. Test a sign-in and read the token claims. Create identity pools. | | Route 53 | Create public and private hosted zones. Manage DNS records and aliases. Associate VPCs. Create health checks. | | Certificate Manager | Request or import certificates. See validation records and details. Manage tags. Copy the PEM. | | ECS | Create clusters. Register task definitions with a form or JSON. Run tasks and services as real containers. Read their logs. | | ECR | Create repositories. Browse and delete images. Edit lifecycle and repository policies. Get the push commands. | | EventBridge | Create event buses, rules with targets, and schedules. Send test events and test event patterns. | | Step Functions | Create and edit state machines. Start and stop executions. Read each execution's input, output and event history. | | VPC | Create and delete VPCs, subnets, route tables with routes, internet gateways and NAT gateways. Manage VPC tags and DNS settings. | | CloudFormation | Create, update and delete stacks from a YAML or JSON template. Follow their events, resources, outputs and parameters. | | Kinesis | Create data streams. Read and put records. Change shards, retention and capacity mode. Manage enhanced fan-out consumers. | | OpenSearch | Create and delete domains. See how to connect. Edit cluster settings, access policy and tags. | | AppSync | Create GraphQL APIs. Edit the schema. Add data sources and resolvers. Manage API keys. Run queries. |
The top bar has a search box for services and pages. Every page has a help panel with the CLI profile.
Use the AWS CLI through the console
The console's own /aws path is a full AWS endpoint. A team needs only one URL:
# ~/.aws/config
[profile floci]
region = us-east-1
endpoint_url = http://your-console-host:8080/aws
aws_access_key_id = test
aws_secret_access_key = testaws --profile floci s3 lsRun it from source
You need Node 22 or newer, pnpm, and a running floci.
pnpm install
cp .env.example .env.local # then set FLOCI_ENDPOINT to your floci address
pnpm dev # http://localhost:5173, with live reloadRun it for a team
pnpm build
FLOCI_ENDPOINT=http://your-floci-host:4566 PORT=8080 pnpm startRun it with Docker
You already have floci. Pull the image and point it at floci:
docker run -d -p 127.0.0.1:8080:8080 \
-e FLOCI_ENDPOINT=http://your-floci-host:4566 \
ghcr.io/varun1505/floci-aws-ui:latestThen open http://localhost:8080.
You have nothing yet. compose.yaml starts floci and the console together:
docker compose up -dBoth commands listen on your own machine only. Use -p 8080:8080 to let other machines in. Read the warning about login above first.
Let floci start it. floci can run this console as its own sidecar. Set one variable on floci:
services:
floci:
image: floci/floci:latest
ports:
- "4566:4566"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
environment:
FLOCI_SERVICES_UI_IMAGE: ghcr.io/varun1505/floci-aws-ui:latestThen open http://localhost:4566/_floci/ui. floci starts the console and sends you to it on port 4500.
This works because the image follows the Floci Console Contract v1. It listens on PORT, reads AWS_ENDPOINT_URL, and answers GET /api/health with ok only when it can reach floci.
| Image tag | What it is |
|-----------|------------|
| latest | The newest commit on main. |
| 1.2.3, 1.2 | A release. |
The image runs on amd64 and arm64. To build it yourself: docker build -t floci-console .
Tests
pnpm test # run all tests once
pnpm typecheck # check the typesThe tests need no floci and no network. They cover the helper functions, the shared components, the navigation, one full page (SQS queues) with a fake SDK client, the production server with a fake floci, and the floci-aws-ui command.
How it works
browser -> this server (/aws/*) -> floci (:4566)- The pages use the normal AWS SDK for JavaScript. The SDK points at
/awson the same server. - The server forwards
/aws/*to floci. This is needed because floci does not answer browser CORS preflight requests. - floci accepts any credentials. The console sends
test/test. Nothing reaches real AWS.
Settings
| Variable | Default | Meaning |
|----------|---------|---------|
| AWS_ENDPOINT_URL | http://localhost:4566 | Where floci listens. http:// or https://. |
| FLOCI_ENDPOINT | | The same. Read when AWS_ENDPOINT_URL is not set. |
| FLOCI_TLS_SKIP_VERIFY | not set | Set to 1 to accept floci's self-signed certificate. |
| PORT | 8080 | Port for the production server. |
| HOST | all addresses | Address the production server listens on. npx floci-aws-ui serve uses 127.0.0.1 unless you set it. |
Known limits
- No login. Anyone who can open the console can change everything in floci. Keep it on a private network.
- floci keeps state in memory unless it was started with
--persist. A floci restart wipes all resources. - floci does not write the
START,ENDandREPORTlines to Lambda logs. You only see what your code prints. - floci does not publish Lambda or EC2 metrics on its own. The Metrics page shows only metrics your apps send.
- EC2 instances run as containers on the floci host. There is no serial console output.
- IAM stores users, roles and policies, but floci does not enforce them. A call that a policy denies still works here.
- SES sends no real email. Read sent messages on the Mailbox page.
- Load balancers are created and listed. Sending traffic through one is not tested.
- An RDS endpoint address is internal to Docker. Connect to the floci host on the port the page shows.
- API Gateway stages answer at
<console>/aws/_aws/execute-api/<api-id>/<stage>/<path>, not at anamazonaws.comURL. - A CloudFront distribution gets a
cloudfront.netname, but that name does not resolve on your network. Serving content through a distribution is not tested.
Add a service
- Add a client in
src/clients/. - Add pages in
src/pages/<service>/.ResourceTablegives you the standard list page. - Add the routes in
src/App.tsxand the side navigation insrc/components/nav.ts.
See docs/STATUS.md for what was tested, what floci does differently, and how the code is laid out.
