The following scenarios tested in Camel should be also tested in Camel Quarkus to make sure that they work also in native mode: 

 I did an investigation from QE POV:

• Via producer:
  • Multipart upload (Camel)
  • copyObject (Camel)
  • listBuckets (Camel)
  • deleteBucket (Camel)
  • downloadLink (Camel)
  • getObjectRange (Camel)
  • Using KMS to encrypt data (Camel - Localstack)
• Via consumer:
• As customer i would like to use the same AWS client for Camel and plain Quarkus (see https://quarkus.io/guides/amazon-s3) - so they are aligned and configured once