Skip to content

Commit

Permalink
Do not be explicit about iops constraints
Browse files Browse the repository at this point in the history
IOPS constrained for individual volumes may vary over time.
Rather, direct a reader to the AWS documentation instead of
explicitly stating the boundaries.
  • Loading branch information
ingvagabund committed Mar 26, 2019
1 parent 995e3e2 commit 575e8d4
Showing 1 changed file with 3 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -190,8 +190,9 @@ type EBSBlockDeviceSpec struct {
// and bursting, see Amazon EBS Volume Types (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html)
// in the Amazon Elastic Compute Cloud User Guide.
//
// Constraint: Range is 100-20000 IOPS for io1 volumes and 100-10000 IOPS for
// gp2 volumes.
// Minimal and maximal IOPS for io1 and gp2 are constrained. Please, check
// https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html
// for precise boundaries for individual volumes.
//
// Condition: This parameter is required for requests to create io1 volumes;
// it is not used in requests to create gp2, st1, sc1, or standard volumes.
Expand Down

0 comments on commit 575e8d4

Please sign in to comment.