AWS announces AWS Interconnect – multicloud (preview), providing simple, resilient, high-speed private connections to other cloud service providers. AWS Interconnect - multicloud is easy to configure and provides high-speed, resilient connectivity with dedicated bandwidth, enabling customers to interconnect AWS networking services such as AWS Transit Gateway, AWS Cloud WAN, and Amazon VPC to other cloud service providers with ease.
Getting Charges even though not having any instance running , My free tier is not even 50% used and month is just yet started
i created my aws account recently and i have created one instance + 1 load balancer + 1 s3 bucket with a video stored in it and started uploading my applications backend code to that instance , as you know that all these comes under free tier but i started getting a bill of 0.10 dollar , i paid it and tried to figure out whats the problem then i started again from 1st february and created one more instance but started getting charged for ec2 T3 vCPU credits and vpc ipvc4 address from just starting of february and then i though it might be because of the new instance that i created so i stopped the new one but kept the older one running (backend) one but when i opened billing next day i found i am still getting charged and my bill was increased for that single instance which wasnt even yet "correctly" setted but it was deployed from mobxterm pm2 and was having my code running with some minor errors , still these are under free tier and i havent even used 50% of any of my free tier service yet . Then when i didnt get the answer from anywhere i decided to delete everything (instance , load balancer ,target group , security group etc) and i killed my hardwork😖😖 and planned to restart by next day but as soon as i was about to start doing evrything i thought of checking my bill one more time and guess what , i was still getting heavily charged for T3 vCPU credits 😣my confidence is literally broken please help me i need your help to complete my dream , i beg you
- Newest
- Most votes
- Most comments
I understand your frustration with unexpected charges on your AWS account, especially when you believe you're operating within the Free Tier limits. Let me explain some possible reasons for these charges and provide some suggestions:
-
T3 vCPU Credits: Even if you're within the Free Tier, T3 instances can incur charges if they use more CPU credits than allocated. This can happen if your application is CPU-intensive or if there's a misconfiguration causing high CPU usage.
-
VPC IPv4 Addresses: AWS now charges for public IPv4 addresses, even within the Free Tier. If your instances or other resources are using public IPs, you may see these charges.
-
Elastic Load Balancer: Load balancers are not fully covered by the Free Tier and can incur charges.
-
S3 Storage: While S3 has some Free Tier allowance, storing large files (like videos) might exceed this limit.
To address these issues:
-
Review your EC2 instance types and ensure they align with Free Tier offerings (t2.micro or t3.micro in some regions).
-
Monitor your CPU credit usage and consider optimizing your application if it's consuming too many credits.
-
Use private IPs where possible to avoid charges for public IPv4 addresses.
-
Be cautious with services not fully covered by Free Tier, like load balancers.
-
Set up billing alerts to notify you when you're approaching Free Tier limits.
-
Regularly check the AWS Billing dashboard to understand your usage and charges.
-
If you believe there's an error, contact AWS Support for clarification.
Remember, even if you delete resources, there might be some residual charges for the time they were active. Don't be discouraged – managing cloud resources efficiently is a learning process. With careful monitoring and optimization, you can minimize costs while building your project.
Sources
Why have I been billed without running any instances? | AWS re:Post
Billing without active service | AWS re:Post
iam not using vpc | AWS re:Post
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 7 months ago
