AEMaaCS - Creating a new Asset from Service

[sjn]

Hi all,

We have a use case where we want to upload some files to the DAM from an AEM service.
The service is using a 3rd party API to generate some images which are stored externally stored (AWS S3). The service has the URLs for these images. We'd like to get then get these images into the DAM.

The service would run as follows:

1. Use existing asset to call external 3rd party API (This produces an asset stored in the S3)

2. Take the results (list of S3 locations) and upload to the DAM

This would be a fully automated process, but having trouble with that second step at present

From what I've read it looks like we can no longer use the Asset Manager API in AEMaaCS and now have to use an asset microservice API as detailed here: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/admin/develo...

Although when looking at that page we have the message "Execute these steps in an external application and not within the Experience Manager JVM."

Just looking for advice on AEMaaCS best practices so we can create an Asset in the DAM from within a Experience Manager Service we've written.

Thanks

[Mani_kumar_]

If I understand correctly you want to download and asset from the external service and upload that in AEM.

If you have S3 then you can used the ACS commons s3 investor to ingest the assets into AEm

Else place the assets in one common UNIX box and use CSV asset importer to import the assets into AEM

Please find the below references for the same.

https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp-tools/asset-ingestion/s3-as...

https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp-tools/asset-ingestion/url-a...

[sjn]

Thanks for the links - unfortunately neither of those ACS Commons seem to be compatible with AEMaaCS.

[Mani_kumar_]

This is the alternative for the importer

https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp-tools/data-importer/index.h...

This will work in cloud as well.

[sjn]

Thanks. Whilst that should work, ideally I'd like to add the asset in the AEM service rather than rely on something external to the process.

The service would run as follows:

1. Use existing asset to call external API (This produces an asset stored in the S3)

2. Take the results (list of S3 locations) and upload to the DAM

This would be a fully automated process, but having trouble with that second step at present