AWS EC2 Provisioner does not support temporary credentials with session token. about inletsctl

[alexellis]

Thanks for raising this. You could also set up your VM as required and download the inlets server manually, or using CloudFormation/TF/Pullumi.

Inletsctl uses cloud init, so a similar approach is what I'd expect to work with other tooling.

I would be interested in any possible solution that you may see? That was part of the original template. How does the AWS SDK enable the third leg of authentication?

@Waterdrips may also have ideas or @rgee0

[rgee0]

This should be relatively straightforward to implement. It’s a case of capturing a new flag value and passing it through to the provisioner, which currently passes “” in the token field.

You’d probably want to split the two suggested approaches. Offer through a flag initially and then consider environment variables later.

[rgee0]

inlets/cloud-provision#8 is the first part

[rgee0]

#105 provides for the use of temporary credentials.

@nathanpeck if you're interested I'd appreciate an extra set of eyes on the testing.

[rgee0]

Doco here:https://github.com/inlets/docs/pull/18

[alexellis]

Thanks @rgee0 that was excellent timing 👍

Nathan, you can still set up your tunnel servers however you like, but inletsctl 0.8.8 now supports the request above:

https://github.com/inlets/inletsctl/releases/tag/0.8.8