ec2_instance: Support throughtput parameter for GP3 volume types as part of volumes parameter

[gtie]

SUMMARY

Support throughtput parameter for GP3 volume types as part of the ec2.volumes parameter

ISSUE TYPE

• Feature Idea

COMPONENT NAME

ec2.py

ADDITIONAL INFORMATION

While GP3 EBS volumes can be created together with an EC2 instance using the ec2 module, the feature of setting a custom throughput parameter is still missing. This leads to very ugly workarounds.

Ideally, we should be able to specify it directly as in:

- amazon.aws.ec2:
    key_name: mykey
    group: webserver
    instance_type: c3.medium
    image: ami-123456
    wait: yes
    wait_timeout: 500
    volumes:
      - device_name: /dev/xvda
        volume_type: gp3
        volume_size: 8
        throughput: 250

This type of definition is already supported by the ec2_vol module, but it's not yet present in ec2

[ansibullbot]

Files identified in the description:

• [plugins/modules/ec2.py](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/ec2.py)

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @jillr @lwade @s-hertel @tgerla @tremble @wimnat
click here for bot help

[tremble]

Hi @gtie,

While we haven't officially started the deprecation process for the ec2 module, it's based upon the 'old' Amazon SDK (boto) rather than the 'new' SDK (boto3/botocore) and can generally be considered deprecated. The boto module doesn't support most modern features (including various regions and things like GP3 throughput) and as such support will not be added to the ec2 module for the throughput option.

The ec2_instance module largely replaces this functionality and I would recommend you migrate if possible. (ec2_instance doesn't support throughput yet either, however support would be possible)

As a work around support for throughput has been added to the most recent versions of the ec2_vol module.

[gtie]

The ec2_vol support is not enough unfortunately - it wouldn't update an existing EBS module (at least in Ansible 2.10). @tremble , shall we repurpose this issue for the ec2_instance update?

[tremble]

I believe you need either Ansible 3.4.0 or to explicitly install amazon.aws 1.5.0 and community.aws 1.5.0 for the version of ec2_vol which supports updating the throughput option:

https://docs.ansible.com/ansible/latest/collections/amazon/aws/ec2_vol_module.html#parameter-throughput

re repurposing: yes.