Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(aws): Ability to specify a subnet #313

Closed
shanman190 opened this issue May 19, 2023 · 1 comment · Fixed by loft-sh/devpod-provider-aws#5
Closed

(aws): Ability to specify a subnet #313

shanman190 opened this issue May 19, 2023 · 1 comment · Fixed by loft-sh/devpod-provider-aws#5
Assignees

Comments

@shanman190
Copy link
Contributor

shanman190 commented May 19, 2023

Is your feature request related to a problem?
For anything other than the default VPC, you need to specify the subnet that the instance should be launched in as part of the RunInstances API call. At the moment, the vpc id is available to be set, but the subnet is not.

Which solution do you suggest?
Expose an optional subnet field that propagates all the way into the RunInstances API call.

Which alternative solutions exist?
None

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants