Skip to content
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.

cfn-signal is not sent in time or at all after beinstances are created #26

Open
gregcsh opened this issue Feb 12, 2023 · 1 comment
Open

Comments

@gregcsh
Copy link

gregcsh commented Feb 12, 2023

The beinstances are not sending the success signal or the timeout is too low. I checked the code in the BEStack and it was set to 10M which I increased to 30M and it still timed out. I can see the instance in EC2 console and all seems to be ok. Not sure why the stack is not getting the success signal. I have tried both templates, the new VPC and my own and get the same error.

@ss892714028
Copy link

ss892714028 commented Feb 13, 2023

@gregcsh Thank you for submitting the issue. To fix this, we have submitted PR #25 , which is currently under review.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants