AWS Cloud
Browse community images, manage private AMIs, and deploy EC2 instances
AWS credentials not configured
Make sure AWS CLI is configured: aws configure
Community Images
Free-tier-compatible public AMIs from Amazon, Canonical, and Debian. Copy one to your account to use it as a private AMI.
| OS | Name | AMI ID | Arch | Size | Created | Actions |
|---|---|---|---|---|---|---|
| ✓ |
Private AMIs
AMIs owned by your AWS account, including any copied from community images.
| AMI Name | AMI ID | State | Arch | Size | Created | Actions | |
|---|---|---|---|---|---|---|---|
| ⚠ No ENA ✓ ENA |
Deployed EC2 Instances
| Status | Name | Instance ID | Type | Public IP | Private IP | Launched | Actions |
|---|---|---|---|---|---|---|---|
Copy to Private AMI
SSH Key
Key pair:
Key not found
Store the .pem contents in Secrets Manager with the name shown above, then try again.
Replace <key-file> with the path to your saved .pem file,
and adjust the username for your AMI (e.g. ubuntu,
ec2-user, admin).
Save Instance as Image
·
Deploy AMI
⚠ This AMI does not have ENA enabled
The selected instance type ()
requires Enhanced Networking (ENA). This deployment will fail unless you first click
Enable ENA (creates a new -ena copy of the AMI), or select a t2.* instance type instead.
Bulk Deploy AMIs
deployments queued successfully!
Each instance is deploying in the background. Track each job below.
Edit the name for each instance before launching.
Key retrieved:
No security groups found.
Select at least one security group.