Second this one, as we've hit several issues with NoClassDefFoundError errors in our lambdas due to the lax version ranges of the aws-lambda-java-events pom. While minor and patch releases generally should not break apis this way, these version ranges would also bump major versions which definitely would break apis.

Temporarily we exclude all dependencies we actually depend on from the aws-lambda-java-events module to lock down version numbers in explicit dependencies instead

<dependency>
  <groupId>com.amazonaws</groupId>
  <artifactId>aws-lambda-java-events</artifactId>
  <version>${aws.lambda.version}</version>
  <exclusions>
    <exclusion>
      <groupId>com.amazonaws</groupId>
      <artifactId>aws-java-sdk-s3</artifactId>
    </exclusion>
    <exclusion>
      <groupId>com.amazonaws</groupId>
      <artifactId>aws-java-sdk-sqs</artifactId>
    </exclusion>
  </exclusions>
</dependency>

This can be closed as the latest version removes the dynamic version ranges.

617af84 65ef84f