Group: EBS I/O Requests, EBS IOPS, EC2-Dedicated Usage, ELB:Balancer, ELB:Balancing, ElasticIP:AdditionalAddress, ElasticIP:Address, ElasticIP:Remap, NGW:NatGateway NetworkPerformance: 10 Gigabit, 20 Gigabit, 25 Gigabit, High, Low to Moderate, Low, Moderate, NA, Up to 10 Gigabit, Very Low OperatingSystem: Linux, NA, RHEL, SUSE, WindowsĬlockSpeed: 2 GHz, 2.3 GHz, 2.4 GHz, 2.4 GHz, 2.5 GHz, 2.6 GHz, 2.8 GHz, 2.9 GHz, 3.0 Ghz, Up to 3.0 GHz, Up to 3.3 GHz InstanceFamily: Compute optimized, GPU instance, General purpose, Memory optimized, Micro instances, Storage optimized VolumeType: Cold HDD, General Purpose, Magnetic, Provisioned IOPS, Throughput Optimized HDD Here are the range of Amazon EC2 filtering attributes and values that you can call. So, the filter function call will be as below You can basically do full range of filtering based on the EC2 Attributes and values in order to nail down that is the instance price.įor example, I have an Linux instance located at US East (N. From the set of API libraries that you could call from boto3.client('pricing'). One of the most important blog that published recently from Amazon about the same objective. Recently, boto3 is allowing the developers to query is the json pricing objects online without downloading the json files. Here is a link describing how you could achieve the purpose. This index.json will eventually guide you to download another set of index.json files as per service Code, for example: AmazonEC2. AWS pricing seem to be difficult to find out, because aws yields out a list of json files for user to parse on prices( ).
0 Comments
Leave a Reply. |