title: Why does the newly created EC2 instance does not send resource signal to AWS Cloud Formation after I replace the AMI?
body: <p>I have a WordPress AWS Cloud formation stack that runs some custom scripts and module on server side. The current Cloud formation template attached AMI does not have those custom scripts and modules in it. So I was replacing the CFN AMI with my newly created AMI with same configuration only additional scripts and modules installed in it.</p>
  
  <p>What is happening is once I change the old AMI Id with my new AMI ID and update the stack the instance is getting created but the newly created instance is it not sending the resource signal to CFN and AWS CFN is rolling it back to old AMI. How do I fix this issue ?</p>