The default location for cloud init user data is already /var/log/cloud-init-output.log, in AWS, DigitalOcean and most other cloud providers. You don’t need to set up any additional logging to see the output.
While re-running all of cloud-init without reboot isn’t a recommended approach, the following commands will allow you to accomplish this on a system. The commands have been updated so to re-run you need to clean out the existing config: sudo cloud-init clean –logs cloud-init typically runs multiple boot stages in order due to systemd service … Read more
From https://git.launchpad.net/cloud-init/tree/config/cloud.cfg (thanks to garbelini) (As of Sep 2017 the above link is incorrect and is now https://git.launchpad.net/cloud-init/tree/config/cloud.cfg.tmpl, see note below) # The modules that run in the ‘init’ stage cloud_init_modules: – migrator – ubuntu-init-switch – seed_random – bootcmd – write-files – growpart – resizefs – set_hostname – update_hostname – update_etc_hosts – ca-certs – rsyslog … Read more
Is there an advantage over CloudInit? Yes, absolutely, many of them! Sure, you can write top to bottom run once CloudInit scripts to provision a server. But what happens when you need to change a configuration file, add a user, update a package, or install a new package? You will end up logging into servers … Read more