Home/ Questions/Q 7889551
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T06:07:43+00:00

I have an EC2 instance running an AMI based on the Amazon Linux AMI.

  • 0

I have an EC2 instance running an AMI based on the Amazon Linux AMI. Like all such AMIs, it supports the cloud-init system for running startup scripts based on the User Data passed into every instance. In this particular case, my User Data input happens to be an Include file that sources several other startup scripts:

#include
http://s3.amazonaws.com/path/to/script/1
http://s3.amazonaws.com/path/to/script/2

The first time I boot my instance, the cloud-init startup script runs correctly. However, if I do a soft reboot of the instance (by running sudo shutdown -r now, for instance), the instance comes back up without running the startup script the second time around. If I go into the system logs, I can see:

Running cloud-init user-scripts
user-scripts already ran once-per-instance
[  OK  ]

This is not what I want — I can see the utility of having startup scripts that only run once per instance lifetime, but in my case these should run every time the instance starts up, like normal startup scripts.

I realize that one possible solution is to manually have my scripts insert themselves into rc.local after running the first time. This seems burdensome, however, since the cloud-init and rc.d environments are subtly different and I would now have to debug scripts on first launch and all subsequent launches separately.

Does anyone know how I can tell cloud-init to always run my scripts? This certainly sounds like something the designers of cloud-init would have considered.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In 11.10, 12.04 and later, you can achieve this by making the ‘scripts-user’ run ‘always’.
    In /etc/cloud/cloud.cfg you’ll see something like:

    cloud_final_modules:
 - rightscale_userdata
 - scripts-per-once
 - scripts-per-boot
 - scripts-per-instance
 - scripts-user
 - keys-to-console
 - phone-home
 - final-message

    This can be modified after boot, or cloud-config data overriding this stanza can be inserted via user-data. Ie, in user-data you can provide:

    #cloud-config
cloud_final_modules:
 - rightscale_userdata
 - scripts-per-once
 - scripts-per-boot
 - scripts-per-instance
 - [scripts-user, always]
 - keys-to-console
 - phone-home
 - final-message

    That can also be ‘#included’ as you’ve done in your description.
    Unfortunately, right now, you cannot modify the ‘cloud_final_modules’, but only override it. I hope to add the ability to modify config sections at some point.

    There is a bit more information on this in the cloud-config doc at
    https://github.com/canonical/cloud-init/tree/master/doc/examples

    Alternatively, you can put files in /var/lib/cloud/scripts/per-boot , and they’ll be run by the ‘scripts-per-boot’ path.

    • 0