1 個回答
- 最新
- 最多得票
- 最多評論
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.
相關內容
- AWS 官方已更新 3 年前
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.