ligoj/plugin-prov-aws

Ligoj plugin for AWS provisioning : fetch prices and Terraform implementation

plugin-prov-aws's Issues

Migrate storage prices to SKU keys

For storage services, there are 2 indexes : code (SKU) and location,type
But the price import use the location,type as primary merge method. Swith to codemethod when this plugin will be upgraded to next major version.

Add secret/access key parameters

Add secret/access key parameters for terraform generation and future API calls

Add China AWS price import

China price API: https://www.amazonaws.cn/en/ec2/pricing/ec2-linux-pricing
No regional endpoint.

Use EC2 and RDS index files to discover regions

Use EC2 and RDS index files to discover regions: "/offers/v1.0/aws/AmazonEC2/current/region_index.json"

Currently, use EBS service as region source.

Manage spot price

There is no way to define the spot price of an instance.

Link between storage and instance lost

When I edit an instance storage (size in my case), the storage is detached from its instance.

Handle broken spot instance price

AWS provides a separated Spot prices reference from the EC2 catalog.
Sometimes, the spot refers to a not yet described EC2 instance.

Support RDS pricing

Add home link to the account

To perform this, we may :

• either add a dependendy to ligoj/plugin-vm-aws, ligoj/plugin-vm-azure, ... And these plugins would maintain the "account" parameter. This allow plugin-prov-x to create dynamically on subscription for each instance to the related plugin-vm-x plugin.
• either add the "account" parameter on this plugin-prov. The good part is the separate life cycle for this plugin, on the other side, there is no relation with the plugin-vm-x plugins. So unable to create dynamically the subscriptions to these plugins. But we could "import" plugin-prov-x instances from the plugin-vm-x.

Add Savings Plan support

Add Savings Plan support. Requires convertible requirement to distinguish "Reserved Instance" (standard+convertible), "EC2 Savings Plan "and "Compute Savings plan"

Use EC2 service instead of S3 to valid accounts

Current S3 API is used to validate the account, but EC2 would be more suitable for Ligoj since S3 is not a mandatory API for the provisioning features.

Support licensing pricing

Filter imported AWS catalog by instance type

In addition to region and OS, add instance type filtering when importing AWS catalog.

Add spot termination frequency in the model

Use data from there: https://aws.amazon.com/ec2/spot/instance-advisor/
The % data would be a risk to associate to #1