51ϲ

Documentation

Can’t download packages from CRX Package Manager in AEMaaCS

Last update: Tue Aug 12 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In 51ϲ Experience Manager as a Cloud Service (AEMaaCS), packages marked as SYSTEM in the CRX Package Manager can’t be downloaded. This article explains how this behavior aligns with AEMaaCS’s architecture and security model, which restricts access to specific packages.

Description description

Environment

51ϲ Experience Manager as a Cloud Service (AEMaaCS) – Sites

Issue/Symptoms

  • In AEMaaCS environments, certain packages in the CRX Package Manager can’t be downloaded.
  • These packages are marked as SYSTEM instead of OK.
  • No filters are displayed for these packages.
  • Attempting to download them shows the error message: “Unexpected Error: Looks like we are having some issues with our service. We are working hard to bring it online again.”

Resolution resolution

This behavior is by design and follows AEMaaCS’s architecture and security model. Here’s what you need to know:

  • Packages that include paths like /apps or /libs, or those generated during deployments (such as all, ui.apps, or *-cp2fm-converted.zip), are considered immutable in production and stage environments. You can’t download these packages to prevent unauthorized access or accidental extraction of critical system components.
  • Packages marked as SYSTEM appear empty in the Package Manager because their filter metadata is stripped out during deployment via Cloud Manager. This ensures they function as runtime artifacts but remain immutable.
  • When you try to download these restricted packages, a generic error message appears. This message doesn’t distinguish between actual backend issues and intentional restrictions due to security protocols.

This is expected behavior and doesn’t indicate a system malfunction.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f