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 Joshua, that example (<https://github.com/pulumi/examples/tree/master/cloud-js-containers>) should work "out of the box". I just deployed it and am able to hit the URL successfully.

My stack config looks like this:
```
config:
  aws:region: us-west-2
  cloud-aws:useFargate: "true"
```

Here's my pulumi output fwiw. <https://gist.github.com/clstokes/053a2958400ca69f6b065b23a3f02877>

so it outputs `url` instead of `hostname`? but does it still have a full `http://...<http://amazonaws.com|amazonaws.com>` url?

Hmm, in my case it gets deployed into the default VPC in my account. So it doesn't require the additional setup of an internet gateway.

Is it deployed to your default VPC too? Does your default VPC restrict inbound access?

I opened up access but still see this issue. Must be something related to that