Easy Puppet Server with Some Tweaks Needed
This AMI was easy to launch and after a few tweaks was in our environment and ready to start managing servers.
After launching it is highly recommended that if you are not going to use the AWS assigned hostname in your puppet configs that you rename the server BEFORE running the install script indicated in the usage instructions.
After the installations script was run, at least in my case, I was required to do the following to make puppetboard work.
Apache was throwing 500 errors and 'ImportError: No module named parse' was showing up in the logs.
Python is in a vitual environment on this AMI so you must switch to it an install.
Following that I still got the error and determined that a tweak to the python script '/srv/puppetboard/virtenv-puppetboard/lib/python2.7/site-packages/pypuppetdb/api.py' was required.
The import of parse was written in support of Python 3, but this system runs with Python 2.
So I used the following to make the script more flexible.
try:
from urllib import quote # Python 2.X
except ImportError:
from urllib.parse import quote # Python 3+
After that, smooth sailing. As a puppet admin I recommend this AMI bearing in mind the tweaks above or if the vendor fixes the AMI in the future to incorporate these tweaks.
Great that the installer did the trick for you and that you were able to resolve the Puppetboard issue - Puppetboard is a rather tricky beast to automate reliably when its underlying dependencies change over time. Your comment about the hostname is exactly correct. Our new Puppet 6-based image is about to go into AWS review. In it we document and warn about using Amazon-style hostname. It will also have several new features like deploying a control repository automatically, which is very useful for dynamic testing environment.