https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# aws
s
This message was deleted.
r
load balancer health checks go on 'target groups', which can be created easily from an 
ApplicationLoadBalancer
instance.
when I was hosting a few Fargate services from a shared ALB, I made different target groups for each separate service I had, then set up appropriate healthchecks on each target group, then used each target group as the 
portMappings
for the service it matched to
i
That's what I have right now. When looking through the console, there is a health check, but all it does is check 
/
and expect 
200
return code
index.ts
r
what about making the target group explicitly (ie one of these: https://github.com/pulumi/pulumi-awsx/blob/master/nodejs/awsx/lb/targetGroup.ts) and adding the instance to that?
i
Yeah, trying to figure out how the syntax of that works
r
something like:
Copy code
const tg = alb.createTargetGroup("my-tg", {
    port: 80,
    protocol: "HTTP",
    healthCheck: {
        path: "/",
        port: "80",
        protocol: "HTTP",
        matcher: "200",
    }
});

tg.attachTarget("server-attach", server);
?
i
Nice, thank you! Let me try that out
r
you can of course tweak the check for whatever parameters you need
i
What's that 
"server-attach"
in the 
attachTarget
?
r
you've got to give a name to the 
targetgroupattachment
that is created as part of the 
attachTarget
call
Copy code
public attachTarget(name: string, args: mod.LoadBalancerTarget, opts: pulumi.CustomResourceOptions = {}) {
        return new mod.TargetGroupAttachment(name, this, args, opts);
    }
(from the source code)
i
OK, thanks.
Ah, I see, it complained at me about duplicate entries, I see now what's happening 👍
Apparently I need to attach that target group to the listener, any idea how to do that? I wasn't able to find that yet. There appears to be 
listener.defaultTargetGroup
but I wasn't able to figure out yet how to use it
r
oh, yes. you make a listener on the alb (alb.CreateListener), add a rule for the new listener via 
listener.addListenerRule
, and in tha rule set an 
action
of 
type
"forward", and 
targetGroupArn
of your new target group
something like
Copy code
// listen for https traffic. by default returns 404, will have rules added to forward to the requisite groups
const listener = alb.createListener("http-traffic", {
    port: 80,
    protocol: "HTTP",
    external: true,
    defaultAction: {
        type: "fixed-response",
        fixedResponse: {
            contentType: "text/plain",
            statusCode: "404"
        }
    },
});

/// this listener forwards all traffic to the identity server
listener.addListenerRule("plain-traffic-to-server", {
    priority: 49999, // priority goes from 1 to 50000 with lower numbers going first, so this makes the rule always eval last
    conditions: [{ httpRequestMethod: { values: ["GET", "PUT", "POST", "HEAD", "OPTIONS"] } } as aws.types.output.lb.ListenerRuleCondition], // all HTTP methods
    actions: [
        {
            type: "forward",
            targetGroupArn: tg.targetGroup.arn // targetgroups in pulumi have a 'targetGroup' property with the arn on it
        }
    ]
});
this makes a listener with a default-reject rule, and then makes another rule to allow all methods to the target group
i
Yeah, so far by going from https://github.com/pulumi/infrastructure-as-code-workshop/blob/master/labs/02-app-arch/code/01-provisioning-vms/step4.ts I had
Copy code
const listener = alb.createListener("web-listener", { port: 80 });
Apparently I need much more :P
r
yeah 🙂 I got to this pattern when I needed to start doing path-based routing, not just port forwarding
i
Seems to work, thank you!
index.ts
r
glad to hear it! I got to this point starting from the code samples and then checking out the source code to see what the 'defaults' were, then changing them to my needs
3 Views
Open in Slack
PreviousNext
Powered by