Skip to main content
← Back to list
01Issue
BugOpenSwamp CLITeam
AssigneesNone

Relationships

#1324 Bundled extension model cannot deserialize AWS SDK S3 XML that works in direct Deno

Opened by evrardjp · 7/21/2026

Problem

A model extension importing npm:@aws-sdk/client-s3@3.1091.0 fails to deserialize valid S3 XML when executed by swamp, while the identical client and request succeed under direct Deno 2.8.3.

Environment

  • Swamp 20260720.221015.0-sha.472127ff
  • Deno 2.8.3
  • AWS SDK npm:@aws-sdk/client-s3@3.1091.0
  • Floci floci/floci:1.5.11 S3 endpoint

Reproduction

  1. Start Floci on http://[IP-1]:4566.
  2. Run a direct Deno S3Client with endpoint override, static test credentials, us-east-1, and forcePathStyle: true; ListBuckets and CreateBucket succeed.
  3. Put the same client calls in a minimal swamp model extension, add it as an extension source, create a model, and run the method.

Actual

Both operations fail only in the bundled model runtime with:

@aws-sdk XML parse error: unexpected content.
Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object.

The raw ListBuckets response is HTTP 200, content-type: application/xml;charset=UTF-8, and valid AWS S3 XML. The same package version parses it correctly in direct Deno.

Expected

An npm AWS SDK client bundled as part of a swamp extension should deserialize the same HTTP response identically to the same import executed directly by Deno.

A complete local reproduction and workaround are retained in evrardjp/swamp-extensions/floci-aws/issue-drafts/swamp-extension-aws-sdk-bundling.md.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED

Open

7/21/2026, 5:28:08 PM

No activity in this phase yet.

03Sludge Pulse

Sign in to post a ripple.