Merge pull request #99346 from dlepow/acifresh3

[ACI] TLS and emptydir

Author: PRMerger20

articles/container-instances/container-instances-overview.md

@@ -16,14 +16,20 @@ Azure Container Instances is a great solution for any scenario that can operate
 
 Containers offer significant startup benefits over virtual machines (VMs). Azure Container Instances can start containers in Azure in seconds, without the need to provision and manage VMs.
 
-## Public IP connectivity and DNS name
+## Container access
 
-Azure Container Instances enables exposing your containers directly to the internet with an IP address and a fully qualified domain name (FQDN). When you create a container instance, you can specify a custom DNS name label so your application is reachable at *customlabel*.*azureregion*.azurecontainer.io.
+Azure Container Instances enables exposing your container groups directly to the internet with an IP address and a fully qualified domain name (FQDN). When you create a container instance, you can specify a custom DNS name label so your application is reachable at *customlabel*.*azureregion*.azurecontainer.io.
+
+Azure Container Instances also supports executing a command in a running container by providing an interactive shell to help with application development and troubleshooting. Access takes places over HTTPS, using TLS to secure client connections.
+
+> [!IMPORTANT]
+> Starting January 13, 2020, Azure Container Instances will require all secure connections from servers and applications to use TLS 1.2. Support for TLS 1.0 and 1.1 will be retired.
 
 ## Hypervisor-level security
 
 Historically, containers have offered application dependency isolation and resource governance but have not been considered sufficiently hardened for hostile multi-tenant usage. Azure Container Instances guarantees your application is as isolated in a container as it would be in a VM.
 
+
 ## Custom sizes
 
 Containers are typically optimized to run just a single application, but the exact needs of those applications can differ greatly. Azure Container Instances provides optimum utilization by allowing exact specifications of CPU cores and memory. You pay based on what you need and get billed by the second, so you can fine-tune your spending based on actual need.
@@ -32,7 +38,7 @@ For compute-intensive jobs such as machine learning, Azure Container Instances c
 
 ## Persistent storage
 
-To retrieve and persist state with Azure Container Instances, we offer direct [mounting of Azure Files shares](container-instances-mounting-azure-files-volume.md).
+To retrieve and persist state with Azure Container Instances, we offer direct [mounting of Azure Files shares](container-instances-mounting-azure-files-volume.md) backed by Azure Storage.
 
 ## Linux and Windows containers
 

articles/container-instances/container-instances-volume-emptydir.md

@@ -7,7 +7,7 @@ ms.date: 02/08/2018
 
 # Mount an emptyDir volume in Azure Container Instances
 
-Learn how to mount an *emptyDir* volume to share data between the containers in a container group in Azure Container Instances.
+Learn how to mount an *emptyDir* volume to share data between the containers in a container group in Azure Container Instances. Use *emptyDir* volumes as ephemeral caches for your containerized workloads.
 
 > [!NOTE]
 > Mounting an *emptyDir* volume is currently restricted to Linux containers. While we are working to bring all features to Windows containers, you can find current platform differences in the [overview](container-instances-overview.md#linux-and-windows-containers).
@@ -22,7 +22,7 @@ Some example uses for an *emptyDir* volume:
 * Checkpointing during long-running tasks
 * Store data retrieved by a sidecar container and served by an application container
 
-Data in an *emptyDir* volume is persisted through container crashes. Containers that are restarted, however, are not guaranteed to persist the data in an *emptyDir* volume.
+Data in an *emptyDir* volume is persisted through container crashes. Containers that are restarted, however, are not guaranteed to persist the data in an *emptyDir* volume. If you stop a container group, the *emptyDir* volume is not persisted.
 
 ## Mount an emptyDir volume