- Newest
- Most votes
- Most comments
Hello! Even though we won't begin charging for all public IPv4 addresses until next February, we started providing usage data in the CUR shortly after the announcement. If you haven't already noticed an increase in storage related to public IP usage then I wouldn't expect that to change once the new pricing model takes effect. I don't have easy access to a CUR with daily granularity, but I don't see why AWS would treat this usage differently than anything else. The identity_time_interval
field should help you confirm this. If you are set up to query your CUR with Athena [1] you could run the following query for a quick confirmation:
select * from customer_all where line_item_usage_type like '%-PublicIPv4:IdleAddress' limit 10;
Hope this helps.
[1] https://docs.aws.amazon.com/cur/latest/userguide/cur-query-athena.html
did you check what you have on the "pricing_unit" column? This usually answer the question.
Relevant content
- asked 5 months ago
- asked 8 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
Oh, I already received it as part of the cur!
After referring to the query you posted, I found that the description of public IP usage in daily cur data is expressed as
$0.005 per In-use public IPv4 address per hour
, but the lineItem/usageAmount value is set to24
.In the end, in daily cur data, if a specific instance uses a public IP all day, only 1 row will be added.
thank you have a good day :)