
ℹ️ Information: A custom Amazon Machine Image (AMI) allows you to capture the configuration, software, and data of an EC2 instance, enabling you to launch identical instances quickly. This is essential for maintaining consistency across your infrastructure and accelerating deployment processes.
Sign in to the AWS Management Console

Verify the instance has completely stopped:

⚠️ Warning: For Windows instances, it’s recommended to stop the instance completely before creating an AMI to ensure that the Sysprep function (configured in lab 3.2) is fully processed. This ensures your AMI will have proper Sysprep configuration information.
With the instance selected:

In the Create image dialog:
Custom Windows AMICustom Windows AMI
💡 Pro Tip: Uncheck Reboot instance option prevents AWS from rebooting your instance during AMI creation. This is useful when you want to avoid downtime or prevent changes to the instance’s public IP address (for instances in public subnets without Elastic IPs). However, disabling reboot means means AWS cannot guarantee file system integrity in the created image.
Complete the AMI creation:

Navigate to the AMIs section:
Monitor the AMI creation process:

🔒 Security Note: Custom AMIs contain all data from the source instance. Ensure you’ve removed any sensitive information, credentials, or personal data before creating an AMI that might be shared with others or used across multiple environments.