AEM TO S3 Blocker UseCase ->
Environment – AEM As a cloud service
Dependency not resolved –
We are using the AEM as a cloud service environment and we are finding issues in using the AWS SDK libraries using as a maven dependencies. We found the way to update the couple of configurations in AEM quickstart folder which is not possible in AEM as cloud service straight forward as we don't have access to unix box to update the same. Developer console also give access for Felix configs.
Failed as we are looking for system configs to get added and as per suggestion from Adobe Added the same configs in Runmode but this doesn’t support the technical usecase.
Failed as AEM as a cloud service won’t allow to install any package under /libs as it is only having read access and needs to be build this package through bundle.
ZIP building for project codebase and deploy as a package in direct instance as Approach 2 failed.
Failed as AEM as a cloud service won’t allow to install any package under /apps as it is only having read access and needs to be build this package through bundle.
ZIP building from project codebase as Approach 2 and 3 failed.
This will allow to add S3 connector zip from project bundle as per given reference. But that way of implementation also didn’t work as it is giving same error as,
14:00:46,076 [main] [ERROR] Error resolving dependencies for project com.pacificlifeinsurancecompanydam:aem-pacificlifeinsurancecompanydam-project.all
14:00:46,077 [main] [ERROR] Failed to collect dependencies at com.adobe.granite:com.adobe.granite.oak.s3connector:zip:1.10.10
Failed as a given reference of updating embedded packages for Vendor packagesof s3connector, adding s3 depdencies and <allowIndexDefinitions>true</allowIndexDefinitions> still not worked.
Creating the non-osgi aws-java-sdk-osgi bundle to osgi compatible manner. Added the dependencies but still does not work.
Failed as loads of depdencies not resolved with the osgi package in felix.
Thanks and Regards,
@kiranparab I think you can refer to ACS commons code on how they have done the dependency setup to be compatible with OSGI, though their S3 connectors not compatible with AEM Cloud, baseline code deploys and resolves in AEM cloud as well.
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,
https://mvnrepository.com/artifact/com.amazonaws/aws-java-sdk-osgi/1.12.13 is AWS Java SDK with support for OSGi. It is an OSGi bundle that can be installed directly in Felix but when tried in my local AEM 6.5.0 instance, some of its run time dependencies are not resolved.
So in order to resolve this,
If you would like to try in your local AEMasCS SDK instance,
@kiranparabYou would have to add this bundle in the embed-dependency section as described here: