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

I am trying to get an App Load Balancer and related ECS task (flask API) to use HTTPS in a demo app where I do not have a domain name and am just using the `dns_name` of the ALB.  In trying to create a listener that uses the cert with `alb.dns_name` I am receiving an error that the cert is not found after it seems to be generated successfully (Pulumi doesn’t error out).  I then look in my pulumi console and see in fact the cert does have a `FAILED` status.  Since the docs all show the creation of the cert with an `<http://www.example.com|www.example.com>` domain, I am not clear how to adjust for an aws generated domain.  Any guidance?

In terms of the pulumi API, I was looking for something similar to the cloudfront arg `cloudfront_default_certificate` that make it easy to use a default SSL cert for a container-based (ECS) flask API service if I am not coming with my own domain name.

Well, maybe this is not pulumi’s problem: <https://docs.aws.amazon.com/acm/latest/userguide/troubleshooting-failed.html>