Skip to content

bug: AWS s3 is returning a different XML object than localstack does with the new Localstack s3 provider #7541

@daringordon

Description

@daringordon

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

S3 requests to localstack are failing using aws clients written in various languages (Elixir, Rust).

I illustrate the crash in Elixir using the following executable example HERE

If you wish to reproduce this problem with Rust, simply clone the official aws-sdk-rust library and run LOCALSTACK=true cargo run --bin use-localstack from the root directory, after you've installed rust (using rustup).

as per @thrau :

anyway i checked and can confirm AWS s3 is returning a different XML object than localstack with our new s3 provider.
by default, list-buckets returns a object (that is not defined in the spec actually - happens often in s3), but we return a object (which is the default name in the spec). this is probably why the official aws sdks can handle the response. the parsed response is the same, it's just the container that's different (edited)

Expected Behavior

No response

How are you starting LocalStack?

With a docker-compose file

Steps To Reproduce

see the README of the project I link to in the description above

Environment

- OS:  macos (m1)
- LocalStack:  latest

Anything else?

No response

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions