Developing and deploying apps, managing infrastructure, monitoring, logging activity, and other development and operations procedures can all be automated using C-Sharp DevOps libraries. The programming language C# is frequently used to create various applications, including backend services, desktop, mobile, and web based. On the .NET platform, which offers a wealth of libraries and tools for creating, deploying, and maintaining applications, C# serves as the principal language for developing applications.  

Building and deploying apps, managing infrastructure, and monitoring and logging are just a few development and operations processes that can be automated in DevOps using C# libraries. By automating and streamlining their operations, these libraries can aid developers, and DevOps engineers in producing higher-quality software more rapidly and effectively. DevOps aims to make it possible for businesses to produce higher-quality, more reliable, and quicker software. A software development process called DevOps strongly emphasizes teamwork, communication, and integration between IT operations teams and software developers. Azure Microsoft offers a suite of DevOps tools and services for creating, delivering, and managing applications. It is a cloud-based platform that interfaces with various tools and services, such as GitHub, Azure, and Visual Studio, to offer a full range of DevOps capabilities. 

Check out the below list to find the best C# DevOps libraries for your application: 

Cloud computing Module 1:

The platforms that provides on-demand computing resources from application to data server to clients over the internet for a fee per use basis.

It's composed of:

5 essential characteristics are:

1. On-demand self-service: Clients are provided multiple services such as application, servers, storages etc.
2. Broad network access: Client is given access to all these resources using network.
3. Resource pooling: Gives providers economies of scale, which they pass on to their customers making cloud cost effective. Resources are dynamically assigned and reassigned.
4. Rapid Elasticity: You can use more resources when you need them, and scale back when you don't.
5. Measured services: You only pay for what you use or reserve.

3 Deployment models:

1. Public: Is when you use cloud services on open internet on cloud provider's hardware, but its usage is shared by other companies.
2. Private: Is when cloud services are used by a single organization. It could run on premises or owned, managed by service providers.
3. Hybrid: Is when you use the mixture of public and private cloud.

3 service models:

1. Infrastructure (IaaS) Infrastructure as a Services: You are provided with a complete infrastructure and physical resources such as networking, storages or servers without the worry to manage them.
2. Platform (PaaS): clients are provided with hardware and software tools required for developing and deploying application to users.
3. Application (SaaS): also known as on-demand software, where a subscription based application are hosted and provided to those who wish to pay for them or sometimes for free.

Pay-as-you-go: pay per use.

Key drivers for organization to move into cloud computing are:

agility, flexibility and competitiveness.

Key consideration for organizations:

Infrastructure and workload: The cost of building data center and purchasing servers can be reduced using cloud computing as you only need to pay-as-you-go.

SaaS and Development Platforms: Paying for application access costs less than buying COTS applications and later paying for upgrades etc.

Speed and productivity: getting the server to run in just few hours VS waiting for week for traditional server/platforms.

Benefits of Cloud adoption:

Flexibility:

Scale services up and down as per need, get customized applications, and access to resources from anywhere. It also provide security using private clouds, encryptions and API keys.

Efficiency:

You can get application quickly to market and not worry about its infrastructure or maintenance, also you can access it from any internet-connected devices and no data loss due to hardware failure.

strategic value:

Provides competitive advantage by providing most innovative technology to clients.

Challenges of cloud adoption:

Data security: loss or unavailability of data can cause business disruption.

governance, legal and regulatory issues

problem in choosing right deployment and service model for specific needs

partnering with right cloud providers.

Some cloud service providers:

Alibaba cloud (aliyun)

AWS amazon web services

Google cloud platform (GCP)

IBM cloud

Microsoft azure

Oracle cloud etc.

Business Case for Cloud:

The adoption of cloud technologies is enabling enterprises, big and small, to be agile, innovative, and competitive, and to create differentiated customer experiences. The question organizations are asking is not whether they should move to the cloud, rather what strategy they should adopt to move to the cloud.

Some case studies that demonstrate the impact businesses have created by adopting cloud:

• American Airlines adopting cloud technologies to deliver customer value rapidly across its enterprise
• UBank leveraging cloud platform services to give more control to their developers thereby removing barriers to innovation
• Bitly leveraging the scalability offered by cloud infrastructure for low-latency delivery to its geographically disbursed enterprise customers
• ActivTrades leveraging the infrastructure, storage, network, and security offerings on the cloud to accelerate execution and delivery of new functions in their online trading systems to their customers

Emerging Technologies accelerated by cloud:

Emerging technologies, powered by the cloud, are disrupting existing business models and creating unprecedented opportunities for businesses to grow, innovate, and create value for their customers.

Some case studies that demonstrate how the use of emerging technologies on the cloud is creating value for millions around the world:

• The use of the Internet of Things on the cloud to combat poaching of endangered rhinos in South Africa
• Artificial Intelligence on the cloud being leveraged to deliver unique digital experiences to millions of fans around the world by the United States Tennis Association
• Blockchain on the cloud helping farmers reduce waste by building traceability and transparency in the food supply chain
• The use of data analytics for driving predictive maintenance solutions for a city’s infrastructure by KONE

Cloud Computing Module 2:

Discusses service models:

IaaS: Provides networking, storage and computing resources to customer on pay-per-use basis. It also provides virtualization and hypervisor layer.

1. Here customer can use VMs that provides hypervisor, OSs and you can also install middleware, applications of your choice.
2. You can create a storage of you choice for backups and workloads.
3. It also provides tracking and monitoring the performance and usage of cloud resources and disaster recovery.
4. It helps organization in setting up test and development environment faster, and focus on productivity than on managing infrastructure.
5. It also provides business continuity and disaster recovery.
6. Also helps in fast deployment and scaling.
7. Also helps in data analysis.
8. Fastest growing cloud model today.

Concerns: Lack of transparency and dependency on third-party.

PaaS: Provides customers with a platform to manage, develop and deploy software without having to worry about the inner infrastructure.

Advantages:

• Scalability
• Faster time to market
• Agility

Risks:

• Cybersecurity threats
• Dependency on platform providers
• Lack of control over changing services etc.

Use cases:

• IoT
• API development
• Business analytics

Essential characteristics:

• Run-time environment
• Support services and APIs to help in development
• Rapid deployment
• High level of abstraction.

SaaS: provides customers to access cloud-based software against a subscription fee.

everything is managed by provides such as security, servers, databases etc.

• Benefits:
• reduces time from decision to value
• increase efficiency and productivity

Use Case:

• Minimal input
• Avoid upgrades, maintenance
• Reduce on-premises IT infrastructure

Concerns:

• Data safety and ownership
• third-party maintaining critical data
• require internet connection all time.

Deployment models:

Indicate where the infrastructure resides, who owns and manages it, and how cloud resources and services are made available to users. There are three main deployment models available on the cloud—Public, Private, and Hybrid.

Public cloud model, the service provider owns, manages, provisions, and maintains the physical infrastructure such as data centers, servers, networking equipment, and storage, with users accessing virtualized compute, networking and storage resources as services.

Advantages:

• On-demand resources
• Economies of scale
• Highly reliable

Concerns:

• Security
• Data sovereignty compliance

Use cases:

• Reduce time-to-market
• Fluctuating resource needs
• Backup for disaster recovery etc.
• greater accessibility

Private cloud model, the provider provisions the cloud infrastructure for exclusive use by a single organization. The private cloud infrastructure can be internal to the organization and run or on-premises. Or, it can be on a public cloud, as in case of Virtual Private Clouds (VPC){a private computing environment in a shared public cloud} and be owned, managed, and operated by the cloud provider.

Benefits:

• Scalability
• Internal control
• Reduced cost
• Controlled access and security

Use Case:

• Data and service import
• portability in software devolopment
• full control over critical security

Hybrid cloud model, an organization’s on-premise private cloud and third-party, public cloud is connected as a single, flexible infrastructure leveraging the features and benefits of both Public and Private clouds.

Types:

Mono: single provider

Multi: can be deployed on any public cloud infrastructure

composite: can move single application over multiple providers, thus greater flexibility.

• Benefits:
• Security and compliance
• Scalability and resilience
• Resource optimization
• Cost Saving

Module 3 Cloud infrastructure:

Overview:

• Customers need to plan the infrastructure architecture after choosing the cloud service model and type offered by vendors.
• The infrastructure layer consists of physical resources housed in Regions, Zones, and Data Centers.
• Cloud providers’ IT environment is distributed across many regions worldwide, and each region can have multiple Zones.
• Availability Zones (AZs) are distinct Data Centers with their own resources, which improves fault tolerance and decreases latency.
• Cloud providers offer several compute options: Virtual Servers, Bare Metal Servers, and Server-less computing resources.
• Information and data can be stored in many different types of storage options on the Cloud, including Block, File, and Object storage.
• Networking infrastructure in a cloud data center includes traditional networking hardware, router and switches, but also Software Defined Networking (SDN) options for easier network provisioning and management.
• Public and private network interfaces need to be set up when provisioning servers in the cloud.
• Security measures like Security Groups and Access Control Lists (ACLs) can be set up to control access to resources in the cloud.

Virtualization and Hypervisors:

Virtualization and its importance in cloud computing. It defines virtualization as the process of creating a virtual version of something using a hypervisor. There are two main types of hypervisors, Type 1 and Type 2, with Type 1 being the most secure and frequently used. Virtual machines (VMs) are software-based computers that are independent of one another and can run on a hypervisor. VMs are portable and can be moved from one hypervisor to another almost instantly. The key benefits of virtualization include cost savings, agility and speed, and lower downtime. Virtualization and VMs are essential components of cloud computing.

Virtual Machine and its Types:

• Virtual Machines (VMs) are known by various names depending on the cloud provider.
• Cloud providers offer VMs in various configurations and deployment options to cater to different use cases.
• When creating a virtual server, you specify the region, zone or data center, operating system, shared or dedicated VMs, and storage and networking options.
• Cloud providers offer predefined sizes and configurations for VMs ranging from single virtual core to multiple virtual cores with larger amounts of RAM to cater to different workloads.
• Public or shared cloud VMs are provider-managed, multi-tenant deployments that can be provisioned on-demand with predefined sizes.
• Transient or spot VMs take advantage of unused capacity in a cloud data center, are available at a discount, and are suitable for non-production workloads.
• Reserved virtual server instances allow you to reserve capacity and guarantee resources for future deployments and can lower costs compared to hourly or monthly instances.
• Dedicated hosts offer single-tenant isolation, maximum control over workload placement, and are used to meet compliance, regulatory requirements, or specific licensing terms.

Bare metal server:

• Bare metal server is a single-tenant, dedicated physical server that is managed by the cloud provider.
• Customer is responsible for administering and managing everything except OS on the server.
• Bare metal servers can be preconfigured or custom-configured as per customer specifications, including the processors, RAM, hard drives, specialized components, and the OS.
• Bare metal servers are fully customizable, expensive and intended for long-term, high-performance use in highly secure and isolated environments.
• Customers have full access and control of bare metal servers, which can be used for high-performance computing or data intense applications that require minimal latency-related delays.
• Bare metal servers work best for CPU and I/O intensive workloads, excel with highest performance and security, satisfy strict compliance requirements, and offer complete flexibility, control and transparency but come with added management and operational overhead.
• Virtual servers are rapidly provisioned, provide an elastic and scalable environment, and are low cost to use, but can be limited in throughput and performance due to sharing underlying hardware with other virtual servers.

Secure Networking in Cloud:

• Building a secure cloud networking presence is crucial as cloud environments gain greater adoption and digital data invites rapidly increasing cybersecurity threats.
• Building a cloud network is not much different from deploying a network in an on-premises data center, except that logical instances of networking elements are used in the cloud.
• Networking functions are delivered as a service in the cloud, rather than in the form of rack-mounted devices.
• Cloud networks are deployed in networking spaces that are logically separated segments of the networks using options such as Virtual private Cloud (VPC) that in turn can be divided into smaller segments called subnets.
• Cloud resources, such as VMs or Virtual Server Instances (VSIs), storage, network connectivity, and load balancers are deployed into subnets.
• Subnets are the main area where security is implemented in the cloud, with every subnet protected by Access Control Lists (ACLS) that serve as a subnet-level firewall.
• Security Groups are used to provide security at the instance level, such as VSIs.
• Public gateways are added to the network to enable user access to the application in the internet tier, while VPNs are used to securely connect on-premises resources to the cloud.
• Load Balancers are used to ensure availability of bandwidth for different applications.
• Dedicated high-speed connections between clouds and on-premises resources are a more secure and efficient way than public connectivity solutions.
• Cloud network building entails creating a set of logical constructs that deliver networking functionality similar to data center networks.

Containers:

• Containers are an executable unit of software that package application code, libraries, and dependencies in a common way to run anywhere, including desktop, traditional IT, and the cloud.
• Containers are small, fast, and portable, and do not require a guest OS in every instance, unlike virtual machines.
• Container technology has been around since 2008 when the Linux kernel introduced C groups and control groups.
• Container technology includes Docker, Cloud Foundry, Rocket, and other container runtimes.
• Containers solve compatibility issues that arise when applications developed on one machine are pushed into production on another.
• The containerization process involves creating a manifest that describes the container, creating an image, and creating the container itself.
• The container runs on a host operating system with a runtime engine instead of a hypervisor.
• Containers are much more lightweight than virtual machines, making it easier to deploy multiple containers.

Cloud Storage:

Overview to cloud storage:

• Cloud storage refers to saving data and files in the cloud.
• Cloud providers manage and maintain the storage infrastructure to ensure data accessibility.
• Cloud storage services allow for easy scalability and pay-as-you-go pricing.
• There are four main types of cloud storage: Direct Attached, File Storage, Block Storage, and Object Storage.
• Direct Attached storage is typically only used to store an operating system due to its limitations.
• File Storage is presented to compute nodes over an ethernet network and can be mounted or used on multiple servers.
• Block Storage is presented using high-speed fiber connections and is suitable for use with databases and applications where disk speed is important.
• IOPS refers to the speed of the storage and how quickly data can be read from or written to it.
• Persistence is a term used when provisioning File or Block storage and relates to what happens to the storage once the compute node it is attached to is terminated.
• Snapshots are a way to backup data in the cloud and are fast to create, don't require downtime, and record only changes to the data.
• Object Storage is accessed via an API and is the cheapest and slowest in terms of read and write speeds but is infinite in size to the end user, making it a great repository for unstructured data types.

File storage:

1. File Storage is a type of storage that needs to be attached to a compute node before it can be accessed and used.
2. File Storage is less expensive, more resilient to failure, and requires lesser disk management and maintenance than direct attached storage.
3. File Storage can provision larger amounts of storage and present it as a disk to a server.
4. File Storage is mounted from remote storage appliances, making it more secure and offering services such as encryption in transit and at rest.
5. File Storage is mounted to compute nodes via an ethernet network, which can sometimes affect its speed or bandwidth.
6. File Storage can typically be mounted onto more than one compute node at a time, making it an ideal solution for common storage requirements.
7. IOPS capacity is an important consideration when provisioning File Storage, as it determines the speed at which disks can write and read data and can affect the performance of applications.
8. File Storage is suitable for workloads where consistent high network speeds are not a requirement, such as departmental file shares or landing zones for incoming files.

Block storage:

• Block storage breaks files into chunks or blocks of data and stores each block separately under a unique address.
• Block storage must be attached to a compute node before it can be utilized for workloads.
• Block storage can be mounted from remote storage appliances, making it resilient to failure and more secure due to encryption services available on these appliances.
• Block storage is mounted as a volume to compute nodes using a dedicated fiber optic network, which is more expensive than the ethernet network used for file storage.
• Block storage is suitable for workloads that need low-latency storage, such as databases and mail servers, but not for workloads requiring disk sharing between compute nodes.
• IOPS capacity must be considered when provisioning block storage.
• Both block and file storage are taken from appliances maintained by the service provider and often include data encryption at rest and in transit.
• File storage is attached to compute nodes using an ethernet network and can be mounted onto multiple nodes at once.
• File storage is a good choice where file shares are required and cost is a factor, or where workloads do not require lightning fast connectivity to storage.
• Block storage is a good choice for applications that need consistent fast access to disk.
• The next video will cover Object Storage.

Object storage:

• Object Storage does not require connection to a compute node; data is managed through an API
• Object Storage is less expensive than other cloud storage options
• Object Storage is effectively infinite, as you only pay for the storage you use
• Object Storage is great for storing large amounts of unstructured data
• Buckets are used to store objects in a structurally flat way
• Objects can have metadata added to them for locating and accessing the data
• Service providers ensure sufficient storage capacity, resilience, and high availability
• Object Storage is suitable for static data such as text files, audio and video files, IOT data, virtual machine images, backup files, and data archives
• Object Storage is not suitable for running operating systems or applications such as databases
• Multiple buckets can be used, but buckets cannot be nested within each other
• Different types of buckets may be offered with different charges based on resilience, availability, and frequency of access.

CDN content delivery network:

• A Content Delivery Network (CDN) is a distributed server network that delivers temporarily stored, or cached, copies of website content to users based on their geographic location.
• CDN stores content in distributed locations, reducing the distance between website visitors and the website server.
• The main benefit of a CDN is that it makes the website faster by reducing the amount of time it takes to deliver the content.
• Users accessing a website from different parts of the world experience different round-trip times, which affects website speed.
• CDN places content delivery network endpoints in as many locations around the world as possible to reduce the distance between the user and the content.
• CDN retrieves content from the server and distributes it to users in different locations, reducing the amount of time it takes to retrieve the content.
• The reduction in distance between the user and content not only benefits the end-user but also indirectly reduces the load on the server and increases uptime and security.

Module 4:

Hybrid and multi cloud

• Hybrid Cloud connects an organization's private cloud and third-party public cloud into a single infrastructure for running applications
• Multi-cloud is a cloud adoption strategy that embraces a mix of cloud models from different service providers
• Hybrid Multi-cloud implies leveraging the best of cloud models and services across different service providers for seamless application and workload management
• Use cases for hybrid or multi-cloud include cloud scaling, building a composite cloud, modernizing reservation systems in the airline industry, and using data and AI to improve airline maintenance and reduce delays
• Cloud scaling allows businesses to scale up in response to user load and deprovision resources when no longer needed
• Building a composite cloud involves composing an application across multiple cloud environments to scale up portions in response to specific events while keeping other portions scaled individually
• Modernizing reservation systems involves creating new user experiences using mobile applications and cloud-based recommendation features
• Using data and AI in the airline industry allows businesses to take advantage of historical data to improve maintenance and reduce delays

Microservices:

• Microservices architecture is an approach in which a single application is composed of many loosely coupled and independently deployable, smaller components or services.
• These services have their own stack running on their own containers and communicate with one another over a combination of APIs, event streaming, and message brokers.
• Microservices enable developers to work more efficiently by developing and updating application components independently and using different stacks and runtime environments for different components.
• Microservices also allow for independent scaling of components, reducing waste and cost associated with having to scale entire applications.
• Cloud development platforms provide developers with an ecosystem of code that can be easily and securely integrated into applications.
• Microservices break down large applications into their core functions and are developed independently of one another, yet work together on the cloud development platform to create a functioning application.
• Microservices approach allows developers to quickly innovate applications in parallel and lets users focus on the things that really interest them.
• Microservices help businesses keep up and grow with their customers.
• The use case presented in the passage is about an online streaming media service called Dream Game that uses microservices to develop a better user experience for viewers.

Serverless:

• Serverless computing offloads responsibility for infrastructure management tasks to cloud providers, allowing developers to focus on code and business logic.
• Serverless computing runs code only on-demand on a per-request basis, scaling transparently with the number of requests being served.
• End users only pay for resources being used, never for idle capacity.
• Code is executed as individual functions inside a stateless container, with no prior execution context required for each request.
• Applications that qualify for a serverless architecture include short-running stateless functions, seasonal workloads with varying off-peak and peaks, production volumetric data with too much idle time, event-based processing, asynchronous request processing, and microservices that can be built as functions that are stateless.
• Serverless is well-suited for use cases around data and event processing, IoT, microservices, and mobile backends.
• Challenges worth considering include vendor dependency and potential lock-in, long-running processes that may be better suited for traditional server environments, and delays associated with starting up a new instance of a function to serve a new request.

Cloud Native applications:

• A cloud native application is an application developed specifically for the cloud environment, or an existing app that has been refactored and reconfigured with cloud native principles.
• A cloud native application consists of microservices that work together to comprise an application, yet each can be independently scaled and iterated through automation and orchestration processes.
• Microservices are often packaged in containers, which are executable units of software that can be run anywhere, enabling frequent, iterative improvement of cloud native applications without disrupting the end-user experience.
• Cloud native applications are unlike traditional, or monolithic applications, which are built out of one huge piece of software that tightly couples the user interface, business-logic layer, and data-layer.
• Cloud native apps can be used for anything that lives in the cloud and should be designed with standardized logging, events, and distributed tracing to enable innovation and business agility.
• Cloud native apps are about enterprise and engineering at scale, and the benefits include enabling innovation, business agility, and commoditization of the solution stack.

DevOps:

• DevOps is a collaborative approach where development, operations, and quality assurance teams work together to continuously deliver software with the goal of improving productivity, reducing overhead, and accelerating customer feedback cycles.
• DevOps applies agile and lean thinking principles to all stakeholders involved in the software supply chain, including customers, suppliers, and partners.
• The DevOps process involves Continuous Delivery, Continuous Integration, Continuous Deployment, Continuous Monitoring, and Delivery Pipeline.
• DevOps best practices are especially valuable for cloud-native applications due to their complex distributed system and rapid release cycles.
• DevOps provides capabilities such as programmatically provisioning servers, building middleware, automating installation processes, creating fully automated deployment pipelines, and defining how people work together to build, deploy, and manage applications in a cloud-native approach.
• DevOps also enables low-cost, production-like test environments and enables systems to be rebuilt quickly and reliably in the event of compromise or natural disasters.

Application modernization:

• Many organizations have invested in existing applications that are siloed in legacy systems and are difficult and expensive to update and maintain.
• Application modernization can unlock benefits such as accelerating digital transformations, enabling organizations to take advantage of new technologies and services, and becoming more responsive to customers' needs and changing market dynamics.
• Cloud computing is one of the three main ingredients in application modernization.
• The three main transformations in application modernization are changes in architecture, infrastructure, and ways of working (how organizations deliver).
• Traditional applications were monolithic and ran on physical servers using waterfall style development.
• Most organizations today use a distributed architecture with web services talking to each other, databases on the backend, and front-ends that go through all of that.
• Infrastructure has evolved to virtualization and more density, and agile development is the norm.
• The next phase of application modernization involves a microservice architecture with small, focused services, rest-based communication, and more independence.
• Cloud infrastructure, both public and private, is a key component of modernization.
• DevOps and site reliability engineering are critical to modernization in how applications are delivered, built, and what they are.
• Microservices and cloud infrastructure are tied, and organizations need these new ways of working to take advantage of these new infrastructures and architectures.
• Speed, resiliency, and adaptability are critical components of modernization. Organizations cannot rely on one-year project plans and need to be more agile.

Module 5:

Cloud security:

• Cloud computing has a shared responsibility model, where the cloud provider is responsible for managing the security of the platform, while the user is responsible for securing the applications, workload, and data.
• The adoption model of cloud computing (IaaS, PaaS, SaaS) impacts the level of control and responsibility the user has.
• When designing a secure architecture for data, encryption at rest and in motion, key management, and access control are crucial.
• Application security should be ensured through dynamic and static scanning of code and images.
• Identity and access management are important to control who can access the application and data.
• Network access control and protection against cyber-attacks should also be considered.
• Continuous security monitoring is necessary to ensure compliance and manage threats.
• A set of tools and approach is required to manage security and compliance posture.
• Insights about posture, compliance, and threats can be gained from the deployment environment, such as security events, audit logs, and flow logs.
• Actionable intelligence is needed to remediate any vulnerabilities or threats identified.
• DevOps should be approached with security as a forethought, not an afterthought.
• SecDevOps approach should be used to embed security into the entire lifecycle of building, managing, and running applications.
• Security should be shifted left and incorporated into the planning and design phases of the process.
• A secure design and architecture should be developed, taking into account the data classification, applications, and integrations required.
• Security should be embedded into the building process of applications, including the use of security-aware applications and encryption of sensitive data.
• A closed loop process should be established to remediate any issues found and adapt to the evolving threats landscape.

Identity and Access management:

• Data loss and leakage is the top cloud security concern of cybersecurity professionals.
• Identity and Access Management (IAM) works as the first line of defense to authenticate and authorize users, and provide user-specific access to cloud resources, services, and applications.
• IAM has three main types of users: Administrative Users, Developer Users, and Application Users.
• The key components of IAM are Authentication, Multifactor authentication, Cloud Directory services, Reporting, Audit and Compliance, and User and Service Access Management.
• Cloud providers offer IAM services, including the ability to create access groups, add users to access groups, and manage access for existing users.
• Access groups provide a more streamlined access assignment process as compared to assigning individual access to each user and help reduce the number of policies in an account.
• IAM controls help secure sensitive accounts of administrators or developers by provisioning users, setting password policies, using multifactor authentication, and immediately de-provisioning access when users leave or change roles.

cloud encryption:

• Encryption is a crucial part of data security and privacy in public cloud environments.
• Encryption ensures that only authorized users have access to sensitive data and makes data unreadable and meaningless when accessed without authorization.
• Cloud providers offer various cloud encryption services such as limited encryption of sensitive data or end-to-end encryption of all data uploaded to the cloud.
• Encryption needs to protect data in three states: at rest, in transit, and in use.
• Keys need to be managed securely, and losing them can result in data becoming unreadable.
• Cloud providers offer multi-cloud data encryption services that combine to deliver scalability and flexibility to protect sensitive workloads across the enterprise.
• Encryption does not eliminate data security risk but separates the security risk from the data itself by moving security to the encryption keys.
• Key Management Services offered by some cloud providers help perform life cycle management for encryption keys and enable customers to encrypt sensitive data at rest and manage the entire lifecycle of cryptographic keys.
• Best practices for encryption key management include storing keys separately from the encrypted data, taking key backups offsite, refreshing keys periodically, and implementing multi-factor authentication for both the master and recovery keys.

cloud monitoring:

• Cloud-based deployments can be complex and require monitoring across the entire stack of applications and services.
• Cloud monitoring solutions assess data, application, and infrastructure behaviors for performance, resource allocation, network availability, compliance, and security risks and threats.
• Cloud monitoring is not just about automated tools, it includes strategies, practices, and processes for analyzing, tracking, and managing cloud-based services and applications.
• Cloud monitoring helps accelerate the diagnosis and resolution of performance incidents, control the cost of monitoring infrastructure, and mitigate the impact of abnormal situations with proactive notifications.
• Cloud monitoring solutions provide visibility and control over an organization's entire cloud-based infrastructure, including real-time monitoring of virtual machines, services, databases, and applications.
• Infrastructure, Database, and Application Performance monitoring are categories of cloud monitoring tools.
• Cloud monitoring best practices include leveraging end-user experience monitoring solutions, moving all infrastructure under one unified monitoring platform, tracking cloud resource usage and cost, increasing cloud monitoring automation, and simulating outages and breach scenarios.
• Cloud monitoring is essential for organizations looking to optimize cloud resources for cost and performance and create better customer experiences.