This message was deleted.
# contributors
b
This message was deleted.
👀 1
w
I added my thoughts here, and vented on twitter here 😂
c
I was finding the same thing but I wasn’t sure if the problem was AWS, the pricing service, or an out of date mongo db dump. It would be interesting to see what charge (if any) AWS puts in the HCUR for cpu credits in other regions, but I guess there’s slim chance that we know anybody who would have that 🤷‍♂️
w
tru dat, would be great if we could trace a price record in mongo to the AWS pricing API so we can rule out issues in the pricing service
l
Copy code
curl <https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonNeptune/current/index.json> 2>/dev/null | grep "CPU Credits" -B 5 -A 3
Only shows Hong Kong and Sao Paulo
🙌 1
p
If CPU cost only exist for Hong Kong or Sao Paulo. How can I test this resource , if other cost components are missing in those regions?
w
maybe just hard-code the usagetype=
APE1-CPUCredits:db.t3
price for all regions for that CPU credits cost-component. The other cost components should be ok but you can check them if you like