Explore projects

How to create an azure blob storage to be used for cache for GitLab Runner

Full-featured and highly configurable SFTP, HTTP/S, FTP/S and WebDAV server - S3, Google Cloud Storage, Azure Blob

"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files

Team Adapter: Itential integration with Azure Blob Storage

"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files

Hands-on DevOps project that provisions a two-tier web application on Azure using Terraform and Ansible. Terraform builds a VNet with public/private subnets, Linux VMs (web + PostgreSQL DB), NSGs, a public Load Balancer, VM Scale Set with CPU-based autoscaling, and an Azure Blob Storage account for image hosting. Ansible configures the DB server (PostgreSQL install, access rules, DB/user creation) and app server (Flask app deployment with virtualenv, health checks, and log collection) using a dynamic inventory generated from Terraform outputs. The Flask application exposes form and JSON endpoints for writing records to PostgreSQL, serves an image from Azure Blob Storage, and provides a /healthz endpoint to verify database connectivity and write health status to healthz.log.

Manages storage resources on Azure, such as storage accounts, blob containers, file shares, etc.

This project demonstrates how to use Microsoft Entra ID (Azure AD) identities to securely access Azure Blob Storage with Terraform-provisioned resources.

It covers three identity types:

Azure AD User (Human Identity): Interactive login with MFA to access quote.txt.

Service Principal (Workload Identity): Programmatic login using credentials to fetch the blob.

Managed Identity (Workload Identity): Windows VM authenticates to Azure Storage without secrets.

What’s Included

Terraform scripts to provision Entra ID users, service principals, managed identities, storage accounts, blobs, role assignments, and a test VM.

Examples of logging in via Azure CLI and PowerShell.

Step-by-step instructions for testing each identity flow.

Key takeaway: The repo shows how different Entra ID identities (human, workload, and device) can all securely authenticate and access the same storage resource.

REST API .NET 8 use of design patterns own implementation of the mediator Azure : ServiceBus, Blobs

"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files

Easily manage the contents of your storage account with Azure Storage Explorer. Upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities. Gain easy access to manage your virtual machine disks. Work with either Azure Resource Manager or classic storage accounts, plus manage and configure cross-origin resource sharing (CORS) rules.

"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files