feat(autoscaling): add includeSignalCommand option to control cfn-sig… #35970
+1,690
−630
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue # (if applicable)
Closes #34847 - [AutoScalingGroup]: Add flag to remove automatic cfn-signal addition to userdata when using init property
Reason for this change
When using CloudFormation Init with AutoScalingGroups, cfn-signal is automatically called immediately after cfn-init, causing instances to signal "ready" before applications are fully initialized. This leads to premature instance replacement during updates.
Description of changes
Added includeSignalCommand option to ApplyCloudFormationInitOptions to allow users to disable automatic cfn-signal addition and manage signaling manually.
Key changes:
Description of how you validated changes
Checklist