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

Provision a Windows VM as a Bastion jumpbox #187

Closed
glennmusa opened this issue Apr 29, 2021 · 0 comments · Fixed by #210
Closed

Provision a Windows VM as a Bastion jumpbox #187

glennmusa opened this issue Apr 29, 2021 · 0 comments · Fixed by #210
Assignees
Labels
core New feature or request

Comments

@glennmusa
Copy link
Contributor

glennmusa commented Apr 29, 2021

Benefit/Result/Outcome
I have a Windows machine to remote into as part of a Bastion deployment

Description
When I provision a Bastion host using the Bastion module, I expect to provision a Windows virtual machine to use as a jumpbox using windows_virtual_machine

https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/windows_virtual_machine

Acceptance Criteria

  • I get this vm when I provision the Bastion host using the Bastion module
  • The vm is configured for a valid subnet for bastion jumpboxes in the same virtual network as the bastion subnet
  • The login credentials are variable, but generated by MLZ (we can store them later in a KeyVault later in Store virtual machine login credentials in a KeyVault #190)
  • The "size" / SKU of the virtual machine is variable, but defaulted by MLZ
  • The source image/marketplace image is variable, but defaulted by MLZ
@glennmusa glennmusa changed the title Provision a Windows VM in the Hub VNet Provision a Windows VM in the Hub VNet as a Bastion jumpbox Apr 29, 2021
@glennmusa glennmusa changed the title Provision a Windows VM in the Hub VNet as a Bastion jumpbox Provision a Windows VM as a Bastion jumpbox Apr 29, 2021
@brooke-hamilton brooke-hamilton added core New feature or request persona: IT admin and removed needs triage labels May 3, 2021
@glennmusa glennmusa self-assigned this May 17, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants