title: Attach Capacity Provider to a ECS Cluster created in different Cloudformation stacks
body: <p>My team's current task is to develop an <strong>ECS Cluster</strong> to be able to migrate from Elastic Beanstalk.</p>
  <p>Since we have our entire infrastructure in Cloudformation we had to stich this implementation to our current templates.</p>
  <p>The idea is to have the cluster created separately with the underlying infrastructure that will be shared between the services that will eventually be deployed to the cluster.</p>
  <p>There is a different template for the <strong>empty</strong> ECS Cluster and another for the Services (and all resources specific to Services).</p>
  <p>The capacity providers are created with (and attached to) the services. From what I could find there is no way in Cloudformation to make a capacity provider appear as part of the cluster after the cluster is created. The capacity provider appears on the Services but not on the cluster and the Service ends up with no resources to provision its tasks.</p>
  <p>The workaround I have right now is to define a lambda as a custom resource to call the <code>putClusterCapacityProvider</code> action, and pass an empty array to the <code>defaultCapacityProviderStrategy</code> property.</p>
  <p>This strategy is working but feels a little too hacky. Am I missing something? Is there another way to have the capacity providers appear on the cluster after the cluster is created?</p>