While creating the wait condition resource in AWS CloudFormation, a SysOps Administrator receives the error `received 0 signals out of the 1 expected from the EC2 instance`. What steps should be taken to troubleshoot this issue? (Choose two.)
A.
Confirm from the cfn logs that the cfn-signal command was successfully run on the instance.
B.
Try to re-create the stack with a different IAM user.
C.
Check that the instance has a route to the Internet through a NAT device.
D.
Update the AWS CloudFormation stack service role to have iam:PassRole permission.
E.
Delete the existing stack and attempt to create a new once.
At first, I agreed with wshyang, who said D might be correct. But then (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-servicerole.html) I understood that is not the cloudformation stack the one that should have the IAM:PassRole but the user that give the roles to the Cloudformation stack, according to the docu. Then I agreed with the other ones, to solve the situation: A or C
Difficult question, but it is A and C according to this page:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-dependency-error
"Last updated: 2020-03-05
In AWS CloudFormation, I receive the following error message: "Failed to receive X resource signal(s) within the specified duration." How can I resolve this error?
Short Description
You get this error when an Amazon Elastic Compute Cloud (Amazon EC2) instance, Auto Scaling group, or a WaitCondition doesn't receive success signals from one or more instances in the time period specified by the CreationPolicy attribute.
This error can occur in one of the following scenarios:
Scenario 1: The cfn-signal script isn't installed on one or more instances of the AWS CloudFormation stack.
Scenario 2: There are syntax errors or incorrect values in the AWS CloudFormation template.
Scenario 3: The value of the Timeout property for the CreationPolicy attribute is too low.
Scenario 4: The cfn-signal isn't sent from the Amazon EC2 instance.
Note: The troubleshooting scenarios for this error apply only to AWS CloudFormation stacks created with Linux instances. The scenarios don't apply to Windows instances."
A and C. See the exact description of CloudFormation dependency error section in
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-dependency-error
A and C are correct. You can refer to section "Wait Condition Didn't Receive the Required Number of Signals from an Amazon EC2 Instance" in below link
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html
An Internet route used to be required. This changed in Sept. 2018: https://aws.amazon.com/blogs/mt/signaling-aws-cloudformation-waitconditions-using-aws-privatelink/
I don't think C is right, D might be correct.
If C is indeed correct then cloudformation won't be able to provision any private subnet ASG instances ever, which is quite a lousy bug.
Correct answer is A & C
A - obvious
C - If instance don't have connectivity to internet then instance wont be able to talk to Cloud foramation (tricky to understand)
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
waterzhong
11 months, 1 week agoFinger41
11 months, 2 weeks agoVishya
1 year agoablazleon
1 year, 2 months agoFHU
1 year, 3 months agoyfwang
1 year, 5 months agonarayanan010
1 year, 6 months agonarayanan010
1 year, 6 months agowinmacman
1 year, 6 months agoHaroldFinch
1 year, 7 months agopleasespammelater
1 year, 7 months agowshyang
1 year, 7 months agoMoon
1 year, 7 months agoAbhishekGupta
1 year, 7 months agokarmaah
1 year, 7 months ago