I have 2 EC2 instances created, 1. t3a.micro 2. t3a.medium The 2nd instance is switched on/off by an API daily running on t3a.micro instance. I see unexpected 4.5$ charge with VPC as service. So I dive into the cost explorer and with "API Operation" as dimension I see 2 entries * AssociateAddressVPC - $ 2.82 * AllocateAddressVPC - $ 1.69 Under "Usage type" dimension I see * APS3-PublicIPv4:InUseAddress - $ 2.82 * APS3-PublicIPv4:IdleAddress - $ 1.69 I am using elastic IPs for both instances. But I don't remember it being this expensive!

Unexpected VPC charges on my monthly bill

I have 2 EC2 instances created,

t3a.micro
t3a.medium

The 2nd instance is switched on/off by an API daily running on t3a.micro instance. I see unexpected 4.5$ charge with VPC as service. So I dive into the cost explorer and with "API Operation" as dimension I see 2 entries

AssociateAddressVPC - $ 2.82
AllocateAddressVPC - $ 1.69 Under "Usage type" dimension I see
APS3-PublicIPv4:InUseAddress - $ 2.82
APS3-PublicIPv4:IdleAddress - $ 1.69 I am using elastic IPs for both instances. But I don't remember it being this expensive!

トピック

ネットワークとコンテンツ配信計算するクラウド財務管理

タグ

Amazon VPC Amazon EC2 AWS Billing

言語

English

質問済み 2ヶ月前385ビュー

1回答

新しい順
投票が多い順
コメントが多い順

Hello.

AWS started charging for public IPv4 in February.
Public IPv4 addresses are charged at $0.005 per hour.
It is unknown how long your EC2 has been in use, but if you owned ElasitcIP during February, it would not be strange for the fee to be around that amount.
https://aws.amazon.com/jp/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
https://aws.amazon.com/vpc/pricing/?nc1=h_ls

エキスパート

Riku_Kobayashi

回答済み 2ヶ月前

エキスパート

Kallu

レビュー済み 2ヶ月前

Unexpected VPC charges on my monthly bill

関連するコンテンツ