<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kiran Mayee N on Medium]]></title>
        <description><![CDATA[Stories by Kiran Mayee N on Medium]]></description>
        <link>https://medium.com/@kiran_mayee?source=rss-93887a061c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LYYdc9zahSwUyRdJQ0UQxg.jpeg</url>
            <title>Stories by Kiran Mayee N on Medium</title>
            <link>https://medium.com/@kiran_mayee?source=rss-93887a061c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:09:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kiran_mayee/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I Tried All 5 AEM Agents on Adobe’s Playground. Here’s What Actually Works (and What Doesn’t).]]></title>
            <link>https://medium.com/@kiran_mayee/i-tried-all-5-aem-agents-on-adobes-playground-here-s-what-actually-works-and-what-doesn-t-8c22233a457c?source=rss-93887a061c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c22233a457c</guid>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[adobe]]></category>
            <dc:creator><![CDATA[Kiran Mayee N]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 05:36:51 GMT</pubDate>
            <atom:updated>2026-06-04T05:49:22.175Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A hands-on, no-hype walkthrough of every AI agent in AEM as a Cloud Service — with real prompts, real results, and honest limitations.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sojeihaJR9yIbNzFFCvPng.png" /><figcaption>AEM Agents</figcaption></figure><p>If you’ve been anywhere near the AEM ecosystem this year, you’ve heard the buzzword: <strong>Agents</strong>. Adobe Summit 2026 was practically an agents showcase. Every keynote, every demo, every slide deck — agents, agents, agents.</p><p>But here’s the thing. Most of the content out there is marketing material. Flashy demos on stage with perfectly curated data. Nobody’s telling you what happens when <em>you</em> actually try it on a real (or Playground) environment.</p><p>So I did. I spent time on Adobe’s AEM Playground — a free sandbox loaded with a fictitious coffee brand called <strong>Frescopa</strong> — and tested every agent myself. Five agents. Real prompts. Real results. And real disappointments.</p><p>Here’s everything I found.</p><h3>First — What Are Agents, and Why Should You Care?</h3><p>Let me clear up the biggest misconception first.</p><p><strong>Agents are NOT chatbots.</strong></p><p>The AI Assistant in AEM has been around for a while — you ask it a question about AEM, it answers from Adobe Experience League docs. That’s a chatbot. Useful, but not revolutionary.</p><p>An <strong>agent</strong> is different. An agent doesn’t just answer questions — it <strong>takes actions inside AEM</strong>. It reads your pages, searches your DAM, modifies content, creates forms, validates brand compliance, and analyzes pipeline logs. It does work. For you.</p><p>AEM now has five agents, and each one has a specific role — like five specialists on your content team:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*FpCyZYl55GZ6okQRonhX7g.png" /></figure><p>And underneath all five sits <strong>Brand Intelligence</strong> — the reasoning engine that makes every agent brand-aware instead of generic.</p><p>Let’s look at each one.</p><h3>Agent 1: Discovery Agent — The One That Actually Blew My Mind</h3><p>Of all five agents, this is the one I’d show to a non-technical stakeholder first. It’s visual):, it’s instant, and it works.</p><p><strong>The problem it solves:</strong></p><p>You know the drill. Your DAM has thousands of assets across hundreds of folders. Finding the right image means browsing folders, applying metadata filters, guessing tag names, and hoping someone tagged things properly. It’s 2026 and we’re still doing this.</p><p><strong>What I typed on the Playground:</strong></p><pre>Find images of coffee cups</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kXbteCBYKp8tHi2tQNScfQ.png" /><figcaption>AEM Discovery Agent Demo 1</figcaption></figure><p>That’s it. One sentence.</p><p><strong>What happened:</strong></p><p>The agent searched across Assets, Content Fragments, Pages, and Forms — all at once. It returned a curated set of results with thumbnails, metadata (file name, format, dimensions, tags), and delivery URLs. No folder browsing. No filters. No tag guessing.</p><p>I followed up with:</p><pre>Find approved lifestyle photos with landscape orientation</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CqwnT8xNXwDbODvDfhhAnw.png" /><figcaption>AEM Discovery Agent Demo 2</figcaption></figure><p>Same thing — instant, relevant results.</p><p><strong>Why this matters:</strong></p><p>If you have content authors spending 20–30 minutes per search session browsing the DAM, multiply that across a team of 50 authors. Discovery Agent turns that into a 10-second conversation. The ROI argument writes itself.</p><p><strong>Verdict: ✅ Works. Impressive. Show this to your stakeholders first.</strong></p><h3>Agent 2: Optimization Agent — Great in Theory, Needs Dynamic Media</h3><p>The Discovery Agent finds your assets. The Optimization Agent transforms them — crops, resizes, sharpens, changes backgrounds, creates channel-ready versions.</p><p><strong>What I tried:</strong></p><p>After Discovery returned results, I typed:</p><pre>For the first result, create a 1080x1080 square crop as JPEG</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/509/1*unRuN3N8780YybQJDYc3UA.png" /><figcaption>AEM Optimization Agent Demo 1</figcaption></figure><p><strong>What happened:</strong></p><p>On the Playground, this depends on whether Dynamic Media with OpenAPI is enabled on your environment. If it is — you get an instant channel-ready rendition with a delivery URL. Instagram-ready in one sentence.</p><p>Other prompts that work when Dynamic Media is enabled:</p><pre>Sharpen the image</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/385/1*T5Lk_tIBxzdQ416VwW9fjQ.png" /><figcaption>AEM Optimization Agent Demo 2</figcaption></figure><pre><br>Change the background color to #2c1810</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*lO0Pq_QLiWKg-3LNwGs_gQ.png" /><figcaption>AEM Optimization Agent Demo 3</figcaption></figure><pre>Flip it horizontally</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*laWBNmJSxcMt6Pl807GZ2w.png" /><figcaption>AEM Optimization Agent Demo 4</figcaption></figure><p><strong>The catch:</strong></p><p>Dynamic Media with OpenAPI isn’t always configured in Playground environments. If it’s not, Discovery works fine but Optimization won’t. This is the first of several “it depends on your setup” moments.</p><p><strong>Verdict: ✅ Works beautifully when Dynamic Media is enabled. ⚠️ Won’t work without it.</strong></p><h3>Agent 3: Production Agent — Half Genius, Half Work-in-Progress</h3><p>The Production Agent modifies your AEM content — page updates, new pages, forms — without opening a single editor dialog.</p><p><strong>Form creation: nailed it.</strong></p><pre>Create a feedback form with: Name, Email, Rating, Comments, Submit button</pre><p>The agent generated the form structure, detected field types, added validation, and asked me to choose between Core Components or EDS adaptive form templates. Half a day of developer work — under a minute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*HPHzyovTyWohO6po6pa0lg.png" /><figcaption>AEM Production Agent Demo 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VmOxUkjpbOLGHh3I2mYF0w.png" /><figcaption>AEM Production Agent Demo 1 — Edit Form</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9N3h7WHldwAEWZSOTwMG2Q.png" /><figcaption>AEM Production Agent Demo 1 — View Form</figcaption></figure><p><strong>Content updates: not so much.</strong></p><pre>Update the hero headline on the homepage to &quot;Wake Up to Something Extraordinary&quot;</pre><p>The agent did everything right on paper — identified the page, passed a brand guideline check, created a Launch, gave me a Preview link, and reported: <em>“The plan successfully completed!”</em></p><p>I opened the preview. Nothing had changed.</p><p>I got more specific:</p><pre>In index page, modify &quot;Your perfect coffee is four questions away!&quot; to &quot;Wake Up to Something Extraordinary&quot;</pre><p>Same outcome. <em>“Changes applied.”</em> Page — untouched.</p><p><strong>Why I’m sharing this:</strong> Not to bash the agent. If you try this on the Playground and hit the same wall, I want you to know — it’s not you. The workflow executes correctly (Launches, brand checks, confirmations), but the last mile — actually modifying the rendered component — didn’t land on Frescopa’s demo site. The content structure likely doesn’t map cleanly to what the agent expects.</p><p>Adobe will close this gap. But today, in June 2026, this is where things stand.</p><p><strong>The safety net I appreciated:</strong> Every change creates a Launch first. Nothing goes live until you type “accept.” That’s non-negotiable for enterprise use — and it works.</p><p><strong>The catch:</strong></p><p>The Production Agent needs to be provisioned separately. It’s not just an Admin Console toggle — it requires the Agentic SKU or the Try Before You Buy program. On the Playground, availability varies.</p><p><strong>Verdict: ✅ Form creation works beautifully. ⚠️ Content updates executed but didn’t visibly change the page on the Playground. Better results expected on properly configured environments.</strong></p><h3>Agent 4: Governance Agent — The Brand Police</h3><p>Every piece of content your team creates — whether by hand or by AI — needs to be on-brand before it goes live. Right tone? Approved claims? Correct logo usage? The Governance Agent checks all of that.</p><p><strong>What I tried:</strong></p><pre>Show me my brand guidelines</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*rczTuiAbFlBE3xuCX1s96g.png" /><figcaption>AEM Governance Agent Demo 1</figcaption></figure><p><strong>What should happen:</strong></p><p>If brand guidelines have been imported (you upload your brand PDF and the AI converts it into structured, enforceable checks), the agent displays the rules. Then you can validate any page:</p><pre>Check if the homepage follows our brand guidelines</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*t5T68ctPfFxPUAwhPQ39Lg.png" /><figcaption>AEM Production Agent Demo 2</figcaption></figure><p>It returns pass/fail for tone, claims, logos, typography, and imagery.</p><p>Beyond brand validation, the Governance Agent also handles:</p><ul><li><strong>ABAC (Attribute-Based Access Control)</strong> — Rule-based permissions in Content Hub. Instead of managing access per user or per folder, you set rules based on attributes: role, department, product line, region.</li><li><strong>Digital Rights Management</strong> — Watermarking, content credentials (provenance tracking), and asset expiry management.</li></ul><p><strong>The catch:</strong></p><p>Brand guidelines need to be imported first. If nobody has uploaded the brand PDF, the agent has nothing to validate against. The Playground may or may not have this configured.</p><p><strong>Verdict: ⚠️ Conceptually the most valuable agent for enterprise teams. But useless without brand guidelines being imported first.</strong></p><h3>Agent 5: Development Agent — 2 Hours → 2 Minutes</h3><p>This one’s for developers. When a Cloud Manager pipeline fails, you know what happens: open Cloud Manager, find the execution, download logs, scroll through 500 lines of stack traces, cross-reference with your code, Google the error. Two hours gone.</p><p><strong>What the Development Agent does:</strong></p><pre>Why did pipeline wknd-prod-deploy fail?</pre><p>It reads the build logs, identifies the exact failing test (e.g., a unit test failure in BylineImpl.java), shows the assertion that broke, and suggests a specific code fix.</p><p><strong>What’s supported right now:</strong></p><p>Pipeline StepStatusBuild &amp; Unit Testing<strong>GA</strong>Code Scanning (SonarQube)<strong>GA</strong>Web Tier Config Pipeline<strong>Beta</strong> (email <a href="/service/mailto:aem-devagent@adobe.com">aem-devagent@adobe.com</a>)</p><p><strong>Hands-on tip:</strong> If you want to test this yourself, clone the WKND Sites Project and checkout the tutorial/dev-agent/unit-test-failure branch. Push it to Cloud Manager, run a Code Quality pipeline — it&#39;ll fail intentionally. Then ask the agent why. The whole exercise takes about 20 minutes and is very satisfying.</p><p><strong>Verdict: ✅ Works. Genuinely saves hours. The most immediately useful agent for developers.</strong></p><h3>The Engine Behind Everything: Brand Intelligence</h3><p>Every agent draws from the same reasoning engine — <strong>Brand Intelligence</strong>. It’s not a product you open or interact with directly. It’s the layer underneath that makes the agents brand-aware.</p><p>Three capabilities:</p><ol><li><strong>Validate</strong> — What the Governance Agent uses to check content against brand rules.</li><li><strong>Instruct</strong> — What teaches AI your brand’s voice, tone, and approved terms when generating content.</li><li><strong>Predict</strong> — And this is the interesting one. It watches your team’s review process. Every approval teaches it what “good” looks like. Every rejection teaches it what to avoid. Every annotation a reviewer leaves captures nuances no style guide could cover.</li></ol><p>Over time, the content AI generates gets closer to what your brand team would produce themselves. Your review process becomes training data — not just overhead.</p><h3>How to Try This Yourself — Three Paths</h3><p><strong>Path 1: The Playground (Free, Instant)</strong></p><p>Go to <a href="https://www.aem.live/developer/aem-playground">aem.live/developer/aem-playground</a>. Sign in with your Adobe ID. You get an instant sandbox with the Frescopa demo brand — pages, images, content fragments, five agents. Deletes after 30 days. Zero risk.</p><p>You can also create a Playground from Experience Hub — look for “Create Playground” in the Product Announcements panel.</p><p><strong>Path 2: Try Before You Buy</strong></p><p>Adobe is rolling this out in phases. Talk to your CSM or TAM to confirm availability for your organization. Details: <a href="https://experienceleague.adobe.com/en/docs/experience-cloud-ai/experience-cloud-ai/agents/trial">experienceleague.adobe.com/en/docs/experience-cloud-ai/experience-cloud-ai/agents/trial</a></p><p><strong>Path 3: Agentic SKU</strong></p><p>Full production access. Connect with your CSM or TAM if agents fit your roadmap.</p><p><strong>Important:</strong> All agents are <strong>AEM Cloud Service + Edge Delivery Services only</strong>. Not available on AEM 6.5, on-prem, or Managed Services.</p><h3>The Honest Summary</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bJD49iQ6YoWHSLUseyU8cg.png" /></figure><p>AEM Agents aren’t vaporware. They work. But they’re also not magic — each one has prerequisites, and the enterprise reality of provisioning, configuration, and licensing means you won’t flip a switch and have all five running tomorrow.</p><p>My recommendation: Open the Playground today. Start with Discovery Agent — type Find images of coffee cups and see what comes back. Then try the Development Agent on a failed pipeline. Those two alone will convince you that the future of AEM development has fundamentally changed.</p><blockquote>One thing became clear through all of this: AI agents won’t replace AEM developers anytime soon. But developers who know how to use these agents effectively — who understand when to use Discovery over manual browsing, when to let the Development Agent read the logs, and when to just open the editor yourself — will have a real advantage.</blockquote><blockquote>The agents don’t replace your expertise. They amplify it.</blockquote><p>Happy exploring! 🚀</p><p><em>I’m Kiran Mayee N —Senior AEM developer at Publicis Sapient. Previously at Bounteous, where I wrote the </em><a href="https://medium.com/activate-aem/enhancing-aem-lucene-search-advanced-techniques-for-improved-search-functionality-part-1-effbbc4ab5e9"><em>Enhancing AEM Lucene Search</em></a><em> series on the Activate AEM publication. I write about AEM, cloud development, and making enterprise tech less painful. Connect with me on </em><a href="https://linkedin.com/in/kiran-mayee"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c22233a457c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Rapid Development Environment (RDE) in AEM Cloud Manager — A Developer’s Guide]]></title>
            <link>https://medium.com/@kiran_mayee/using-rapid-development-environment-rde-in-aem-cloud-manager-a-developers-guide-f5ef01ef2ff8?source=rss-93887a061c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5ef01ef2ff8</guid>
            <category><![CDATA[adobe]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[aem-developer]]></category>
            <dc:creator><![CDATA[Kiran Mayee N]]></dc:creator>
            <pubDate>Fri, 31 Oct 2025 22:27:31 GMT</pubDate>
            <atom:updated>2025-10-31T22:35:07.446Z</atom:updated>
            <content:encoded><![CDATA[<h3>Using Rapid Development Environment (RDE) in AEM Cloud Manager — A Developer’s Guide</h3><p>If you’ve been working with AEM as a Cloud Service, you’ve probably seen environments like <strong>DEV</strong>, <strong>QA</strong>, <strong>UAT</strong>, <strong>STAGE</strong>, and <strong>PROD</strong>. Recently, Adobe introduced something new to make developers’ lives easier — the <strong>Rapid Development Environment (RDE)</strong>.</p><p>I’ve been exploring this feature for a while, and in this post, I’ll walk through how I set it up locally, deploy code, view or download logs, and reset it when needed — all using <strong>Adobe I/O CLI</strong>.</p><p><em>(My older Medium account: </em><a href="https://medium.com/@kiran.mayee"><em>@kiran.mayee</em></a><em> is no longer active, so I’ll be continuing my AEM write-ups here.)</em></p><figure><img alt="Adobe AEM RDE" src="https://cdn-images-1.medium.com/max/1024/1*wHjeHo-lvetzmQFMB-KGFA.jpeg" /></figure><h3>Why RDE?</h3><p>Deploying through the Cloud Manager pipeline to DEV or QA can be time-consuming. Every build passes through several quality and security gates — which is great for production, but slows down developers who just want to test a small change.</p><p>That’s where <strong>Rapid Development Environment (RDE)</strong> comes in.</p><p>It’s a <strong>cloud-hosted development environment</strong> meant for quick deployments and testing.<br> You can push code directly from your local machine to AEM Cloud, without waiting for the full CI/CD cycle.</p><h3>Key takeaways:</h3><ul><li>⚡ Designed for fast, iterative testing</li><li>🧱 Always runs the latest AEM version</li><li>🧩 Perfect for validating features, configs, and quick fixes</li><li>💤 Automatically hibernates after inactivity to save resources</li></ul><h3>Prerequisites</h3><p>Before jumping in, make sure you’ve got the following ready:</p><ol><li><strong>Node.js</strong> — version 18+ recommended.<br> You can check with:</li></ol><pre>node -v<br>npm -v</pre><p>If not installed, grab it from <a href="https://nodejs.org/">nodejs.org</a>.</p><p><strong>2. Access permissions</strong> — you need to be part of the Cloud Manager program with at least <em>Developer role</em> and permissions to deploy to RDE.</p><p><strong>3. Adobe I/O CLI</strong> — this is your command-line bridge to Cloud Manager and RDE.</p><p><strong>4. Your Program ID, Environment ID, and Org ID</strong> —</p><ul><li>Go to <a href="https://experience.adobe.com/#/cloud-manager">Cloud Manager</a></li><li>Open your <strong>Program</strong>, then check the <strong>URL</strong>:</li></ul><pre>https://experience.adobe.com/#/@your-org/cloud-manager/program/&lt;program-id&gt;/environment/&lt;environment-id&gt;</pre><ul><li>In this example:</li><li><strong>Program ID</strong> → &lt;program-id&gt;</li><li><strong>Environment ID</strong> → &lt;environment-id&gt;</li><li><strong>Org ID</strong> → visible in the upper-right user info (ends with @AdobeOrg).</li></ul><h3>Creating a Rapid Development Environment</h3><p>To create an RDE:</p><ol><li>Go to <strong>Cloud Manager → Your Program</strong></li><li>Under <strong>Environments</strong>, click <strong>Add Environment</strong></li><li>Select <strong>Rapid Development Environment (RDE)</strong></li><li>Give it a name and click <strong>Save</strong></li></ol><p>That’s it — once provisioned, you’ll see it listed among your environments.</p><h3>Setting Up Adobe I/O CLI and RDE Plugins</h3><p>Here’s the exact setup I used — line by line:</p><pre>npm install -g @adobe/aio-cli</pre><pre>aio plugins:install @adobe/aio-cli-plugin-cloudmanager</pre><pre>aio plugins:install @adobe/aio-cli-plugin-aem-rde</pre><pre>aio plugins:update</pre><p>Now configure your environment identifiers:</p><pre>aio config:set cloudmanager_orgid &lt;your-org-id&gt;@AdobeOrg<br>aio config:set cloudmanager_programid &lt;your-program-id&gt;<br>aio config:set cloudmanager_environmentid &lt;your-environment-id&gt;</pre><p>You can verify them using:</p><pre>aio config:list<br>aio where<br>aio login<br>aio aem:rde:setup<br>aio aem rde setup --show<br>aio aem:rde:status</pre><p>Once setup is done, deploy your AEM package like this:</p><pre>aio aem:rde:install .\all\target\aem-guides-wknd.all-4.0.5-SNAPSHOT.zip</pre><p>💡 <strong>Tip:</strong><br> The <strong>dispatcher configuration</strong> does <strong>not</strong> automatically install with the .all package.<br> You have to send it separately using:</p><pre>aio aem:rde:install dispatcher/target/&lt;your-project&gt;.dispatcher.cloud-1.0.0-SNAPSHOT.zip</pre><h3>Setting Up Dispatcher for RDE</h3><p>When deploying to RDE, the publisher’s domain is different from your usual environments.<br> To ensure requests reach your RDE publish instance correctly, update your <strong>dispatcher farm</strong> file.</p><p>In your dispatcher configuration, add the <strong>RDE publish host</strong> under virtualhosts:</p><pre>/virtualhosts {<br>  &quot;publish-rde-&lt;programid&gt;-&lt;environmentid&gt;.adobeaemcloud.com&quot;<br>}</pre><p>This helps your dispatcher route traffic correctly for the RDE publisher domain.</p><h3>Viewing and Downloading Logs</h3><p>When something goes wrong (and it will, at some point 😄), logs are your best friend.</p><p>You can either <strong>tail logs live</strong> from your terminal or <strong>download them</strong> directly from <strong>Cloud Manager</strong> or the <strong>CLI</strong>.</p><h3>🧭 Option 1: Using Cloud Manager UI</h3><p>If you prefer a visual way —</p><ol><li>Go to <strong>Cloud Manager → Environments → (RDE)</strong></li><li>Click on <strong>Logs</strong> in the top navigation</li><li>Choose <strong>Author</strong>, <strong>Publish</strong>, or <strong>Dispatcher</strong></li><li>Download the specific log files (like aemerror.log, request.log, or dispatcher.log)</li></ol><p>This is great for when you quickly need to inspect logs without setting up CLI access.</p><h3>💻 Option 2: Using Adobe I/O CLI</h3><p>If you like working from the terminal, here are some handy commands:</p><p>List all available log types for your RDE:</p><pre>aio cloudmanager:list-available-log-options</pre><p>Tail logs in real time (these stream directly from AEM Cloud):</p><pre>aio cloudmanager:environment:tail-log author aemerror<br>aio cloudmanager:environment:tail-log dispatcher aemdispatcher</pre><blockquote><em>⚠️ It can take a few seconds to load logs from Cloud — so don’t panic if you see a short delay.</em></blockquote><p>Or, download logs locally (faster and ideal for grepping):</p><pre>aio cloudmanager:environment:download-logs author aemerror</pre><p>This saves the log file in your current directory — handy for offline debugging or archiving.</p><h3>Resetting and Checking Deployment History</h3><p>Need a clean slate? You can reset your RDE from the UI or CLI.</p><h3>Option 1: From Cloud Manager</h3><p>Go to <strong>Environments → (RDE) → … → Reset</strong></p><h3>Option 2: Using CLI</h3><pre>aio aem:rde:reset</pre><p>To view what’s been deployed so far:</p><pre>aio aem:rde:history</pre><p>This lists all your previous deployments with timestamps.</p><h3>Why I Found RDE Useful</h3><p>In simple words — <strong>speed</strong>.<br> You can validate your changes in an actual cloud environment within minutes.</p><p>It’s been incredibly useful for:</p><ul><li>Testing OSGi configuration changes</li><li>Verifying Sling Models and GraphQL endpoints</li><li>Experimenting with dispatcher and cache rules</li><li>Debugging cloud-only issues</li></ul><p>Once your feature is stable, you can promote the same code through the regular pipeline.</p><h3>Wrapping Up</h3><p>RDE bridges the gap between local SDK testing and the slower Cloud Manager pipelines.<br> It’s perfect for quick iterations, debugging, and validating code in a real AEM Cloud setup — without the overhead of a full build cycle.</p><p>If you haven’t tried it yet, set it up once — it barely takes 15 minutes and will noticeably speed up your day-to-day AEM development.</p><p>This write-up is based on what I’ve set up and tested locally, so it should help you get started smoothly with RDE.</p><p>For detailed reference and screenshots, check the official Adobe docs:</p><ul><li><strong>Setup RDE:</strong> <a href="https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/developing/rde/how-to-setup">https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/developing/rde/how-to-setup</a></li><li><strong>Get Organization ID:</strong> <a href="https://experienceleague.adobe.com/en/docs/core-services/interface/administration/organizations#concept_EA8AEE5B02CF46ACBDAD6A8508646255">https://experienceleague.adobe.com/en/docs/core-services/interface/administration/organizations#concept_EA8AEE5B02CF46ACBDAD6A8508646255</a></li><li><strong>Deploy Code to RDE:</strong> <a href="https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/developing/rde/how-to-use">https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/developing/rde/how-to-use</a></li></ul><p>See ya!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5ef01ef2ff8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>