Professional Services & Staffing · The Cloud Operations Portal on AEM: Multi-Cloud Orchestration Through Authorable Forms
The Cloud Operations Portal on AEM: Multi-Cloud Orchestration Through Authorable Forms
Turning fragmented, manual cloud provisioning into a single self-service portal across Azure, AWS, and ServiceNow
The Client · One of the world's largest professional services and consulting firms operating in over 150 countries
Overview
The firm engaged Taller to rebuild how its internal technology organization provisions cloud infrastructure and handles IT service requests, the platforms its own developers and operations teams run on.
The Problem
Cloud infrastructure requests and IT service operations ran through fragmented, manual channels: environment provisioning, VM management, and service requests scattered across emails, spreadsheets, and standalone ticketing systems with little integration. With no unified interface across Azure, AWS, and ServiceNow, every task meant separate logins, context switches, and manual handoffs; content and configurations were hardcoded or developer-managed, with no self-service for non-technical stakeholders. Provisioning took days to weeks, rework added an estimated 20-30% overhead on routine tasks, and request status was invisible without directly pinging someone, with security exposure, shadow-IT risk, and talent frustration compounding at the firm's scale.
The Solution
Taller designed and developed a unified internal web platform built on Adobe Experience Manager, deliberately architecting AEM as a full application and integration platform, something most AEM shops wouldn't attempt. Users logged in, saw role-appropriate tools, and submitted requests through intelligent dynamic forms; the platform acted as an orchestration layer that communicated with Azure, AWS, or ServiceNow behind the scenes through a dedicated OSGi integration layer centralizing all external API communication. A dynamic, reusable form engine built on AEM components let content authors and administrators extend forms and workflows without code; dashboards gave real-time visibility into VMs, requests, and resource utilization; and role-based access control drove dynamic behavior throughout. A focused Taller squad (a technical lead, AEM developers, and a frontend developer, peaking at five to six people) delivered it end to end in Java, OSGi, Apache Sling, and HTL, deployed through Azure DevOps and Adobe Cloud Manager.
The Impact
Environment provisioning and service-request turnaround dropped from days or weeks to hours, roughly ten times faster. Developer time spent on routine requests and configuration fell by an estimated 60-70%, developer intervention for content and workflow changes by around 80%, and cross-platform context switching to zero, down from three to five separate systems. Audit-trail and access-control coverage went from near-zero visibility to full.
