This tutorial requires the following services to be provisioning and accessible via the learner’s Adobe ID.
All Adobe services must be accessible through the same Adobe Org, using your Adobe ID.
Ensure you have access to all of the aforementioned services, prior to continuing through this tutorial.
Review sections below on how to set and provision the required services.
Access to an AEM as a Cloud Service environment is required in order to configure AEM Assets Processing Profiles to invoke the custom Asset Compute worker.
Ideally a sandbox program or a non-sandbox Development environment is available for use.
Note that a local AEM SDK is insufficient to complete this tutorial, as the local AEM SDK cannot communicate with Asset Compute microservices, instead a true AEM as a Cloud Service environment is required.
The App Builder framework is used for building and deploying custom actions to Adobe I/O Runtime, Adobe’s serverless platform. AEM Asset Compute projects are specially built App Builder projects that integrate with AEM Assets via Processing Profiles, and provide the ability to access and process asset binaries.
To gain access to App Builder, sign-up for the preview.
Cloud storage is required for local development of Asset Compute projects.
When Asset Compute workers are deployed to the Adobe I/O Runtime for direct use by AEM as a Cloud Service, this cloud storage is not strictly required as AEM provides the cloud storage from which the asset is read and rendition written to.
If you do not already have access to Microsoft Azure Blob Storage, sign up for a free 12 month account.
This tutorial will use Azure Blob Storage, however Amazon S3 can be used as well only minor variation to the tutorial.
Click-through of provisioning Azure Blob Storage (No audio)
If using Amazon S3 storage, specify the Amazon S3 cloud storage credentials when configuring the project’s environment variables.
If you need to provision cloud storage specially for this tutorial, we recommend using Azure Blob Storage.