amazon-web-services - Cloudformation 中的循环依赖

Question

我陷入了 Cfn(ECS 堆栈)中的循环依赖循环，这可以通过隔离不同堆栈中的资源来轻松解决，但挑战是在相同/单个堆栈中解决它。花了一个晚上解决这个问题，仍然没有解决它。经过大量调试最终寻求一些帮助，请告诉我是否有人可以帮助我，我真的很感激任何线索或帮助。`

AWSTemplateFormatVersion: '2010-09-09'
Description: This stack will deploy following resources , May 
# Metadata:
Parameters:
  VPC:
    Description: Select One VPC available in your existing account
    Type: AWS::EC2::VPC::Id
  PubSubnets:
    Type: 'List<AWS::EC2::Subnet::Id>'
    Description: The list of PubSubnetIds in selected VPC)
  PvtSubnets:
    Type: 'List<AWS::EC2::Subnet::Id>'
    Description: The list of PvtSubnetIds in selected VPC)
  ClientName:
    Type: String
    Default: test

# Mappings: 

# Conditions: 

Resources:
  ELBTargetGroup:
   Type: 'AWS::ElasticLoadBalancingV2::TargetGroup'
  #  DependsOn:
  #   - ElasticLoadBalancer
   Properties:
     Name: "ELB-TG"
     HealthCheckIntervalSeconds: 6
     HealthCheckTimeoutSeconds: 5
     HealthyThresholdCount: 2
     Port: 80
     Protocol: HTTP
     UnhealthyThresholdCount: 2
     VpcId: !Ref VPC
     TargetType: instance
  
  ELBSecurityGroup:
    Type: AWS::EC2::SecurityGroup
    Properties:
      GroupName: "ELBTraffic"
      GroupDescription: "Enable HTTP access on the inbound port for ELB"
      VpcId: !Ref VPC
      SecurityGroupIngress:
        - IpProtocol: tcp
          FromPort: 80
          ToPort: 80
          CidrIp: 0.0.0.0/0
      Tags:
        - Key: Name
          Value: ELBSecurityGroup
  
  ElasticLoadBalancer:
    Type: AWS::ElasticLoadBalancingV2::LoadBalancer
    # DependsOn:
    #   - ELBSecurityGroup
    Properties:
      Subnets: 
      - !Ref PubSubnets
      SecurityGroups: 
        - !Ref ELBSecurityGroup
  
  ElbListener:
   Type: 'AWS::ElasticLoadBalancingV2::Listener'
  #  DependsOn:
  #   - ElasticLoadBalancer
   Properties:
     DefaultActions:
       - Type: forward
         TargetGroupArn: !Ref ELBTargetGroup
     LoadBalancerArn: !Ref ElasticLoadBalancer
     Port: 80
     Protocol: HTTP
  
  AsgConfig:
    Type: AWS::EC2::LaunchTemplate
    DependsOn:
      - ELBSecurityGroup
    Properties:
      LaunchTemplateName: !Sub ${ClientName}-launch-template
      LaunchTemplateData:
        ImageId: ami-0171959e760b38d59
        InstanceType: t3.medium
        SecurityGroups:
        - !Ref ELBSecurityGroup
        #ImageId: "ami-0171959e760b38d59"
        UserData:
          Fn::Base64: !Sub |
            #!/bin/bash -xe
            echo ECS_CLUSTER=${ECSCluster} >> /etc/ecs/ecs.config
            sudo yum install -y python-pip pip
            yum install -y aws-cfn-bootstrap
            /opt/aws/apitools/cfn-init-2.0-6/bin/cfn-signal -e $? --stack ${AWS::StackId} --resource AsGroup --region ${AWS::Region}
            /opt/aws/apitools/cfn-init-2.0-6/bin/cfn-init -v --stack ${AWS::StackName} --resource AsgConfig --region ${AWS::Region} -c default
  
  AsGroup:
    Type: AWS::AutoScaling::AutoScalingGroup
    DependsOn:
      - AsgConfig
    Properties:
      VPCZoneIdentifier: 
        - !Ref PvtSubnets
      LaunchTemplate:
        LaunchTemplateId: !Ref AsgConfig
        Version: !GetAtt AsgConfig.LatestVersionNumber
      # LaunchConfigurationName: !Ref AsgConfig
      MinSize: '1'
      DesiredCapacity: '2'
      MaxSize: '4'
      TargetGroupARNs:
        - !Ref ELBTargetGroup
  
  CapacityProvider:
    Type: AWS::ECS::CapacityProvider
    DependsOn:
      - AsGroup
    Properties:
      AutoScalingGroupProvider:
        AutoScalingGroupArn: !Ref AsGroup 
  
  CodeCommitRepository1:
    Type: AWS::CodeCommit::Repository
    Properties:
      RepositoryDescription: "HTML code"
      RepositoryName: "HTML_code"
  CodeCommitRepository2:
    Type: AWS::CodeCommit::Repository
    Properties:
      RepositoryDescription: "Python code"
      RepositoryName: "Python_code"
  CodeCommitRepository3:
    Type: AWS::CodeCommit::Repository
    Properties:
      RepositoryDescription: "Node code"
      RepositoryName: "Node_code"
  
  ECRrepo:
    Type: AWS::ECR::Repository
    Properties:
      RepositoryName: "cfn_repo"
  
  ECSCluster:
    Type: AWS::ECS::Cluster
    DependsOn:
      - CapacityProvider
    Properties:
      CapacityProviders:
        - !Ref CapacityProvider
      ClusterName: !Ref ClientName
      Configuration:
       ExecuteCommandConfiguration:
          Logging: DEFAULT
      ClusterSettings:
        - Name: containerInsights
          Value: enabled
  
  ECSServiceRole:
    Type: AWS::IAM::Role
    Properties:
      RoleName: "ecs-service-role"
      AssumeRolePolicyDocument:
        Statement:
          - Effect: Allow
            Principal:
              Service: ecs.amazonaws.com
            Action: sts:AssumeRole
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/service-role/AmazonEC2ContainerServiceRole
  
  ExecutionRole:
    Type: AWS::IAM::Role
    Properties:
      RoleName: "ecs-execution-role"
      AssumeRolePolicyDocument:
        Statement:
          - Effect: Allow
            Principal:
              Service: ecs-tasks.amazonaws.com
            Action: sts:AssumeRole
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/service-role/AmazonECSTaskExecutionRolePolicy
  
  ContainerSecurityGroup:
    Type: AWS::EC2::SecurityGroup
    Properties:
      GroupName: "ContainerSecurityGroup"
      GroupDescription: "Security group for container"
      SecurityGroupIngress:
        - IpProtocol: tcp
          FromPort: 80
          ToPort: 80
          CidrIp: 0.0.0.0/0
  Service:
    Type: AWS::ECS::Service
    DependsOn:
      - ECSCluster
      - ElasticLoadBalancer
      # - ECSServiceRole
      # - TaskDefinition
      - ELBTargetGroup
    Properties:
      Cluster: !Ref ECSCluster
      Role: !Ref ECSServiceRole
      DesiredCount: 1
      TaskDefinition: !Ref TaskDefinition
      LaunchType: EC2
      LoadBalancers:
        - ContainerName: "deployment-container"
          ContainerPort: 80
          TargetGroupArn: !Ref ELBTargetGroup
  
  AutoScalingRole:
    Type: AWS::IAM::Role
    Properties:
      RoleName: service-auto-scaling-role
      AssumeRolePolicyDocument:
        Statement:
          - Effect: Allow
            Principal:
              Service: [application-autoscaling.amazonaws.com]
            Action: ["sts:AssumeRole"]
      Policies:
        - PolicyName: service-auto-scaling-policy
          PolicyDocument:
            Version: "2012-10-17"
            Statement:
              - Effect: Allow
                Action:
                  - ecs:DescribeServices
                  - ecs:UpdateService
                  - cloudwatch:PutMetricAlarm
                  - cloudwatch:DescribeAlarms
                  - cloudwatch:DeleteAlarms
                Resource:
                  - "*"

  ScalableTarget:
    Type: AWS::ApplicationAutoScaling::ScalableTarget
    # DependsOn:
    #   - 
    Properties:
      RoleARN: !GetAtt AutoScalingRole.Arn
      ResourceId: !Sub service/${ClientName}/Service
      ServiceNamespace: ecs
      ScalableDimension: ecs:Service:DesiredCount
      MinCapacity: 1
      MaxCapacity: 5
  
  ScalingPolicy:
    Type: AWS::ApplicationAutoScaling::ScalingPolicy
    DependsOn:
      - ScalableTarget
    Properties:
      PolicyName: service-auto-scaling-policy
      PolicyType: TargetTrackingScaling
      ScalingTargetId: !Ref ScalableTarget
      TargetTrackingScalingPolicyConfiguration:
        PredefinedMetricSpecification:
          PredefinedMetricType: ECSServiceAverageCPUUtilization
        TargetValue: 80.0

  TaskDefinition:
    Type: AWS::ECS::TaskDefinition
    # DependsOn:
    #   - ExecutionRole
      # - Service
    Properties:
      Family: deployment-task
      Cpu: "256"
      Memory: "512"
      NetworkMode: bridge
      ExecutionRoleArn: !Ref ExecutionRole
      ContainerDefinitions:
        - Name: deployment-container
          Image: cfn_repo/cfnrepo:latest
          PortMappings:
            - ContainerPort: 80      
      RequiresCompatibilities:
        - EC2
       
# Outputs:
#   outputELBTargetGroup:
#     Description: A reference to the created Target Group
#     Value: !Ref ELBTargetGroup
#   outputELBSecurityGroup:
#     Description: A reference to the created Security Group
#     Value: !Ref ELBSecurityGroup
#   outputElasticLoadBalancer:
#     Description: A reference to the created Elastic Load Balancer
#     Value: !Ref ElasticLoadBalancer
#   outputElasticListener:
#     Description: A reference to the created Elastic Load Balancer Listener
#     Value: !Ref ElbListener
#   outputAsgConfig: 
#     Description: Id for autoscaling launch configuration
#     Value: !Ref AsgConfig
#   outputAsgGroup: 
#     Description: Id for autoscaling group
#     Value: !Ref AsgGroup 
#   outputECSCluster: 
#     Description: Cluster name
#     Value: !Ref ECSCluster

`

Answer 1

您有一个循环依赖项，如下所示:

1. AsGroup 取决于 AsgConfig
2. AsgConfig 依赖于 ECSCluster，因为用户数据中 echo ECS_CLUSTER=${ECSCluster}
3. ECSCluster 依赖于 CapacityProvider
4. CapacityProvider 依赖于 AsGroup(即上面的 #1)

我建议您不要使用 CapacityProvider 配置 ECSCluster，而只需创建不带容量提供程序(并且不带 DependsOn)的 ECSCluster，然后添加稍后的 AWS::ECS::ClusterCapacityProviderAssociations 以将 CapacityProvider 与 ECSCluster 关联起来。

例如(请注意，我尚未对此进行测试，因此可能需要进行一些调整):

CapacityProvider:
  Type: AWS::ECS::CapacityProvider
  DependsOn:
    - AsGroup
  Properties:
    AutoScalingGroupProvider:
      AutoScalingGroupArn: !Ref AsGroup 

ECSCluster:
  Type: AWS::ECS::Cluster
  Properties:
    ClusterName: !Ref ClientName
    Configuration:
      ExecuteCommandConfiguration:
        Logging: DEFAULT
    ClusterSettings:
      - Name: containerInsights
        Value: enabled

ClusterCapacityProviderAssociation:
  Type: AWS::ECS::ClusterCapacityProviderAssociations
  Properties: 
    CapacityProviders: 
      - !Ref CapacityProvider
    Cluster: ECSCluster
    DefaultCapacityProviderStrategy: 
      - Base: 0
        Weight: 1
        CapacityProvider: !Ref CapacityProvider