Closed pjr closed 1 year ago
Hi @pjr,
Yeah, unfortunately this is a limitation of the data set we are using for aws-pricing. We pull from the pricing page data, which can tend to remove the instance classes they've deemed legacy pretty quickly. We don't use the pricing API data because the file size (121MB for RDS above) would take too long to load and parse in the time we need.
Something I've wanted to do is take the pricing API data, break it into smaller categories (eg: region, pricing type, instance class) and upload those as separate JSON files that this addon could then use. However, I haven't been able to find the time to complete that as a project.
I'm going to leave this issue open at the moment so that others, looking for the same, can find this.
Cheers,
Mike
@john-macroscope Do we know if this has been corrected with the refreshed data?
@aryounce I think so, the formula with this instance works for reserved and ondemand, for different regions: =AWS_RDS("aurora/mysql", "db.r4.4xlarge", "us-east-1", "reserved", "3yr", "partial_upfront") =AWS_RDS("aurora/mysql", "db.r4.4xlarge", "us-east-2", "ondemand")
@pjr We believe this has been addressed. Please try the new version of the add-on and let us know if you encounter any problems.
I'm afraid I'm not close to this anymore to test although I appreciate the work on it! Sorry I can't help confirm
It looks like even through the db.r4.* instances are available via the Pricing API that these are not available via this plugin.
db.r5.* all seem to be available.
not sure if this is a limitation or a bug?