- Newest
- Most votes
- Most comments
Hello, so this is by design when you build an Image via EC2 Image Builder as part of the final build steps AWS EC2 Image Builder runs Microsoft Sysprep this is done to generalize your image so that it can be deployed as a golden image for multiple EC2 Instances. Part of the Sysprep process by default for EC2Launch V2 which is used by Windows Server 2022 will reset the Administrator password to use the EC2 key pair that is assigned when launching a new image using the outputted AMI by EC2 Image Builder. If you are providing a custom AMI and then using the component update-windows this will run Microsoft updates but as part of the build workflow there is a step "RunSysPrepScript" that is executing sysprep that will reset the Administrator password.
To be able to connect to your Instances that are launched from the AMI that was created by Image Builder assign a key pair when creating the instance and use that to decrypt the Administrator password to login. As per this documentation. For some additional information regarding sysprep for image builder refer to this documentation and in general for creating customizable sysprep images refer to these articles
https://repost.aws/knowledge-center/sysprep-create-install-ec2-windows-amis https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/Creating_EBSbacked_WinAMI.html#ami-create-standard
What happens if I do something like get the initial password for Windows?
https://repost.aws/knowledge-center/retrieve-windows-admin-password
Relevant content
- asked 2 years ago
- asked 23 days ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 6 months ago
When you say the Administrator password looks correct, are you able to RDP into the other instance with the attached volume that is using the new AMI? Is there a specific error you are getting when you attempt to RDP into the instance using the new AMI? (i.e. The Username or Password is Incorrect.)