title: Cannot Delete Amazon ECS Cluster using CloudFormation
body: <p>I am using the following CloudFormation template to create ECS Cluster.</p>
  
  <pre><code>AWSTemplateFormatVersion: '2010-09-09'
  Description: 'AWS Cloudformation Template to create the Infrastructure'
  Resources:
    ECSCluster:
      Type: AWS::ECS::Cluster
      Properties:
      ClusterName: 'Blog-iac-test-1'
    EC2InstanceProfile:
      Type: AWS::IAM::InstanceProfile
      Properties:
      Path: /
      Roles: [!Ref 'EC2Role']
    ECSAutoScalingGroup:
      Type: AWS::AutoScaling::AutoScalingGroup
    Properties:
      VPCZoneIdentifier:
      - subnet-****
      LaunchConfigurationName: !Ref 'ECSAutoscalingLC'
      MinSize: '1'
      MaxSize: '2'
      DesiredCapacity: '1'
   ECSAutoscalingLC:
      Type: AWS::AutoScaling::LaunchConfiguration
      Properties:
        AssociatePublicIpAddress: true
        ImageId: 'ami-b743bed1'
        SecurityGroups:
        - sg-****
        InstanceType: 't2.micro'
        IamInstanceProfile: !Ref 'EC2InstanceProfile'
        KeyName: 'test'
        UserData:
          Fn::Base64: !Sub |
          #!/bin/bash -xe
          echo ECS_CLUSTER=Blog-iac-test-1 &gt;&gt; /etc/ecs/ecs.config
    EC2Role:
      Type: AWS::IAM::Role
      Properties:
        AssumeRolePolicyDocument:
        Statement:
        - Effect: Allow
        Principal:
          Service: [ec2.amazonaws.com]
          Action: ['sts:AssumeRole']
        Path: /
    ECSServicePolicy:
      Type: "AWS::IAM::Policy"
      Properties: 
        PolicyName: "root"
        PolicyDocument: 
          Version: "2012-10-17"
          Statement: 
          - Effect: Allow
          Action: ['ecs:*', 'logs:*', 'ecr:*', 's3:*']
          Resource: '*'
      Roles: [!Ref 'EC2Role']
  </code></pre>
  
  <p>The stack is created successfully, but while destroying, I am getting the  following error:<br>
  <strong>The Cluster cannot be deleted while Container Instances are active or draining.</strong></p>
  
  <p>I was able to delete the stack earlier, this issue started to occur recently. 
  What could be a workaround to avoid this issue ? Should I need to add some dependencies ?</p>