- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello,
I'd like to suggest to first make sure you upgrade all AWS PV Drivers, ENA and/or NVMe and upgrade to Ec2Launch v2 (1), then perform sysprep (2) to create a new reusable AMI. Drivers would help so that the new Instance is compatible with any Instance type, while sysprep will remove unique identifiers so the AMI can be deployed anywhere.
Keep in mind that sysprep would disjoin the Instance if it is part of any domain, so you will be required to have local credentials to log back in and join it back to the Domain.
I hope this helps. Good luck!
References (1) Migrate to latest generation instance types - https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/migrating-latest-types.html (2) How can I use Sysprep to create and install custom reusable Windows AMIs in Amazon EC2? - https://aws.amazon.com/premiumsupport/knowledge-center/sysprep-create-install-ec2-windows-amis/
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
Accepted this answer. The reason was the static IP address on Network Interface. Configuring it to get IP address from DHCP fixed the issue.