├── .gitignore ├── Day-01 ├── 01-basics.md └── 02-important-concepts.md ├── Day-02 ├── 01-regions.md └── 02-IaaS-PaaS-SaaS.md ├── Day-03 └── 01-basics.md ├── Day-04 ├── 01-virtualization.md ├── 02-vm-types.md └── 03-useful-links.md ├── Day-05 └── README.md ├── Day-06 └── README.md ├── LICENSE └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | # If you prefer the allow list template instead of the deny list, see community template: 2 | # https://github.com/github/gitignore/blob/main/community/Golang/Go.AllowList.gitignore 3 | # 4 | # Binaries for programs and plugins 5 | *.exe 6 | *.exe~ 7 | *.dll 8 | *.so 9 | *.dylib 10 | 11 | # Test binary, built with `go test -c` 12 | *.test 13 | 14 | # Output of the go coverage tool, specifically when used with LiteIDE 15 | *.out 16 | 17 | # Dependency directories (remove the comment below to include it) 18 | # vendor/ 19 | 20 | # Go workspace file 21 | go.work 22 | -------------------------------------------------------------------------------- /Day-01/01-basics.md: -------------------------------------------------------------------------------- 1 | # Basics of Cloud Computing 2 | 3 | ## What is Cloud ? 4 | 5 | In simpler terms, imagine the cloud as a vast, virtual space where you can store files, run software, and access various services over the internet. 6 | 7 | It's like having a powerful computer somewhere out there on the web that you can use for tasks without needing to own or physically manage the hardware. This allows users to access data and applications from anywhere with an internet connection. 8 | 9 | ## What is Cloud Computing ? 10 | 11 | Cloud computing is a technology model that involves the delivery of computing services over the internet. Instead of owning and maintaining physical servers and infrastructure, users can access and use computing resources, applications, and storage provided by either third-party service providers (public cloud) or their own organization (private cloud) through the internet. These services are hosted in data centers located around the world. 12 | 13 | In essence, cloud computing can involve both third-party providers (public cloud) and an organization's internal resources (private cloud). The distinction lies in whether the computing resources are shared among multiple customers (public cloud) or dedicated to a single organization (private cloud). The flexibility of cloud computing allows organizations to choose the deployment model that best aligns with their needs and requirements. 14 | 15 | ## Public Cloud: 16 | 17 | **Who Uses It:** Everyone, like individuals, businesses, and organizations. 18 | 19 | **What It's Like:** Imagine a giant, shared computer space on the internet. It's like using apps, storing files, or doing tasks on the internet that anyone can access. 20 | 21 | **Example:** Think of Google Drive or Amazon Web Services (AWS). 22 | 23 | ## Private Cloud: 24 | 25 | **Who Uses It:** One specific organization or business. 26 | 27 | **What It's Like:** Picture having your own personal, private computer space. It's like a digital clubhouse where only you and your team have access. Others can't just drop in. 28 | 29 | **Example:** A company using its own server for all its digital needs. 30 | 31 | ## Hybrid Cloud: 32 | 33 | **Who Uses It:** A mix of everyone, depending on needs. 34 | 35 | **What It's Like:** It's like having your private computer space, but sometimes you use the shared internet space too. 36 | 37 | **Example:** A business storing sensitive data in its private space but using the public cloud for extra storage or specific tasks. 38 | 39 | ### In a Nutshell: 40 | 41 | **Public Cloud:** Shared digital space for everyone. 42 | 43 | **Private Cloud:** Your own exclusive digital space. 44 | 45 | **Hybrid Cloud:** Using both your private space and the shared online space when needed. -------------------------------------------------------------------------------- /Day-01/02-important-concepts.md: -------------------------------------------------------------------------------- 1 | # Vocabulary in Cloud Computing 2 | 3 | ## Virtualization 4 | 5 | Virtualization is the process of creating a virtual version of something, such as an operating system, server, storage, or network resources. 6 | 7 | ## Virtual Machine 8 | 9 | A Virtual Machine (VM) is a software-based emulation of a physical computer. It allows running multiple operating systems on a single physical machine. 10 | 11 | ## API (Application Programming Interface) 12 | 13 | API is a set of rules and protocols that allows different software applications to communicate with each other. It defines how software components should interact. 14 | 15 | ## Regions 16 | 17 | Regions in cloud computing refer to geographic locations where cloud providers have data centers. Each region contains multiple data centers. 18 | 19 | ## Availability Zones 20 | 21 | Availability Zones are isolated locations within a region that have their own power, cooling, and networking. They are designed to provide high availability and fault tolerance. 22 | 23 | ## Scalability 24 | 25 | Scalability is the ability of a system to handle an increasing amount of work or its potential to be enlarged to accommodate that growth. 26 | 27 | ## Elasticity 28 | 29 | Elasticity in cloud computing refers to the ability to dynamically scale resources up or down based on demand. 30 | 31 | ## Agility 32 | 33 | Agility is the capability of quickly and easily adapting to changes. In the context of cloud computing, it involves the rapid deployment of resources and applications. 34 | 35 | ## High Availability 36 | 37 | High Availability (HA) ensures that a system or application is operational and accessible for a high percentage of time, typically 99.9% or higher. 38 | 39 | ## Fault Tolerance 40 | 41 | Fault Tolerance is the ability of a system to continue operating without interruption in the presence of hardware or software failures. 42 | 43 | ## Disaster Recovery 44 | 45 | Disaster Recovery involves the planning and processes for restoring and recovering data and systems after a natural or human-induced disaster. 46 | 47 | ## Load Balancing 48 | 49 | Load Balancing is the distribution of network traffic or computing workload across multiple servers to ensure no single server is overwhelmed. 50 | -------------------------------------------------------------------------------- /Day-02/01-regions.md: -------------------------------------------------------------------------------- 1 | # Exploring Regions and Availability Zones in Azure 2 | 3 | ## Regions in Azure 4 | 5 | Azure is a cloud computing platform provided by Microsoft, and it is globally distributed across multiple geographic locations known as regions. Each Azure region is a set of data centers deployed within a defined geographic area, and it is designed to provide low-latency access to Azure services for users and applications in that region. 6 | 7 | ### Key Points about Azure Regions: 8 | 9 | - **Global Presence:** Azure has a vast global presence with data centers strategically located around the world. 10 | 11 | - **Region Pairing:** Azure regions are often paired for data redundancy and resiliency. In the event of a regional failure, paired regions can help ensure continuity. 12 | 13 | - **Compliance and Data Residency:** Organizations can choose specific regions to comply with data residency requirements and regulations. 14 | 15 | ## Availability Zones in Azure 16 | 17 | Azure Availability Zones are part of Azure's high-availability architecture, providing redundancy and resiliency for applications and data. Each Azure region is divided into multiple Availability Zones, which are essentially unique physical locations with independent power, cooling, and networking. 18 | 19 | ### Key Points about Azure Availability Zones: 20 | 21 | - **High Availability:** By distributing resources across Availability Zones, Azure ensures that applications remain available even in the face of localized failures, such as hardware or network failures. 22 | 23 | - **Fault Isolation:** Availability Zones are designed to be isolated from one another, meaning a failure in one zone does not impact the availability of resources in other zones. 24 | 25 | - **Multi-Data Center Architectures:** Availability Zones are essential for designing and deploying multi-data center architectures in Azure. 26 | 27 | ## How to Choose Regions and Availability Zones 28 | 29 | When deploying resources in Azure, it's crucial to consider factors such as: 30 | 31 | - **Proximity to Users:** Choose a region that is geographically close to your users to minimize latency. 32 | 33 | - **Compliance Requirements:** Ensure that the chosen region complies with regulatory and data residency requirements. 34 | 35 | - **High Availability Needs:** If high availability is a priority, distribute resources across multiple Availability Zones within a region. 36 | 37 | - **Disaster Recovery Planning:** Leverage region pairing for effective disaster recovery planning. 38 | 39 | 40 | -------------------------------------------------------------------------------- /Day-02/02-IaaS-PaaS-SaaS.md: -------------------------------------------------------------------------------- 1 | # IaaS vs PaaS vs SaaS models in Azure 2 | 3 | ## Infrastructure as a Service (IaaS) 4 | 5 | IaaS is a cloud computing model that provides virtualized computing resources over the internet. In Azure, IaaS offerings include virtual machines, storage, and networking components. Users have more control over the infrastructure but are responsible for managing and maintaining the operating system, middleware, and applications. 6 | 7 | ### Key Characteristics of Azure IaaS: 8 | 9 | - **Scalability:** Easily scale resources up or down based on demand. 10 | 11 | - **Full Control:** Users have control over the underlying infrastructure, including operating systems and applications. 12 | 13 | - **Flexibility:** IaaS is suitable for a wide range of applications, offering flexibility in terms of technology stack. 14 | 15 | ## Platform as a Service (PaaS) 16 | 17 | PaaS is a cloud computing model that provides a platform allowing customers to develop, run, and manage applications without dealing with the complexity of underlying infrastructure. In Azure, PaaS offerings include Azure App Service, Azure SQL Database, and Azure Functions. 18 | 19 | ### Key Characteristics of Azure PaaS: 20 | 21 | - **Simplified Development:** Developers can focus on coding and application logic, while Azure manages the underlying infrastructure. 22 | 23 | - **Automatic Scaling:** PaaS offerings often include built-in scaling capabilities, automatically adjusting resources based on demand. 24 | 25 | - **Reduced Maintenance:** Azure handles tasks like patching, updates, and maintenance, freeing up resources for innovation. 26 | 27 | ## Software as a Service (SaaS) 28 | 29 | SaaS is a cloud computing model that delivers software applications over the internet. Users can access the software through a web browser without the need for installation or maintenance. In Azure, SaaS offerings include Microsoft 365, Dynamics 365, and many third-party applications. 30 | 31 | ### Key Characteristics of Azure SaaS: 32 | 33 | - **Accessibility:** Access software applications from any device with an internet connection. 34 | 35 | - **Managed by Providers:** SaaS providers handle maintenance, updates, and security, reducing the burden on end-users. 36 | 37 | - **Subscription-Based:** SaaS applications are typically offered on a subscription basis, allowing users to pay for what they use. 38 | 39 | ## Choosing the Right Model in Azure 40 | 41 | When deciding between IaaS, PaaS, and SaaS in Azure, consider factors such as: 42 | 43 | - **Development Needs:** Choose PaaS for streamlined development, IaaS for more control, and SaaS for off-the-shelf solutions. 44 | 45 | - **Maintenance Preferences:** If you want to minimize maintenance tasks, opt for PaaS or SaaS. 46 | 47 | - **Resource Control:** Choose IaaS if you need more control over the underlying infrastructure. 48 | 49 | - **Cost Considerations:** Evaluate pricing models for each service and choose based on your budget and usage patterns. -------------------------------------------------------------------------------- /Day-03/01-basics.md: -------------------------------------------------------------------------------- 1 | # Azure Resources 2 | 3 | Azure resources are the building blocks of your cloud infrastructure in Microsoft Azure. These resources can be virtual machines, databases, storage accounts, or any other service offered by Azure. Each resource is a manageable item in Azure, and they are provisioned and managed individually. 4 | 5 | ## Resource Groups in Azure 6 | 7 | A **Resource Group** in Azure is a logical container for resources that share the same lifecycle, permissions, and policies. It helps you organize and manage related Azure resources efficiently. Resources within a group can be deployed, updated, and deleted together as a single management unit. 8 | 9 | ### Key Points about Resource Groups: 10 | 11 | - **Lifecycle Management:** Resources within a group can be managed collectively, making it easy to handle deployments, updates, and deletions. 12 | 13 | - **Resource Organization:** Grouping resources based on projects, environments, or applications helps keep your Azure environment well-organized. 14 | 15 | - **Role-Based Access Control (RBAC):** Permissions and access control are applied at the resource group level, allowing you to manage who can access and modify resources within a group. 16 | 17 | ## Azure Resource Manager (ARM) Overview 18 | 19 | **Azure Resource Manager (ARM)** is the deployment and management service for Azure. It provides a consistent management layer that enables you to deploy resources with declarative templates. ARM templates describe the resources you need and their configurations, allowing you to deploy and update resources in a predictable manner. 20 | 21 | ### Key Features of Azure Resource Manager: 22 | 23 | - **Template-Based Deployment:** ARM uses JSON templates to define the infrastructure and configuration of your Azure resources. This enables repeatable and consistent deployments. 24 | 25 | - **Dependency Management:** ARM automatically handles dependencies between resources, ensuring they are deployed in the correct order. 26 | 27 | - **Rollback and Roll-forward:** In case of deployment failures, ARM can automatically roll back changes to maintain the desired state, or roll forward to the last known good state. 28 | 29 | - **Tagging and Categorization:** You can use tags to label and categorize resources, making it easier to manage and organize your Azure environment. 30 | 31 | **Note:** Understanding Azure resources, resource groups, and Azure Resource Manager is fundamental to effectively utilize and manage your resources in the Azure cloud. 32 | 33 | -------------------------------------------------------------------------------- /Day-04/01-virtualization.md: -------------------------------------------------------------------------------- 1 | # Virtualization: An In-Depth Explanation 2 | 3 | ## Background 4 | 5 | In traditional computing, a single physical server runs a single operating system, and applications are installed directly on that OS. This approach has limitations, such as underutilization of hardware resources, difficulty in managing multiple servers, and lack of flexibility in scaling. 6 | 7 | **Virtualization** addresses these challenges by introducing a layer of abstraction between the hardware and the operating system. It enables the creation of multiple virtual instances, each running its own operating system and applications, on a single physical server. This technology has become fundamental in modern data centers and cloud computing environments. 8 | 9 | ## Components of Virtualization 10 | 11 | 1. **Hypervisor (Virtual Machine Monitor):** 12 | - The hypervisor is a crucial component of virtualization. It sits between the hardware and the operating systems, managing and allocating resources to virtual machines (VMs). 13 | - There are two types of hypervisors: Type 1 (bare-metal) runs directly on the hardware, while Type 2 (hosted) runs on top of an existing operating system. 14 | 15 | 2. **Virtual Machines (VMs):** 16 | - VMs are the instances created by the hypervisor. Each VM operates as an independent computer with its own virtualized hardware, including CPU, memory, storage, and network interfaces. 17 | - Multiple VMs can run on a single physical server, allowing for efficient resource utilization. 18 | 19 | ## Key Concepts in Virtualization 20 | 21 | 1. **Server Virtualization:** 22 | - In server virtualization, a physical server is divided into multiple VMs, each running its own OS. This allows for better utilization of hardware resources and easier management of servers. 23 | 24 | 2. **Resource Pooling:** 25 | - Virtualization enables the pooling of physical resources, such as CPU, memory, and storage. These resources can be dynamically allocated to VMs based on demand. 26 | 27 | 3. **Isolation:** 28 | - VMs operate independently of each other. This isolation ensures that issues in one VM do not affect others, providing a more secure and stable environment. 29 | 30 | 4. **Snapshotting and Cloning:** 31 | - Virtualization allows the creation of snapshots, which capture the state of a VM at a specific point in time. This facilitates easy backup and recovery. Cloning enables the rapid duplication of VMs for scalability. 32 | 33 | ## Benefits of Virtualization 34 | 35 | 1. **Server Consolidation:** 36 | - Multiple VMs can run on a single physical server, reducing the need for a large number of physical machines. This leads to cost savings and energy efficiency. 37 | 38 | 2. **Flexibility and Scalability:** 39 | - Virtualization allows for the easy creation, modification, and scaling of VMs. This flexibility is essential in dynamic computing environments. 40 | 41 | 3. **Disaster Recovery:** 42 | - Virtualization simplifies disaster recovery by enabling the quick restoration of VMs from snapshots or backups. 43 | 44 | 4. **Resource Optimization:** 45 | - Resources can be allocated and deallocated dynamically based on workload, optimizing resource utilization. 46 | 47 | 5. **Testing and Development:** 48 | - Virtualization provides a sandbox for testing and development. VMs can be easily created, modified, and discarded without affecting the production environment. -------------------------------------------------------------------------------- /Day-04/02-vm-types.md: -------------------------------------------------------------------------------- 1 | # Types of Virtual Machines on Azure 2 | 3 | Azure provides a variety of virtual machine (VM) offerings to cater to different workload requirements. Each VM type is designed with specific hardware configurations to meet diverse performance and scalability needs. 4 | 5 | ## General Purpose VMs 6 | 7 | **Example: Standard_D2s_v3** 8 | 9 | - **Description:** General-purpose VMs are well-balanced machines suitable for a variety of workloads. They offer a good balance of CPU-to-memory ratio and are suitable for development, testing, and small to medium-sized databases. 10 | 11 | - **Use Case:** Hosting websites, lightweight applications, or development and testing environments. 12 | 13 | ## Compute Optimized VMs 14 | 15 | **Example: Standard_F2s_v2** 16 | 17 | - **Description:** Compute optimized VMs are designed for compute-intensive workloads that require high CPU power. They provide a high CPU-to-memory ratio, making them suitable for data analytics and computational tasks. 18 | 19 | - **Use Case:** Batch processing, gaming applications, and other CPU-intensive workloads. 20 | 21 | ## Memory Optimized VMs 22 | 23 | **Example: Standard_E16s_v3** 24 | 25 | - **Description:** Memory optimized VMs are tailored for memory-intensive applications. They provide a high memory-to-CPU ratio, making them suitable for databases, in-memory caching, and analytics. 26 | 27 | - **Use Case:** Running large databases, in-memory caching, and analytics applications. 28 | 29 | ## Storage Optimized VMs 30 | 31 | **Example: Standard_L8s_v2** 32 | 33 | - **Description:** Storage optimized VMs are designed for workloads that require high storage throughput and I/O performance. They provide high local disk throughput, making them suitable for big data and large databases. 34 | 35 | - **Use Case:** Big data applications, data warehousing, and large-scale databases. 36 | 37 | ## GPU VMs 38 | 39 | **Example: Standard_NC6s_v3** 40 | 41 | - **Description:** GPU (Graphics Processing Unit) VMs are equipped with powerful graphics processors, suitable for graphics-intensive applications and parallel processing tasks. 42 | 43 | - **Use Case:** Machine learning, graphics rendering, and simulations that require GPU acceleration. 44 | 45 | ## High-Performance Compute VMs 46 | 47 | **Example: Standard_H16r** 48 | 49 | - **Description:** High-Performance Compute VMs are designed for demanding, parallel processing and high-performance computing (HPC) applications. 50 | 51 | - **Use Case:** Simulations, modeling, and scenarios that require massive parallel processing. 52 | 53 | ## Burstable VMs 54 | 55 | **Example: B1s** 56 | 57 | - **Description:** Burstable VMs provide a baseline level of CPU performance with the ability to burst above the baseline for a certain period. They are cost-effective for workloads with varying CPU usage. 58 | 59 | - **Use Case:** Development and testing environments, small websites, and applications with variable workloads. -------------------------------------------------------------------------------- /Day-04/03-useful-links.md: -------------------------------------------------------------------------------- 1 | # References 2 | 3 | ### Azure Virtual Machine Series 4 | https://azure.microsoft.com/en-in/pricing/details/virtual-machines/series/ 5 | 6 | ### Jenkins Installation Steps 7 | https://github.com/iam-veeramalla/Jenkins-Zero-To-Hero 8 | 9 | ### Download Git Bash 10 | https://git-scm.com/downloads 11 | -------------------------------------------------------------------------------- /Day-05/README.md: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ShivaSRK0/Azure-zero-to-hero-by-Abhishek-veeramalla/e181a1cb2c95f8133a2d4cc26753785ee2f13fd7/Day-05/README.md -------------------------------------------------------------------------------- /Day-06/README.md: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ShivaSRK0/Azure-zero-to-hero-by-Abhishek-veeramalla/e181a1cb2c95f8133a2d4cc26753785ee2f13fd7/Day-06/README.md -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2023 Abhishek Veeramalla 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Azure Zero to Hero Course 2 | 3 | ![Add a heading(13)](https://github.com/iam-veeramalla/Azure-zero-to-hero/assets/43399466/c64cb363-661d-4411-8a30-9cb55255ba30) 4 | 5 | ## If you like the content, Don't forget to give this repository a :star: 6 | 7 | ## Day 1: Understanding Cloud Concepts, Vocabulary and Terminology 8 | - What is cloud ? 9 | - What is the difference between public, private and hybrid cloud ? 10 | - What is cloud computing ? 11 | - Vocabulary 12 | - Virtualization 13 | - Virtual Machine 14 | - API 15 | - Regions 16 | - Avalaibility Zones 17 | - Scalability 18 | - Elasticity 19 | - Agility 20 | - High Availability 21 | - Fault Tolerance 22 | - Disaster Recovery 23 | - Load Balancing 24 | 25 | ## Day 2: Getting Started with Azure 26 | - Creating an Account with Azure 27 | - Exploring Regions and Availability Zones in Azure 28 | - IaaS vs PaaS vs SaaS models in Azure 29 | 30 | ## Day 3: Azure Resources,Resource Groups and Resource Manager 31 | - Resources in Azure 32 | - Resource Groups in Azure 33 | - Azure Resource Manager Overview 34 | 35 | ## Day 4: Azure Virtual Machines 36 | - Virtualization recap 37 | - Create a Virtual Machine in Azure 38 | - Connect to the Virtual Machine 39 | - Deploy your first application on an Azure VM 40 | - Virtual Machine ScaleSets for Autoscaling 41 | 42 | ## Day 5: Azure Networking Services 43 | - Overview of Azure Networking (Real World Example) 44 | - Virtual Network 45 | - Subnets, CIDR 46 | - Routes and Route Tables 47 | - Network Security Groups(NSGs) 48 | - Application Security Groups(ASGs) 49 | 50 | ## Day 6: Advanced Networking Services 51 | - Azure App Gateway & WAF 52 | - Azure Load Balancer 53 | - Azure DNS 54 | - Azure Firewall 55 | - Virtual Network Peering and VNet Gateway 56 | - VPN Gateway 57 | 58 | ## Day 7: Azure Interview Questions (Compute and Networking) 59 | - Interview Questions on the topics covered till Day 6 60 | - Cloud computing concepts 61 | - Azure Basics 62 | - Azure Networking 63 | 64 | ## Day 8: Deploying a two tier application on Azure - (PROJECT 1) 65 | - Practical Hands on video that explains 66 | - How to set up the networking for two tier app 67 | - How to deploy the two tier applcition on Azure VMs with Networking. 68 | - Overview of the setup and troubleshooting. 69 | 70 | ## Day 9: Azure Storage Services 71 | - Types of Azure Storage Services 72 | - Use Cases and Demonstrations 73 | 74 | ## Day 10: Command Line Interface for Azure 75 | - Azure CLI Deep Dive 76 | - Using Azure CLI to create resources on Azure 77 | - Usecases and multiple references 78 | 79 | ## Day 11: Azure Resource Manager 80 | - Azure Resource Manager and Azure Templates Deep Dive 81 | 82 | ## Day 12: Azure Authentication and Identity Management 83 | - Authentication Services in Azure 84 | - Identity Access Management (IAM) 85 | - Implementing RBAC 86 | - Best Practices for RBAC 87 | 88 | ## Day 13: Azure Cloud Watch(Monitor) and Monitoring Services 89 | - Monitoring Overview 90 | - Setting Up Monitoring in Azure 91 | 92 | ## Day 14: Introduction to Azure DevOps 93 | - Overview of Azure DevOps 94 | - Introduction to the Azure DevOps services 95 | - Setting Up Projects and Repositories 96 | 97 | ## Day 15: Azure DevOps - CI Setup - (PROJECT 2) 98 | - Implementing Continuous Integration (CI) 99 | 100 | ## Day 16: Azure DevOps - CD Setup - (PROJECT 3) 101 | - Implementing Continuous Deployment (CD) 102 | 103 | ## Day 17: Azure Kubernetes Services(AKS Deep Dive) - (PROJECT 4) 104 | - Hands on sessions on AKS 105 | - Deploying applciation to AKS 106 | - Expose the application with Ingress configuration on AKS 107 | 108 | ## Day 18: Deploying a Three Tier architecture E-commerce (8 Services, 2 Databases) on AKS - (PROJECT 5) 109 | - Understand what is three tier architecuture 110 | - How different services connect to each other in three tier architecture 111 | - How to create Dockerfiles for each service ? 112 | - How to create Deployment, Service and Ingress 113 | - How does Ingress controller work ? 114 | - Expose the three tier application to end users. 115 | 116 | ## Day 19: Azure DevOps Interview Questions 117 | - Beginner level Azure DevOps Interview Q&A 118 | - Advanced level Azure DevOps Interview Q&A 119 | 120 | ## Day 20: Azure Key Vault 121 | - Secrets Management with Key Vault 122 | - Security Best Practices 123 | 124 | ## Day 21: Azure Serverless 125 | - Understanding Azure Serverless Services 126 | - Going Serverless with Azure 127 | 128 | ## Day 22: Cloud Management Strategies for Azure - (PROJECT 6) 129 | - Cost Optimization 130 | - Scaling and Performance Optimization 131 | 132 | ## Day 23: Complicance on Azure - (PROJECT 7) 133 | - Azure Resource Tags 134 | - Using the Serverless Functions to implement the compliance requirements on Azure 135 | 136 | ## Day 24: Manage Azure Resources using Terraform - (PROJECT 8) 137 | - How to connect Azure with Terraform 138 | - How to create resources on Azure with Terraform 139 | - State file management of Terraform in Azure 140 | - Best Practices 141 | 142 | ## Day 25: Azure Interview Preparion 143 | - Review of Key Concepts 144 | - Interviews Questions and Practice Sessions 145 | --------------------------------------------------------------------------------