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'm migrating from using `ebsBlockDevices` on my EC2 instances to doing `new aws.ec2.VolumeAttachment(..)` because of <https://github.com/pulumi/pulumi-aws/issues/420> (I found it pretty disturbing this isn't noted in the documentation!)

Previously I was using cloud-init to `bootcmd` format the drive, and this worked find because drives attached via `ebsBlockDevices` seem to be attached before this command is run.

Using VolumeAttachments this doesn't seem to be the case.

Is there a best way of doing this? I have a bunch of things that I was doing at startup that rely on this volume being available (eg, installing and starting various daemons that depend on this volume) and it's not super-clear to me what the best approach here is?