AWS Usage report

[anmolsingh0219]

To create an AWS Usage report and how where the costs are divided

[anmolsingh0219]

List of services used

• Virtual Private Cloud (VPC)
• Elastic Compute Cloud (EC2)
• Elastic Load Balancing (ELB)
• Route 53
• AWS Certificate Manager (ACM)

Major Costs Incurred

VPC Cost
Our primary cost comes from public IPv4 addresses within our VPC. We have 750 hrs of free VPC usage which we exceed every month.

This usage comes from the public IPv4 addresses which are in use and cost $0.005 per hour.

Load Balancer in Multiple Availability Zones

• Load Balancer and IP Usage: Our load balancer is deployed across three availability zones (ap-south-1a, ap-south-1b, ap-south-1c). When a load balancer is set up across multiple availability zones, AWS assigns a public IP for each availability zone.

• Calculation: If our load balancer is active for the full month and is using three public IPs (one in each availability zone), the hours will accumulate as:

  • 1 IP x 750 hours/month = 750 hours (for 1 zone)
  • 3 IPs x 750 hours = 2,250 hours (for 3 zones)

Why the High VPC Hours

• The high usage hours for our VPC (over 2,500 hours) are likely because the load balancer’s public IP addresses are being counted separately for each availability zone. Since we have 3 availability zones enabled, the total hours are the sum of the hours for each zone.

Ec2 Instance Type

• The EC2 instance type shown in the image is t2.micro. This is a low-cost instance type that is part of the AWS Free Tier for 750 hours per month for the first 12 months. It's suitable for low-traffic applications, testing, and development environments.

[bprashanth]

3 AZ in APAC is probably not required

1. Unless there are 3 vms
2. OR we want to terminate TLS closer to the user and save a few milliseconds in performance

Neither of which I believe really apply, so maybe we can start off with just 1AZ.

ap-south-2 Asia Pacific (Hyderabad)
ap-south-1 Asia Pacific (Mumbai)

The vm is in ap-south-1. When we need higher availability we can distribute both vms and lbs across regions. For now we can stick to ap-south-1 (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html)

There might be ways to get away without even needing an ELB (static ips on vms?) but lets start with bringing down the number of ips behind this elb.