Just doing some test in AWS Tokyo DC. To my surprise, it took unusually long time for the instance status being ready. It may be issues on AWS side, but it also triggered issue in the module.
An error occurred (IncorrectState) when calling the AttachVolume operation: Instance 'i-006add0eb74fbe0a2' is not 'running'.
Just doing some test in AWS Tokyo DC. To my surprise, it took unusually long time for the instance status being ready. It may be issues on AWS side, but it also triggered issue in the module.
EBS attaching failed due to above error.