- 新しい順
- 投票が多い順
- コメントが多い順
As the error suggests, you cannot use more than one subnet for the same availability zone. In VPC, each subnet is associated with an availability zone. Please make sure to use another subnet in another AZ to have multiple subnets for the load balancer.
You enable one or more Availability Zones for your load balancer when you create it. If you enable multiple Availability Zones for your load balancer, this increases the fault tolerance of your applications. You can't disable Availability Zones for a Network Load Balancer after you create it, but you can enable additional Availability Zones.
Note that you can select only one subnet per Availability Zone.
Thanks guys,
so now, I have added the 2 public subnets to my compose file:
version: '3.8'
x-aws-vpc: "vpc-0f64c8ba9cb5bb10f"
x-aws-subnets:
- subnet-044ddbc9a47c8744a
- subnet-0a16347f784acfb76
services:
osticket:
container_name: osticket-web
image: osticket/osticket
environment:
MYSQL_HOST: db
MYSQL_PASSWORD: secret
depends_on:
- db
ports:
- 80:80
db:
container_name: osticket-db
image: mariadb
restart: always
environment:
MYSQL_ROOT_PASSWORD: secret
MYSQL_DATABASE: osticket
MYSQL_USER: osticket
MYSQL_PASSWORD: secret
But I am still getting the same error: A load balancer cannot be attached to multiple subnets in the same Availability Zone (Service: AmazonElasticLoadBalancing; Status Code: 400; Error Code: InvalidConfigurationRequest; Request ID: c742256e-4938-420e-ad97-63f75fb73979; Proxy: null)
Am I suing the x-aws-subnets in a wrong context or place?
関連するコンテンツ
- AWS公式更新しました 2年前
- AWS公式更新しました 7ヶ月前
- AWS公式更新しました 3年前