-
Notifications
You must be signed in to change notification settings - Fork 2
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
Security hardening / private endpoints / DNS #37
Comments
web-icenetuat-application (public) - pvt-icenetuat-application module.application.azurerm_private_endpoint.application app-icenetuat-pygeoapi (public) - pvt-icenetuat-pygeoapi module.pygeoapi.azurerm_private_endpoint.pygeoapi sticenetuatdata (public) - pvt-icenetuat-data-blob and ...-file module.data.azurerm_private_endpoint.data_blob module.data.azurerm_private_endpoint.data_file app-icenetuat-event-processing (private) module.forecast_processor.azurerm_private_endpoint.event_proc_endpoint app-icenetuat-processing (private) module.forecast_processor.azurerm_private_endpoint.proc_endpoint psql-icenetuat-database (private) module.data.azurerm_private_endpoint.database egd-icenetuat-processing-domain (private) module.forecast_processor.azurerm_private_endpoint.event_domain_endpoint sticenetuatappfcproc (private) module.forecast_processor.azurerm_private_endpoint.evtproc_app_storage_endpoint sticenetuatappproc (private) module.processing.azurerm_private_endpoint.proc_app_storage_endpoint
The private endpoints caused an amazing nuisance, with the web application being unable to mount the share from the main storage, promptly breaking the container host with no real messaging. Going to get the rest of the infrastructure set up behind the LB for access and then lock down from the edge, then transition into the private endpoint architecture. Azure is really a bit wobbly to use, with things failing silently all over the shop |
Builds on from #31
Expose and restrict
The text was updated successfully, but these errors were encountered: