extension push: adversarial-review report hash is platform-dependent (macOS vs Linux), so committed reviews never match a cross-OS runner

All @swamp/aws/* model types default region to us-east-1 when the region global argument is not explicitly set in a model's globalArguments. This ignores the AWS profile's configured default region (~/.aws/config region = or AWS_REGION/AWS_DEFAULT_REGION env vars).

The result is a silent footgun: a model created without an explicit region arg issues CloudControl API calls against us-east-1, producing a misleading "resource does not exist" error even when the resource is present in the profile's actual default region.

Steps to reproduce

AWS profile has region = eu-west-2 configured in ~/.aws/config
swamp model create @swamp/aws/ec2/vpc my-vpc --global-arg name=my-vpc --global-arg CidrBlock=10.0.0.0/16 (no --global-arg region=eu-west-2)
A VPC with ID vpc-0effc1af4da64c5ea exists in eu-west-2
swamp model method run my-vpc get --input identifier=vpc-0effc1af4da64c5ea
Expected: returns the VPC attributes from eu-west-2
Actual: Error: "AWS::EC2::VPC Handler returned status FAILED: The vpc ID 'vpc-0effc1af4da64c5ea' does not exist"

The error gives no indication that the wrong region is being queried. The user is left debugging the wrong thing (permissions, VPC ID format, etc.) before discovering that region: eu-west-2 needs to be added to globalArguments.

Proposed fix

When region is not set in globalArguments, resolve it in priority order:

AWS_REGION env var
AWS_DEFAULT_REGION env var
The active AWS profile's region value (from ~/.aws/config or the profile resolved by AWS_PROFILE)
Current fallback: us-east-1

This matches the behaviour of the AWS CLI and all AWS SDKs, where the region is resolved from the environment rather than hard-defaulting to us-east-1.

Why the current default is harmful

us-east-1 is a valid region and the call succeeds at the API level — it just returns "not found" for resources that exist elsewhere. This makes the failure look like a resource-identity problem rather than a configuration problem, sending users on a long debugging detour.

Affected scope

All @swamp/aws/* model types that accept a region global argument — not just ec2 and s3. This includes rds, lambda, iam, elb, and any other AWS service families. The fix should be applied at the shared credential/region resolution layer used by all AWS model types, not patched per-type.

02Bog Flow

Shipped

6/15/2026, 9:24:02 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack726/15/2026, 8:22:02 PM

stack72 commented 6/15/2026, 9:24:28 PM

Thanks @mellens for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Support epoch seconds as the version suffix to avoid push collisions

Implement ephemeral data as in-memory repository

Design: serve authentication & authorization (TLS, OAuth, access control)

Private collectives

extension push: adversarial-review report hash is platform-dependent (macOS vs Linux), so committed reviews never match a cross-OS runner

Can't click on repository from swamp extension search.

extension pull: detect ghost-row conflicts and suggest swamp doctor extensions

`extension quality` false-positive bare-import detection on string literal "flexible"

Remote Execution tutorial

SQLite run tracker subsystem for in-flight run lifecycle

Honour AWS profile default region when 'region' globalArg is omitted

swamp serve does not open the UI

Docs: document --compact flag for model type describe

datastore setup migration relocates and deletes repo-root .swamp/secrets, breaking all local_encryption vault.get

Registry content-type search filter can match versions absent from the displayed extension

Docs: document reports.require failure semantics in the manual (unresolvable required report fails the run)

Reports tab on extension page is non-functional

vault read-secret mixes log output into stdout

Resource-leak test failures on main: extension_rubric_scorer_test and worker_gateway_test

Landing page clips the curl install command instead of rendering the full text

model delete --json output shape doesn't match the documented {deleted, modelId, modelName, artifactsDeleted}

model search --json returns a bare model object instead of {query, results} when exactly one model matches

Extension author gitignore guidance: add .swamp.yaml and CLAUDE.md to recommended excludes

reports.require in workflow YAML does not auto-execute pulled extension reports

Yanked extension version still shown as active on swamp-club.com and in 'extension search'

Add deprecate/yank/unyank actions for own extensions on the web interface

Expose per-run memory/CPU metrics for method & workflow executions

model method run OOMs at 4GB V8 heap on long high-fan-out methods; non-configurable heap + crash leaves run stuck in "running"

Tier-up announcements never fire for direct score contributions (badge awards, feed credits)

CI never runs the discord-bot service test suite

Discord role sync never assigns lower leaderboard tiers (Swamp Baby / Muck Runt / Sludge Whelp)

Docs: document globalArgument input reference validation in workflow validate

Remote execution: UAT coverage for tokens, enrollment, and dispatch

Remote execution: comprehensive reference documentation

doctor extensions: pulled-extension source files reported as orphans that --repair can't evict (nested @swamp/aws/* sibling mis-attribution)

Channel-based publishing for local extension backports

Feature: make extension yank channel-scoped (--channel) so it doesn't nuke every channel

swamp update --setup-auto does not work with bluefin44 (crontab not found, should

Feature: demote / withdraw an extension version from the stable channel

Docs: extension-publish skill guide doesn't cover release channels

workflow validate: resolve model globalArguments expressions against the calling workflow's declared inputs

Add a way to list registered report definitions (report search only lists results)

Inconsistent resource-field accessor: data get returns content, data query and CEL use attributes

Extension API: allow export const extension to add resource specs, or document that it cannot

@swamp/aws/cloudformation: expose StackSet instances, drift, and operations (Cloud Control cannot)

workflow validate: method args with a Zod .default() are treated as required

Profile months overlap in trajectory

model type describe --json: bloated output (40% duplicated specs, no compact mode) and lost method-to-output mapping drive agents to read extension source

UAT: Release channel CLI and adversarial tests

Docs: Add release channel documentation to the manual

Test skill evals with Fable in multi-skill eval tests

Guide users toward filing feature requests when @swamp extensions lack a needed capability

Guide users toward filing feature requests when @swamp extensions are missing features

correcting capitlization of Swamp, Swamp Club, and The Swamp on the swamp-club.com website

API: Add release channel support for extension versions (beta, rc, stable)

Add @swamp/hetzner-cloud/server-types model for availability and project limits

Resident/warm worker mode — `model method run` has ~6s fixed per-invocation overhead that rules out latency-sensitive use

Issue submission returns wrong URL path

Dynamic resource attribute refresh for model instances

`vault put` inside workflow steps still acquires global `.datastore.lock` after #382

extension quality scorer mis-detects quoted phrases in comments as bare imports

extension push: credentials-sensitive-field false positive when .meta({ sensitive: true }) is on a continuation line

Local source-loading should discover a report co-located with its model in a paths.base:manifest extension

extension push: optionally sync the published bundle to the manifest `repository:` (git mirror)

Add 'creek' extension kind for cross-querying external systems alongside swamp data

Docs: vault refresh hooks (--refresh-from, --refresh-ttl, --clear-refresh)

Support CI-friendly adversarial review artifacts for extension push

Deprecate "No slow types" (fast-check) rubric factor on server-side scorer

Registry scorer fails on bare specifiers — mirror CLI fix from #505

Official extension for GitHub repository configuration (environments, variables, secrets)

Feature request: @swamp/tailscale extension

Option to change email in your Swamp Club profile or delete account

Docs: vault reference in manual promotes inline KEY=VALUE as primary example

extension push error for disallowed file types doesn't mention binaries field

swamp help extension omits yank and unyank (machine-readable CLI schema misses real subcommands)

Extension model method execute lacks typed args/context — every author has to use ': any' to unblock tests

@webframp/hashicorp-vault: empty KV engine causes 'data.data.keys is not iterable' on vault put

workflow resume fails to register all extension model types (local and pulled) — "Unknown model type"

model method run: cannot pass arrays, numbers, or booleans via --input

extension push --dry-run --json reports local helper imports as bogus model entries