// Key takeaways

• EDS origin URLs are wide-open by default
• Persistent API keys are needed to lock it down
• Securing it is easy provided your users use the Sidekick

Using the AIO CLI to Push CDN Configs to the RDE's CDN

Once you have an AEM RDE set up and ready to accept your CDN configuration (noted in my article here), you're ready to set up your workstation to be able to push CDN configs to the RDE.

1. Get NPM, Node and NVM on your machine. You'll want to use nodejs 20 or 22
2. install the Adobe I/O runtime with npm install -g @adobe/aio-cli
3. install and update your AIO plugins:
   aio plugins:install @adobe/aio-cli-plugin-cloudmanager
aio plugins:install @adobe/aio-cli-plugin-aem-rde
aio plugins:update
4. Authenticate with aio login which will pop a browser window - make sure you use your IMS profile for the AEMaaCS account you're working with, otherwise you may need to aio logout and re-select.
5. Set your organization with aio cloudmanager:org:select
6. List programs with aio cloudmanager:list-programs and copy the id of your Program
7. Set your program ID to your org's ID with aio config:set cloudmanager_programid {YOUR PROGRAM ID GOES HERE}
8. If you want to see the environments you have access to, use aio cloudmanager:list-environments. This will show you which environment the RDE is located in
9. Use this to set the CloudManager EnvironmentID. This can be done by using aio config:set cloudmanager_environmentID {YOUR ENVIRONMENT ID GOES HERE}
10. Initiate your RDE setup with aio aem:rde:setup - it will ask if you want to store locally, say yes please
11. Try aio aem:rde:status and see if it lets you use the RDE.
12. Make sure you're in the parent directory of your AEMaaCS project ( ~/git/orgname/projectname), and push CDN configs with
    aio aem:rde:install -t env-config ./config

Tailing Logs on an AEMaaCS Environment

Need to watch live log output from an AEMaaCS Author, Publish, or Dispatcher? The AIO CLI makes this straightforward once you're authenticated and have your program/environment IDs configured.

1. Make sure you're authenticated: aio login. If you're already logged in from a previous session, you can verify with aio whoami.
2. Set (or confirm) your program ID: aio config:set cloudmanager_programid {YOUR PROGRAM ID}
3. List your available environments to find the one you want to tail: aio cloudmanager:list-environments
4. Set your target environment ID: aio config:set cloudmanager_environmentID {YOUR ENVIRONMENT ID}
5. List the available log types for that environment to see what's streaming: aio cloudmanager:list-available-log-options — this returns a table of service (author, publish, dispatcher) and log name (aemerror, aemaccess, httpdaccess, etc.)
6. Tail the log you want using the service name and log name from the previous step: aio cloudmanager:tail-log {service} {logName}
   For example, to tail the AEM error log on Publish: aio cloudmanager:tail-log publish aemerror
7. To tail the Author error log instead: aio cloudmanager:tail-log author aemerror
8. To tail the Dispatcher access log: aio cloudmanager:tail-log dispatcher httpdaccess
9. Press Ctrl+C to stop tailing at any time.

Pro tip: If you need to download a full log file rather than tail it live, use aio cloudmanager:download-log {service} {logName} {outputDir} to pull the latest log file to your local machine.

// Related reading

• Field Notes · AEM

  Using the Content Transfer Tool to Migrate AEM 6.5 Assets to AEMaaCS

  Read the runbook →

• Field Notes · DevOps

  Tailing and viewing Adobe Cloud Manager build logs

  Read the runbook →

CTA Band