feat(graalvm): GraalVM support for Idempotency utility

[phipag]

Summary

This PR introduces GraalVM support for the idempotency module including native unit and e2e tests.

Other improvements:

• Use aws-powertools_ubuntu-latest_8-core for GraalVM build which cuts build time in half
• Fix a lot of sonar findings in unit tests
• Remove Mac M1 dependency for DynamoDB local. This is treated as an external JVM process now also making it compatible with GraalVM native tests.
• Add GraalVM example with better README.md file (let me know what you think and I'll apply the same README style to the other GraalVM examples)
• Update overall example README (it was outdated and had broken links)
• Add --platform linux/amd64 to CDK Bundling options to fix builds on podman 5.6.0 (https://blog.podman.io/2025/08/podman-5-6-released-rosetta-status-update/)
  • at the cost of build time performance unfortunately ...

Changes

Issue number: #1834

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ❌ 2 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ⚠️ 10 package(s) with unknown licenses.
• ⚠️ 2 packages with OpenSSF Scorecard issues.

View full job summary

[phipag]

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > putRecord_shouldThrowIdempotencyItemAlreadyExistsException_IfRecordAlreadyExist() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > idempotencyDisabled_noClientShouldBeCreated() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > getRecord_shouldReturnExistingRecord() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > putRecord_shouldCreateRecordInDynamoDB() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > putRecord_shouldCreateRecordInDynamoDB_IfLambdaWasInProgressAndTimedOut() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > deleteRecord_shouldDeleteRecord() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > getRecord_shouldThrowException_whenRecordIsAbsent() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > endToEndWithCustomAttrNamesAndSortKey() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > putRecord_shouldBlockUpdate_IfRecordAlreadyExistAndProgressNotExpiredAfterLambdaTimedOut() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > putRecord_shouldCreateRecordInDynamoDB_IfPreviousExpired() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.DynamoDBPersistenceStoreTest > updateRecord_shouldUpdateRecord() SUCCESSFUL

software.amazon.lambda.powertools.idempotency.persistence.dynamodb.IdempotencyTest > endToEndTest() SUCCESSFUL


Test run finished after 204 ms
[         3 containers found      ]
[         0 containers skipped    ]
[         3 containers started    ]
[         0 containers aborted    ]
[         3 containers successful ]
[         0 containers failed     ]
[        12 tests found           ]
[         0 tests skipped         ]
[        12 tests started         ]
[         0 tests aborted         ]
[        12 tests successful      ]
[         0 tests failed          ]

[phipag]

E2E tests pass now.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dreamorosi]

I see one of the CI checks is failing, is it related to changes in this PR?

[phipag]

I see one of the CI checks is failing, is it related to changes in this PR?

No, it is not related to this. Only due to the changes in this PR it is triggered again. the EPL-2.0 license used in all AspectJ dependencies has no general approval which is why we did not add it to the generally approved licenses list. For this PR, no new package is introduced with an unapproved license.

[dreamorosi]

For future GraalVM PRs I'd exclude examples since I don't know that having an example for each combination of setup x utility is useful.