Need to reduce this cost $0.005 per In-use public IPv4 address per hour
I have created a Wordpress Website on AWS with EC2 instance and there is a load balancer as well which is not connected to the IPv4 of the EC2 instance , but connected to some other IPv4 addresses, shall i delete the IPv4 addresses which are not connected to the EC2 instance but connected to the load balancer and if so then how can i connect the EC2 instance's IPv4 address to the load balancer and make sure the website is running smoothly
I am using bitnami-wordpress-linux-debian-hvm-ebs-nami for wordpress website
These are the resources being used
I am being charged for these "$0.005 per In-use public IPv4 address per hour"
How shall I reduce the cost to fit in the free tier
This the screenshot of the charges being incurred
- Newest
- Most votes
- Most comments
Now it does not matter if your public IP address is used or not
Hourly charge for In-use Public IPv4 Address $0.005
Hourly charge for Idle Public IPv4 Address $0.005
the cheapest option for you would be creating an "Internet facing" Load Balancer and direct traffic from it to Private EC2 instances (which don't have public IPs)
Relevant content
- asked 5 years ago
- Accepted Answerasked a year ago
AWS OFFICIALUpdated 3 years ago- AWS OFFICIALUpdated 2 years ago
- How can I troubleshoot issues when I use the AWS Load Balancer Controller to create a load balancer?AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
Just a note, load-balancer free-tier is 750 hours a month, for 12 months. After free tier the load balancer will be much more expensive than the IPv4. Also you will pay for the Public IPs associated with the load-balancer anyway, so this will not actually reduce costs.