Repository navigation
Releases
v0.4.12: Bedrock playground
A Bedrock playground, contributed by @vaibhavkr993630-droid.
Bedrock
Bedrock now has its own view, with three tabs:
- Playground: pick a text model, write a prompt (and a system prompt if you like), set max tokens, temperature and top P, and send it through the Converse API. You get the reply, the stop reason, token usage and latency. (#184, part of #134)
- Models: the text foundation models the endpoint offers, with their providers and modalities.
- Custom models: the models trained or imported in the account.
It works with any endpoint that serves Bedrock, including AWS Emulator, and with real AWS.
On real AWS, each prompt runs on your account and is billed per token. The playground says so next to the button. Max tokens starts at 512, and Converse calls are never retried, so a slow answer isn't billed twice. Like Lambda invokes, prompts stay allowed in read-only mode, since they don't change any resource.
When an endpoint doesn't serve Bedrock, the view says so. Other errors (credentials, TLS, an unreachable endpoint) show the same explanations as the rest of the console.
Thanks @vaibhavkr993630-droid for building it and for working through two rounds of review!
Full changelog: v0.4.11...v0.4.12
v0.4.11: Activity, emulator reset, Try it and connection details
See what happened, reset an emulator, call your APIs and connect to your databases, all from the console.
Activity
A new Activity page lists the API calls CloudTrail recorded, newest first: what was called, by whom, on which resources, and whether it failed. Filter by time range and by one lookup attribute, open any event's full record, export, and auto-refresh every 10 seconds. It starts on calls that change something. (#229)
What shows up depends on what each emulator records; the README has a table. AWS Emulator records about a dozen services, and MiniStack records everything when started with CLOUDTRAIL_RECORDING=1.
Emulator details and reset
Settings now shows the emulator behind the endpoint you're browsing: its version, a link to its docs, and the limits worth knowing. For example, AWS Emulator's 16 MiB request cap, its S3 storage caps, and its Python and Node.js Lambda runtimes also appear next to S3 uploads and Lambda invokes. (#228)
Emulators with a reset (MiniStack, Floci, Moto) get a Reset emulator button that wipes their state after you type the endpoint's name. It's never offered for real AWS and is blocked in read-only mode.
Try it
Send requests to API Gateway stages and Lambda function URLs from the console, and see the status, headers, body and timing. StackPort builds the right address for each emulator and for real AWS, and only ever sends to the selected endpoint's own invoke addresses. (#230)
Connection details
RDS, ElastiCache, OpenSearch, MSK and SQS details now show how to connect from your machine: the address to use and commands to copy (psql, mysql, redis-cli, curl, the AWS CLI and more), with notes when an emulator needs a setting to make an address reachable. (#231)
Docs
- The README, which is also this package's page on PyPI and Docker Hub, has a "Works with" table, a quick start for each emulator, and a short FAQ. Emulators are listed as AWS Emulator, MiniStack, Floci, LocalStack, Moto. MiniStack is StackPort's partner project. (#232)
- The pip and
docker runcommands for MiniStack, Floci, LocalStack and Moto now pass test keys, so they work on a machine without AWS credentials. - The website, stackport.cloud, was refreshed with a guide for AWS Emulator and a page for the API Explorer.
Fixes
- A URL counts as AWS only when its host is an AWS host. A path or query mentioning
amazonaws.comno longer turns a local endpoint into "AWS", and an uppercase AWS host is no longer treated as local. - Request bodies with
NaN,Infinityor a lone surrogate character get a 422 instead of a 500.
Full changelog: v0.4.10...v0.4.11
v0.4.10: API Explorer and 16 more services
An API Explorer for every operation of every service, 16 more services on the dashboard, and a much lighter backend.
API Explorer
A new page calls any operation of any service botocore knows against the selected endpoint, including the many services StackPort has no view for. (#219)
- Catalog: every service and operation comes from botocore's own models, with their docs and Read/Write badges.
- Request: a form generated from the operation's parameters, plus a JSON view of the whole request.
- Response: JSON, with status, request ID and timing. Endpoint errors show with the endpoint's own message.
- Copy as AWS CLI or boto3. With AWS Emulator, the snippets include the setup it needs (keys, certificate, host prefixes).
- Pagination, deep links (
/explorer?service=sqs&operation=ListQueues) and a short local history. - Read-only mode only runs operations that read. Reads that hand out credentials or tokens, like
sts GetSessionToken, count as writes. On real AWS, writes ask first.
16 more services
EventBridge Scheduler, EventBridge Pipes, AppConfig, Cloud Map, CodeBuild, CodePipeline, CodeCommit, CodeDeploy, Batch, EKS, OpenSearch, MSK, Bedrock, CloudTrail, X-Ray and Verified Permissions are now counted on the dashboard, listed and opened in the resource browser. SES also lists configuration sets and email templates. That's 51 services by default. (#218)
Services an endpoint doesn't have show as "not supported", now also on MiniStack, where they used to show as unavailable.
Lighter and faster
- StackPort used to create a separate boto3 session for every client, so each endpoint's clients took about 500 MB. Clients with the same credentials now share a session. With two endpoints, memory went from about 1 GB to about 330 MB, and the first dashboard load from 3.3 s to 0.4 s. (#225)
Fixes
- Endpoint errors keep their status everywhere. A missing resource or a bad parameter is now a 4xx with the endpoint's message in every route, instead of a 500 with botocore's text. (#220)
- Real AWS stays real AWS.
AWS_ENDPOINT_URL_<SERVICE>variables and a profile'sendpoint_urlorservicessettings no longer redirect some calls of a real-AWS endpoint. A profile still provides the credentials. (#221) - No secrets in debug logs. With
LOG_LEVEL=DEBUG, botocore's request and response logs, which include parameter values and session tokens, now stay out unless you setSTACKPORT_LOG_AWS_WIRE=true.
Changes in behaviour
| Change | If it affects you |
|---|---|
AWS_ENDPOINT_URL_<SERVICE> and profile endpoint settings don't apply to StackPort |
Set the endpoint URL on the StackPort endpoint instead |
| Credentials are read once per credential set | After editing a static key in ~/.aws/credentials, use Test connection, edit the endpoint, or restart |
botocore's wire logs are off at LOG_LEVEL=DEBUG |
Set STACKPORT_LOG_AWS_WIRE=true to see them |
| The dashboard probes 51 services by default | Set STACKPORT_SERVICES to probe fewer |
Full changelog: v0.4.9...v0.4.10
v0.4.9: fixes found testing against AWS Emulator
Bug fixes found by running StackPort end to end against AWS Emulator. Almost all of them affected every emulator and real AWS too.
IAM
- Policy documents show again. Trust policies, inline policies and managed policy documents were always empty. (#198)
- The dashboard counts your own IAM policies, like the IAM view, instead of every AWS managed one.
S3
- Large uploads work on AWS Emulator. Files of 8 MiB or more go up in 8 MiB parts, under AWS Emulator's 16 MiB request limit. Tested on AWS Emulator, MiniStack, Floci, LocalStack and Moto. (#202)
- Downloads are about 14 times faster, and files with any name download (names outside Latin-1 used to fail). (#203)
- The object list no longer labels every object
application/octet-stream: the Type column shows the extension, and the object detail shows the real content type. (#203)
DynamoDB
- Decimals save exactly in Plain JSON, including numbers with more digits than a float holds. (#197)
- A missing table shows a clear "not found" error instead of an empty table. (#207)
- Item count and size are labelled as approximate, and "Get live item count" counts the items with a scan. On real AWS it asks before scanning, since the scan is billed. (#208)
SQS
- Editing a queue's settings keeps its long polling wait time instead of resetting it to 0. (#205)
- Invalid message attributes get a clear error instead of a 500. (#206)
CloudWatch Logs and tags
- Log streams show their last event time, and every time is shown in your own time zone. (#200)
- Tags can be read and edited on log groups and SQS queues from the resource table. (#201)
Resource table
- EC2 instances are listed and counted as instances, not reservations. Load balancers, CloudFormation stacks and EventBridge rules on custom buses open their details, and the SQS detail is no longer empty. (#199)
- Every resource type is now tested end to end, from the listing to its detail. Thanks @amjadjibon for the idea. (#175)
- Errors from the endpoint come back with its own status and message instead of a 500.
Changes in behaviour
| Change | If it affects you |
|---|---|
| The SQS API answers 422 for fields it doesn't know | Scripts calling /api/sqs/... should send only documented fields |
Unknown /api/... paths answer a JSON 404 instead of the UI page |
Nothing to do |
content_type is null in the S3 object list |
Read it from the object detail |
| Requires boto3 1.36 or newer | pip install -U stackport upgrades it |
For contributors
The test suite no longer sends requests to an emulator running on its default port (4566 or 9297) on your machine. (#215)
Full changelog: v0.4.8...v0.4.9
v0.4.8: AWS Emulator follow-ups
Follow-ups to the AWS Emulator release.
Fixes
- Temporary AWS credentials:
AWS_SESSION_TOKENis now passed along withAWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY, so SSO exports and assumed roles work against real AWS. Empty credential variables count as unset. (#191) - The CLI uses your saved endpoint's settings:
stackport status,list,describeandexportnow use a saved endpoint's profile or keys, region and TLS settings, the same way the web app does. A name that matches no saved endpoint is now an error instead of quietly using the default one. (#189) - Live stats for each endpoint: two saved endpoints on the same URL with a different region, credentials or TLS settings now get their own live dashboard stats. Editing an endpoint refreshes them right away, and a deleted endpoint shows an error instead of another endpoint's numbers. (#190)
- Learn with AWS Emulator: lesson steps with an AWS CLI command now show the
exportlines AWS Emulator needs (its keys, certificate and host prefix setting). Nothing changes for other emulators. (#192) - Docker image: the UI is built once per release instead of once per platform, so the arm64 build no longer hangs. (#188)
Changes in default behaviour
| Change | If it affects you |
|---|---|
Without --region, the CLI uses the endpoint's region before AWS_REGION |
Pass --region to choose another one |
The CLI stops with an error (exit code 2) when --endpoint names an endpoint that isn't saved |
The error lists the saved names |
Full changelog: v0.4.7...v0.4.8
v0.4.7: AWS Emulator support
AWS Emulator
StackPort now works with AWS Emulator, AWS's new local emulator, out of the box:
AWS_ENDPOINT_URL=https://127.0.0.1:9297 stackportAWS Emulator serves HTTPS with a certificate it creates on every start, and only accepts requests signed with keys it also creates on every start. StackPort reads both from ~/.aws/emulator/<port>/ and follows them when a restart rotates them. To run both with Docker, use examples/docker-compose.aws-emulator.yml.
For every emulator
- TLS settings per endpoint: a CA bundle, or verification off, in Settings.
- Errors that say what to do: an operation the emulator doesn't implement, rejected credentials, an untrusted certificate, or an emulator that isn't running each get their own message and hint.
- Dashboard statuses: Available, Not supported by this endpoint, or Unavailable with the reason, plus one banner when the whole endpoint is down.
- The emulator's name in the UI: MiniStack, Floci, LocalStack, Moto and AWS Emulator are recognised the same way.
- Lambda "Download code" works with Compose host names and self-signed certificates.
- A stopped emulator shows up in seconds, not about 40. Calls to local emulators aren't retried, and
STACKPORT_PROBE_TIMEOUTis now the connect timeout. - SQS: the long-polling wait time set in the UI now reaches the queue.
Security
- Files outside the UI: the UI file handler could serve other files from the machine (
/%2Fetc%2Fhosts). Fixed. - Cross-site requests: other websites could change resources through StackPort with "simple" requests, such as a form POST or an image URL. Those requests are now refused.
- DNS rebinding: browsers have to open StackPort through
localhost, an IP address, or a host name inSTACKPORT_ALLOWED_HOSTS. - Truncated downloads: a download cut off halfway no longer reaches the browser looking complete.
Changes in default behaviour
| Change | If it affects you |
|---|---|
stackport serve listens on 127.0.0.1. The Docker image still listens on 0.0.0.0, and the Compose examples publish on 127.0.0.1:8080 |
stackport serve --host 0.0.0.0 or STACKPORT_HOST=0.0.0.0 |
| The API doesn't allow calls from other websites (CORS) | STACKPORT_CORS_ORIGINS=https://your.site |
Browsers must use localhost or an IP address |
STACKPORT_ALLOWED_HOSTS=your.host for reverse proxies, Codespaces-style URLs, or machine names |
AWS_ENDPOINT_URL sets the default endpoint every time StackPort starts with it, not only the first time |
Nothing to do |
Full changelog: v0.4.6...v0.4.7
v0.4.6 — DynamoDB actions column fix
StackPort 0.4.6
Edit and Delete stay on one line in the DynamoDB items table (#182, #183)
Items with wide attribute values (UUIDs in a few columns were enough) squeezed the Edit/Delete column until both links wrapped one letter per line. The column now keeps its width no matter how wide the rest of the table gets. The SQS message list had the same layout, so its Delete column got the same fix.
Thanks to @bozzaj for the report, the sample item to reproduce it, and the min-width fix itself.
Upgrade
pip install -U stackport
# or
docker pull davireis/stackport:0.4.6
Full Changelog: v0.4.5...v0.4.6
v0.4.5 — KMS browser
StackPort 0.4.5
KMS browser (#77, #178)
KMS now has its own view instead of the generic table. The key list shows each key's ID, ARN, creation date, usage, spec, and state, with a status indicator per state: enabled, disabled, pending deletion, pending import, and the rest. Opening a key shows its details (origin, description, expiry, and whether rotation is on, with period and next date), the key policy as JSON, its tags, its grants with grantee and operations, and its aliases. Keys deep-link with ?id=, and every list pages.
It works on emulators that don't implement every KMS call. When ListGrants isn't supported, the Grants tab shows an empty list instead of an error, and aliases without a creation date show a dash. Tested on MiniStack and Floci.
Thanks to @muneebIsLOL for the whole view, his first contribution here. The alias column in the key list, the full key metadata, and a couple of real-AWS edge cases are tracked in #180.
Grants show up once an emulator can create them. For MiniStack, CreateGrant is in review in ministackorg/ministack#1847.
Upgrade
pip install -U stackport
# or
docker pull davireis/stackport:0.4.5
Full Changelog: v0.4.4...v0.4.5
v0.4.4 — Binary data in DynamoDB, correct ids for five more resource types
StackPort 0.4.4
Two fixes, both reported or picked up by the community.
DynamoDB tables with binary data open again (#176, #177)
A table holding binary (B or BS) data that is not valid UTF-8 returned 500 as soon as you opened it. Binary now travels as base64, which is how AWS writes B in DynamoDB JSON, and it works end to end: scanning, paginating on a binary key, querying by a binary key, editing an item, and deleting it.
This also fixes a quieter bug. Saving an item with a binary attribute used to store the base64 text itself as the bytes. It now stores the real bytes. Items written from the StackPort editor before this release may hold that base64 text, so check and rewrite any binary attributes you edited there. Thanks to @mspiller for the report.
Correct ids for five more resource types (#170, #174)
IAM policies, EC2 subnets and security groups, EFS file systems, and RDS clusters listed a field that was not their real identifier, so the detail view returned 500. They now list the identifier the describe call expects, in the web UI and in stackport list. The test reads each list and describe shape from botocore, so a new collision like this would fail CI. Thanks to @amjadjibon, his second fix in a week.
Upgrade
pip install -U stackport
# or
docker pull davireis/stackport:0.4.4
Full Changelog: v0.4.3...v0.4.4
v0.4.3 — Bug fixes and emulator docs
StackPort 0.4.3
A fix release. Three bugs reported or found by the community, plus a rework of how the docs talk about emulators.
DynamoDB items show as values again (#163, #169)
The items table showed raw DynamoDB-typed JSON ({"S": "Hello"}) instead of Hello, the edit modal opened on typed data and wrapped it a second time when switching to DynamoDB JSON, and Delete sent a double-encoded key. Items now render as plain values, Edit opens in Plain JSON like the AWS console, switching to DynamoDB JSON on an untouched item shows the exact typed form, and Delete sends the key as the API returned it. Thanks to @jin-gizmo for the report and @vaibhavkr993630-droid for the fix. Saving sets or binary from Plain JSON still rewrites their type, that is tracked in #172.
API Gateway v2 detail no longer 500s (#164, #165)
HTTP APIs carry both Name and ApiId, and the list emitted the name, so the detail lookup called get_api with a value it does not accept. The list now emits ApiId, and stackport list prints the same ids the web UI uses. Thanks to @amjadjibon. The same pattern turned up in five more resource types and is tracked in #170.
CLI honours --endpoint again, and stackport status works (#171, #173)
Once the web UI had saved endpoints to ~/.stackport, the CLI ignored --endpoint and AWS_ENDPOINT_URL and used the saved default instead. Commands now resolve the endpoint explicitly: flag or env var wins, otherwise the saved default. stackport status had also been exiting with a missing-argument error since the probe helper gained a required parameter; it probes all 35 services again.
Emulators side by side (#161, #168)
There is a new Docker Compose example for Floci with a one-shot seed that populates the dashboard, contributed by @hectorvent, and the MiniStack example got the same seed. The Quick Start shows both emulators next to each other, the README has an Origin section pointing at the MiniStack pull request the project grew out of, and CONTRIBUTING has a "Supported emulators" section with the ground rules: same depth for every emulator, one fixed order, no default. Thanks to @Nahuel990 for pushing on this.
Upgrade
pip install -U stackport
# or
docker pull davireis/stackport:0.4.3
Full Changelog: v0.4.2...v0.4.3