Because of mutable concept we can't create non OSGI to osgi bundle and deploy. We need to keep this as a part of codebase through embed dependency only.

Yes we are using AWS SDK to use in our codebase to move AEM to S3 assets and JSON metadata. We are finding issue when adding the respective depdencies like,Maven Repository: com.adobe.granite » com.adobe.granite.oak.s3connector » 1.10.10 (mvnrepository.com... and https://mvnrepository.com/artifact/c...

Hi Team, AEM TO S3 Blocker UseCase -> AWS libraries for S3 connector configs not resolved in AEM as a cloud service instanceEnvironment – AEM As a cloud service Issue – Dependency not resolved –  We are using the AEM as a cloud service environment and we are finding issues in using the AWS SDK libra...