Skip to content

Commit dba2037

Browse files
authored
Merge pull request #102297 from dlepow/acissl
[ACI] SSL options
2 parents 368d1c9 + 89755a6 commit dba2037

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

articles/container-instances/container-instances-container-group-ssl.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,11 @@ ms.date: 04/03/2019
88

99
This article shows how to create a [container group](container-instances-container-groups.md) with an application container and a sidecar container running an SSL provider. By setting up a container group with a separate SSL endpoint, you enable SSL connections for your application without changing your application code.
1010

11-
You set up a container group consisting of two containers:
11+
You set up an example container group consisting of two containers:
1212
* An application container that runs a simple web app using the public Microsoft [aci-helloworld](https://hub.docker.com/_/microsoft-azuredocs-aci-helloworld) image.
1313
* A sidecar container running the public [Nginx](https://hub.docker.com/_/nginx) image, configured to use SSL.
1414

15-
In this example, the container group only exposes port 443 for Nginx with its public IP address. Nginx routes HTTPS requests to the companion web app, which listens internally on port 80. You can adapt the example for container apps that listen on other ports.
15+
In this example, the container group only exposes port 443 for Nginx with its public IP address. Nginx routes HTTPS requests to the companion web app, which listens internally on port 80. You can adapt the example for container apps that listen on other ports. See [Next steps](#next-steps) for other approaches to enabling SSL in a container group.
1616

1717
[!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
1818

@@ -229,4 +229,10 @@ This article showed you how to set up an Nginx container to enable SSL connectio
229229

230230
While this article uses Nginx in the sidecar, you can use another SSL provider such as [Caddy](https://caddyserver.com/).
231231

232-
Another approach to enabling SSL in a container group is to deploy the group in an [Azure virtual network](container-instances-vnet.md) with an [Azure application gateway](../application-gateway/overview.md). The gateway can be set up as an SSL endpoint. See a sample [deployment template](https://github.com/Azure/azure-quickstart-templates/tree/master/201-aci-wordpress-vnet) you can adapt to enable SSL termination on the gateway.
232+
If you deploy your container group in an [Azure virtual network](container-instances-vnet.md), you can consider other options to enable an SSL endpoint for a backend container instance, including:
233+
234+
* [Azure Functions Proxies](../azure-functions/functions-proxies.md)
235+
* [Azure API Management](../api-management/api-management-key-concepts.md)
236+
* [Azure Application Gateway](../application-gateway/overview.md)
237+
238+
To use an application gateway, see a sample [deployment template](https://github.com/Azure/azure-quickstart-templates/tree/master/201-aci-wordpress-vnet).

0 commit comments

Comments
 (0)