Adobe Experience Manager Sites

We are looking to manage OSGi configurations in the AMS environment instead of storing sensitive values in the codebase. In Adobe Cloud Manager, there is an option to manage environment-specific secrets and configurations. Is there a similar approach available in AMS, and if so, how can we manage these configurations securely?

 I have an running AEM 6.5.1 LTS instance that contains a lot of own content and code packages, as well as own configurations. Now  I want to upgrade this instance to 6.5.2. I download the release service pack and figured out, the “service pack” is a jar and not a single zip file.My current experience is when I execute this jar file I will get an instance with default and lose my content. Does not really exists another way? 

Hi All, Getting the below issue - C:\Users\admin\AppData\Local\@adobe\aio-cli>aio aem-migration:dispatcher-converter -t=ams********** Executing Dispatcher Converter **********Converting Dispatcher Configurations...Found usage of undefined variable:target/dispatcher/src/conf.d/available_vhosts/aem_publish.vhost:${PUBLISH_DEFAULT_HOSTNAME}Apache configuration uses non-whitelisted directives:target/dispatcher/src/conf.d/available_vhosts/aem_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/projA_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/projB_portal_publish.vhost:64 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/projB_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/projC_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/brandD_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/brandE_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/brandF_publis

Business ProblemToday, AJO Forms are managed separately from the AEM page experience. This creates inconsistencies in look and feel, limits the ability to leverage AEM page context, and makes it more difficult to provide a seamless personalized customer experience across Signify digital properties.Proposed EnhancementProvide a native AEM Component that allows authors to embed and configure AJO Forms directly within AEM pages.The component should:Allow authors to drag-and-drop AJO Forms into AEM pages. Inherit page styling and branding guidelines. Pass page and campaign context automatically to the embedded form. Support Adobe Experience Platform and AJO personalization capabilities. Enable consistent analytics and tracking across page interactions and form submissions.Business BenefitsConsistent User ExperienceAJO Forms become a natural part of the website experience instead of appearing as a separate application. Authors can maintain a unified design system and branding across pages a

Hi, I have a Dispatcher filter rule to allow for DELETE method for a specific url path. It works fine on my local AEM instance Dispatcher. The same errors out “406 Not Acceptable”Can you please suggest a fix for the AEMaaCS environment?The following is how the rule looks in the sites_filters.any file./0123 { /type "allow" /method "DELETE" /url "/service/xyz.json” 

Just been going through some of the announcements from Adobe Summit 2026 around AEM as a Cloud Service and wanted to get a real-world pulse from folks actually building on it day to day.A few things I’ve been thinking about after working on enterprise AEM Cloud implementations:The Edge Delivery Services push is getting louder but I’m curious how many teams are actually migrating existing Sites implementations versus greenfield only. In practice the replatforming effort is significant and I haven’t seen a clean story for brownfield migrations yet.Universal Editor is getting a lot of attention but author adoption in enterprise environments has been mixed in my experience. Has anyone actually rolled it out to a large non-technical authoring team and how did that go?On the pipeline and CI/CD side, Cloud Manager has improved but environment promotion still feels like it needs work especially around content variable management across stages.Would love to hear from others are these things you

Adobe Summit 2026 is packed with innovation across AEM, Agentic AI, LLM Optimization, DAM, Forms, Brand Concierge, and more. To make it easy for everyone, we’ve created one single, complete list of all AEM-related sessions in one place, so you can:Quickly scan everything Plan your schedule Share with your team Register directly Bookmark this post for recordings (they’ll be available at the same links after Summit)How to Use This PostClick the session title to go directly to the Summit catalog  Register from there After Summit, revisit the same link to access recordings (when available) Share this page with peers so no one misses outSession Title Session Description Schedule Location Speakers Session Type L335 – Build An Experience in Adobe Experience Manager the Agentic Way Generate new sites and features faster by leveraging generative AI in Adobe Experience Manager to transform specs into websites in hours. 2026-04-20 • 9:30 AM–11:00 AM • 90 min Marcello 2 Gabriel

Currently AEMaaCS does NOT offer an efficient way to create a set of pages from different hierarchies of the website which should be sent to translation in multiple target languages.If you have one page you can use the SITES console to create a translation project, also here the option is to include their subpages. But if you need to create a package of pages which are stored in different hierarchies of the website structure, you need to go to Projects > Translation Project and you need to add those pages to EACH target language that you have. Let’s say you have 30 languages of your website - so you need to do this adding of pages 30 times!This manual task is NOT efficient at all and takes a lot of time!AEMaaCS as an enterprise CMS should offer a smart way so that you have to do the selection just one time and then just select the target languages that apply. Current situation is more than disappointing!

Hi Community,I'm learning Adobe Experience Platform and wanted to understand a challenge that seems common in real-world implementations. When customer data is ingested from multiple channels, there can be situations where profiles are either incorrectly merged or remain fragmented due to identity conflicts. This can affect audience segmentation, personalization, and reporting. How do you typically identify, troubleshoot, and prevent identity stitching issues in production AEP environments? Any lessons learned or best practices would be greatly appreciated.

Please build API where you can store the user activity from 12 months to var node and so that based on that we can able to identify the how many active users are there from past 12 months. 

Hello,I am trying to work on allowing the Adobe Creative Cloud on our network and am looking for the minimum required list just to authenticate via the Creative Cloud and use Premiere Pro. Our network & security teams are very strict on what gets whitelisted and will question if there are 10+ domains added to a request.What is the bare minimum to just allow us to log into creative cloud and use Premiere Pro?Thank you

I’ve been experimenting with Playwright for testing the AEM authoring experience — not just the rendered pages.A few interesting issues surfaced that component/rendering tests simply wouldn’t catch:Dialog validation that didn’t match the field description A field that silently accepted an invalid configuration Rich-text input losing characters Test cleanup failing because of browser/API session differences Shared/included dialog fields that were easy to miss in component-based test coverageThese bugs lived in the authoring interaction — the clicks, typing, dialog state and sequence of actions an author actually performs.I wrote up the lessons learned, including some of the Playwright patterns that worked (and the ones that didn't 😄):👉 Testing the Click, Not the RenderCurious how others are approaching automated testing of the AEM authoring experience. Are you testing the editor UI today, or mainly the rendered output?

With the release of service pack 3 for LTS, I was wondering if there has been any changes or updates to address the segmentstore corruption issue?Has the offline compaction issue been address in SP 3? Is there any plan for a future service pack to resolve this issue?  When approaching an upgrade from 6.5 with the latest service pack to LTS with this latest service pack, is it best to skip offline compaction before the upgrade? In the materials for the LTS update it recommends offline compaction before migrating by during the offline revision cleanup: https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/implementing/deploying/upgrading/pre-upgrade-maintenance-tasks . It would be good to update these guides with the current best practices with regards to the offline compaction issue.Or is there a  new version of oak-run that will avoid this issue? The release page doesn’t give very much info.https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/cont

IntroductionPersonalization and caching can initially appear to be opposing concepts.Caching works best when many users requesting the same URL can reuse exactly the same response. Personalization, on the other hand, means that the same URL may produce different content depending on the context of the request.This becomes particularly interesting when the personalization criterion is the visitor's geographical location.Consider a global website built on Adobe Experience Manager as a Cloud Service where the same page must: display different content depending on the visitor's geographical market; show or hide certain components for specific markets; render the final personalized HTML on the server; remain SEO-friendly; avoid client-side content replacement; and continue benefiting from both Adobe's CDN and Dispatcher caching. A naive implementation can easily solve the personalization requirement while significantly reducing the cache hit ratio.This article describes an archite

My local instance of AEM 6.6.2 (6.5 lts sp2) runs on a Windows computer. I’m using Java21. When I install a content package with DAM assets, my local file error.log will be flooded with following error message: java.nio.file.InvalidPathException: Illegal char <:> at index 39: /content/dam/940x530.jpg/jcr:content/jcr:lastModifiedBy    at java.base/sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:204)According the Internet, the method function WindowsPathParser is internal used by Java’s Path.of()How can I fix this?

Our AEM as a Cloud Service site is currently experiencing heavy bot traffic and repeated bot attacks. We are evaluating Akamai Bot Management as an edge security layer and need confirmation on the supported architecture for AEMaaCS with Adobe Managed CDN �.Questions :Can Akamai Bot Management be placed in front of Adobe Managed CDN as a customer-managed CDN layer for AEMaaCS? �Is the recommended approach to keep Adobe Managed CDN and add Akamai in front, rather than replacing Adobe Managed CDN entirely? �Are there any restrictions, supported headers, or configuration requirements for this setup? �

Dear AEM Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for August 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEM. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEM-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – empowering you to provide a truly personalized experience to your customers with AEM.Start supercharging your problem-solving skills today by exploring our Top KCS Articles!Take a look:

Hi Team,We have a requirement to replace existing hardcoded /content/dam asset references in RTE and Text Components with Asset Delivery URLs (URN-based).Since the content has already been migrated to AEM Cloud, we are looking for the recommended approach to:Map existing DAM paths to Asset Delivery URLs. Update existing content containing /content/dam references. Follow AEM Cloud/Adobe best practices for this conversion.Could you please share your recommendations on the preferred architectural approach and any considerations we should keep in mind?

I am frequently getting the below warnings in my error log whenever I access any page. Anyone know how to fix this. I am using AEM 6.5  and using editable templates for pages.*WARN* [40.77.167.42 [1787899933431] GET  org.apache.sling.caconfig.resource.impl.def.DefaultConfigurationResourceResolvingStrategy Ignoring reference to /conf/ahn/settings from /conf/sites/settings - Probably misconfigured as it ends with '/settings' 

Hello All,                I wanted to add a custom styles dropdown to the latest content fragment RTE Editor Tiptap. I see no documentation regarding that, is it possible to add our custom dropdowns here.  Any information or leads plz let me know.Thanks,Sujan

Thank you to Karthik Muralidharan, Director, Strategy and Product Marketing, for the insightful presentation and demo on Adobe Brand Visibility! So many exciting things coming to the Generative Engine Optimization space!If you missed out, or want to replay the session, check out the links below:Slides Webinar Recording Check out the product yourself: play.bv.nowFeel free to use this space to keep the conversation going! Add your thoughts, follow-up questions or takeaways here and maybe let us know what feature you’re most excited about.If you missed it, check out the session we did in July with Darrel Smith from WK Kellogg and Emily Kellman-Kessel from Adobe.com. They shared their experiences of marketing in the world of AI. Also, save the date for September 22, for our next AI Search and Discovery Forum session – registration link coming soon!