Aws-elb health check failing at 302 code

0 votes

Hi i created ALB listener 443 and target group instance on 7070 port (not-ssl)

I can access instanceip:7070 without problem , but with https://elb-dns-name not able to access.. instance health check also failed with 302 code

ALB listener port https and instance is http protocol ,

when i browse with https://dns-name it redirecting to http://elb-dns-name

Aug 30, 2018 in AWS by bug_seeker
• 15,350 points
606 views

1 answer to this question.

0 votes

you get 302 when performing URL redirection, any ELB Health check will look for success code 200 for the health check to pass. In ALB, this can be configured under health check in the ELB console.

To modify the health check settings of a target group using the console

  1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
  2. On the navigation pane, under LOAD BALANCING, choose Target Groups. Select the target group.
  3. On the Health checks tab, choose Edit.
  4. On the Edit target group page, modify the setting Success Codes to 302 or as needed, and then choose Save.

enter image description here

answered Aug 30, 2018 by Priyaj
• 56,900 points

Related Questions In AWS

0 votes
1 answer

How to test code written against AWS API

The actual uploading and the tests that ...READ MORE

answered May 17, 2018 in AWS by Flying geek
• 3,160 points
33 views
0 votes
1 answer

I'm trying to integrate Bitbucket into AWS Code Pipeline? What is the best approach?

You can integrate Bitbucket with AWS CodePipeline ...READ MORE

answered Aug 17, 2018 in AWS by Priyaj
• 56,900 points
665 views
0 votes
1 answer

AWS Network ELB take 4 minutes to recognise target as healthy

We hit this issue with NLBs and ...READ MORE

answered Sep 5, 2018 in AWS by Priyaj
• 56,900 points
30 views
0 votes
1 answer
0 votes
1 answer
0 votes
1 answer