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 creating EC2 machine and right after that I am running ansible. But the problem is machine state gets to “running” after some time and due to that ansible fails to reach the server. 
Is there await or anything in native pulumi as an option while creating EC2?

I know we can add our own custom loop and check state of the machine and then continue but I want to try pulumi option if available. 

Hi <@U01JCEY3GM9> 

No Pulumi has no custom way to handle this at this time

can you create an AMI or have ansible run from user data?

<@UHTP242EB> can we convert ec2.ID() i.e pulimi.IDOutput to string and *string?

You could go to the AWS SDK in your pulumi code and run a loop waiting for the state of the machine to change to running before hitting ansible.

Yup but I want to avoid using vanilla sdk if I am using pulumi. 

To me, this is WHY I use pulumi.  The ability to piggy back on the authentication, and seamlessly integrate is awesome.  No shelling out, custom provisioners... Just code.