Azure Container Instances (ACI) allows you to run Docker containers in a managed, serverless cloud environment, without having to set up VMs, clusters, or orchestrators.
This article introduces how confidential containers on Azure Container Instances (ACI) can enable you to secure your workloads running in the cloud. This article provides background about the feature set, scenarios, limitations, and resources. Confidential containers on Azure Container Instances enable customers to run Linux containers within a hardware-based and attested Trusted Execution ...
Confidential containers on ACI enables fast and easy deployment of containers natively in Azure and with the ability to protect data and code in use thanks to AMD EPYC™ processors with confidential computing capabilities. This is because your container (s) runs in a hardware-based and attested Trusted Execution Environment (TEE) without the need to adopt a specialized programming model and ...
The ACI service recommends applying observability solutions such as Application Insights SDK, container group metrics, and container group logs to determine why the application experienced issues. Second, customers may experience restarts initiated by the ACI infrastructure due to maintenance events.
ACI is a great solution for any scenario that can operate in isolated container. ACI provides fast start-up times, hyper-visor level security, custom container sizes, and more. The following information helps you determine if Azure Container Instances is best for your scenario.
Note For this quickstart, you use default settings to deploy the public Microsoft aci-helloworld:latest image. This sample Linux image packages a small web app written in Node.js that serves a static HTML page. You can also bring your own container images stored in Azure Container Registry, Docker Hub, or other registries.