How to ingest assets into Adobe Experience Manager Assets as a Cloud Service
summary
Built‑in AEM Assets Bulk Import streams cloud-to-cloud from S3 or Azure for thousands or millions of files, creates upload/download URLs, and applies metadata mapped to target folders; AEM Upload (node.js / aio cli) recursively uploads folders, shards binaries for speed (demo: 877 files in ~1m10s) but doesn’t import metadata. Processing uses folder‑scoped Processing Profiles that call Asset Compute workers, integrate Photoshop/Lightroom and Sensei, emit Adobe I/O events, and auto-retry failed jobs. AEM Desktop supports resumable, foldered uploads for creators.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:37Agenda
- 1:10Use Cases
- 2:59Bulk Import
- 4:36Demo
- 6:23Dependencies
- 7:39Import
- 8:28Create local user
- 9:07Import assets
- 10:25Processing Profiles
- 13:23Setting up a Processing Profile
- 15:24Asset Compute Services
- 17:12Workers Job
- 21:02Creative Processing
- 21:37Processing after upload
related talks
02mAEM Shorts: Leveraging Cloud Manager to Optimize the DevOps Process
34mEfficient Development on Experience Manager as a Cloud Service
43mLearn workflows and tips for faster deployments with RDE
33mUsing Aerospike as a Real-time System-of-Record for Adobe Experience Cloud Services on Azure
25mContent creation under a new creative paradigm from on-premises to cloud
34mDisruption and reinvention of media and entertainment
30mAI-Assisted Creative for Automated Marketing using Python
37mReinventing Event Photography: Transform Community Moments