Working with Adobe Managed Services (AMS) I’ve wished I had a guide to the common activities I need to log into a server to perform. Here is a quick starter to help you find your way around the servers provisioned by Adobe Managed Services. Since I can’t guarantee AMS environments are consistent (and checking with other teams I’ve confirmed they’re not) you may find these commands or paths don’t exactly match yours, but they should be a good start.
Before you can SSH into the AMS hosts, you will need to reach out to the CSE in order to create a user name and add your public key to the ~/.ssh/authorized_keys file on the host. I’d note that some AMS customers are still issued password-based users (in 2020!!) so ssh-copy-id may come in handy.
By default, the CSE will create a single username for all users to access. You can request they create named users as well, however, you will need to be vigilant in adding/removing users as these users are not managed in a centralized repository.
Lower vs. Upper Environment Access
By default, you will have more (if still limited) access to the Lower environments as compared to the upper environments. Even in the upper environments, you can request a “jailed user” with read-only access to the logs.
Inspired Digital Experiences for Manufacturing & Automotive
Whether you’re just beginning your digital transformation journey or are well on your way, we invite you to explore our partnership with Adobe and our diverse capabilities in manufacturing and automotive.
In the lower environments, you will be able to do a number of “write” activities by invoking sudo. For a full list of the commands you can execute run:
Your allowed sudo commands will generally use the full file path, it’s important to note in that case, you cannot just execute the command from the relative directory, e.g. this won’t work:
sudo vi dispatcher_vhost.conf
but this will:
sudo vi /etc/httpd/conf.d/dispatcher_vhost.conf
For those not experienced with AEM, Dispatcher servers run Apache httpd with a special module called the Dispatcher and serve as a proxy, cache and quasi-security layer for the AEM Authors and Publishers.
Note – you will not be able to change to the log directory and must use sudo
- Apache Docroot:
- Apache Server Configuration:
- Dispatcher Configuration:
- Restart Apache:
sudo service httpd restart
- Diagnose build errors:
sudo journalctl --system -u httpd
- List the Apache environment variables:
- List log files:
sudo ls /mnt/var/log/httpd/
- Tail log file:
sudo tail -f /mnt/var/log/httpd/[log-file-name]
Note – you cannot tail
/mnt/var/log/httpd/*, you need to explicitly mention the log files to tail, e.g:
sudo tail -f /mnt/var/log/httpd/access_log /mnt/var/log/httpd/error_log
- Edit a dispatcher configuration file:
sudo vi /etc/httpd/conf.dispatcher.d/[configuration-file]
This applies for both AEM Author and Publish instances as the setup of each from the AMS perspective is nearly identical besides the runmode.
- AEM Installation:
Note – You won’t be able to access the parent of the crx-quickstart folder and have to change directly into the crx-quickstart path
- Restart AEM:
sudo /etc/init.d/cq5 restart
- List Logs:
- Tail logs:
tail -f /mnt/crx/[author|publish]/crx-quickstart/logs/[log-file]
Hopefully, this helps you feel your away around your AMS installation and remember, we’re always here to help. Having trouble getting to something or diagnosing an issue? Leave a comment!