Book Image

Hands-On Linux Administration on Azure

By : Frederik Vos
Book Image

Hands-On Linux Administration on Azure

By: Frederik Vos

Overview of this book

Azure’s market share has increased massively and enterprises are adopting it rapidly, while Linux is a widely-used operating system and has proven to be one of the most popular workloads on Azure. It has thus become crucial for Linux administrators and Microsoft professionals to be well versed with managing Linux workloads in an Azure environment. With this guide, system administrators will be able to deploy, automate, and orchestrate containers in Linux on Azure. The book follows a hands-on approach to help you understand DevOps, monitor Linux workloads on Azure and perform advanced system administration. Complete with systematic explanations of concepts, examples and self-assessment questions, the chapters will give you useful insights into Linux and Azure. You’ll explore some of Linux’s advanced features for managing multiple workloads and learn to deploy virtual machines (VMs) in Azure. Dedicated sections will also guide you with managing and extending Azure VMs’ capabilities and understanding automation and orchestration with Ansible and PowerShell DSC. In later chapters, you’ll cover useful Linux troubleshooting and monitoring techniques that will enable you to maintain your workload on Azure. By the end of this book, you’ll be able to make the most out of Azure’s services to efficiently deploy and manage your Linux workloads.
Table of Contents (14 chapters)

Systemd security

The systemd units can also provide an extra layer of security. You can add several options to your unit file to make your unit more secure.

Just edit the unit file using systemctl --edit and add the security measures. For instance, execute the following:

sudo systemctl --edit sshd

Add the following lines:

[Service]
ProtectHome=read-only

Save the file, reread the systemctl configuration, and restart sshd:

sudo systemctl daemon-reload

sudo systemctl restart sshd

Now log in again with your SSH client and try to save a file in your home. It will fail because it's a read-only filesystem:

Restricting access to the filesystem

The ProtectHome parameter is a very interesting one. The following values are available...