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

The loop isn't relevant to deployment. All your code does is set things up for deployment; the engine does all the deployment later, after your code has done its thing.
The default value for the `--parallel` option for up is _unbounded_, so they should all be deployment in parallel.

How are you determining that deployment is happening sequentially? The Pulumi graph output would be a reasonable indicator. Another option would be to use `pulumi.log` or `console.log` in an `apply()` on some output of the resource, like the ARN. If the logs are unordered then you can be reasonably confident that the resources are being deployed asynchronously.

the logs in the GHA runner, and what I can see happening in AWS console tell me its happening sequentially