microsoft / microsoft/AzureTRE
Redesign airlock to reduce number of storage accounts used
Open
feature
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
The airlock uses a large number of storage accounts. The number of accounts (particularly the workspace ones) are a bind on scalability, and also increase the overall cost.
Is it possible to consolidate some of these accounts, and use containers to segregate data instead?
Per account:
- Private endpoint $7.30/account/month
- Defender scanning $10/account/month
E.g. TRE with 10 workspaces = 6 core airlock accounts, 50 workspace airlock accounts
Airlock storage accounts - core
| Name | Description |
|---|---|
st + airlockp + <TRE_ID> |
Airlock Processor |
st + alexapp + <TRE_ID> |
Airlock Export Approved |
st + alimblocked + <TRE_ID> |
Airlock Import Blocked |
st + alimex + <TRE_ID> |
Airlock Import External |
st + alimip + <TRE_ID> |
Airlock Import In Progress |
st + alimrej + <TRE_ID> |
Airlock Import Rejected |
Airlock storage accounts - per workspace
| Name | Description |
|---|---|
st + alexblocked + ws + <WS_ID> |
Airlock Export Blocked |
st + alexint + ws + <WS_ID> |
Airlock Export Internal |
st + alexip + ws + <WS_ID> |
Airlock Export In Progress |
st + alexrej + ws + <WS_ID> |
Airlock Export Rejected |
st + alimapp + ws + <WS_ID> |
Airlock Import Approved |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.