A DevOps Engineer is setting up a container-based architecture. The Engineer has decided to use AWS CloudFormation to automatically provision an Amazon ECS cluster and an Amazon EC2 Auto Scaling group to launch the EC2 container instances. After successfully creating the CloudFormation stack, the Engineer noticed that, even though the ECS cluster and the EC2 instances were created successfully and the stack finished the creation, the EC2 instances were associating with a different cluster.
How should the DevOps Engineer update the CloudFormation template to resolve this issue?
A . Reference the EC2 instances in the AWS::ECS::Cluster resource and reference the ECS cluster in the AWS::ECS::Service resource.
B . Reference the ECS cluster in the AWS::AutoScaling::LaunchConfiguration resource of the UserData property.
C . Reference the ECS cluster in the AWS::EC2::Instance resource of the UserData property.
D . Reference the ECS cluster in the AWS::CloudFormation::CustomResource resource to trigger an AWS Lambda function that registers the EC2 instances with the appropriate ECS cluster.
Answer: B
Explanation:
Reference: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-aslaunchconfig.html