503 temporary service unavailabale

[ranjeetrj]

Describe the Bug

I created elastic beanstalk env with the shared load balancer using this repo code and when I hit the DNS URL of beanstalk env or route 53 url I got a 503 error on the browser.

But if I add "associate_public_ip_address = true" this parameter is in main.tf block, it's working perfectly.

May I know if am i missing something or if it is default behavior?

The actual problem is instance is not reachable as I haven't assigned a public IP to this.
SO I just wanted to know. do I need to assign a public IP to an instance in shared load balancer env?
If I didn't assign then the health check would fail.

Expected Behavior

The shared load balancer should work except for this parameter ""associate_public_ip_address = true""

Steps to Reproduce

Create your own vpc
Go inside the shared-alb folder, and in main.tf change vpc_id, subnet_id,security_group_id
execute the below commands,
terraform init
terraform plan
terraform apply

Screenshots

module.elastic_beanstalk_environment.aws_elastic_beanstalk_environment.default[0]: Still creating... [17m51s elapsed]
╷
│ Error: creating Elastic Beanstalk Environment (e-j4zkjtqr7y): 2 errors occurred:
│ * 2023-11-20 08:14:29.361 +0000 UTC Stack named 'awseb-e-j4zkjtqr7y-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBInstanceLaunchWaitCondition].
│ * 2023-11-20 08:14:29.465 +0000 UTC The EC2 instances failed to communicate with AWS Elastic Beanstalk, either because of configuration problems with the VPC or a failed EC2 instance. Check your VPC configuration and try launching the environment again.
│
│
│
│ with module.elastic_beanstalk_environment.aws_elastic_beanstalk_environment.default[0],
│ on ....\main.tf line 602, in resource "aws_elastic_beanstalk_environment" "default":
│ 602: resource "aws_elastic_beanstalk_environment" "default" {
│

Environment

No response

Additional Context

No response

[joe-niland]

I'm guessing the issue is with your VPC. Can you share the full Terraform code, including the vpc config?

[ranjeetrj]

Sure here it is,
For creating vpc I have used my own model. I have deployed Beanstalk env in a public subnet.

terra-vpc-demo.zip
shared-alb.zip

[joe-niland]

From looking at your files, and the error message above, it seems that the issue is that your VPC doesn't have a NAT gateway or VPC endpoint. This means your instances can't communicate with the Elastic Beanstalk service to signal that they're healthy.

I will close now as it's not a bug with the module.

I suggest you check the examples directory again and implement your module based on them. For example, using the dynamic-subnets module will save you a lot of time.

[ranjeetrj]

Hello Joe, You are right, After creating the NAT gateway the issue is resolved. Thank you for your help.

…

On Tue, Nov 21, 2023 at 1:10 PM Joe Niland ***@***.***> wrote: From looking at your files, and the error message above, it seems that the issue is that your VPC doesn't have a NAT gateway or VPC endpoint. This means your instances can't communicate with the Elastic Beanstalk service to signal that they're healthy. I will close now as it's not a bug with the module. I suggest you check the examples directory again and implement your module based on them. For example, using the dynamic-subnets module will save you a lot of time. — Reply to this email directly, view it on GitHub <#250 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APQW52Z2XCOSSKF5MVWEVE3YFRLGZAVCNFSM6AAAAAA7SQE4LOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRQGM4DINZSHA> . You are receiving this because you authored the thread.Message ID: <cloudposse/terraform-aws-elastic-beanstalk-environment/issues/250/1820384728 @github.com>