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

Hi Rodrigo, you can get started with the AI generated example - <https://www.pulumi.com/ai/conversations/11249816-9853-4c78-92f4-411d0d3cbe64>

Thanks I tried it but it seems to reference a version of pulumi packages that is not matching the latest one, using the script provided by pulimi AI gives me type errors

There’s no out of the box template, but you can try an example here:
<https://github.com/search?q=repo%3Ajaxxstorm%2Fpulumi-examples%20fargate&amp;type=code>

you have to do this: <https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html>

and then <https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html>

<https://devpress.csdn.net/cicd/62ec87d089d9027116a112c0.html> this example helped me to go to good track

for the HTTPS configuration, just use the annotations defined in this documentation <https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.5/guide/ingress/annotations/#tls>

thank you <@UCWG26BH7> and <@U05TV183P1A>

I will post a case study on my use case, I ended up finding out that pulumi/awsx package exports `classic` which allows you to reference the non wrapped awsx exports, which from the ai provided scripts it seemed that it was referencing `classic` instead of the `pulumi/awsx` awsx export