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

Implement using Private endpoint #244

Open
maayanlux opened this issue Mar 7, 2024 · 5 comments
Open

Implement using Private endpoint #244

maayanlux opened this issue Mar 7, 2024 · 5 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@maayanlux
Copy link

Hi,
I tried to implement the solution in my environment, but I must use a private endpoint to all the public resources: Web app, cosmos db, and a key vault.
When I configured the private endpoints, I received a 500 network error code, and in the "Application log", I received the error attached.
can you please explain how to use the solution using private endpoints?
and, why do we need all the "outbound addresses"? what is there use? can we disable it and how?

Thanks

image ipam error
@DCMattyG DCMattyG self-assigned this Mar 7, 2024
@DCMattyG DCMattyG added the help wanted Extra attention is needed label Mar 7, 2024
@DCMattyG
Copy link
Contributor

DCMattyG commented Mar 7, 2024

Hi @maayanlux, thank you for reaching out on this topic!

The high-level process to make this solution private is as follows:

  1. Deploy the solution with the provided deploy.ps1 script.
  2. Create Private Endpoints for all of the Azure resources (App Services, CosmosDB, KeyVault)
  3. Enable Virtual Network Integration for the App Service

The process of creating the Private Endpoints should also create the required Private DNS Zones, or you can choose to link those Private Endpoints to your existing/centralized Private DNS Zone you may already have within your environment.

I'm guessing the reason that you're seeing the error message above is likely DNS related as the App Service will need to be able to resolve the Private for CosmosDB.

That is the very high level process, and I am indeed working on some more thorough documentation on this process which I'll post soon. In the meantime, if you'd like some additional assistance please feel free to ping me on Team at Matthew.Garrett@microsoft.com, or even drop me an email. We can schedule some time to take a look at your environment together if that would be helpful. Let me know, thanks!

@egnirra
Copy link

egnirra commented May 29, 2024

I have deployed everything using Terraform with private endpoints and vnet integration, no public access allowed.
Not sure if it's of any interest since not everyone uses Terraform.

Let me know and i could perhaps share my terraform module in some way.

@vamsee33
Copy link

vamsee33 commented Jun 20, 2024

@egnirra , I would like to approach for the same requirement. Could you please assist me to implement and please provide a strategy to achieve it . Please let me know if we can connect over email?

@cmgksims
Copy link

I have deployed everything using Terraform with private endpoints and vnet integration, no public access allowed. Not sure if it's of any interest since not everyone uses Terraform.

Let me know and i could perhaps share my terraform module in some way.

Could you share your terraform

@vamsee33
Copy link

vamsee33 commented Sep 5, 2024

I have deployed everything using Terraform with private endpoints and vnet integration, no public access allowed. Not sure if it's of any interest since not everyone uses Terraform.

Let me know and i could perhaps share my terraform module in some way.

Can you share some steps to implement this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants