@@ -400,6 +400,9 @@ Resources:
400400 - !Ref VpcPublicSubnet2Id
401401 - !Ref VpcPublicSubnet3Id
402402
403+ # The capacity provider is associated with the ECS cluster in the x86-64
404+ # template, for that's where the association resource was originally created
405+ # and it's a pain to move.
403406 DefaultCapacityProvider :
404407 Type : AWS::ECS::CapacityProvider
405408 Properties :
@@ -424,21 +427,9 @@ Resources:
424427 - { Key: prx:cloudformation:root-stack-id, Value: !Ref RootStackId }
425428 - { Key: prx:ops:environment, Value: !Ref EnvironmentType }
426429 - { Key: prx:dev:application, Value: Common }
427- ClusterCapacityProviderAssociation :
428- Type : AWS::ECS::ClusterCapacityProviderAssociations
429- Properties :
430- Cluster : !Ref EcsClusterName
431- CapacityProviders :
432- - !Ref DefaultCapacityProvider
433- - !If [IsStaging, FARGATE, !Ref "AWS::NoValue"]
434- - !If [IsStaging, FARGATE_SPOT, !Ref "AWS::NoValue"]
435- DefaultCapacityProviderStrategy :
436- # With only one default capacity provider, the base and weight won't
437- # factor into scheduling; everything will be even within the ASG
438- - Base : 0
439- Weight : 1
440- CapacityProvider : !Ref DefaultCapacityProvider
441430
442431Outputs :
443432 AsgName :
444433 Value : !Ref Asg
434+ CapacityProviderName :
435+ Value : !Ref DefaultCapacityProvider
0 commit comments