Closed retgits closed 4 years ago
looks like the Helm chart doesn't support --secret-key-file, which is required for ec2 and Scaleway.
I can add support for that to the chart. In terms of documentation, there doesn't appear to be any for EC2 provider in this repo, Ill draw some up when amending the chart.
Thanks for the feedback @retgits In terms of least-privilege, I would have to have a play about, the tricky thing would be the AMIs as they differ by region.
/assign: me
If there is anything I can help out with, do let me know 😄
@Waterdrips do you have an update on this? It seems fairly important to me, where would you rate it on urgency?
@retgits a PR would be nice, if you can get to it sooner.
@alexellis @retgits this must have slipped through the net - ill do it now.
Current Behaviour
Currently, there is no documentation on how to use the EC2 provider. While I think I figured out most of it, there are still a few things that I'm not sure on. Documentating this for other people will help them get up to speed with using Inlets faster.
Possible Solution
If I got everything right (which I assume, because I was able to complete the tutorial), you can start inlets-operator with the following parameters if you want to use the EC2 provider:
For my trial, I used an account that had all privileges but considering the implications of that I want to have the least-privileged capabilities it needs to create the AWS resources. Would that be something like