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.

Sign up for GitHub

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

Jump to bottom

Add option to the landing zone (VNET; Policies, App Configuration) #12

Open

Mimetis opened this issue Apr 28, 2021 · 0 comments

Assignees

Labels

Azure enhancement .Net Core

Owner

Mimetis commented Apr 28, 2021 •

edited by elenaterenzi

Loading

Idea

Add new option to the landing zone deployment

Today

For now, when creating an engine, the landing zone is created with

A Databricks spark cluster
A Data Factory V2 used as an orchestrator
An Application Insights used to aggregate the metrics
A Key Vault to store some sensitive data
A Storage Account containing the ingested data and the Delta Lake

Expectation

We can imagine having more components likes

VNET to encapsulates the whole landing zone in a VNET
Private link (https://docs.microsoft.com/en-us/azure/private-link/)
Azure Policies to handles the security requirement
App Configuration to store configuration settings
DNS Zone to have better endpoints
Key Vault-backed Secret Scope for Databricks
Main Key Vault for storing SP credentials (and other stuff?)
More ?

Mimetis added enhancement .Net Core Azure labels

Mimetis self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment