gpt4 book ai didi

amazon-web-services - 自动伸缩组实例未在 ALB 上注册

转载 作者:行者123 更新时间:2023-12-03 07:11:58 25 4
gpt4 key购买 nike

我有以下Cloudformation模板,但实例在导致终止状态之前仅运行几秒钟。

我认为这与“宽限”期、“超时”期有关,但仍然无法弄清楚。

基本上,此模板是创建具有多个实例的自动缩放组(目标组)并在 ALB 上注册。

如何解决此问题以及调试的最佳方法是什么?

AWSTemplateFormatVersion: 2010-09-09
Description: ec2-instance

Parameters:
# Azs:
# Description: Avialbility zones
# Type: String
# Default: ap-southeast-2a

AMIs:
Description: AMIs
Type: String
Default: Linux
AllowedValues:
- Linux
- Windows

InstanceCount:
Description: Number of instances
Type: Number
Default: 1

Environment:
Description: Hosting Environment
Type: String
Default: Dev
AllowedValues:
- Dev
- Prod

Subnet01:
Description: Subnet1
Type: String
Default: 10.0.1.0/24

Subnet02:
Description: Subnet2
Type: String
Default: 10.0.2.0/24

LaunchTemplateVersionNumber:
Default: 1
Type: String
# Metadata:

Mappings:
FreeTier:
Linux:
HVM64: ami-0d9f286195031c3d9
Windows:
HVM64: ami-09cf24ffd6d332930

Conditions:
SelectImage: !Equals [!Ref AMIs, Linux]
SelectEnv: !Equals [ !Ref Environment, Dev]

# Transform:

Resources:

ApplicationLB:
Type: AWS::ElasticLoadBalancingV2::LoadBalancer
Properties:
Type: application
IpAddressType: ipv4
Scheme: internet-facing
Subnets:
- !Ref MySubnet01
- !Ref MySubnet02
Name: WebAppLB
SecurityGroups:
- !Ref SecurityALB



ALBListner:
Type: AWS::ElasticLoadBalancingV2::Listener
Properties:
LoadBalancerArn: !Ref ApplicationLB
DefaultActions:
- Type: forward
TargetGroupArn: !Ref MyTargetGroup
Port: 80
Protocol: "HTTP"

MyTargetGroup:
Type: AWS::ElasticLoadBalancingV2::TargetGroup
Properties:
HealthCheckEnabled: true
HealthCheckIntervalSeconds: 30
HealthCheckPath: /index.html
HealthCheckPort: 80
Port: 80
Protocol: HTTP
VpcId: !Ref MyVpc
TargetType: "instance"
Matcher:
HttpCode: "200"
TargetGroupAttributes:
- Key: load_balancing.algorithm.type
Value: round_robin
- Key: "deregistration_delay.timeout_seconds"
Value: "3000"


MyVpc:
Type: AWS::EC2::VPC
Properties:
CidrBlock: 10.0.0.0/16
EnableDnsHostnames: true
EnableDnsSupport: true

MySubnet01:
Type: AWS::EC2::Subnet
Properties:
AvailabilityZone:
Fn::Select:
- 0
- Fn::GetAZs:
Ref: AWS::Region
CidrBlock: !Ref Subnet01
VpcId: !Ref MyVpc

MySubnet02:
Type: AWS::EC2::Subnet
Properties:
AvailabilityZone:
Fn::Select:
- 1
- Fn::GetAZs:
Ref: AWS::Region
CidrBlock: !Ref Subnet02
VpcId: !Ref MyVpc

MyRouteTable:
Type: AWS::EC2::RouteTable
Properties:
VpcId: !Ref MyVpc

MyIgw:
Type: AWS::EC2::InternetGateway

Subnet01RouteTableAssociation:
Type: AWS::EC2::SubnetRouteTableAssociation
Properties:
SubnetId: !Ref MySubnet01
RouteTableId: !Ref MyRouteTable

Subnet02RouteTableAssociation:
Type: AWS::EC2::SubnetRouteTableAssociation
Properties:
SubnetId: !Ref MySubnet02
RouteTableId: !Ref MyRouteTable

VPCGatewayAttachment:
Type: AWS::EC2::VPCGatewayAttachment
Properties:
InternetGatewayId: !Ref MyIgw
VpcId: !Ref MyVpc

Route:
DependsOn: VPCGatewayAttachment
Type: AWS::EC2::Route
Properties:
RouteTableId: !Ref MyRouteTable
DestinationCidrBlock: 0.0.0.0/0
GatewayId: !Ref MyIgw

Launchtemplate:
Type: AWS::EC2::LaunchTemplate
Properties:
LaunchTemplateData:
ImageId: !If [SelectImage, !FindInMap [ FreeTier, Linux, HVM64 ], !FindInMap [ FreeTier, Windows, HVM64 ]]
InstanceType: t2.micro
KeyName: cfn-putty
UserData:
Fn::Base64: |
#!/bin/bash
sudo yum -y install httpd
sudo touch /var/www/html/index.html
echo "webserver v1" > /var/www/html/index.html
sudo hostname >> /var/www/html/index.html
sudo ifconfig >> /var/www/html/index.html
systemctl start httpd.service

SecurityGroups:
- !Ref enbalessh


LauncConfig:
Type: AWS::AutoScaling::AutoScalingGroup
Properties:
DefaultInstanceWarmup: 60
HealthCheckGracePeriod: 120
HealthCheckType: ELB
AvailabilityZones:
Fn::GetAZs:
Ref: "AWS::Region"
MaxSize: 3
MinSize: 1
TargetGroupARNs:
- !Ref MyTargetGroup
DesiredCapacity: !Ref InstanceCount
LaunchTemplate:
LaunchTemplateId: !Ref Launchtemplate
Version: !Ref LaunchTemplateVersionNumber
Tags:
- Key: "Environment"
PropagateAtLaunch: true
Value: !If [SelectEnv,Dev,Prod]
- Key: "Name"
PropagateAtLaunch: true
Value: !Sub
- "web-${os}-${env}"
- os: !Ref AMIs
env: !Ref Environment


enbalessh:
Type: AWS::EC2::SecurityGroup
Properties:
GroupDescription: enable-ssh
SecurityGroupIngress:
- IpProtocol: tcp
FromPort: '22'
ToPort: '22'
CidrIp: "0.0.0.0/0"
- IpProtocol: tcp
FromPort: 80
ToPort: 80
CidrIp: "0.0.0.0/0"

SecurityALB:
Type: AWS::EC2::SecurityGroup
Properties:
GroupDescription: Incoming-traffic-lb
SecurityGroupIngress:
- IpProtocol: tcp
FromPort: '80'
ToPort: '80'
CidrIp: "0.0.0.0/0"
VpcId: !Ref MyVpc

最佳答案

可能是因为您是在默认 VPC 中创建实例及其关联的安全组,所以您的 ALB 位于自定义 VPC 中。

因此,要修复实例和 ALB 必须位于同一 VPC 中的问题。如果没有 VPC 对等连接,您无法跨 VPC 加入它们。

关于amazon-web-services - 自动伸缩组实例未在 ALB 上注册,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/75969850/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com