Upgrade from Spring Cloud Function AWS dependencies from 4.2.0 to 5.0.1 increase the artifact size by 60%

[Vadym79]

I upgraded my sample application to deploy on AWS Lambda using spring-cloud-function-adapter-aws and spring-cloud-function-web dependencies. With their version 4.2.0 the artifact size is 32 MB, by switching to 5.0.1 it increases by 60% to 52 MB. Even the Spring Boot update from 3.4 to 4.0 adds only 5 additional MB (from 27 to 32 MB).
To deploy on AWS each byte counts, because the bigger the artifact is, the higher the cold start time of the Lambda function generally is. If I look into the jar, I see in the lib folder of the 5.0.1 version 124 other jars comparing to 64 with 4.2.0. Those include additional countless netty dependencies and spring boot dependencies. Are they all needed?

Can you please document those changes a describe what maybe can be exluded depending on the application type.

I also see that AWS Lambda SnapStart doesn't work (snapshot works, restore runs into 10 second timeout) any more for one of the priming types, but I'm in contact to AWS that they check it, as I dont see any error message.

[Vadym79]

I could reduce the artifact size significantly by excluding many spring boot starters from the spring-cloud-function-adapter-aws dependency , see pom.xml as an example. I still don't understand why this dependency includes so many spring boot starters by default if I can provide on my own what starters my application exactly needs.