Describe the bug
The example listed in the documentation renders:
1:27:28 PM | CREATE_FAILED | AWS::EC2::Instance | BastionHost30F9ED05
Invalid device name EBSBastionHost (Service: AmazonEC2; Status Code: 400; Error Code: InvalidBlockDeviceMapping; Request ID: 3bd4a132-0230-4769-8ef5-5ceaa559ad36; P
roxy: null)
The proposed deviceName does not align with the supported ones.
Additionally:
volume: ec2.BlockDeviceVolume.ebs(10, { encrypted: true }),
has an implicit volumeType default of GP2, while it should now be GP3 by default if not specified.
Expected Behavior
The example from documentation should work when copy-pasted.
Current Behavior
As above.
Reproduction Steps
As above.
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.127.0 (build 6c90efc)
Framework Version
No response
Node.js Version
v18.18.2
OS
MacOS
Language
TypeScript
Language Version
No response
Other information
No response
Describe the bug
The example listed in the documentation renders:
The proposed
deviceNamedoes not align with the supported ones.Additionally:
has an implicit volumeType default of GP2, while it should now be GP3 by default if not specified.
Expected Behavior
The example from documentation should work when copy-pasted.
Current Behavior
As above.
Reproduction Steps
As above.
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.127.0 (build 6c90efc)
Framework Version
No response
Node.js Version
v18.18.2
OS
MacOS
Language
TypeScript
Language Version
No response
Other information
No response