DaviReisVieira/stackport v0.3.0 on GitHub

What's New

Per-endpoint AWS Authentication

Each endpoint can now use its own authentication method, configured from the Settings UI:

Auth Type	Description	Use Case
Default	Env vars (`AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY`) or instance role	Local emulators, EC2/ECS
AWS Profile	Named profile from `~/.aws/config`	SSO, AssumeRole, multiple accounts
Static Credentials	Per-endpoint access key / secret key	Service accounts, cross-account

Test Connection (add & edit)

You can now test connections before saving — the "Test Connection" button is available in both the add and edit endpoint dialogs.

SSO Support

Profile auth supports SSO, AssumeRole, and credential_process — anything boto3.Session(profile_name=...) handles. If your SSO token expires, StackPort returns a clear error with instructions to run aws sso login --profile <name>.

Docker Profile Auth

Mount your AWS config to use profiles inside containers:

volumes:
  - ~/.aws:/root/.aws

Bug Fixes

Fixed: SSO/AssumeRole calls were routed to local emulators when AWS_ENDPOINT_URL was set globally (e.g. in Docker). StackPort now removes it from os.environ after reading it.

Backward Compatibility

Existing endpoints.json auto-migrates to v2 format (adds auth_type: "default")
All existing endpoints continue working unchanged
Emulator-only and Docker users: zero impact

Full Changelog

v0.2.6...v0.3.0

DaviReisVieira/stackport v0.3.0 v0.3.0 — Per-endpoint AWS Authentication on GitHub