Explanation:
When a CloudFormation stack includes a WaitCondition or a CreationPolicy, the EC2 instances must send a signal back to the CloudFormation service to indicate successful provisioning. This is typically done using the cfn-signal helper script over HTTPS (port 443). If the security group associated with the instances does not allow outbound traffic on port 443, the signal cannot reach the CloudFormation endpoint, causing the creation to time out and fail. While option A mentions cfn-signal (misspelled as cf-n-signal), the most common infrastructure-level fix for a missing signal is ensuring connectivity to the AWS API endpoints.
Ultimate access to all questions.
Question 12. A SysOps administrator is creating resources from an AWS CloudFormation template that defines an Auto Scaling group of Amazon EC2 instances. The Auto Scaling group launch template provisions each EC2 instance by using a user data script. The creation of the Auto Scaling group resource is failing because of an error. The wait condition is not receiving the required number of signals. How should the SysOps administrator resolve this error?
A
Run cf-n-signal at the completion of the user data script.
B
Modify the EC2 instances’ security group to allow outgoing traffic on port 443.
C
Reduce the Auto Scaling group’s DesiredCapacity value in the CloudFormation template.
D
Set the AssociatePublicIpAddress property to True in the Auto Scaling group launch template.
E
None
F
None
No comments yet.