[Snyk] Security upgrade com.amazonaws:aws-lambda-java-events from 1.3.0 to 3.0.0

[dexterinbk]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• base/dump-java8/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-15365924	170	com.amazonaws:aws-lambda-java-events: 1.3.0 -> 3.0.0 Major version upgrade No Path Found Proof of Concept

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[dexterinbk]

The upgrade from com.amazonaws:aws-lambda-java-events v1.3.0 to v3.0.0 is a major version change with significant breaking changes. The primary change is the removal of the dependency on the AWS SDK for Java v1.

Breaking Changes:

• AWS SDK v1 Dependency Removed: Version 3.0.0 removes the transitive dependency on the AWS SDK for Java v1. Previously, your project might have had access to AWS SDK v1 classes (like those for S3, Kinesis, and DynamoDB) just by including aws-lambda-java-events. This is no longer the case.
• Internal Model Classes: To replace the SDK dependency, the library now includes its own model classes for S3, Kinesis, and DynamoDB events under the com.amazonaws.services.lambda.runtime.events.models namespace. Code that interacted with event objects from these services will need to be updated to use these new, internally-managed classes instead of the ones from the AWS SDK v1.

Recommendation:

This upgrade requires code modifications. You must review your Lambda functions to:

1. Explicitly add the AWS SDK for Java (either v1 or v2) as a direct dependency to your project if your code uses the SDK for anything other than the event models.
2. Update any code that processes S3, Kinesis, or DynamoDB events to use the new model classes bundled with aws-lambda-java-events v3.
3. Alternatively, consider using the aws-lambda-java-events-sdk-transformer library to help convert between the new event models and the AWS SDK models.

Source: Release notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.