Set up accounts and services
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.
-
- Provisioning can take between 2 - 10 days
-
Cloud storage
AEM as a Cloud Service aem-as-a-cloud-service
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.
App Builder app-builder
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.
- Sign up for App Builder trial.
- Wait approximately 2 - 10 days until you’re notified via e-mail that you are provisioned before continuing with the tutorial.
- If you are unsure if you’ve been provisioned, continue with the next steps and if you are unable to create a App Builder project in Adobe Developer Console you still have not been provisioned.
Cloud storage
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.
Microsoft Azure Blob Storage azure-blob-storage
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)
-
Log in to your Microsoft Azure account.
-
Navigate to the Storage Accounts Azure services section
-
Tap + Add to create a new Blob Storage account
-
Create a new Resource group as needed, for example:
aem-as-a-cloud-service -
Provide a Storage account name, for example:
aemguideswkndassetcomput- The Storage account name used for configuring cloud storage in the local Asset Compute Development Tool
- The Access keys associated with the storage account are also required when configuring cloud storage.
-
Leave everything else as default, and tap the Review + create button
- Optionally, select the location close to you.
-
Review the provisioning request for correctness, and tap Create button if satified
Amazon S3 amazon-s3
Using Microsoft Azure Blob Storage is recommended for completing this tutorial, however Amazon S3 can also be used.
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.