Support issue with EC2 provisioner and AWS EC2 Classic about inlets-operator

[alexellis]

Thanks for the report.

I'll ping @Waterdrips to see if he can repro.

@adamjohnson01 do you mind taking a look as the author of the AWS provisioning code? https://github.com/inlets/inletsctl/tree/master/pkg/provision#maintainers-for-each-provider

[alexellis]

/set title: Support issue with EC2 provisioner

[alexellis]

@digitalsanctum what kind of documentation (specifically) do you think needs adding?

[thesurlydev]

@alexellis Perhaps it's enough just to update this section: https://github.com/inlets/inlets-operator#using-a-provider-which-requires-an-access-key-and-secret-key-aws-ec2-scaleway

It was only through trial and error that I got the right combination of args that worked with AWS. For args that accept a file/path, specify what's expected to be in the file.

Another hiccup related to documentation is that the required fields for specific providers are not obvious so that was more trial and error. For AWS and possibly other providers, there's no way to specify a VPC (if you have more than one in a region).

[alexellis]

Happy to take a suggested block of text to add here, or via a PR (more paperwork and process) - both will give the same end result.

[Waterdrips]

@digitalsanctum - Do you have an old AWS account with EC2 Classic enabled?

I was able to get tunnels spun up on AWS EC2 using a new AMI user with EC2 full access into eu-west-1 region with default settings.

Worked with both inlets and inlets-pro.

[thesurlydev]

@Waterdrips I do have an old account with EC2 classic enabled. I also don't have a default VPC which is why I'm guessing the code as it is works without specifying a VPC. I'm guessing that providing an optional VPC arg may help in this case and the other case I mentioned above where there might be more than one VPC in the target account/region.

[thesurlydev]

I've found the same issue occurs when using inletsctl so I'm going to attempt to update code there to get things working for me. I'll report back when I know more.

[Waterdrips]

/set title: Support issue with EC2 provisioner and AWS EC2 Classic

[thesurlydev]

I think this issue has more to do with no default VPC being available. See my PR against inetsctl for proposed fix: inlets/inletsctl#75

[adamjohnson01]

@alexellis, I would but i will not have access to a computer for a few weeks.

[Waterdrips]

This depends on inlets/inletsctl#75

[thesurlydev]

@alexellis I'm happy to propagate fix here from my fix in inletsctl.