Posting articles about Microsoft Azure, cloud security, infrastructure as code, DevOps and site reliability engineering topics.
In the 2nd part of this 2 part series on securing Azure Container Apps Environment, we will look into a deployment example. We will make use of Azure Verified Modules as far as possible. Then we will cover some scenarios on how you can make this available to your development teams and how development teams can perform deployments of Azure Container Apps into the managed environment safely.
By now we all know Azure Container Apps is an amazing service, which provides us with a quick way to get up and running with the deployment of our containerized workloads. Azure Container Apps also gives us the opportunity of using containers at scale without the complexities of managing our own Kubernetes cluster. However, Azure Container apps is a configurable PaaS service and is not secure by default. In this article, which is part 01 of a series, I will cover some of the configuration options we have available to make our deployments more secure.
Why do I need this? - Using Docker Desktop for commercial use requires a license!
Docker Desktop is only free for small businesses with fewer than 250 employees AND less than $10 million in annual revenue. Docker Subscription Service Agreement
Dev Containers in Visual Studio Code are Docker containers used as full-featured development environments. They allow opening any folder inside a container, leveraging VS Code’s features. The contents of the dev container can be defined using a devcontainer.json file.
If you are a developer who works with Azure or wants to work with Azure, you might already be aware of the Azure Developer CLI (azd), a "new-ish" command-line tool that simplifies and enhances your Azure development experience. Lets run over some of the basics and some thoughts I have on how to make use of azd in a more "production ready" fashion.