1 Answer
- Newest
- Most votes
- Most comments
2
Hello.
What commands are you running with "EB CLI"?
If you are running the "eb create" command, try specifying two subnets to be used by ALB with "--vpc.elbsubnets".
Also, please select a subnet in a different availability zone.
You may find the following documentation examples helpful.
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb3-create.html#eb3-createexample1
eb create dev-vpc --vpc.id vpc-0ce8dd99 --vpc.elbsubnets subnet-b356d7c6,subnet-02f74b0c --vpc.ec2subnets subnet-0bb7f0cd,subnet-3b6697c1 --vpc.securitygroup sg-70cff265
Relevant content
- asked 10 months ago
- asked 2 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
I followed your comment and the problem was fixed, but another error states that the "security group doesnt exist in the VPC" even though it does:
2024-02-26 00:08:31 ERROR Failed createEnvironment activity. Reason: Configuration validation exception: Invalid option value: 'sg-0d8e69 8f62e8e529b' (Namespace: 'aws:autoscaling:launchconfiguration', OptionName: 'SecurityGroups'): The security group 'sg-0d***' does not exist in vpc 'vpc-02a*****'
I made sure it exists in the VPC.