Azure / Azure/HubAndSpokeResearchEnclave

Allow a choice between centralized airlock or distributed airlock

Open
#8 0 comments 0 reactions 1 assignee Claimed by @SvenAelterman View on GitHub
enhancement in-progress low priority
Dominant language
Bicep
Stars
18
Forks
18
Avg merge
4d 19h
Merged PRs (30d)
3

Description

In either case, each enclave will have some customization options, such as who is notified when an export is requested. However, in the centralized airlock, there will be a single VM (to be deployed in the hub) that will be used by any reviewer, regardless of which enclave the export is from. This is the best scenario when there is a common group of reviewers. However, if the reviewers of the exports differs by research project, a distributed model is better.

### Tasks

- [ ] Move keyVault.bicep and related modules to shared-modules folder.
- [ ] Deploy AVD for review VM if centralized.
- [ ] Deploy file share for review if centralized (and domain join or Entra ID join).
- [ ] Deploy Key Vault to store file share connection string if centralized.
- [ ] Modify spoke Logic App parameters with centralized airlock values.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.