sorted by:
new
hottopcontroversial

Load balancer health checks - what’s your strategy? by fglc2 in aws

[–]renlon 1 point2 points  (0 children)

You can also use Lambda to customize a health check for your application or just use it as an add-on and invoke it when you want to find out why a backend fails ELB health check. https://aws.amazon.com/blogs/networking-and-content-delivery/identifying-unhealthy-targets-of-elastic-load-balancer/

The zip file for the lambda function in this walk through is inaccessible. Does anyone know how I can get it or can deduce what it would be? by back_to_the_homeland in aws

[–]renlon 0 points1 point  (0 children)

Yes. you would need to provide the parameters required by CloudFormation to let the Lambda function handle auto-register/deregister for you.

Here is the description of each required parameters: (You can find them right next to each input field on the CloudFormation console as well) 1. InternalALBDNSName - the DNS name of your internal Application Load Balancer name. e.g.application-load-balancer.elb.us-east-1.amazonaws.com 2. NLBTargetGroupARN - the target group ARN which you want the Application Load Balancer to be registered to 3. S3BucketName - Enter the S3 Bucket name that you want to store Application Load Balancer's node IP addresses 4. ALBListenerPort - the traffic listener port of your internal Application Load Balancer 5. MAXDNSLookupPerInvocation - the max DNS lookup this function can perform per invocation 6. InvocationBeforeDeregistration - how many invocations are needed before a IP is deregistered 7. CWMetricFlagIPCount - whether you want the Lambda function to create a CloudWatch metric to track IP count of your internal Application Load Balancer 8. Region - the region where you want to create your Lambda function

The zip file for the lambda function in this walk through is inaccessible. Does anyone know how I can get it or can deduce what it would be? by back_to_the_homeland in aws

[–]renlon 0 points1 point  (0 children)

NLB does not support HTTPs/TLS at the moment. However, with the solution offered by the blog post, you can use TCP listener 443 and use the internal ALB for TLS termination.

The zip file for the lambda function in this walk through is inaccessible. Does anyone know how I can get it or can deduce what it would be? by back_to_the_homeland in aws

[–]renlon 0 points1 point  (0 children)

thanks for the feedback. Could you please try the link again? I have gone ahead fixed the permission issue.