# Amazonka Requests for Testing

**URL:** <https://discourse.haskell.org/t/amazonka-requests-for-testing/11591>\
**Category:** Announcements\
**Created:** [March 10, 2025, 10:26am UTC](https://discourse.haskell.org/t/amazonka-requests-for-testing/11591 "2025-03-10T10:26:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jackdk](https://avatars.discourse-cdn.com/v4/letter/j/9f8e36/32.png) [@jackdk](https://discourse.haskell.org/u/jackdk)\
**Post date:** [March 10, 2025, 10:26am UTC](https://discourse.haskell.org/t/amazonka-requests-for-testing/11591/1 "2025-03-10T10:26:19Z")

</div>

This thread is for particularly tricky PRs against the Amazonka repository, where I’d really appreciate some additional testing (because I can’t test everything myself, the service is not being offered to new customers, it’s a risky change with wide effect, etc.). If you are a user of Amazonka large or small, I would appreciate you subscribing here and helping out if you can.

My first request is for help testing [PR 1031](https://github.com/brendanhay/amazonka/pull/1031), which fixes the canonicalisation of query string parameters. This seems to fix a bug in S3 Select (which I do not have access to, as it’s not being offered to new customers), but query strings may be used in other AWS APIs. `grep`ping `botocore` suggests that the following services might use them:

- IAM
- SNS
- SimpleDB
- CloudWatch
- SES
- RDS
- STS
- Elastic Load Balancing (v1 or v2)
- SQS
- DocumentDB
- CloudSearch
- Redshift
- Application Auto Scaling
- CloudFormation
- Neptune
- Elasticache (the control plane, not redis/memcache connections)
- Elastic Beanstalk
- Import/Export

If you use Amazonka to make API requests against one of these services, can you please test whether those requests continue to work under this PR?

---

<div class="post-metadata">

**Author:** ![jhrcek](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/jhrcek/32/319_2.png) [@jhrcek](https://discourse.haskell.org/u/jhrcek)\
**Post date:** [March 14, 2025, 9:14am UTC](https://discourse.haskell.org/t/amazonka-requests-for-testing/11591/2 "2025-03-14T09:14:57Z")

</div>

Thank you for all your hard work on Amazonka!

I just tested the [latest commit](https://github.com/brendanhay/amazonka/pull/1031/commits/23343f531d8d5dfa9465981d855d577c6ea5638c) in your PR branch with Holmusk’s codebase (proprietary). From your list of affected packages we’re only using amazonka-ses. On top of that we’re also using amazonka-(autoscaling|ec2|s3|secretsmanager). Though we’re not using S3 Select. But I can at least confirm that none of the changes (since the official amazonka 2.0 release that we normally depend on) introduced any issues for us.

---

<div class="post-metadata">

**Author:** ![jackdk](https://avatars.discourse-cdn.com/v4/letter/j/9f8e36/32.png) [@jackdk](https://discourse.haskell.org/u/jackdk)\
**Post date:** [March 14, 2025, 10:43pm UTC](https://discourse.haskell.org/t/amazonka-requests-for-testing/11591/3 "2025-03-14T22:43:36Z")

</div>

Thank you for this, it gives me at least some confidence that signing is still working in general.

---

<div class="post-metadata">

**Author:** ![jackdk](https://avatars.discourse-cdn.com/v4/letter/j/9f8e36/32.png) [@jackdk](https://discourse.haskell.org/u/jackdk)\
**Post date:** [October 25, 2026, 11:02pm UTC](https://discourse.haskell.org/t/amazonka-requests-for-testing/11591/4 "2026-10-25T23:02:24Z")

</div>

I have finished work on adding idempotency token support to Amazonka. These are tokens that you can set to ensure certain requests don’t get acted upon twice if resent.

The PR with the service regenerations is [PR 1070](https://github.com/brendanhay/amazonka/pull/1070). To see if a service you care about has changed, see [the `CHANGELOG.md` on the PR branch](https://github.com/endgame/amazonka/blob/6d9c2184dff32b851ef704aeb730b6c1ef51915f/lib/amazonka/CHANGELOG.md).

If you use idempotency tokens, please comment on PR 1070 that they’re working or not.

If you don’t use idempotency tokens, please comment on PR 1070 whether or not I’ve broken Amazonka for you.