costs

All of this is on the Amazon pricing site, but it's a pain to scroll through every time. for now, I'm going to summarize here:

Elastic IP (required for Eureka and maybe WXS catalog server):

• .00 for one Elastic IP address associated with a running instance
• .005 per additional Elastic IP address associated with a running instance per hour on a pro rata basis
• .005 per Elastic IP address not associated with a running instance per hour on a pro rata basis
• .00 per Elastic IP address remap for the first 100 remaps per month
• .10 per Elastic IP address remap for additional remaps over 100 per month
• Summary - $0.00 for one as long as it's being used, $0.005 for each additional with 100 changes to it per month (with $.10 per change over 100)
• Likely cost for our investigation 6 (three AZ across 2 regions) * 0.005 * 24 * 30 = $3.60 / month

EC2 instances

• m1.large running "linux" (Amazon Linux) - $176/month (running 24/7), $41/month (running 40 hours/week)
• 2 vcore, 4.0 ECU, 7.5G RAM
• c1.medium running "linux" (Amazon Linux) - $106/month (running 24/7), $25/month (running 40 hours/week)
• 2 vcore, 5.0 ECU, 1.7G RAM
• m1.medium running "linux" (Amazon Linux) - $88/month (running 24/7), $21/month (running 40 hours/week)
• 1 vcore, 2.0 ECU, 3.7G RAM
• m1.small running "linux" (Amazon Linux) - $44/month (running 24/7), $10/month (running 40 hours/week)
• 1 vcore, 1.0 ECU, 1.6G RAM
• m1.micro running "linux" (Amazon Linux) - $15/month (running 24/7), $4/month (running 40 hours/week)
• 1 vcore, up to 2.0 ECU, 0.6G RAM

Cloudwatch (??)

• 3.50 per instance per month, provided at 1-minute frequency
• 0.00 per instance per month, provided at 5-minute frequency

ELB

• $0.025 per Elastic Load Balancer-hour (or partial hour) - ($18/month)
• $0.008 per GB of data processed by an Elastic Load Balancer

Data Transfer (??)

• Lots of pricing structures, but tends to only cost for data transfer IN/OUT an Elastic IP (shouldn't have much of this - this would just be directly viewing Eureka console until we can learn how to VPN to it), or cross availability zones (this should be minimal and only in cases of HA failure kicking in). There is data transfer out to the internet (this should be cases where we are ssh'ing into instances). The cost of the data out via standard use should be the cost of the ELB transfer.

VPC

• Should consider eventually

Amazon Route 53

• Only when we get to region level testing

Other instances that are not ours

• 19 c1.mediums (19*$106 = $2014)
• 15 m1.larges (15*$176 = $2640)
• 1 t1.micro ($15)