Features
- Auto-Scaling
- CloudWatch Monitoring
- Free-Tier
- Marketplace for Amazon Machine Images and Services
Free Tier
Micro instances are eligible for the AWS free usage tier. For the first 12 months following your AWS sign-up date, you get up to 750 hours of micro instances each month. When your free usage tier expires or if your usage exceeds the free tier restrictions, you pay standard, pay-as-you-go service rates.
Learn more about free usage tier eligibility and restrictions.
The free tier has the following monthly limits:
- Up to 750 compute hours
- Up to 30GB of General Purpose SSD volume storage
- Up to 5GB of S3 storage
- Up to 750 hours of Amazon RDS database usage
- 1M requests to Amazon Lambda
- 1GB of SPICE capacity on Amazon QuickSight
Manual Instance Deployment
Steps should seem fairly familiar:
- Sign into AWS Console, and choose Services → Compute → EC2
- Choose Instances on the left side
- Click "Launch instance"
- On the left, choose Marketplace
- Search for, and select, CoreOS
- Choose t2.micro (free) for your instance size
- Configure instance details (networking / monitoring/ auto-scaling / protection from accidental termination / etc)
- Configure tags (completely optional and arbitrary)
- Configure security groups (you'll likely want to add at the very least SSH / HTTP / HTTPS)
- Review and click "Launch" and you'll be prompted to assign or create a key pair for this instance
I was then able to SSH in and clone ndslabs-startup to try to run our cluster - startup went fairly smoothly (aside from my free instance being entirely too small).
I needed to assign a DNS rule pointing www.awsdev.ndslabs.org to this instance
Now, I am running into the same issues as my VirtualBox VM:
503 5.0.0 Need RCPT (recipient)
Gotchas
- Restarting an instance assigns it a new public IP (probably unless we pay more for a static IP)
Deploying via kube-aws (CoreOS-only)
Deploying via Kargo