Presented at the AWS Washington DC User Group and updated for September 25 While AWS is very affordable, it can get really costly for the average at-home user. The free tier is a great way to get started but how do you use AWS long-term while keeping costs low? Michael Soh, unashamed cheap skate and the unofficial chief innovation engineer at the Inova Translational Medicine Institute, shares his journey into AWS and how the average user can get the most out of their dollars. This work is released via the CC-BY-SA license.

1. A Cheapskate’s Guide to AWS
Michael Soh

2. Definition of a Cheapskate
● Flexible: Quality and Time
● Constraint: Cost
● Take advantage of free or low-cost platforms
● Use services outside of their intended purpose (e.g. use GitHub to serve web
pages)
Do as much as possible as cheaply as possible, regardless of time and quality.

3. What is NOT a Cheapskate
● Gaming the system
● Taking advantage of unsuspecting organizations or individuals
○ Cryptomining on unsuspecting visitors to your website
○ Vulnerability-based or other grey-web applications (e.g. unpublished APIs, shared API keys, etc)
● Violating TOS or Acceptable Use Guidelines

4. An Ethical Cheapskate’s Guide to AWS
Michael Soh

5. AWS Free Tier
● Many AWS Services are available for free either for a limited time or forever but
under certain thresholds
○ https://aws.amazon.com/free
● Understand what is free now and won’t be later
○ After one year, EC2, S3, RDS, EBS, Networking are no longer free, but very inexpensive
○ Lambda, DynamoDB, CodeCommit are free in perpetuity, with some limitations
● Learn where to save money
○ Reserved Instances if you want a VPS-like experience (or just use Lightsail)
○ Remove unnecessary items from S3
○ If you’re feeling lucky (and particularly cheap):
■ Move your DB to the same EC2 instance as your web server
■ Containerize your web server through self-managed Docker

6. mikesoh.com -- Use Case
● Grew up from a cPanel-based LAMP stack to fully-managed AWS LAMP stack
(with plans to make it DevOps-y in the near future -- check my Github repo for
details)
● Primarily used to host hundreds of email addresses used for spam avoidance and
detection
● VERY few public visitors
● Bandwidth concerns minimal
● Goal: $20 / month

7. Let’s Focus on After 1-Year on AWS
All Prices are as of September 2018, based on us-east-1 (Northern Virginia)
In General:
● Compute tends to be the cost you need to control. Storage is often a drop in the
bucket
Service Cost / 30-day Month
EC2 (t2.micro) On-Demand $7.488 (was $8.352 in May 2018)
EC2 (t2.micro) Reserved (1 year) $4.4167 (was $4.9167 in May 2018)
Equivalent Lightsail (incl. 40 GB SSD) $5

8. Other Ways to Reduce Cost
● GitHub for overall code-repository
○ EC2 deployment code
○ VPC Configuration
● Bitbucket/CodeCommit for anything sensitive that must be version-controlled
○ Website Configuration
○ Email Configuration
● S3 for backups and other sensitive information
○ Pull-only/Deployment SSH keys
○ Database Backups, etc.
● Use Spot Instances when testing new configurations
○ 8-hour t2.micro is usually $0.028 (subject to fluctuations)
● Cloudflare for free domain resolution
○ Route 53 is pretty cheap ($0.50 / zone, $0.40 / 1M queries) but...
○ Cloudflare is free and offers DDOS mitigation out of the box

9. Things can go bad if you’re not careful
● Single-point of failure
○ DevOps, DevOps, DevOps
● Personal Solutions are rarely “Enterprise Solutions”
○ Hosting email on the same system as your web server may work for me personally, but would never
do this in a production, enterprise environment
● Walled-Garden
○ Too Much Dependence on AWS
● Single-Source-of-Truth can be difficult if not managed correctly
○ “Where did I put the ssh keys? Are they in the same place as the ssh configuration?”
● Know your risks!

10. $15
My Monthly AWS Bill

11. Questions?
Comments?
michael.c.soh@gmail.com
sohmc
sohmc
Link to SlideShare: