ℹ️ Information: Custom AMIs allow you to quickly deploy pre-configured instances with your specific software, configurations, and data. This significantly reduces deployment time and ensures consistency across your environment.
In the EC2 console:
Provide a descriptive name for your instance:
Windows Server AMI
in the Name fieldVerify the AMI selection:
Configure instance specifications:
In the Create key pair dialog:
kp-windows2
🔒 Security Note: Store your key pair file (.pem) in a secure location. This file is required to decrypt the administrator password for your Windows instance and cannot be recovered if lost.
Under Network settings, click Edit and configure:
💡 Pro Tip: Using existing security groups ensures consistent network access controls across similar instances. Review the security group rules to confirm they match your requirements before proceeding.
Review all configuration settings:
After successful creation:
Wait for instance initialization:
Once the instance is running:
ℹ️ Information: The custom AMI you created includes the Sysprep configuration from lab 3.2, which ensures a clean Windows environment. This eliminates warning messages typically seen when retrieving the administrator password for a new instance.
⚠️ Warning: When connecting to Windows instances, always use the RDP protocol over secure networks or VPN connections. Consider implementing additional security measures such as just-in-time access or session recording for production environments.