This message was deleted.

sparse-intern-71089

04/26/2022, 10:41 PM

This message was deleted.

billowy-army-68599

04/26/2022, 10:46 PM

this is a networking problem, you either need to use a bastion/jumpbox or a vpn

little-cartoon-10569

04/27/2022, 12:27 AM

Commands for initialization can also be handled through SSM (aws.ssm has the Document and Association resources that you'd need for this approach), or you can use userdata (cloud-init package's GetConfig function is the way to go here).

green-musician-49057

04/27/2022, 4:17 AM

You also pair pulumi's

command.local.Command

to use the aws CLI to invoke handy built-in AWS SSM / Systems Manager features, like running remote commands/scripts, or starting a port forwarding session. One of the nice parts of this approach is that your automations never touch your SSH keys...but there are some pre-reqs for using Systems Manager.

little-cartoon-10569

04/27/2022, 4:34 AM

And you still need access, since the command does run on the machine. cloud-init and SSM documents run on the machine itself, which makes it handy if the machine is on an isolated subnet, for example.

60 Views

Open in Slack

Previous Next

Pulumi Community

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.