-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
(aws-autoscaling): Missing KeyPair field on autoScalingGroupProps #29237
Closed
Brads3290 opened this issue
Feb 23, 2024
· 2 comments
· Fixed by #29679 or rwlxxvii/containers#140 · May be fixed by NOUIY/aws-solutions-constructs#102, paralus/eks-blueprints-addon#3 or NOUIY/aws-solutions-constructs#103
Closed
(aws-autoscaling): Missing KeyPair field on autoScalingGroupProps #29237
Brads3290 opened this issue
Feb 23, 2024
· 2 comments
· Fixed by #29679 or rwlxxvii/containers#140 · May be fixed by NOUIY/aws-solutions-constructs#102, paralus/eks-blueprints-addon#3 or NOUIY/aws-solutions-constructs#103
Labels
@aws-cdk/aws-autoscaling
Related to Amazon EC2 Auto Scaling
bug
This issue is a bug.
effort/medium
Medium work item – several days of effort
p2
Comments
Brads3290
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Feb 23, 2024
github-actions
bot
added
the
@aws-cdk/aws-autoscaling
Related to Amazon EC2 Auto Scaling
label
Feb 23, 2024
Yes, as AutoScaling is using LaunchTemplate L2 to create the launch template when feature flag is enabled:
I think we should follow the convention as here
|
pahud
added
p2
effort/medium
Medium work item – several days of effort
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Feb 26, 2024
1 task
mergify bot
pushed a commit
that referenced
this issue
May 10, 2024
### Issue When creating an instance directly through the asg, it is not possible to define the `keyPair`, in addition to bringing a warning message that the `keyName` will be removed This configuration allows sending the `keyPair` to the asg since the LaunchTemplate allows its integration Warning: > [WARNING] aws-cdk-lib.aws_ec2.LaunchTemplateProps#keyName is deprecated. Closes #29237 ### Reason for this change I'm working directly with CDK and needed to implement a way to use my `keyPair` and avoid warning that `keyName` will be removed soon when i'm creating my ASG ### Description of changes - Add `keyPair` to CommonAutoScalingGroupProps interface - Prevent `keyPair` and `keyName` from being set at the same time - Send `keyPair` when creating LaunchTemplate if flag `AUTOSCALING_GENERATE_LAUNCH_TEMPLATE` is enabled - Prevent `keyPair` if the flag `AUTOSCALING_GENERATE_LAUNCH_TEMPLATE` is disabled ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
This was referenced Jun 22, 2024
This was referenced Jul 5, 2024
This was referenced Jul 16, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
@aws-cdk/aws-autoscaling
Related to Amazon EC2 Auto Scaling
bug
This issue is a bug.
effort/medium
Medium work item – several days of effort
p2
Describe the bug
Using the KeyName to specify a key pair will be deprecated on the launchTemplateProps construct.
When using
KeyName
on autoScalingGroupProps, CDK gives the following warning on synth:Presumably autoScalingGroupProps uses launchTemplateProps underneath. autoScalingGroupProps should have a
KeyPair
property that is passed to the underlying launchTemplateProps.Expected Behavior
autoScalingGroupProps should have a
KeyPair
property that is passed to the underlying launchTemplateProps.Current Behavior
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.129.0 (build d5ab0df)
Framework Version
No response
Node.js Version
v18.16.1
OS
MacOS
Language
.NET
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: