|
…
|
||
|---|---|---|
| .. | ||
| images | ||
| README.md | ||
| azuredeploy.json | ||
| azuredeploy.parameters.json | ||
| main.bicep | ||
| metadata.json | ||
README.md
| description | page_type | products | urlFragment | languages | ||||
|---|---|---|---|---|---|---|---|---|
| This template creates a Front Door Standard/Premium with a container group. | sample |
|
front-door-standard-premium-container-instances-public |
|
Front Door Standard/Premium with Azure Container Instances
This template deploys a Front Door Standard/Premium with an Azure Container Instances origin, using a public IP address for the container group.
Sample overview and deployed resources
This sample template creates an Azure Container Instances container group and a Front Door profile. The container group has a public IP address associated with it.
The following resources are deployed as part of the solution:
Container Instances
- Container group, with a single container deployed from the Hello World image.
Front Door Standard/Premium
- A Front Door profile with an endpoint, which is configured with an origin group, origin, and route to direct traffic to the container group.
- Note that you can use either the standard or premium Front Door SKU for this sample. By default, the standard SKU is used.
In this sample, traffic can flow directly to the container group. There is no mechanism to ensure the traffic has passed through Front Door. To restrict access, consider deploying the container group with virtual network integration and deploy an Application Gateway instance to restrict traffic. The Front Door Standard/Premium with Container Instances and Application Gateway origin sample illustrates this scenario.
The following diagram illustrates the components of this sample.
Deployment steps
You can click the "deploy to Azure" button at the beginning of this document or follow the instructions for command line deployment using the scripts in the root of this repo.
Usage
Connect
Once you have deployed the Azure Resource Manager template, wait a few minutes before you attempt to access your Front Door endpoint to allow time for Front Door to propagate the settings throughout its network.
You can then access the Front Door endpoint. The hostname is emitted as an output from the deployment - the output is named frontDoorEndpointHostName. If you access the base hostname you should see a page saying Welcome to Azure Container Instances!. If you see a different error page, wait a few minutes and try again.
Tags: Microsoft.ContainerInstance/containerGroups, Public, Microsoft.Cdn/profiles, Microsoft.Cdn/profiles/afdEndpoints, Microsoft.Cdn/profiles/originGroups, Microsoft.Cdn/profiles/originGroups/origins, Microsoft.Cdn/profiles/afdEndpoints/routes