1 回答
- 最新
- 投票最多
- 评论最多
0
The most likely cause here is that the network drivers (that were automatically installed and enabled for the T3 instance) are not compatible with T2 instances.
You haven't mentioned what operating system you're using so the brute force approach would be:
- Spin up a T2 instance
- Find out what drivers are being used
- Enable (or install and then enable) those drivers on the T3 instance
- Take the snapshot
相关内容
AWS 官方已更新 1 年前- AWS 官方已更新 2 年前
I'm using Amazon Linux 2
You might also try the EC2 Serial Consle to connect to the T2 instance and enable the correct network drivers.