aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
AWS::EC2::Instance::BlockDeviceMapping::EBS should support throughput
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::EC2::Instance
### Resource name
AWS::EC2::Instance::BlockDeviceMapping::EBS
### Description
### 1. Title
AWS::EC2::Instance::BlockDeviceMapping::EBS should support throughput
### 2. Scope of request
AWS::EC2::Volume now supports the Throughput parameter for gp3. AWS::EC2::LaunchTemplate::LaunchTemplateData::BlockDeviceMapping::EBS also supports the Throughput parameter for gp3.
However, we cannot set the Throughput patameter in AWS::EC2::Instance::BlockDeviceMapping::EBS. CloudFormation needs support for this.
### 3. Expected behavior
In Create, it should allow us to set the Throughput parameter on AWS::EC2::Instance::BlockDeviceMapping::EBS .
### 4. Suggest specific test cases
When launching a new instance, we want to be able to configure the root volume to have the maximum possible throughput.
### 5. Helpful Links to speed up research and evaluation
LauncTemplate Throughput Support: https://docs.aws.amazon.com/en_us/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-blockdevicemapping-ebs.html
EC2 Volume Throughput Support: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-ebs-volume.html
EC2 Instance Throughput Support missing: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-blockdev-template.html
### Other Details
_No response_
Contributor guide
Research direction
Start by comparing the linked AWS::EC2::Volume and AWS::EC2::LaunchTemplate::LaunchTemplateData::BlockDeviceMapping::EBS documentation with AWS::EC2::Instance::BlockDeviceMapping::EBS. Confirm how Throughput is represented for gp3 volumes, then verify that Create accepts it when configuring an instance root volume.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100