1 Answer
- Newest
- Most votes
- Most comments
1
Hi cvasilak. Thanks for reporting this issue. It appears that the nested Ignition stack is trying to launch an AMI that has been recently deprecated. I'll post a comment here when it's fixed or when more is known. Apologies for the inconvenience.
Relevant content
- asked 10 months ago
- Accepted Answerasked 7 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 22 days ago
The workshop owners have fixed it immediately. Please retry and let us know how you go.
Hello @Greg_B, works great now 👍 thank you for the prompt reply.