Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
Follows #259
Instead of using the Zenko version of S3, this switches to using the Localstack version.
We may wish to use Localstack to avoid future maintenance issues with the Zenko images that don't seem to have been updated in the last 2 years, and so that we can use the ECR public versions of the Localstack images to avoid potential throttling on docker hub (which has been an issue in the past.
Note
This change required updated the tests as some of the error messages emitted by the Localstack S3 container image around bucket naming are different from the Zenko image. I have not determined which is "correct" as per comparison to S3 but allowed both.
How to test
How can we measure success?
Tests can pass, we can release things.
Have we considered potential risks?
The differing errors may mean that Localstack is incorrect when compared to S3, we've kept both old and new error messages as valid to mitigate.