<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Shalin Patel on Medium]]></title>
        <description><![CDATA[Stories by Shalin Patel on Medium]]></description>
        <link>https://medium.com/@shalinpatel.?source=rss-788747bff9ef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mFgZkdYmOikdOXhXN-9azQ.gif</url>
            <title>Stories by Shalin Patel on Medium</title>
            <link>https://medium.com/@shalinpatel.?source=rss-788747bff9ef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 06:52:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shalinpatel./feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[(Site to Site VPN)How to create a VPN between Azure and AWS using only managed solutions]]></title>
            <link>https://medium.com/@shalinpatel./site-to-site-vpn-how-to-create-a-vpn-between-azure-and-aws-using-only-managed-solutions-bd9c9776adbf?source=rss-788747bff9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd9c9776adbf</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[practice]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Shalin Patel]]></dc:creator>
            <pubDate>Sun, 28 Jan 2024 13:51:58 GMT</pubDate>
            <atom:updated>2024-01-28T13:51:58.159Z</atom:updated>
            <content:encoded><![CDATA[<p>What if you can establish a connection between Azure and AWS using only managed solutions instead to have to use virtual machines? This is exactly what we’ll be covering on this article connecting AWS Virtual Private Gateway with the Azure VPN Gateway directly without worry to manage IaaS resources like virtual machines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*0JT5zRwbxaqmRSGn" /></figure><p>Regarding the high availability, please note that on AWS, by default a VPN connection always will have 2 Public IPs, one per tunnel. On Azure it doesn’t happens by default and in this case you will be using Active/Passive from Azure side.</p><p>This means that we will be setting only one “node” from Azure VPN Gateway to establish two VPN connections with AWS. In case of a failure, the second node from Azure VPN Gateway will connect to AWS in a Active/Passive mode.</p><h3>Configuring Azure</h3><p><strong>1. Crate a resource group on Azure to deploy the resources on that</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/0*RsRf7Epc-1TUGPSt" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/0*2Mo2DgGTBfrZDahU" /></figure><p>Choose the subscription, the name and the region to be deployed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/0*foOKK_3hKMPFKpm_" /></figure><p><strong>2. Create a Virtual Network and a subnet</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/0*hZ9YO3G_F8ju3mFM" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/0*kzVf4_J1y5JNqfCo" /></figure><p>Define the subscription, resource group, name and region to be deployed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/0*PQckgl8jx248e8mq" /></figure><p>Set the address space for the virtual network and for the subnet. Here I’m defining the virtual network address space to <strong>172.10.0.0/16</strong>, changing the “default” subnet name to <strong>“subnet-01”</strong> and defining the subnet address range to <strong>172.10.1.0/24</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*OFflOnSrmqfi60Pc" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/0*cKCH-zVwxI-oPQMS" /></figure><p><strong>3. Create the VPN Gateway</strong></p><p>The Azure VPN Gateway is a resource composed of 2 or more VM’s that are deployed to a specific subnet called Gateway Subnet where the recommendation is to use a /27. He contain routing tables and run specific gateway services. Note that you can’t access those VM’s.</p><p>To create, go to your Resource Group, then click to <strong>+ Add</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/0*Lu_1Fb2ZXGrqntKf" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/0*QI3nBTIK95fez9mh" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/0*b9hVHUTGA7PxVGRV" /></figure><p>Then fill the fields like below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/0*p4xRLN9R6qwPKT4g" /></figure><p>After click to Review + create, in a few minutes the Virtual Network Gateway will be ready:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*lkxQfnCy8Ypz92xa" /></figure><h3>Configuring AWS</h3><p><strong>4. Create the Virtual Private Cloud (VPC)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/0*xWa7pcGcA6wMxFDz" /></figure><p><strong>5. Create a subnet inside the VPC (Virtual Network)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*cLmnddkPu_QFbd9F" /></figure><p><strong>6. Create a customer gateway pointing to the public ip address of Azure VPN Gateway</strong></p><p>The Customer Gateway is an AWS resource with information to AWS about the customer gateway device, which in this case is the Azure VPN Gateway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*NhhToJ-QgnKd-Hhs" /></figure><p><strong>7. Create the Virtual Private Gateway then attach to the VPC</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*ZuKz9FRdiqcknZkt" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*cGsbJtke7W1SQQBx" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*IbQLIhmy2ViwWFtD" /></figure><p><strong>8. Create a site-to-site VPN Connection</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/0*Tpr0Ph-U9XRKiL4A" /></figure><p>Set the routing as static pointing to the azure subnet-01 prefix (172.10.1.0/24)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*SptIsPMsGovPwwph" /></figure><p>After fill the options, click to create.</p><p><strong>9. Download the configuration file</strong></p><p>Please note that you need to change the Vendor, Platform and Software to Generic since Azure isn’t a valid option:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/0*85ze_BNuJBijF0r6" /></figure><p>In this configuration file you will note that there are the Shared Keys and the Public Ip Address for each of one of the two IPSec tunnels created by AWS:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/0*l-Q5Plf5vU19S80d" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*aSn-ES8YuD2GDG1J" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/0*8BLFJEuOKKeDSZ54" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/0*qM9lj_SVy6ZalGvl" /></figure><p>After the creation, you should have something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*mX3PUwon0eH4kkFQ" /></figure><h3>Adding the AWS information on Azure Configuration</h3><p><strong>10. Now let’s create the Local Network Gateway</strong></p><p>The Local Network Gateway is an Azure resource with information to Azure about the customer gateway device, in this case the AWS Virtual Private Gateway</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/0*zu9z9BDbyVOsm25y" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/0*CePj8zAU2AcjeZwj" /></figure><p>Now you need to specify the public ip address from the AWS Virtual Private Gateway and the VPC CIDR prefix.</p><p>Please note that the public address from the AWS Virtual Private Gateway is described at the configuration file you have downloaded.</p><p>As mentioned earlier, AWS creates two IPSec tunnels to high availability purposes. I’ll use the public ip address from the IPSec Tunnel #1 for now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/0*F-Mob5OTP60MMgKK" /></figure><p><strong>11. Then let’s create the connection on the Virtual Network Gateway</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/0*HUc91ojNp_cK40b0" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/0*DruqGWLhT32erchF" /></figure><p>You should fill the fields according below. Please note that the Shared key was obtained at the configuration file downloaded earlier and In this case, I’m using the Shared Key for the Ipsec tunnel #1 created by AWS and described at the configuration file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/0*aFgq9pIxS5XbV-k7" /></figure><p>After a few minutes, you can see the connection established:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*cit7dKPN77Ke4hSd" /></figure><p>In the same way, we can check on AWS that the 1st tunnel is up:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*4_UOft8sZcqvzcNn" /></figure><p>Now let’s edit the route table associated with our VPC</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*RuZQrav5d87ZdIfy" /></figure><p>And add the route to Azure subnet through the Virtual Private Gateway:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*oT0S7m2BxJUHxCXe" /></figure><p><strong>12. Adding high availability</strong></p><p>Now we can create a 2nd connection to ensure high availability. To do this let’s create another Local Network Gateway which we will point to the public ip address of the IPSec tunnel #2 on the AWS</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/0*rWSmxWEAeIK-pOih" /></figure><p>Then we can create the 2nd connection on the Virtual Network Gateway:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/0*LbVRhtLWvbVYlelF" /></figure><p>And in a few moments we’ll have:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*_nwz4f-9uVEZG6nu" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*4qtvGg5xR_UPm5WF" /></figure><p>With this, our VPN connection is established on both sides and the work is done.</p><p><strong>13. Let’s test!</strong></p><p>First, let’s add an Internet Gateway to our VPC at AWS. The Internet Gateway is a logical connection between an Amazon VPN and the Internet. This resource will allow us to connect through the test VM from their public ip through internet. This is not required for the VPN connection, is just for our test:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/0*0gEe37emfV1jEPwo" /></figure><p>After create, let’s attach to the VPC:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*jbAa6dJIxBL3obMh" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/793/0*3PwQ4MZyIn3qNNep" /></figure><p>Now we can create a route to allow connections to <strong>0.0.0.0/0</strong> (Internet) through the Internet Gateway:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*S99QfOkwujfGqQ2d" /></figure><p>On Azure the route was automatically created. You can check selecting the Azure VM &gt; Networking &gt; Network Interface &gt; Effective routes. Note that we have 2 (1 per connection):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*Cg49OcgwLI-yTtf2" /></figure><p>Now I’ve created a Linux VM on Azure and our environment looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*fpBm-OaEqdADAiJQ" /></figure><p>And I did the same VM creation on AWS that looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*epOSDTfveK7rq20A" /></figure><p>Then we can test the connectivity betweeen Azure and AWS through our VPN connection:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/979/0*dVoXpCrvN6k-4j6E" /></figure><p>If you want to deploy a solution more resilient and using BGP, follow this documentation: <a href="https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-aws-bgp">https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-aws-bgp</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd9c9776adbf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up VPN in AWS & Test Your VPN]]></title>
            <link>https://medium.com/@shalinpatel./setting-up-vpn-in-aws-test-your-vpn-4816e041fabd?source=rss-788747bff9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/4816e041fabd</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Shalin Patel]]></dc:creator>
            <pubDate>Mon, 22 Jan 2024 13:46:29 GMT</pubDate>
            <atom:updated>2024-01-22T13:46:29.748Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*NwBXgDuhoznntJFDPLioJg.png" /></figure><h3>VPN: What is it?</h3><p>Virtual Private Network, or VPN for short, is a technology that gives users access to the internet as though they were on a private network while also offering a private and secure connection. VPNs are frequently utilized for a number of reasons, such as:</p><p>1) Security: By encrypting the data that is sent between your device and a distant server, virtual private networks (VPNs) make it more difficult for outside parties — like hackers or government agencies — to intercept and monitor your online activity. This is especially crucial because public Wi-Fi networks are frequently less secure.</p><p>2) Privacy and Torrenting: By passing your internet traffic via a server located in a foreign country, VPNs conceal your true IP address and location. By making it more difficult for websites and online services to trace your online activity, this helps preserve your online privacy and anonymity.</p><p>Some users use virtual private networks (VPNs) to access torrent websites that may be restricted in their area and to participate in peer-to-peer file sharing or torrenting while remaining anonymous.</p><p>3)Avoiding Geographical Restrictions: In some places, certain websites and content are geoblocked or limited. You can access information and services that would not normally be available in your location by setting up a VPN server in a different location.</p><h3>VPN Configuration with AWS</h3><p>In order to deploy a VPN server on Amazon, first create an EC2 instance and then choose “Browse more AMIs,” as seen below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/0*O1pv6kl7g7NNK8XL" /></figure><p>Search for OpenVPN on the AWS Marketplace AMIs, then choose OpenVPN Access Server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/0*PBSxew8rVuigjxK-" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/0*LyfqoVPe_KYgriBH" /></figure><p>Proceed with additional configuration, choosing a key pair or creating a new key based on your needs and the launch instance.</p><p>After the server is up and running, select Connect. Then, navigate to the SSH section and use the provided command in AWS to establish a connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/0*XcoxfTOBCvsIM5r0" /></figure><p>As you can see from the screenshot above, I was unable to login using root and instead connected as the user “openvpn.”</p><p>Type “yes” and press Enter to accept the agreement after a successful connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/0*mBTN0cTSipNDiw94" /></figure><p>Leave everything as it is, or adjust as necessary. Create a password for your OpenVPN profile (you can also modify the user name during setting).</p><p>Note : I used here system generated password : for Admin login page of Open VPN</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/0*jmE-vT0JDqhbvHFX" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/0*JHH4AroSgzr1j30h" /></figure><p>As soon as the configuration is successfully finished, the URLs for the admin and client user interfaces are displayed.</p><p>When you copy the admin UI address and open it in a browser, the page shown below will load. Enter your password and the username you gave during configuration in the previous stage to log in as openvpn (if your username has changed, use the one you provided).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/0*dlPwMdi_LmRp087E" /></figure><p>In the next window click and “Agree” to continue with the process.<br>After successful login the below pages appears.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J1NjLsxUHi_gteCD" /></figure><p>Save the changes under VPN settings, Change Routing and DNS Settings, as indicated below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HQ8e0pkzrjY0av1s" /></figure><p>Save it . After that you Configure as user (as i configure Vyankatesh)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Kr9fyGi03jGvmGXX" /></figure><p>After copying the Client UI address, visit it. The page below will load; use your login credentials to access it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GuPKH_6h7zeszY7s" /></figure><p>Select a type and install the OpenVPN application to proceed after logging in below.</p><p>Once the application is downloaded, install the application.<br>After successful installation of the application open the application, a below screen will be displayed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BL9CMwQiEh931GU9" /></figure><p>When you install and connect to the VPN profile that comes installed with it or create a new VPN Profile, a password will be needed. input the password that has been configured.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/0*DW_enQIOAEFIOgZp" /></figure><p>Note here your current IP</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bXrm3BSQRViG0K-U" /></figure><h3>📍 Test Your VPN</h3><p>Creating A New VPN profile, where i copy my public ip in and pasted in openVPN .</p><p>Follow Steps</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dxZnf-8Yeh15pCK8" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Rw4KClLR0F4vCRui" /></figure><p>Configure ID and Password and save password you have to put as to connect VPN.</p><p>After a successful connection, the screen below will appear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pLeV5_Y0XPkVvTbb" /></figure><p>So its connected .</p><p>Now check your IP</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/0*6WAlXj_iyUagBHM1" /></figure><p>Which means server is getting all the traffic that required .</p><p>Many congratulations 🏉! You learn about Setting up OpenVPN in #AWS Cloud</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4816e041fabd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AutoScaling In AWS]]></title>
            <link>https://medium.com/@shalinpatel./autoscaling-in-aws-805ee06ded99?source=rss-788747bff9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/805ee06ded99</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-services]]></category>
            <dc:creator><![CDATA[Shalin Patel]]></dc:creator>
            <pubDate>Mon, 22 Jan 2024 13:38:19 GMT</pubDate>
            <atom:updated>2024-01-22T13:38:19.214Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a6AJScehOhhiPdiASkRkzw.png" /></figure><h3>What is AutoScaling ?</h3><p>Auto Scaling is a service that scales up or down computing resources automatically to maintain consistent application performance. The service’s name clearly indicates this. The AWS Auto scaling feature makes sure that there are enough instances or resources available to complete the application.</p><p>When the application’s load increases and the servers become stressed out the AWS auto scaling service will deploy additional servers with identical configurations to scale up the system.</p><h3>👉 Advantages of Automatic Scaling</h3><ol><li>Improved fault tolerance</li><li>High availability of resources</li><li>Better control over expenses</li><li>High reliability of resources</li><li>The high degree of flexibility of the resources</li></ol><h3>💠Types of AutoScaling</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*cVKkzDPAoh7d8MOfICbbfw.png" /></figure><ul><li><strong>Horizontal Scaling</strong></li></ul><ol><li>a) The AWS Auto Scaling service, that allows you to automatically modify the number of EC2 instances in an Auto Scaling group, is used to do this.</li><li>b) The AWS Auto Scaling service, that allows you to automatically modify the number of EC2 instances in an Auto Scaling group, is used to do this.</li></ol><ul><li><strong>Vertical Scaling</strong></li></ul><ol><li>a) By adding more resources to meet rising demand, vertical scaling focuses on increasing the capacity of individual instances.</li><li>b) By changing the instance type or size to a larger configuration, this can be accomplished. When a single, more powerful instance is required and the application architecture is not meant for horizontal scaling, vertical scaling can be suitable.</li><li>c) While vertical scaling offers an easier way of increasing capacity, it’s crucial to remember that there are restrictions on the resources that can be deployed on just one instance, and there may be reduce downtime while the system is expanding.</li></ol><h3>💠Different types of Scaling Strategies</h3><h3><strong>Reactive Scaling</strong></h3><ol><li>Reactive autoscaling increases and decreases resources in reaction to increases in traffic. This method has a strong connection with the real-time resource monitoring. There usually a cooldown period involved, which is a set amount of time when resources are kept at full capacity to handle any additional incremental traffic surges, even in the event that traffic reduces.</li></ol><h3><strong>Predictive Scaling</strong></h3><ol><li>A predictive autoscaling technique makes use of artificial intelligence and machine learning capabilities to assess traffic loads and predict when additional or decreased resources will be required. Predictive scaling uses machine learning to forecast the expected demand for the next two days based on an analysis of each resource’s historical workload. This is comparable to how weather forecasts operate. Using predictive scaling, you can make sure that resource capacity is available before your application needs it by scheduling scaling operations based on the prediction. To put it another way, predictive autoscaling uses analytics, such as historical usage statistics and present usage trends, to automatically grow in accordance with demand forecasts for the future.</li></ol><h3><strong>Scheduled scaling</strong></h3><ol><li>Users can select a period of time that will see the inclusion of new resources. A hybrid solution known as scheduled autoscaling predicts known variations in traffic loads and responds to them at predefined intervals. It works in real-time. The best use cases for scheduled scaling are periods of expected low or high traffic, although the adjustments are typically quite sudden. Rather than waiting for resources to scale up as demand increases, they might be pre-provisioned ahead of time for a big event or during a high period of the day.</li></ol><h3><strong>Manual Scaling</strong></h3><ol><li>In this method, the number of instances is changed by hand. Using a CLI or console, you can manually change the number of instances. When your user doesn’t require automatic scaling, manual scaling is a smart option.</li></ol><h3><strong>Dynamic Scaling</strong></h3><ol><li>In this form of auto scaling, the quantity of EC2 instances is automatically adjusted based on signals received. When there’s a lot of erratic traffic, dynamic scaling makes sense.</li></ol><h3>💠Best Practices for AutoScaling</h3><ol><li>In order to respond to changes in usage patterns more quickly, you should, if at all possible, scale Amazon EC2 instance metrics on a one-minute interval. If you scale on updated measurements every five minutes (or less), you can end up with a longer response time and obsolete metric data. Metric data for Amazon EC2 instances is available by default at 5-minute intervals because these instances are initially set up for basic monitoring. To obtain metrics data for instances within a minute, you can also activate comprehensive monitoring at an additional cost.</li><li>Activating Auto Scaling group metrics is also a smart idea. If you don’t do this, the capacity forecast graphs that become available once the Create Scaling Plan process is finished won’t display the real capacity data. After establishing an Auto Scaling group in the Amazon EC2 console, it would be beneficial if you selected the Enable Group Metrics Collection option in the Amazon EC2 interface. Go to the Monitoring tab and choose Enable Group Metrics Collection to accomplish this. These metrics characterize the group as a whole as opposed to any specific instances within it.</li><li>Verify which Auto Scaling group is utilizing the particular instance type. In certain cases, you might be at risk of exceeding the baseline and then running out of CPU credits, which would have a detrimental effect on performance, based on the goal consumption specified by the scaling plan.</li></ol><h3>💠Use cases :</h3><ul><li>Real-time Video Streaming Services</li></ul><ol><li>A seamless and responsive streaming experience is ensured during peak events via auto scaling, which allows video streaming services to dynamically alter server capacity based on the live viewership.</li></ol><ul><li>Online shopping Flash Sales</li></ul><ol><li>Ensuring peak performance and user experience by automatically scaling web servers to handle an unexpected spike in internet traffic during flash sales.</li></ol><ul><li><strong>Servers for Online Gaming</strong></li></ul><ol><li>In order to maintain a steady gaming experience with enough resources to allow multiplayer interactions, auto scaling modifies the number of game servers in response to player activity.</li></ol><ul><li><strong>Processing of IoT Data</strong></li></ul><ol><li>In Internet of Things applications, auto scaling is used to manage the inflow of data from devices by dynamically modifying the processing capability to account for variations in data volume.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=805ee06ded99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Describe monitoring tools in Azure]]></title>
            <link>https://medium.com/@shalinpatel./describe-monitoring-tools-in-azure-d1e1e08f4e4a?source=rss-788747bff9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1e1e08f4e4a</guid>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Shalin Patel]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 14:49:14 GMT</pubDate>
            <atom:updated>2024-01-19T14:49:14.503Z</atom:updated>
            <content:encoded><![CDATA[<p>In this module, you’ll be introduced to tools that help you monitor your environment and applications, both in Azure and in on-premises or multicloud environments.</p><ul><li>Describe the purpose of Azure Advisor.</li><li>Describe Azure Service Health.</li><li>Describe Azure Monitor, including Azure Log Analytics, Azure Monitor Alerts, and Application Insights.</li></ul><h3>Describe the purpose of Azure Advisor</h3><p>Azure Advisor evaluates your Azure resources and makes recommendations to help improve reliability, security, and performance, achieve operational excellence, and reduce costs. Azure Advisor is designed to help you save time on cloud optimization. The recommendation service includes suggested actions you can take right away, postpone, or dismiss.</p><p>The recommendations are available via the Azure portal and the API, and you can set up notifications to alert you to new recommendations.</p><p>When you’re in the Azure portal, the Advisor dashboard displays personalized recommendations for all your subscriptions. You can use filters to select recommendations for specific subscriptions, resource groups, or services. The recommendations are divided into five categories:</p><ul><li>Reliability is used to ensure and improve the continuity of your business-critical applications.</li><li>Security is used to detect threats and vulnerabilities that might lead to security breaches.</li><li>Performance is used to improve the speed of your applications.</li><li>Operational Excellence is used to help you achieve process and workflow efficiency, resource manageability, and deployment best practices.</li><li>Cost is used to optimize and reduce your overall Azure spending.</li></ul><p>The following image shows the Azure Advisor dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k2WvwxoIzutQ7Ahg.png" /></figure><h3>Describe Azure Service Health</h3><p>Microsoft Azure provides a global cloud solution to help you manage your infrastructure needs, reach your customers, innovate, and adapt rapidly. Knowing the status of the global Azure infrastructure and your individual resources could seem like a daunting task. Azure Service Health helps you keep track of Azure resource, both your specifically deployed resources and the overall status of Azure. Azure service health does this by combining three different Azure services:</p><ul><li>Azure Status is a broad picture of the status of Azure globally. Azure status informs you of service outages in Azure on the Azure Status page. The page is a global view of the health of all Azure services across all Azure regions. It’s a good reference for incidents with widespread impact.</li><li>Service Health provides a narrower view of Azure services and regions. It focuses on the Azure services and regions you’re using. This is the best place to look for service impacting communications about outages, planned maintenance activities, and other health advisories because the authenticated Service Health experience knows which services and resources you currently use. You can even set up Service Health alerts to notify you when service issues, planned maintenance, or other changes may affect the Azure services and regions you use.</li><li>Resource Health is a tailored view of your actual Azure resources. It provides information about the health of your individual cloud resources, such as a specific virtual machine instance. Using Azure Monitor, you can also configure alerts to notify you of availability changes to your cloud resources.</li></ul><p>By using Azure status, Service health, and Resource health, Azure Service Health gives you a complete view of your Azure environment-all the way from the global status of Azure services and regions down to specific resources. Additionally, historical alerts are stored and accessible for later review. Something you initially thought was a simple anomaly that turned into a trend, can readily be reviewed and investigated thanks to the historical alerts.</p><p>Finally, in the event that a workload you’re running is impacted by an event, Azure Service Health provides links to support.</p><h3>Describe Azure Monitor</h3><p>Azure Monitor is a platform for collecting data on your resources, analyzing that data, visualizing the information, and even acting on the results. Azure Monitor can monitor Azure resources, your on-premises resources, and even multi-cloud resources like virtual machines hosted with a different cloud provider.</p><p>The following diagram illustrates just how comprehensive Azure Monitor is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*uUh-c7nmib-sE3AM0LO1BA.png" /></figure><p>On the left is a list of the sources of logging and metric data that can be collected at every layer in your application architecture, from application to operating system and network.</p><p>In the center, the logging and metric data are stored in central repositories.</p><p>On the right, the data is used in several ways. You can view real-time and historical performance across each layer of your architecture or aggregated and detailed information. The data is displayed at different levels for different audiences. You can view high-level reports on the Azure Monitor Dashboard or create custom views by using Power BI and Kusto queries.</p><p>Additionally, you can use the data to help you react to critical events in real time, through alerts delivered to teams via SMS, email, and so on. Or you can use thresholds to trigger autoscaling functionality to scale to meet the demand.</p><h3>Azure Log Analytics</h3><p>Azure Log Analytics is the tool in the Azure portal where you’ll write and run log queries on the data gathered by Azure Monitor. Log Analytics is a robust tool that supports both simple, complex queries, and data analysis. You can write a simple query that returns a set of records and then use features of Log Analytics to sort, filter, and analyze the records. You can write an advanced query to perform statistical analysis and visualize the results in a chart to identify a particular trend. Whether you work with the results of your queries interactively or use them with other Azure Monitor features such as log query alerts or workbooks, Log Analytics is the tool that you’re going to use to write and test those queries.</p><h3>Azure Monitor Alerts</h3><p>Azure Monitor Alerts are an automated way to stay informed when Azure Monitor detects a threshold being crossed. You set the alert conditions, the notification actions, and then Azure Monitor Alerts notifies when an alert is triggered. Depending on your configuration, Azure Monitor Alerts can also attempt corrective action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lQ4OtFfdnmpvteuB.png" /></figure><p>Alerts can be set up to monitor the logs and trigger on certain log events, or they can be set to monitor metrics and trigger when certain metrics are crossed. For example, you could set a metric-based alert up to notify you when the CPU usage on a virtual machine exceeded 80%. Alert rules based on metrics provide near real time alerts based on numeric values. Rules based on logs allow for complex logic across data from multiple sources.</p><p>Azure Monitor Alerts use action groups to configure who to notify and what action to take. An action group is simply a collection of notification and action preferences that you associate with one or multiple alerts. Azure Monitor, Service Health, and Azure Advisor all use actions groups to notify you when an alert has been triggered.</p><h3>Application Insights</h3><p>Application Insights, an Azure Monitor feature, monitors your web applications. Application Insights is capable of monitoring applications that are running in Azure, on-premises, or in a different cloud environment.</p><p>There are two ways to configure Application Insights to help monitor your application. You can either install an SDK in your application, or you can use the Application Insights agent. The Application Insights agent is supported in C#.NET, VB.NET, Java, JavaScript, Node.js, and Python.</p><p>Once Application Insights is up and running, you can use it to monitor a broad array of information, such as:</p><ul><li>Request rates, response times, and failure rates</li><li>Dependency rates, response times, and failure rates, to show whether external services are slowing down performance</li><li>Page views and load performance reported by users’ browsers</li><li>AJAX calls from web pages, including rates, response times, and failure rates</li><li>User and session counts</li><li>Performance counters from Windows or Linux server machines, such as CPU, memory, and network usage</li></ul><p>Not only does Application Insights help you monitor the performance of your application, but you can also configure it to periodically send synthetic requests to your application, allowing you to check the status and monitor your application even during periods of low activity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1e1e08f4e4a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Describe tools for interacting with Azure]]></title>
            <link>https://medium.com/@shalinpatel./describe-tools-for-interacting-with-azure-85c7280aca29?source=rss-788747bff9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/85c7280aca29</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[azure-devops]]></category>
            <dc:creator><![CDATA[Shalin Patel]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 14:48:20 GMT</pubDate>
            <atom:updated>2024-01-19T14:48:20.955Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wU8mtBbiMeNJYJhjvBz6Uw.png" /></figure><p>To get the most out of Azure, you need a way to interact with the Azure environment, the management groups, subscriptions, resource groups, resources, and so on. Azure provides multiple tools for managing your environment, including the:</p><ul><li>Azure portal</li><li>Azure PowerShell</li><li>Azure Command Line Interface (CLI)</li></ul><h3>What is the Azure portal?</h3><p>The Azure portal is a web-based, unified console that provides an alternative to command-line tools. With the Azure portal, you can manage your Azure subscription by using a graphical user interface. You can:</p><ul><li>Build, manage, and monitor everything from simple web apps to complex cloud deployments</li><li>Create custom dashboards for an organized view of resources</li><li>Configure accessibility options for an optimal experience</li></ul><p>The Azure portal is designed for resiliency and continuous availability. It maintains a presence in every Azure datacenter. This configuration makes the Azure portal resilient to individual datacenter failures and avoids network slowdowns by being close to users. The Azure portal updates continuously and requires no downtime for maintenance activities.</p><h3>Azure Cloud Shell</h3><p>Azure Cloud Shell is a browser-based shell tool that allows you to create, configure, and manage Azure resources using a shell. Azure Cloud Shell support both Azure PowerShell and the Azure Command Line Interface (CLI), which is a Bash shell.</p><p>You can access Azure Cloud Shell via the Azure portal by selecting the Cloud Shell icon:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yBDSsUdiDbBU8uPu.png" /></figure><p>Azure Cloud Shell has several features that make it a unique offering to support you in managing Azure. Some of those features are:</p><ul><li>It is a browser-based shell experience, with no local installation or configuration required.</li><li>It is authenticated to your Azure credentials, so when you log in it inherently knows who you are and what permissions you have.</li><li>You choose the shell you’re most familiar with; Azure Cloud Shell supports both Azure PowerShell and the Azure CLI (which uses Bash).</li></ul><h3>What is Azure PowerShell?</h3><p>Azure PowerShell is a shell with which developers, DevOps, and IT professionals can run commands called command-lets (cmdlets). These commands call the Azure REST API to perform management tasks in Azure. Cmdlets can be run independently to handle one-off changes, or they may be combined to help orchestrate complex actions such as:</p><ul><li>The routine setup, teardown, and maintenance of a single resource or multiple connected resources.</li><li>The deployment of an entire infrastructure, which might contain dozens or hundreds of resources, from imperative code.</li></ul><p>Capturing the commands in a script makes the process repeatable and automatable.</p><p>In addition to be available via Azure Cloud Shell, you can install and configure Azure PowerShell on Windows, Linux, and Mac platforms.</p><h3>What is the Azure CLI?</h3><p>The Azure CLI is functionally equivalent to Azure PowerShell, with the primary difference being the syntax of commands. While Azure PowerShell uses PowerShell commands, the Azure CLI uses Bash commands.</p><p>The Azure CLI provides the same benefits of handling discrete tasks or orchestrating complex operations through code. It’s also installable on Windows, Linux, and Mac platforms, as well as through Azure Cloud Shell.</p><p>Due to the similarities in capabilities and access between Azure PowerShell and the Bash based Azure CLI, it mainly comes down to which language you’re most familiar with.</p><h3>Describe the purpose of Azure Arc</h3><p>Managing hybrid and multi-cloud environments can rapidly get complicated. Azure provides a host of tools to provision, configure, and monitor Azure resources. What about the on-premises resources in a hybrid configuration or the cloud resources in a multi-cloud configuration?</p><p>In utilizing Azure Resource Manager (ARM), Arc lets you extend your Azure compliance and monitoring to your hybrid and multi-cloud configurations. Azure Arc simplifies governance and management by delivering a consistent multi-cloud and on-premises management platform.</p><p>Azure Arc provides a centralized, unified way to:</p><ul><li>Manage your entire environment together by projecting your existing non-Azure resources into ARM.</li><li>Manage multi-cloud and hybrid virtual machines, Kubernetes clusters, and databases as if they are running in Azure.</li><li>Use familiar Azure services and management capabilities, regardless of where they live.</li><li>Continue using traditional ITOps while introducing DevOps practices to support new cloud and native patterns in your environment.</li><li>Configure custom locations as an abstraction layer on top of Azure Arc-enabled Kubernetes clusters and cluster extensions.</li></ul><h3>What can Azure Arc do outside of Azure?</h3><p>Currently, Azure Arc allows you to manage the following resource types hosted outside of Azure:</p><ul><li>Servers</li><li>Kubernetes clusters</li><li>Azure data services</li><li>SQL Server</li><li>Virtual machines (preview)</li></ul><h3>Describe Azure Resource Manager and Azure ARM templates</h3><p>Azure Resource Manager (ARM) is the deployment and management service for Azure. It provides a management layer that enables you to create, update, and delete resources in your Azure account. Anytime you do anything with your Azure resources, ARM is involved.</p><p>When a user sends a request from any of the Azure tools, APIs, or SDKs, ARM receives the request. ARM authenticates and authorizes the request. Then, ARM sends the request to the Azure service, which takes the requested action. You see consistent results and capabilities in all the different tools because all requests are handled through the same API.</p><h3>Azure Resource Manager benefits</h3><p>With Azure Resource Manager, you can:</p><ul><li>Manage your infrastructure through declarative templates rather than scripts. A Resource Manager template is a JSON file that defines what you want to deploy to Azure.</li><li>Deploy, manage, and monitor all the resources for your solution as a group, rather than handling these resources individually.</li><li>Re-deploy your solution throughout the development life-cycle and have confidence your resources are deployed in a consistent state.</li><li>Define the dependencies between resources, so they’re deployed in the correct order.</li><li>Apply access control to all services because RBAC is natively integrated into the management platform.</li><li>Apply tags to resources to logically organize all the resources in your subscription.</li><li>Clarify your organization’s billing by viewing costs for a group of resources that share the same tag.</li></ul><h3>Infrastructure as code</h3><p>Infrastructure as code is a concept where you manage your infrastructure as lines of code. At an introductory level, it’s things like using Azure Cloud Shell, Azure PowerShell, or the Azure CLI to manage and configure your resources. As you get more comfortable in the cloud, you can use the infrastructure as code concept to manage entire deployments using repeatable templates and configurations. ARM templates and Bicep are two examples of using infrastructure as code with the Azure Resource Manager to maintain your environment.</p><h3>ARM templates</h3><p>By using ARM templates, you can describe the resources you want to use in a declarative JSON format. With an ARM template, the deployment code is verified before any code is run. This ensures that the resources will be created and connected correctly. The template then orchestrates the creation of those resources in parallel. That is, if you need 50 instances of the same resource, all 50 instances are created at the same time.</p><p>Ultimately, the developer, DevOps professional, or IT professional needs only to define the desired state and configuration of each resource in the ARM template, and the template does the rest. Templates can even execute PowerShell and Bash scripts before or after the resource has been set up.</p><h3>Benefits of using ARM templates</h3><p>ARM templates provide many benefits when planning for deploying Azure resources. Some of those benefits include:</p><ul><li>Declarative syntax: ARM templates allow you to create and deploy an entire Azure infrastructure declaratively. Declarative syntax means you declare what you want to deploy but don’t need to write the actual programming commands and sequence to deploy the resources.</li><li>Repeatable results: Repeatedly deploy your infrastructure throughout the development lifecycle and have confidence your resources are deployed in a consistent manner. You can use the same ARM template to deploy multiple dev/test environments, knowing that all the environments are the same.</li><li>Orchestration: You don’t have to worry about the complexities of ordering operations. Azure Resource Manager orchestrates the deployment of interdependent resources, so they’re created in the correct order. When possible, Azure Resource Manager deploys resources in parallel, so your deployments finish faster than serial deployments. You deploy the template through one command, rather than through multiple imperative commands.</li><li>Modular files: You can break your templates into smaller, reusable components and link them together at deployment time. You can also nest one template inside another template. For example, you could create a template for a VM stack, and then nest that template inside of templates that deploy entire environments, and that VM stack will consistently be deployed in each of the environment templates.</li><li>Extensibility: With deployment scripts, you can add PowerShell or Bash scripts to your templates. The deployment scripts extend your ability to set up resources during deployment. A script can be included in the template or stored in an external source and referenced in the template. Deployment scripts give you the ability to complete your end-to-end environment setup in a single ARM template.</li></ul><h3>Bicep</h3><p>Bicep is a language that uses declarative syntax to deploy Azure resources. A Bicep file defines the infrastructure and configuration. Then, ARM deploys that environment based on your Bicep file. While similar to an ARM template, which is written in JSON, Bicep files tend to use a simpler, more concise style.</p><p>Some benefits of Bicep are:</p><ul><li>Support for all resource types and API versions: Bicep immediately supports all preview and GA versions for Azure services. As soon as a resource provider introduces new resource types and API versions, you can use them in your Bicep file. You don’t have to wait for tools to be updated before using the new services.</li><li>Simple syntax: When compared to the equivalent JSON template, Bicep files are more concise and easier to read. Bicep requires no previous knowledge of programming languages. Bicep syntax is declarative and specifies which resources and resource properties you want to deploy.</li><li>Repeatable results: Repeatedly deploy your infrastructure throughout the development lifecycle and have confidence your resources are deployed in a consistent manner. Bicep files are idempotent, which means you can deploy the same file many times and get the same resource types in the same state. You can develop one file that represents the desired state, rather than developing lots of separate files to represent updates.</li><li>Orchestration: You don’t have to worry about the complexities of ordering operations. Resource Manager orchestrates the deployment of interdependent resources so they’re created in the correct order. When possible, Resource Manager deploys resources in parallel so your deployments finish faster than serial deployments. You deploy the file through one command, rather than through multiple imperative commands.</li><li>Modularity: You can break your Bicep code into manageable parts by using modules. The module deploys a set of related resources. Modules enable you to reuse code and simplify development. Add the module to a Bicep file anytime you need to deploy those resources.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85c7280aca29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Describe the purpose of the Service Trust portal]]></title>
            <link>https://medium.com/@shalinpatel./describe-the-purpose-of-the-service-trust-portal-33f10584f80a?source=rss-788747bff9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/33f10584f80a</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[azure-devops]]></category>
            <dc:creator><![CDATA[Shalin Patel]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 14:47:00 GMT</pubDate>
            <atom:updated>2024-01-19T14:47:00.429Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*gpZi0-dOAOmrlUZ9Nj6uNA.png" /></figure><p>The Microsoft Service Trust Portal is a portal that provides access to various content, tools, and other resources about Microsoft security, privacy, and compliance practices.</p><p>The Service Trust Portal contains details about Microsoft’s implementation of controls and processes that protect our cloud services and the customer data therein. To access some of the resources on the Service Trust Portal, you must sign in as an authenticated user with your Microsoft cloud services account (Microsoft Entra organization account). You’ll need to review and accept the Microsoft non-disclosure agreement for compliance materials.</p><h3>Accessing the Service Trust Portal</h3><p>You can access the Service Trust Portal at <a href="https://servicetrust.microsoft.com/">https://servicetrust.microsoft.com/</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vYTFJD1xzq7R20lZ.png" /></figure><p>The Service Trust Portal features and content are accessible from the main menu. The categories on the main menu are:</p><ul><li>Service Trust Portal provides a quick access hyperlink to return to the Service Trust Portal home page.</li><li>My Library lets you save (or pin) documents to quickly access them on your My Library page. You can also set up to receive notifications when documents in your My Library are updated.</li><li>All Documents is a single landing place for documents on the service trust portal. From All Documents, you can pin documents to have them show up in your My Library.</li></ul><p>Note</p><p>Service Trust Portal reports and documents are available to download for at least 12 months after publishing or until a new version of document becomes available.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33f10584f80a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Exercise — Configure a resource lock]]></title>
            <link>https://medium.com/@shalinpatel./azure-exercise-configure-a-resource-lock-38728fe20569?source=rss-788747bff9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/38728fe20569</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Shalin Patel]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 14:45:44 GMT</pubDate>
            <atom:updated>2024-01-19T14:45:44.323Z</atom:updated>
            <content:encoded><![CDATA[<h3>Azure Exercise — Configure a resource lock</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/299/1*5Y6rmJ5nFe1skUquN05N3Q.jpeg" /></figure><p>In this exercise, you’ll create a resource and configure a resource lock. Storage accounts are one of the easiest types of resource locks to quickly see the impact, so you’ll use a storage account for this exercise.</p><p>This exercise is a Bring your own subscription exercise, meaning you’ll need to provide your own Azure subscription to complete the exercise. Don’t worry though, the entire exercise can be completed for free with the 12 month free services when you sign up for an Azure account.</p><p>For help with signing up for an Azure account, see the <a href="https://learn.microsoft.com/en-us/learn/modules/create-an-azure-account/">Create an Azure account</a> learning module.</p><p>Once you’ve created your free account, follow the steps below. If you don’t have an Azure account, you can review the steps to see the process for adding a simple resource lock to a resource.</p><h3>Task 1: Create a resource</h3><p>In order to apply a resource lock, you have to have a resource created in Azure. The first task focuses on creating a resource that you can then lock in subsequent tasks.</p><ol><li>Sign in to the Azure portal at <a href="https://portal.azure.com/">https://portal.azure.com</a></li><li>Select Create a resource.</li><li>Under Categories, select Storage.</li><li>Under Storage Account, select Create.</li><li>On the Basics tab of the Create storage account blade, fill in the following information. Leave the defaults for everything else.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/769/1*iv9zW1xaw2C4wfYaTWBdlg.png" /></figure><p>6. Select Review + Create to review your storage account settings and allow Azure to validate the configuration.</p><p>7. Once validated, select Create. Wait for the notification that the account was successfully created.</p><p>8. Select Go to resource.</p><h3>Task 2: Apply a read-only resource lock</h3><p>In this task you apply a read-only resource lock to the storage account. What impact do you think that will have on the storage account?</p><ol><li>Scroll down until you find the Settings section of the blade on the left of the screen.</li><li>Select Locks.</li><li>Select + Add.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/0*stYTFvFIGjQ7u__I.png" /></figure><p>4. Enter a Lock name.</p><p>5. Verify the Lock type is set to Read-only.</p><p>6. Select OK.</p><h3>Task 3: Add a container to the storage account</h3><p>In this task, you add a container to the storage account, this container is where you can store your blobs.</p><ol><li>Scroll up until you find the Data storage section of the blade on the left of the screen.</li><li>Select Containers.</li><li>Select + Container.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*YcYXE54yXzZ6wVJq.png" /></figure><p>4. Enter a container name and select Create.</p><p>5. You should receive an error message: Failed to create storage container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/0*PBygr-M-KWccYKJA.png" /></figure><p>Note</p><p>The error message lets you know that you couldn’t create a storage container because a lock is in place. The read-only lock prevents any create or update operations on the storage account, so you’re unable to create a storage container.</p><h3>Task 4: Modify the resource lock and create a storage container</h3><ol><li>Scroll down until you find the Settings section of the blade on the left of the screen.</li><li>Select Locks.</li><li>Select the read-only resource lock you created.</li><li>Change the Lock type to Delete and select OK.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*-w7NIB3KZw6aW19a.png" /></figure><p>5. Scroll up until you find the Data storage section of the blade on the left of the screen.</p><p>6. Select Containers.</p><p>7. Select + Container.</p><p>8. Enter a container name and select Create.</p><p>9. Your storage container should appear in your list of containers.</p><p>You can now understand how the read-only lock prevented you from adding a container to your storage account. Once the lock type was changed (you could have removed it instead), you were able to add a container.</p><h3>Task 5: Delete the storage account</h3><p>You’ll actually do this last task twice. Remember that there is a delete lock on the storage account, so you won’t actually be able to delete the storage account yet.</p><ol><li>Scroll up until you find Overview at the top of the blade on the left of the screen.</li><li>Select Overview.</li><li>Select Delete.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/0*vzIMnOHYr1ncv2qe.png" /></figure><p>You should get a notification letting you know you can’t delete the resource because it has a delete lock. In order to delete the storage account, you’ll need to remove the delete lock.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/0*HMcEdESmGYaa3e6s.png" /></figure><h3>Task 6: Remove the delete lock and delete the storage account</h3><p>In the final task, you remove the resource lock and delete the storage account from your Azure account. This step is important. You want to make sure you don’t have any idle resource just sitting in your account.</p><ol><li>Select your storage account name in the breadcrumb at the top of the screen.</li><li>Scroll down until you find the Settings section of the blade on the left of the screen.</li><li>Select Locks.</li><li>Select Delete.</li><li>Select Home in the breadcrumb at the top of the screen.</li><li>Select Storage accounts</li><li>Select the storage account you used for this exercise.</li><li>Select Delete.</li><li>To prevent accidental deletion, Azure prompts you to enter the name of the storage account you want to delete. Enter the name of the storage account and select Delete.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/729/0*jhXuxvVs8Actc1Ia.png" /></figure><p>10. You should receive a message that the storage account was deleted. If you go Home &gt; Storage accounts, you should see that the storage account you created for this exercise is gone.</p><h3><strong>Congratulations! You’ve completed configuring, updating, and removing a resource lock on an Azure resource.</strong></h3><p><strong>Important</strong></p><p><strong>Make sure you complete Task 6, the removal of the storage account. You are solely responsible for the resources in your Azure account. Make sure you clean up your account after completing this exercise.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38728fe20569" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Describe features and tools in Azure for governance and compliance]]></title>
            <link>https://medium.com/@shalinpatel./describe-features-and-tools-in-azure-for-governance-and-compliance-25ac47c741d6?source=rss-788747bff9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/25ac47c741d6</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[clou]]></category>
            <dc:creator><![CDATA[Shalin Patel]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 14:44:28 GMT</pubDate>
            <atom:updated>2024-01-19T14:44:28.816Z</atom:updated>
            <content:encoded><![CDATA[<p>you’ll be introduced to some of the features and tools you can use to help with governance of your Azure environment. You’ll also learn about tools you can use to help keep resources in compliance with corporate or regulatory requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/317/1*swVRTuZ7juTJCLtkvBZLqw.jpeg" /></figure><h3>Learning objectives</h3><p>After completing this module, you’ll be able to:</p><ul><li>Describe the purpose of Microsoft Purview.</li><li>Describe the purpose of Azure Policy.</li><li>Describe the purpose of resource locks.</li><li>Describe the purpose of the Service Trust portal.</li></ul><h3>Describe the purpose of Microsoft Purview</h3><p>Microsoft Purview is a family of data governance, risk, and compliance solutions that helps you get a single, unified view into your data. Microsoft Purview brings insights about your on-premises, multicloud, and software-as-a-service data together.</p><p>With Microsoft Purview, you can stay up-to-date on your data landscape thanks to:</p><ul><li>Automated data discovery</li><li>Sensitive data classification</li><li>End-to-end data lineage</li></ul><p>Two main solution areas comprise Microsoft Purview: risk and compliance and unified data governance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*xLKgMInB6a-h_9Vi.png" /></figure><h3>Microsoft Purview risk and compliance solutions</h3><p>Microsoft 365 features as a core component of the Microsoft Purview risk and compliance solutions. Microsoft Teams, OneDrive, and Exchange are just some of the Microsoft 365 services that Microsoft Purview uses to help manage and monitor your data. Microsoft Purview, by managing and monitoring your data, is able to help your organization:</p><ul><li>Protect sensitive data across clouds, apps, and devices.</li><li>Identify data risks and manage regulatory compliance requirements.</li><li>Get started with regulatory compliance.</li></ul><h3>Unified data governance</h3><p>Microsoft Purview has robust, unified data governance solutions that help manage your on-premises, multicloud, and software as a service data. Microsoft Purview’s robust data governance capabilities enable you to manage your data stored in Azure, SQL and Hive databases, locally, and even in other clouds like Amazon S3.</p><p>Microsoft Purview’s unified data governance helps your organization:</p><ul><li>Create an up-to-date map of your entire data estate that includes data classification and end-to-end lineage.</li><li>Identify where sensitive data is stored in your estate.</li><li>Create a secure environment for data consumers to find valuable data.</li><li>Generate insights about how your data is stored and used.</li><li>Manage access to the data in your estate securely and at scale.</li></ul><h3>Describe the purpose of Azure Policy</h3><p>How do you ensure that your resources stay compliant? Can you be alerted if a resource’s configuration has changed?</p><p>Azure Policy is a service in Azure that enables you to create, assign, and manage policies that control or audit your resources. These policies enforce different rules across your resource configurations so that those configurations stay compliant with corporate standards.</p><h3>How does Azure Policy define policies?</h3><p>Azure Policy enables you to define both individual policies and groups of related policies, known as initiatives. Azure Policy evaluates your resources and highlights resources that aren’t compliant with the policies you’ve created. Azure Policy can also prevent noncompliant resources from being created.</p><p>Azure Policies can be set at each level, enabling you to set policies on a specific resource, resource group, subscription, and so on. Additionally, Azure Policies are inherited, so if you set a policy at a high level, it will automatically be applied to all of the groupings that fall within the parent. For example, if you set an Azure Policy on a resource group, all resources created within that resource group will automatically receive the same policy.</p><p>Azure Policy comes with built-in policy and initiative definitions for Storage, Networking, Compute, Security Center, and Monitoring. For example, if you define a policy that allows only a certain size for the virtual machines (VMs) to be used in your environment, that policy is invoked when you create a new VM and whenever you resize existing VMs. Azure Policy also evaluates and monitors all current VMs in your environment, including VMs that were created before the policy was created.</p><p>In some cases, Azure Policy can automatically remediate noncompliant resources and configurations to ensure the integrity of the state of the resources. For example, if all resources in a certain resource group should be tagged with AppName tag and a value of “SpecialOrders,” Azure Policy will automatically apply that tag if it is missing. However, you still retain full control of your environment. If you have a specific resource that you don’t want Azure Policy to automatically fix, you can flag that resource as an exception — and the policy won’t automatically fix that resource.</p><p>Azure Policy also integrates with Azure DevOps by applying any continuous integration and delivery pipeline policies that pertain to the pre-deployment and post-deployment phases of your applications.</p><h3>What are Azure Policy initiatives?</h3><p>An Azure Policy initiative is a way of grouping related policies together. The initiative definition contains all of the policy definitions to help track your compliance state for a larger goal.</p><p>For example, Azure Policy includes an initiative named Enable Monitoring in Azure Security Center. Its goal is to monitor all available security recommendations for all Azure resource types in Azure Security Center.</p><p>Under this initiative, the following policy definitions are included:</p><ul><li>Monitor unencrypted SQL Database in Security Center This policy monitors for unencrypted SQL databases and servers.</li><li>Monitor OS vulnerabilities in Security Center This policy monitors servers that don’t satisfy the configured OS vulnerability baseline.</li><li>Monitor missing Endpoint Protection in Security Center This policy monitors for servers that don’t have an installed endpoint protection agent.</li></ul><p>In fact, the Enable Monitoring in Azure Security Center initiative contains over 100 separate policy definitions.</p><h3>Describe the purpose of resource locks</h3><p>resource lock prevents resources from being accidentally deleted or changed.</p><p>Even with Azure role-based access control (Azure RBAC) policies in place, there’s still a risk that people with the right level of access could delete critical cloud resources. Resource locks prevent resources from being deleted or updated, depending on the type of lock. Resource locks can be applied to individual resources, resource groups, or even an entire subscription. Resource locks are inherited, meaning that if you place a resource lock on a resource group, all of the resources within the resource group will also have the resource lock applied.</p><h3>Types of Resource Locks</h3><p>There are two types of resource locks, one that prevents users from deleting and one that prevents users from changing or deleting a resource.</p><ul><li>Delete means authorized users can still read and modify a resource, but they can’t delete the resource.</li><li>ReadOnly means authorized users can read a resource, but they can’t delete or update the resource. Applying this lock is similar to restricting all authorized users to the permissions granted by the Reader role.</li></ul><h3>How do I manage resource locks?</h3><p>You can manage resource locks from the Azure portal, PowerShell, the Azure CLI, or from an Azure Resource Manager template.</p><p>To view, add, or delete locks in the Azure portal, go to the Settings section of any resource’s Settings pane in the Azure portal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/0*iFMm6J4Ge8BNcWV6.png" /></figure><h3>How do I delete or change a locked resource?</h3><p>Although locking helps prevent accidental changes, you can still make changes by following a two-step process.</p><p>To modify a locked resource, you must first remove the lock. After you remove the lock, you can apply any action you have permissions to perform. Resource locks apply regardless of RBAC permissions. Even if you’re an owner of the resource, you must still remove the lock before you can perform the blocked activity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25ac47c741d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Describe the purpose of tags (Azure)]]></title>
            <link>https://medium.com/@shalinpatel./describe-the-purpose-of-tags-azure-b640eea9acc7?source=rss-788747bff9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/b640eea9acc7</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Shalin Patel]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 14:43:17 GMT</pubDate>
            <atom:updated>2024-01-19T14:43:17.014Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*lbm1diIxpFxmFR1pK591iw.png" /></figure><p>As your cloud usage grows, it’s increasingly important to stay organized. A good organization strategy helps you understand your cloud usage and can help you manage costs.</p><p>One way to organize related resources is to place them in their own subscriptions. You can also use resource groups to manage related resources. Resource tags are another way to organize resources. Tags provide extra information, or metadata, about your resources. This metadata is useful for:</p><ul><li>Resource management Tags enable you to locate and act on resources that are associated with specific workloads, environments, business units, and owners.</li><li>Cost management and optimization Tags enable you to group resources so that you can report on costs, allocate internal cost centers, track budgets, and forecast estimated cost.</li><li>Operations management Tags enable you to group resources according to how critical their availability is to your business. This grouping helps you formulate service-level agreements (SLAs). An SLA is an uptime or performance guarantee between you and your users.</li><li>Security Tags enable you to classify data by its security level, such as public or confidential.</li><li>Governance and regulatory compliance Tags enable you to identify resources that align with governance or regulatory compliance requirements, such as ISO 27001. Tags can also be part of your standards enforcement efforts. For example, you might require that all resources be tagged with an owner or department name.</li><li>Workload optimization and automation Tags can help you visualize all of the resources that participate in complex deployments. For example, you might tag a resource with its associated workload or application name and use software such as Azure DevOps to perform automated tasks on those resources.</li></ul><h3>How do I manage resource tags?</h3><p>You can add, modify, or delete resource tags through Windows PowerShell, the Azure CLI, Azure Resource Manager templates, the REST API, or the Azure portal.</p><p>You can use Azure Policy to enforce tagging rules and conventions. For example, you can require that certain tags be added to new resources as they’re provisioned. You can also define rules that reapply tags that have been removed. Resources don’t inherit tags from subscriptions and resource groups, meaning that you can apply tags at one level and not have those tags automatically show up at a different level, allowing you to create custom tagging schemas that change depending on the level (resource, resource group, subscription, and so on).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*jafKhk2zvA7AGg85z06QaA.png" /></figure><p>Keep in mind that you don’t need to enforce that a specific tag is present on all of your resources. For example, you might decide that only mission-critical resources have the Impact tag. All non-tagged resources would then not be considered as mission-critical.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b640eea9acc7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Describe the Microsoft Cost Management tool]]></title>
            <link>https://medium.com/@shalinpatel./describe-the-microsoft-cost-management-tool-65397aee9604?source=rss-788747bff9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/65397aee9604</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Shalin Patel]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 14:41:17 GMT</pubDate>
            <atom:updated>2024-01-19T14:41:17.119Z</atom:updated>
            <content:encoded><![CDATA[<p>Microsoft Azure is a global cloud provider, meaning you can provision resources anywhere in the world. You can provision resources rapidly to meet a sudden demand, or to test out a new feature, or on accident. If you accidentally provision new resources, you may not be aware of them until it’s time for your invoice. Cost Management is a service that helps avoid those situations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*0Rhsfe5Zapv8844kC8p-Ow.png" /></figure><h3>What is Cost Management?</h3><p>Cost Management provides the ability to quickly check Azure resource costs, create alerts based on resource spend, and create budgets that can be used to automate management of resources.</p><p>Cost analysis is a subset of Cost Management that provides a quick visual for your Azure costs. Using cost analysis, you can quickly view the total cost in a variety of different ways, including by billing cycle, region, resource, and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G8RQKCrvmQGZenkX.png" /></figure><p>You use cost analysis to explore and analyze your organizational costs. You can view aggregated costs by organization to understand where costs are accrued and to identify spending trends. And you can see accumulated costs over time to estimate monthly, quarterly, or even yearly cost trends against a budget.</p><h3>Cost alerts</h3><p>Cost alerts provide a single location to quickly check on all of the different alert types that may show up in the Cost Management service. The three types of alerts that may show up are:</p><ul><li>Budget alerts</li><li>Credit alerts</li><li>Department spending quota alerts.</li></ul><h3>Budget alerts</h3><p>Budget alerts notify you when spending, based on usage or cost, reaches or exceeds the amount defined in the alert condition of the budget. Cost Management budgets are created using the Azure portal or the Azure Consumption API.</p><p>In the Azure portal, budgets are defined by cost. Budgets are defined by cost or by consumption usage when using the Azure Consumption API. Budget alerts support both cost-based and usage-based budgets. Budget alerts are generated automatically whenever the budget alert conditions are met. You can view all cost alerts in the Azure portal. Whenever an alert is generated, it appears in cost alerts. An alert email is also sent to the people in the alert recipients list of the budget.</p><h3>Credit alerts</h3><p>Credit alerts notify you when your Azure credit monetary commitments are consumed. Monetary commitments are for organizations with Enterprise Agreements (EAs). Credit alerts are generated automatically at 90% and at 100% of your Azure credit balance. Whenever an alert is generated, it’s reflected in cost alerts, and in the email sent to the account owners.</p><h3>Department spending quota alerts</h3><p>Department spending quota alerts notify you when department spending reaches a fixed threshold of the quota. Spending quotas are configured in the EA portal. Whenever a threshold is met, it generates an email to department owners, and appears in cost alerts. For example, 50 percent or 75 percent of the quota.</p><h3>Budgets</h3><p>A budget is where you set a spending limit for Azure. You can set budgets based on a subscription, resource group, service type, or other criteria. When you set a budget, you will also set a budget alert. When the budget hits the budget alert level, it will trigger a budget alert that shows up in the cost alerts area. If configured, budget alerts will also send an email notification that a budget alert threshold has been triggered.</p><p>A more advanced use of budgets enables budget conditions to trigger automation that suspends or otherwise modifies resources once the trigger condition has occurred.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65397aee9604" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>