Study guide
7.1 AEM Maintenance Releases & Cloud Service Version Updates
Adobe Certified Professional - AEM Sites Developer AD0-E128
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Dispatcher Farm & Multi-Site Configuration
1.1 AEM Dispatcher Configuration & Caching Fundamentals 1.2 Multi-Site Management (MSM) & Blueprint/Live Copy Architecture 1.3 OSGi Configuration Management & Run Modes (.cfg.json)
2 Chapter 2: Oak Indexing & Custom Logging
2.1 Custom Oak Index Definitions & Lucene Query Optimization 2.2 AEM Custom Logging, Logback Configurations & Request Tracing
3 Chapter 3: Component Architecture, HTL & Client Libraries
3.1 Core Components & Proxy Component Pattern 3.2 HTL (HTML Template Language) Block Statements & Context-Aware Escaping 3.3 Client-Side Libraries (Clientlibs) Architecture & Management
4 Chapter 4: Sling Models & OSGi Declarative Services
4.1 Sling Models Framework, Injectors & Model Exporter 4.2 OSGi Declarative Services, Component Lifecycle & Service Rankings
5 Chapter 5: Templates, Fragments & Business Workflows
5.1 Editable Templates, Structure, Initial Content & Content Policies 5.2 Content Fragments, Experience Fragments & Headless Delivery 5.3 AEM Workflows, Custom Process Steps & Launchers
6 Chapter 6: Build, Packaging & Cloud Manager CI/CD
6.1 Maven Project Structure & AEM Project Archetype 6.2 Content Package Types, Packaging Rules & FileVault Validation 6.3 Cloud Manager CI/CD Pipelines & Quality Gates 6.4 Rapid Development Environments (RDE) & Sling Repoinit Scripts
7 Chapter 7: Environment Maintenance & Content Distribution
7.1 AEM Maintenance Releases & Cloud Service Version Updates 7.2 AEM Deployment Topologies & Cloud Architecture 7.3 Replication Agents & Sling Content Distribution 7.4 Repository Maintenance: Revision Cleanup, Compaction & Purge Tasks
8 Chapter 8: Analyzing, Debugging & Diagnostic Tools
8.1 System Log Analysis & Diagnostic Tooling 8.2 Debugging Client-Side Libraries & Granite Dumplibs 8.3 Dispatcher Caching Diagnostics, X-Cache-Info & Local Validation 8.4 Environment Troubleshooting, Web Console & Developer Console
7.1 AEM Maintenance Releases & Cloud Service Version Updates
Key Takeaways Explain This Topic AI
AEM 6.5 maintenance is customer-operated through cumulative Service Packs and applicable hotfixes, with backups, compatibility checks, and planned rollout across instances.
AEM as a Cloud Service separates monthly feature releases from frequent maintenance releases; Adobe currently publishes maintenance releases on a regular cadence rather than as a guaranteed daily update.
A new Cloud Service maintenance release is announced several days before rollout so development and staging validation can occur before production.
Customer functional tests and custom UI tests are blocking for Cloud Service version updates: failure stops rollout while production remains on its current release.
Customers maintain compatible custom code and reliable tests while Adobe manages the platform update and rolling deployment.
Last updated: September 2026
7.1 AEM Maintenance Releases & Cloud Service Version Updates
Quick Answer: AEM 6.5 uses customer-planned cumulative Service Packs and applicable hotfixes. AEM as a Cloud Service is updated by Adobe through monthly feature releases and frequent maintenance releases . Adobe announces a maintenance release several days before automatic rollout, validates it with customer code and tests, and uses rolling deployment to avoid planned downtime.
AEM 6.5 Maintenance
AEM 6.5 is a long-lived release line. A Service Pack is cumulative: installing a supported later Service Pack brings forward the fixes from earlier Service Packs in that line. Adobe may also publish security or product hotfixes with explicit prerequisites. Cumulative Fix Packs belong mainly to earlier AEM 6.x maintenance history; do not assume a CFP is the normal current update vehicle for every AEM 6.5 system.
A controlled AEM 6.5 update normally includes:
Read the release notes, known issues, prerequisites, and compatibility guidance.
Back up repository and configuration state according to the deployment runbook.
Test the Service Pack and custom code in a representative lower environment.
Verify OSGi bundles, repository indexes, workflows, Dispatcher behavior, and integrations.
Roll through author and publish instances with the availability strategy appropriate to the topology.
Perform smoke and regression tests and monitor logs after installation.
Package Manager may be part of an on-premises process, but Cloud Manager can govern AEM Managed Services deployments. The important distinction is ownership: AEM 6.5 customers plan and execute the maintenance release, while Cloud Service platform updates are operated by Adobe.
Cloud Service Release Tracks
AEM as a Cloud Service has two product-release tracks:
Feature releases: generally monthly and described in release notes. They introduce capabilities and product changes.
Maintenance releases: published frequently to deliver fixes, security updates, and reliability improvements. Adobe's current roadmap describes a regular maintenance cadence; it should not be memorized as a guaranteed daily patch.
A maintenance release is published several days before production rollout. Development environments may update automatically or offer an update action during the transition. This gives teams time to run their application against the upcoming release.
Cloud environments are versioned and the SDK has matching releases. Keep the local Quickstart and the aem-sdk-api dependency reasonably aligned with the cloud release being tested. Avoid copying a made-up future SDK build number into documentation or source.
How a Platform Update Is Verified
A Cloud Service version update is separate from a customer-code deployment. The update process combines the candidate AEM release with the customer's deployed application and validates the result before production rollout.
Blocking checks include customer functional tests and custom UI tests. Adobe also runs product-level validation. If a blocking test fails, the AEM release does not proceed to production and the failure is investigated. Production remains on the current release; Cloud Manager does not rewrite a customer's tests or silently bypass them.
A practical customer workflow is:
- keep functional and UI tests deterministic and focused on critical journeys;
- eliminate brittle selectors and timing assumptions;
- test supported APIs rather than internal implementation details;
- review release notes and deprecation notices;
- reproduce any regression on the matching local SDK or a development environment;
open a support case with reproducible evidence when the platform update is the likely cause.
Rolling Version Updates
Cloud Service typically updates without downtime. Rolling updates are possible because each running release has its own immutable product code while old and new nodes can reference the mutable repository during the transition. Ready new nodes take traffic while old nodes are removed gradually.
This is not an excuse to make incompatible repository mutations. During either a customer deployment or a platform update, multiple application versions may coexist. Custom code should use supported public APIs and remain tolerant of the content shapes visible during a rolling release.
Customer Responsibilities
Adobe owns infrastructure provisioning, platform binaries, operating-system maintenance, and the rollout mechanism. The customer still owns:
- custom code compatibility and supported API usage;
- functional and UI regression tests stored with the application;
- Dispatcher and application configuration;
- monitoring and triage of customer-code failures;
- current development dependencies and SDK tooling;
planned migration away from deprecated APIs.
Comparison
Concern AEM 6.5 AEM as a Cloud Service
Platform update Customer installs Service Packs and relevant hotfixes Adobe delivers frequent maintenance and monthly feature releases
Validation Customer plans lower-environment testing Adobe process plus customer functional and UI tests before rollout
- Deployment Depends on customer topology and runbook Managed rolling update
- Local API dependency 6.5 API/uber-jar aligned to Service Pack aem-sdk-api aligned to Cloud Service SDK
- Runtime code areas Customer-managed repository and hosts /apps and /libs immutable at runtime
For exam scenarios, first identify the hosting model. A request to install a Service Pack through Package Manager points to AEM 6.5; a staged, Adobe-managed version rollout with blocking customer tests points to AEM as a Cloud Service.