20

After cloud-init runs a user data script on the first boot of an EC2 instance, a state file is presumably written so that cloud-init won't run the script again on subsequent reboots. There are cases where I'd like to delete this state file so that the user data script will run again. Where is it?

|improve this question
25

rm /var/lib/cloud/instances/*/sem/config_scripts_user

Confirmed working on:

  • CentOS 7.4
  • Ubuntu 14.04
  • Ubuntu 16.04

For the sake of completeness, if you have a situation where you care to keep track of the fact/possibility that this AMI [had a parent AMI that ...] and they all ran cloud-init user data, you can delete only the current semaphore.

rm /var/lib/cloud/instance/sem/config_scripts_user

|improve this answer
  • 2
    You figured that out quickly. – c24w Jun 1 '17 at 9:19
  • 9
    @c24w Those timestamps are misleading. It actually took me a few hours of research and testing, so once I figured it out, I created this question to help the next person looking for a definitive answer. – Mike Conigliaro Jun 1 '17 at 17:21
  • 1
    I've come across this since and didn't realise it was encouraged to post wiki-type Q&As. Appreciate you documenting this! – c24w Jun 8 '17 at 20:11
  • 1
    I'm glad this was encouraged on serverfault. I've seen it downvoted many times on SO – Nathan Apr 11 '18 at 16:51
  • 1
    @flag5 That curl to the metadata service to get the current instance id is unnecessary because /var/lib/cloud/instance is already a symlink to the current instance under /var/lib/cloud/instances. :-) – Mike Conigliaro Aug 13 '18 at 22:21
2

You can put your script in /etc/rc.local, which will run the script on every reboot.

|improve this answer
  • /etc/rc.local has nothing to do with EC2 user data. – Mike Conigliaro May 1 '17 at 20:07
  • @MikeConigliaro I wanted to use user-data to make something run on every boot, so I made the user-data script append it to /etc/rc.local. – user253751 Oct 1 '17 at 2:37
0

You can also configure your user data to re-run on every boot, instead of removing the state file. You have to use cloud_final_modules in your userdata script to re-run the userdata script and for that you have to customise uderdata to have miultiple files in userdata. Example userdata file would be like:

Content-Type: multipart/mixed; boundary="//"
MIME-Version: 1.0

--//
Content-Type: text/cloud-config; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="cloud-config.txt"

#cloud-config
cloud_final_modules:
- [scripts-user, always]

--//
Content-Type: text/x-shellscript; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="userdata.txt"

#!/bin/bash
/bin/echo "Hello World" >> /tmp/userdata-test.txt
--//

This will make userdata script to execute on last step of every boot process. Here only a single line bin/echo "Hello World" >> /tmp/userdata-test.txt to be executed, replace this with your shell script that needs to be executed every time a machine is booted.

|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.