No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

How do you guys configure healthchecks for a backend service that is not a HTTP service? (i.e. a SQS worker) Do you add a lightweight HTTP server to your worker service? If so, does that require deploying a load balancer that is essentially a NOP? Or is there some other AWS mechanism for liveliness of a backend service?

It looks like I can specify a `healthCheck` parameter for ECS: <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#container_definition_healthcheck>. <@UB9JVTW07> is there a way to specify this for an `awsx.ecs.FargateService`? I don't see it in the `awsx.ecs.Container` interface.

This may be due to it not existing whne we originally defined these interfaces

Is the fix to add to the original interface then?

so you should be able to still add these members (and just override TypeScript)

if you wanted to try that to see if it worked, that would be great

and i can then go about updating hte TypeSignatures here.

I think this will do it: <https://github.com/pulumi/pulumi-aws/pull/505>

but it would help to get confirmation on your part that passing along this data works

I actually don't have that healthcheck set up yet so I can't test it. Was just investigating how these sort of healthchecks should be done.

Ok.  if you can test in the future, that would be great.  Thanks!

Added the healthcheck to my app and passed these params to Container. Works as expected.