无法创建ScalingPolicy-未注册可扩展目标

时间:2019-07-16 09:16:25

标签: amazon-web-services amazon-cloudformation

我遵循了示例here,但是当我尝试更新堆栈时,出现以下错误:

No scalable target registered for service namespace: ecs, resource ID: 
service/xxx-prod/xxx-prod-api, scalable dimension: ecs:service:DesiredCount 
(Service: AWSApplicationAutoScaling; Status Code: 400; Error Code: 
ObjectNotFoundException; Request ID: 1232c749-a7a9-11e9-bd34-dfed08b14539)

我看过的所有示例和文档都将资源ID显示为:

service/cluster-name-AB678321674/service-AB672345678

例如:https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-applicationautoscaling-scalabletarget.html

我看不到如何或在何处可以获取这种格式的资源ID。

CF看起来像这样:

 AutoScalingTarget:
    Type: AWS::ApplicationAutoScaling::ScalableTarget
    Properties:
      MinCapacity: !Ref MinContainers
      MaxCapacity: !Ref MaxContainers
      ResourceId: 
        Fn::Join:
        - "/"
        - - service
          - Fn::ImportValue:
              !Join [':', [!Ref AppStackName, 'ClusterName']]
          - !GetAtt Service.Name
      ScalableDimension: ecs:service:DesiredCount
      ServiceNamespace: ecs
      # "The Amazon Resource Name (ARN) of an AWS Identity and Access Management (IAM) role that allows Application Auto Scaling to modify your scalable target."
      RoleARN:
        Fn::ImportValue:
          !Join [':', [!Ref SecurityStackName, 'AutoScaleRole']]

  AutoScalingPolicy:
    Type: AWS::ApplicationAutoScaling::ScalingPolicy
    Properties:
      PolicyName: !Join ['', [!Ref ServiceName, AutoScalingPolicy]]
      PolicyType: TargetTrackingScaling
      ScalingTargetId: !Ref AutoScalingTarget
      TargetTrackingScalingPolicyConfiguration:
        PredefinedMetricSpecification:
          PredefinedMetricType: ECSServiceAverageCPUUtilization
        ScaleInCooldown: 10
        ScaleOutCooldown: 10
        # Keep things at or lower than 50% CPU utilization, for example
        TargetValue: !Ref AutoScalingTargetValue

集群是在单独的堆栈中创建的,因此我必须导出/导入该集群。

有人可以在这里看到我做错了吗?

TIA。

2 个答案:

答案 0 :(得分:0)

好吧,FFS。我删除了目标,然后将目标和策略添加到一起,效果很好。

叹气

答案 1 :(得分:0)

刚刚遇到同样的错误,

不太清楚@Jonesie 将它们加在一起是什么意思,但有两种方法可以解决这个问题:

将“DependsOn: AutoScalingTarget”添加到 AutoScalingPolicy,以便在 AutoScalingPolicy 之前创建可扩展目标

或者使用 ScalingTargetId 代替 ServiceNamespace/ScalableDimension/ResourceId。通过使用 ScalingTargetId 然后使用 !Ref AutoScalingTarget,您正在设置两个资源之间的依赖关系,这是实际问题;)

见:https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-applicationautoscaling-scalingpolicy.html#cfn-applicationautoscaling-scalingpolicy-scalabledimension