anchor.diff:  To illustrate, the project generated by the Maven archetype, generates a JUnit test for the `RequestHandler<?, ?>` implementation, which is shown below.
   The test replicates the execution environment, for the function that is selected for invocation, as described <<choose, above>>.
   
  +To use the integration tests in your project there is a required property, in `src/test/resources/application.properties`. If not included, the integration tests will be in a constant loop.
  +
  +[source,shell]
  +----
  +quarkus.lambda.enable-polling-jvm-mode=true
  +----
  +
  +NOTE: If you are following along with the example Maven archetype project for AWS Lambda in this guide,
  +it includes the required property `quarkus.lambda.enable-polling-jvm-mode=true` in the test `application.properties`.
  +
   [source,java]
   ----
   @QuarkusTest
  
positive.code: 
  [source]
  ----
  docker cp {container-id-from-above}:/opt/graalvm/jre/lib/amd64/libsunec.so src/main/zip.native/ssl
  ----
  
  Second, cacerts, the certificate store.  You may need to periodically obtain an updated copy, also.
  [source]
  ----
  docker cp {container-id-from-above}:/opt/graalvm/jre/lib/security/cacerts src/main/zip.native/ssl
  ----
  
  Your final archive will look like this:
  
negative.code: 
  [[aws-sdk-v2]]
  == Using the AWS Java SDK v2
  
  NOTE: Quarkus now has extensions for DynamoDB, S3, SNS and SQS (more coming). Please check those guides on how to use the various AWS Services with Quarkus, as opposed to wiring manually like below.
  
  With minimal integration, it is possible to leverage the AWS Java SDK v2,
  which can be used to invoke services such as SQS, SNS, S3 and DynamoDB.
  