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

Move SHM firewall to SRE #1871

Closed
5 tasks done
jemrobinson opened this issue May 9, 2024 · 0 comments · Fixed by #1872
Closed
5 tasks done

Move SHM firewall to SRE #1871

jemrobinson opened this issue May 9, 2024 · 0 comments · Fixed by #1872
Labels
enhancement New functionality that should be added to the Safe Haven

Comments

@jemrobinson
Copy link
Member

✅ Checklist

  • I have searched open and closed issues for duplicates.
  • This is a request for a new feature in the Data Safe Haven or an upgrade to an existing feature.
  • The feature is still missing in the latest version.
  • I have read through the documentation.
  • This isn't an open-ended question (open a discussion if it is).

🍓 Suggested change

Having a shared Azure Firewall complicates billing (as usage cannot be easily assigned to an SRE). We're also using a Standard SKU while we would probably be fine with the Basic SKU.

🚂 How could this be done?

Move the firewall to the SRE

@jemrobinson jemrobinson added the enhancement New functionality that should be added to the Safe Haven label May 9, 2024
@jemrobinson jemrobinson added this to the Release 5.0.0rc2 milestone May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New functionality that should be added to the Safe Haven
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant