403 Error during websocket handshake when deployed behind ELB about blockscout-terraform HOT 9 CLOSED

For this issue, we need an Application Load Balancer to handle WebSockets. Currently, we have a Classic Load Balancer

from blockscout-terraform.

@bitwalker How difficult would it be to implement an Application Load Balancer as opposed to a Classic Load Balancer?

from blockscout-terraform.

@acravenho It should be pretty straightforward:

• Create an application load balancer resource
• Create a target group resource (configured with the internal port and protocol, not end-user facing (that is handled by the ALB)
• Create an application load balancer listener resource, configured with the external port/protocol/etc.; configure it to use the target group resource created above
• Replace the use of load_balancers in the auto-scaling group resource with target_group_arns
• Change the CodeDeploy deployment config to use target_group_info rather than elb_info

I believe that should cover everything that needs to change

from blockscout-terraform.

@bitwalker Perfect. I'll give a try today manually and see if I run into any issues 👍

from blockscout-terraform.

@acravenho You probably have already seen it, but if you want to know what options are available for each resource, you can find those docs here

from blockscout-terraform.

@bitwalker I've attempted it before using those docs but now that I have a more defined path I should be able to figure it out. Thank you for the help :)

from blockscout-terraform.

No problem! And yeah, the ALB's have some more moving parts than the classic ELBs, so they are a bit trickier to figure out just from the docs - the target group thing is the main sticking point, once you've got that sorted, they start to feel more familiar

from blockscout-terraform.

Thanks for the help @bitwalker. Couldn't have done it without you.

from blockscout-terraform.

No problem! Happy to help :)

from blockscout-terraform.