You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As #3 has pointed out, the current naming scheme is bad.
We should list US West (Los Angeles) in the us-west-2 region, as API endpoints are there.
Maybe the best solution for this would be to rename spot-az to availability-zone and handle the rest.
We should find mappings for other parameters, like the output of aws ec2 describe-availability-zones --all-availability-zones
gives:
Other problems related to this include describe_spot_price_history doesn't seem to return spot prices for not-opted-in zones, so currently in order to fetch pricing data for them, we should opt-in for all, which may have other consequences.
Maybe we should use https://website.spot.ec2.aws.a2z.com/spotblocks-generic.js for fetching all prices, instead of relying on the API.
The text was updated successfully, but these errors were encountered:
As #3 has pointed out, the current naming scheme is bad.
We should list
US West (Los Angeles)
in theus-west-2
region, as API endpoints are there.Maybe the best solution for this would be to rename
spot-az
toavailability-zone
and handle the rest.We should find mappings for other parameters, like the output of
aws ec2 describe-availability-zones --all-availability-zones
gives:
Other problems related to this include
describe_spot_price_history
doesn't seem to return spot prices fornot-opted-in
zones, so currently in order to fetch pricing data for them, we should opt-in for all, which may have other consequences.Maybe we should use https://website.spot.ec2.aws.a2z.com/spotblocks-generic.js for fetching all prices, instead of relying on the API.
The text was updated successfully, but these errors were encountered: