所以我使用ECS (通过ecs-cli创建)和CloudFormation,并且我在创建自动伸缩组时遇到了问题:

它总是失败,因为它说"LoadBalancer附件不稳定“。有人知道这可能是什么原因吗??
我有两个CloudFormation堆栈,一个主堆栈用于设置我的大部分基础设施,第二个堆栈(它正在失败)用于第二个ECS集群。我正在传递来自第一个/主堆栈输出的输入参数。
我认为这可能是子网大小问题(它们在第一个堆栈中创建,并传递给第二个堆栈,10.0.0.0/24和10.0.1.0/24),所以我尝试在第二个cloudformation模板中创建两个新的子网并使用它们,但结果是相同的错误。
在两个模板文件之间创建的Autoscaling组和ELB是相同的...
第一个堆栈:
"InternetGateway": {
"Condition": "CreateVpcResources",
"Type": "AWS::EC2::InternetGateway"
},
"AttachGateway": {
"Condition": "CreateVpcResources",
"Type": "AWS::EC2::VPCGatewayAttachment",
"Properties": {
"VpcId": {
"Ref": "Vpc"
},
"InternetGatewayId": {
"Ref": "InternetGateway"
}
}
},
"RouteViaIgw": {
"Condition": "CreateVpcResources",
"Type": "AWS::EC2::RouteTable",
"Properties": {
"VpcId": {
"Ref": "Vpc"
}
}
},
"PublicRouteViaIgw": {
"Condition": "CreateVpcResources",
"DependsOn": "AttachGateway",
"Type": "AWS::EC2::Route",
"Properties": {
"RouteTableId": {
"Ref": "RouteViaIgw"
},
"DestinationCidrBlock": "0.0.0.0/0",
"GatewayId": {
"Ref": "InternetGateway"
}
}
},
"PubSubnet1RouteTableAssociation": {
"Condition": "CreateVpcResources",
"Type": "AWS::EC2::SubnetRouteTableAssociation",
"Properties": {
"SubnetId": {
"Ref": "PubSubnetAz1"
},
"RouteTableId": {
"Ref": "RouteViaIgw"
}
}
},
"PubSubnet2RouteTableAssociation": {
"Condition": "CreateVpcResources",
"Type": "AWS::EC2::SubnetRouteTableAssociation",
"Properties": {
"SubnetId": {
"Ref": "PubSubnetAz2"
},
"RouteTableId": {
"Ref": "RouteViaIgw"
}
}
},
"Outputs": {
"VpcId": {
"Value": { "Ref": "Vpc" }
},
"KeyName": {
"Value": { "Ref": "KeyName" }
},
"SourceCidr": {
"Value": { "Ref": "SourceCidr"}
},
"EcsInstancePolicy": {
"Value": { "Ref": "EcsInstancePolicy" }
},
"SubnetIds": {
"Value": {
"Fn::Join": [
",", [{
"Ref": "PubSubnetAz1"
},
{
"Ref": "PubSubnetAz2"
}
]
]
}
},
"CloudSecurityGroup": {
"Value": { "Ref": "EcsSecurityGroup" }
},
"GatewayRouteTable": {
"Value": { "Ref": "PublicRouteViaIgw" }
}
}第二个堆栈:
"Parameters": {
"EcsAmiId": {
"Type": "String",
"Description": "ECS EC2 AMI id",
"Default": ""
},
"EcsInstanceType": {
"Type": "String",
"Description": "ECS EC2 instance type",
"ConstraintDescription": "must be a valid EC2 instance type."
},
"KeyName": {
"Type": "AWS::EC2::KeyPair::KeyName",
"Description": "Required - Name of an existing EC2 KeyPair to enable SSH access to the ECS instances"
},
"VpcId": {
"Type": "String",
"Description": "Required - VPC Id of existing VPC of Central stack.",
"AllowedPattern": "^(?:vpc-[0-9a-f]{8}|)$",
"ConstraintDescription": "VPC Id must begin with 'vpc-'"
},
"SubnetIds": {
"Type": "String",
"Description": "Required - Comma separated list of two (2) existing VPC Subnet Ids where ECS instances will run."
},
"AsgMaxSize": {
"Type": "Number",
"Description": "Maximum size and initial Desired Capacity of ECS Auto Scaling Group",
"Default": "1"
},
"SourceCidr": {
"Type": "String",
"Description": "Required - Input CIDR/IP range to open up for ECS and Aurora"
},
"EcsInstancePolicy": {
"Type": "String",
"Description": "Required - IAM Policy for the ECS instances to use"
},
"EcsCluster": {
"Type": "String",
"Description": "ECS Cluster Name",
"Default": "default"
},
"CloudSecurityGroup": {
"Type": "String",
"Description": "Name of the security group used by the ECS instances in the Cloud cluster"
},
},
"Resources": {
"EcsSecurityGroup": {
"Type": "AWS::EC2::SecurityGroup",
"Properties": {
"GroupDescription": "ECS Allowed Ports",
"VpcId": { "Ref": "VpcId" },
"SecurityGroupIngress": [
{
"IpProtocol": "tcp",
"FromPort": 22,
"ToPort": 22,
"SourceSecurityGroupId": { "Ref": "CloudSecurityGroup" }
},
{
"IpProtocol": "tcp",
"FromPort": 11000,
"ToPort": 11001,
"SourceSecurityGroupId": { "Ref": "CloudSecurityGroup" }
},
{
"IpProtocol": "tcp",
"FromPort": 22,
"ToPort": 22,
"CidrIp": { "Ref": "SourceCidr" }
},
{
"IpProtocol": "tcp",
"FromPort": 11000,
"ToPort": 11001,
"CidrIp": { "Ref": "SourceCidr" }
}
]
}
},
"EcsSecurityGroupIngressSelf": {
"Type": "AWS::EC2::SecurityGroupIngress",
"Properties": {
"GroupId": { "Ref": "EcsSecurityGroup" },
"SourceSecurityGroupId": { "Ref": "EcsSecurityGroup" },
"IpProtocol": "tcp",
"FromPort": 22,
"ToPort": 9999
}
},
"ElasticLoadBalancer": {
"Type": "AWS::ElasticLoadBalancing::LoadBalancer",
"Properties": {
"Subnets": {
"Fn::Split": [
",",
{ "Ref": "SubnetIds" }
]
},
"CrossZone": "true",
"SecurityGroups": [{
"Ref": "EcsSecurityGroup"
}],
"Listeners": [{
"LoadBalancerPort": "22",
"InstancePort": "22",
"Protocol": "TCP"
},
{
"LoadBalancerPort": "11000",
"InstancePort": "11000",
"Protocol": "TCP"
},
{
"LoadBalancerPort": "11001",
"InstancePort": "11001",
"Protocol": "TCP"
}
],
"HealthCheck": {
"HealthyThreshold": "2",
"Interval": "30",
"Target": "TCP:22",
"Timeout": "5",
"UnhealthyThreshold": "5"
}
}
},
"EcsInstanceProfile": {
"Type": "AWS::IAM::InstanceProfile",
"Properties": {
"Path": "/",
"Roles": [{
"Ref": "EcsInstancePolicy"
}]
}
},
"EcsInstanceLc": {
"Type": "AWS::AutoScaling::LaunchConfiguration",
"Properties": {
"ImageId": {
"Ref": "EcsAmiId"
},
"InstanceType": {
"Ref": "EcsInstanceType"
},
"AssociatePublicIpAddress": true,
"IamInstanceProfile": {
"Ref": "EcsInstanceProfile"
},
"KeyName": {
"Ref": "KeyName"
},
"SecurityGroups": [{
"Ref": "EcsSecurityGroup"
}],
"UserData": {
"Fn::Base64": {
"Fn::Join": [
"", [
"#!/bin/bash\n",
"echo ECS_CLUSTER=",
{
"Ref": "EcsCluster"
},
" >> /etc/ecs/ecs.config\n"
]
]
}
}
}
},
"EcsInstanceAsg": {
"Type": "AWS::AutoScaling::AutoScalingGroup",
"Properties": {
"VPCZoneIdentifier": [{ "Ref": "SubnetIds" }],
"LaunchConfigurationName": {
"Ref": "EcsInstanceLc"
},
"MinSize": "1",
"MaxSize": {
"Ref": "AsgMaxSize"
},
"DesiredCapacity": {
"Ref": "AsgMaxSize"
},
"LoadBalancerNames": [{ "Ref": "ElasticLoadBalancer" }],
"Tags": [{
"Key": "Name",
"Value": {
"Fn::Join": [
"", [
"ECS Instance - ",
{
"Ref": "AWS::StackName"
}
]
]
},
"PropagateAtLaunch": "true"
}]
}
},如果有任何额外的信息,请让我知道。
发布于 2017-02-08 07:45:45
从您的屏幕截图中可以看出,CloudFormation堆栈和EcsInstanceAsg自动伸缩组是先前创建的,并且您正在尝试更新自动伸缩组以引用新创建的负载均衡器。
CloudFormation资源在更新时不稳定的最常见问题是由于被引用的资源在CloudFormation堆栈之外被修改和/或删除。根据AWS CloudFormation Best Practices的说法,这会导致CloudFormation修改它再也找不到的资源,这可能会导致随机错误或超时。如果是这样的话,如果可能的话,最好的方法是用一个全新的堆栈重新开始。
如果不是这样,AWS::AutoScaling::AutoScalingGroup中的LoadBalancerNames属性的就地更新可能存在未知的限制或问题(对此属性的就地更新的支持仅为just added on Jan 17 2017,因此可能仍然存在问题)。尝试重新创建您的Auto Scaling Group (在您的模板中更改EcsInstanceAsg资源的名称将导致重新创建它),看看这是否解决了问题。
发布于 2017-02-08 08:43:19
我让它起作用了。解决方案是我所做的以下两个更改中的一个(或两个):
"VPCZoneIdentifier": { "Ref": "SubnetIds" },其中SubnetIds是两个子网ids的字符串,它们之间有一个逗号。(请注意,截至2017年2月7日,The documentation is wrong。它说这个参数接受一个字符串列表,但它显然没有。)https://stackoverflow.com/questions/42099898
复制相似问题