<?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 CloudSewa on Medium]]></title>
        <description><![CDATA[Stories by CloudSewa on Medium]]></description>
        <link>https://medium.com/@101awscloud?source=rss-696bb91d1630------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NzFwCF1c-3agaPG2ustffg.jpeg</url>
            <title>Stories by CloudSewa on Medium</title>
            <link>https://medium.com/@101awscloud?source=rss-696bb91d1630------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:03:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@101awscloud/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[Monitoring & Alerting on Google Cloud Platform of Cloud Compute Engine on Slack and Email]]></title>
            <link>https://medium.com/@101awscloud/monitoring-alerting-on-google-cloud-platform-of-cloud-compute-engine-on-slack-and-email-2c9a144a3f0f?source=rss-696bb91d1630------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c9a144a3f0f</guid>
            <category><![CDATA[vm-instance]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[alerting]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[google-compute-engine]]></category>
            <dc:creator><![CDATA[CloudSewa]]></dc:creator>
            <pubDate>Fri, 27 Jan 2023 11:05:04 GMT</pubDate>
            <atom:updated>2023-01-27T11:05:04.814Z</atom:updated>
            <content:encoded><![CDATA[<p>Go to “<strong><em>Monitoring Dashboard” </em></strong>on gcp project</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9s9qQjPZVILFMei3.png" /></figure><p>Go to<strong> “<em>Uptime Check” </em></strong>&amp; Click on <strong><em>“CREATE UPTIME CHECK”</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nxGItE0u4iyLhTWb" /></figure><p><strong>In Title Section:</strong></p><p>Input all the required information in the given Fields</p><ul><li>Title<strong>:</strong> <strong><em>[Enter required name]</em></strong></li><li>Click on<strong> <em>NEXT</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/447/0*ufH3oYVIYmst92om.png" /></figure><p><strong>In Target Section:</strong></p><ul><li>Protocol: <strong>HTTPS</strong></li><li>Resource Type: <strong>Instance</strong></li><li>Applies to: <strong>Single</strong></li><li>Instance: <strong>instance-1</strong></li><li>Path:<strong> /</strong></li><li>Check frequency:<strong> 1 min</strong></li><li><strong>Click on Next</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2SadENyrB2YR0XpK" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IwypPCCdL_he5rNBiJfs5Q.jpeg" /></figure><p><strong>In Response Validation:</strong></p><ul><li>Response Timeout: <strong>10 seconds</strong></li><li>Others leave <strong>Default</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/549/0*-_s2-lzGASM802JV.png" /></figure><p><strong>In Alert &amp; Notification:</strong></p><ul><li>Name: <strong><em>[Enter required name]</em></strong></li><li>Duration: <strong>1 minute</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/549/0*ifjTC1E6US1Az5VP.png" /></figure><p><strong>For Notification Channels:</strong></p><p>Click<em> </em><strong><em>Manage Notification Channels</em></strong></p><p>Email Address:<strong> verylazycoders@gmail.com</strong></p><p>Display Name:<strong> test</strong></p><p><strong>If needed</strong></p><p>Slack:<strong> #ABC</strong></p><p>Slack Name:<strong> ABC-Slack</strong></p><p>Team:<strong> Team ABC</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3xsY6Dm_u8nfIE3v" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6kSTLzV4C6z_JSU_" /></figure><p>Click on <strong><em>SAVE</em></strong></p><p><strong>Refresh and Select</strong></p><ul><li>Email:<strong> Test</strong></li><li>Click on<strong> OK</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X4THjbbyav_UOnw2" /></figure><p>Click on<strong> <em>Test </em></strong>for testing</p><p>Click on<strong> <em>Create</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a8ag2DYhS7PvyMZY" /></figure><p>After</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NfmPsTERbvMlDp48" /></figure><p><strong>Email Notification:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qpG6wwaDyTZ9hi1i" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c9a144a3f0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Platform CICD Continuous Integration, Continuous Delivery / Continuous Deployment]]></title>
            <link>https://medium.com/@101awscloud/google-cloud-platform-cicd-continuous-integration-continuous-delivery-continuous-deployment-ff9fa1338b7a?source=rss-696bb91d1630------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff9fa1338b7a</guid>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[google-cloud-run]]></category>
            <category><![CDATA[codepipeline]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[cloud-build]]></category>
            <dc:creator><![CDATA[CloudSewa]]></dc:creator>
            <pubDate>Thu, 26 Jan 2023 09:21:02 GMT</pubDate>
            <atom:updated>2023-01-26T09:21:02.252Z</atom:updated>
            <content:encoded><![CDATA[<p>Create account for <strong><em>GCP</em>: </strong><a href="https://cloud.google.com/"><strong>https://cloud.google.com/</strong></a></p><p>Create a <strong>VM instance</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sC6jDZHXhBUt3Zww" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oSEtQLtx_qkWaCqG" /></figure><p>Connecting by<strong> SSH</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p2QNc8Qi8qkceaBb" /></figure><p>[ If you don’t have an <strong>existing SSH key</strong>, Now, copy your public SSH key, go back to the <strong>GCP user interface</strong> and click on the name of your VM instance , click on Edit, scroll down to the <strong>SSH Keys section</strong>, click on the <strong>Add an Item button</strong>, and paste your <strong>public SSH key.]</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lEsYK0zLzwTrRiap" /></figure><ul><li>Before clicking on the <strong>Save</strong> button, take note of the<strong> username of your SSH key </strong>displayed right beside your public SSH key</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K_QVhAP0yxPQQ7ah" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*03oYpqKjbmkAj5nq" /></figure><p>Clone the git repository to the newly created VM instances <strong>[change branch].</strong></p><pre>git clone [Repo name]</pre><p>Add the<strong> Dockerfile environment </strong>and C<strong>loud-build .yaml </strong>to the VM instances.</p><p><strong># Dockerfile</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/0*fm_Dp-jMshysCc9j" /></figure><pre>FROM nginx:alpine<br>WORKDIR /usr/share/nginx/html<br>RUN rm -f *<br>COPY config/default.conf / /etc/nginx/conf.d./default.conf<br>COPY ./ /usr/share/nginx/html</pre><p><strong>#</strong> <strong>Cloudbuild.yaml</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/0*1NXIW5xJjbXNXzih" /></figure><p>To join the <strong>SQL server</strong> to the VM instances</p><pre>- user=root gcloud sql connect myinstance</pre><p>After that, create a database and upload data.</p><p><strong>(In Google Cloud, the cloud SQL admin API should be enabled.)</strong></p><p>Connect and configure the<strong> cloud storage.</strong></p><p>After succe:ssfully running in SSH, the next step is to perform<strong> CI/CD.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/0*ZXmvvE6_q_OMHD8-" /></figure><p>we need to run commit the repo:</p><pre>git commit -m &quot;name&quot;</pre><p>we need to add the origin:</p><pre>git add .</pre><p><strong>Cloud Build</strong></p><p>Upload the file from your git repository.</p><ul><li><em>Builds the docker image in Google Cloud Platform</em></li></ul><pre>docker tag gcr.io/${GOOGLE_CLOUD_PROJECT}/quickstart-image .</pre><ul><li><em>Pushes the container image into the Google Cloud Registry</em></li></ul><p>[Global]</p><pre>docker push gcr.io/myproject/busybox</pre><p>[For specific region]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k1-8zgGkXsgmTBXyOcncBw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aWV_YXQ7zX-HWk9GWh34og.jpeg" /></figure><p>Create the <strong>trigger</strong>.</p><p>(Before creating the trigger, we need to select the repository)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5EpOU7_u9CwwKAaL" /></figure><ul><li>After that, we need to access the branch of the project in branch section.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nSqMwU2ZvF78YTbH" /></figure><ul><li>After that, our trigger Configuration</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j1rCwTWJbjf1NrIn" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jTy4xmMPs6yW3C1g" /></figure><p>Trigger is created,<strong> Cloud Build</strong> has access to deploy to <strong>Cloud Run</strong>.</p><ul><li>go to settings and Enable the <strong>service account permission </strong>for Cloud Run</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MUMmzsxxKX5mHHZi" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zddPd9kg3FHH3gXj" /></figure><p><strong>In History</strong>, you would see that the build has created successfully</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zAk3uTUcs5fnSmTj" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ax2NaJNci9A-Giv9" /></figure><p>After completion, go to <strong>Google Container Registry</strong> and check if Cloud Build has pushed an image or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IBFSHKjyiNcL8L5Y" /></figure><p>Go to Google Cloud Run, Cloud Build has <strong>deployed</strong> a new service</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JArplhD7FsDcfmAx" /></figure><p><strong>Fetch the URL</strong> and access it from the browser</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UktO80LeRGt-wp8K" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff9fa1338b7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Resource Manager (ARM) Templates]]></title>
            <link>https://awstip.com/azure-resource-manager-arm-templates-ab7c0da1ad97?source=rss-696bb91d1630------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab7c0da1ad97</guid>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[arm-template-specs]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[arm-templates]]></category>
            <dc:creator><![CDATA[CloudSewa]]></dc:creator>
            <pubDate>Thu, 26 Jan 2023 03:57:18 GMT</pubDate>
            <atom:updated>2023-01-27T15:43:55.703Z</atom:updated>
            <content:encoded><![CDATA[<p>Azure Resource Manager (ARM) templates are a way to deploy and manage resources on Azure. They use JSON or YAML to define the infrastructure and configuration of Azure resources. The templates can be used to create, update, and delete resources in a consistent and repeatable manner. ARM templates can be deployed using the Azure portal, Azure PowerShell, Azure CLI, or Azure SDKs. They can also be integrated with DevOps tools such as Azure DevOps and GitHub for automated deployment.</p><p>Here are some examples of what you can do with Azure Resource Manager (ARM) templates:</p><ol><li><strong>Create a virtual machine: </strong>You can use an ARM template to create a virtual machine with specific configurations, such as the size of the VM, the image to use, and the storage account.</li><li><strong>Deploy a web app:</strong> You can use an ARM template to deploy a web app to Azure App Service, including the app’s configuration, such as the runtime stack and connection strings.</li><li><strong>Create a storage account:</strong> You can use an ARM template to create a storage account, including the type of storage account, replication options, and access keys.</li><li><strong>Create a virtual network:</strong> You can use an ARM template to create a virtual network, including the subnets, security rules, and DNS settings.</li><li><strong>Deploy a database: </strong>You can use an ARM template to deploy a database to Azure SQL Database, including the configuration options such as the performance level and backup schedule.</li><li><strong>Create a Kubernetes Cluster:</strong> You can use an ARM template to create a Kubernetes cluster in Azure Kubernetes Service (AKS) with specific configurations, such as the number of nodes, container registry and authentication.</li></ol><p>These are just a few examples of what can be done with ARM templates on Azure.</p><p>Here is an example of an Azure Resource Manager (ARM) template that creates a virtual machine with a specific configuration:</p><ul><li>A virtual network</li><li>A subnet</li><li>A public IP address</li><li>A network security group</li><li>A virtual machine</li></ul><pre>{<br>  &quot;$schema&quot;: &quot;https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#&quot;,<br>  &quot;contentVersion&quot;: &quot;1.0.0.0&quot;,<br>  &quot;metadata&quot;: {<br>    &quot;_generator&quot;: {<br>      &quot;name&quot;: &quot;bicep&quot;,<br>      &quot;version&quot;: &quot;0.8.9.13224&quot;,<br>      &quot;templateHash&quot;: &quot;15495738823141086515&quot;<br>    }<br>  },<br>  &quot;parameters&quot;: {<br>    &quot;adminUsername&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;metadata&quot;: {<br>        &quot;description&quot;: &quot;Username for the Virtual Machine.&quot;<br>      }<br>    },<br>    &quot;adminPassword&quot;: {<br>      &quot;type&quot;: &quot;secureString&quot;,<br>      &quot;minLength&quot;: 12,<br>      &quot;metadata&quot;: {<br>        &quot;description&quot;: &quot;Password for the Virtual Machine.&quot;<br>      }<br>    },<br>    &quot;dnsLabelPrefix&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;defaultValue&quot;: &quot;[toLower(format(&#39;{0}-{1}&#39;, parameters(&#39;vmName&#39;), uniqueString(resourceGroup().id, parameters(&#39;vmName&#39;))))]&quot;,<br>      &quot;metadata&quot;: {<br>        &quot;description&quot;: &quot;Unique DNS Name for the Public IP used to access the Virtual Machine.&quot;<br>      }<br>    },<br>    &quot;publicIpName&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;defaultValue&quot;: &quot;myPublicIP&quot;,<br>      &quot;metadata&quot;: {<br>        &quot;description&quot;: &quot;Name for the Public IP used to access the Virtual Machine.&quot;<br>      }<br>    },<br>    &quot;publicIPAllocationMethod&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;defaultValue&quot;: &quot;Dynamic&quot;,<br>      &quot;allowedValues&quot;: [<br>        &quot;Dynamic&quot;,<br>        &quot;Static&quot;<br>      ],<br>      &quot;metadata&quot;: {<br>        &quot;description&quot;: &quot;Allocation method for the Public IP used to access the Virtual Machine.&quot;<br>      }<br>    },<br>    &quot;publicIpSku&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;defaultValue&quot;: &quot;Basic&quot;,<br>      &quot;allowedValues&quot;: [<br>        &quot;Basic&quot;,<br>        &quot;Standard&quot;<br>      ],<br>      &quot;metadata&quot;: {<br>        &quot;description&quot;: &quot;SKU for the Public IP used to access the Virtual Machine.&quot;<br>      }<br>    },<br>    &quot;OSVersion&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;defaultValue&quot;: &quot;2022-datacenter-azure-edition-core&quot;,<br>      &quot;allowedValues&quot;: [<br>        &quot;2008-R2-SP1&quot;,<br>        &quot;2008-R2-SP1-smalldisk&quot;,<br>        &quot;2012-Datacenter&quot;,<br>        &quot;2012-datacenter-gensecond&quot;,<br>        &quot;2012-Datacenter-smalldisk&quot;,<br>        &quot;2012-datacenter-smalldisk-g2&quot;,<br>        &quot;2012-Datacenter-zhcn&quot;,<br>        &quot;2012-datacenter-zhcn-g2&quot;,<br>        &quot;2012-R2-Datacenter&quot;,<br>        &quot;2012-r2-datacenter-gensecond&quot;,<br>        &quot;2012-R2-Datacenter-smalldisk&quot;,<br>        &quot;2012-r2-datacenter-smalldisk-g2&quot;,<br>        &quot;2012-R2-Datacenter-zhcn&quot;,<br>        &quot;2012-r2-datacenter-zhcn-g2&quot;,<br>        &quot;2016-Datacenter&quot;,<br>        &quot;2016-datacenter-gensecond&quot;,<br>        &quot;2016-datacenter-gs&quot;,<br>        &quot;2016-Datacenter-Server-Core&quot;,<br>        &quot;2016-datacenter-server-core-g2&quot;,<br>        &quot;2016-Datacenter-Server-Core-smalldisk&quot;,<br>        &quot;2016-datacenter-server-core-smalldisk-g2&quot;,<br>        &quot;2016-Datacenter-smalldisk&quot;,<br>        &quot;2016-datacenter-smalldisk-g2&quot;,<br>        &quot;2016-Datacenter-with-Containers&quot;,<br>        &quot;2016-datacenter-with-containers-g2&quot;,<br>        &quot;2016-datacenter-with-containers-gs&quot;,<br>        &quot;2016-Datacenter-zhcn&quot;,<br>        &quot;2016-datacenter-zhcn-g2&quot;,<br>        &quot;2019-Datacenter&quot;,<br>        &quot;2019-Datacenter-Core&quot;,<br>        &quot;2019-datacenter-core-g2&quot;,<br>        &quot;2019-Datacenter-Core-smalldisk&quot;,<br>        &quot;2019-datacenter-core-smalldisk-g2&quot;,<br>        &quot;2019-Datacenter-Core-with-Containers&quot;,<br>        &quot;2019-datacenter-core-with-containers-g2&quot;,<br>        &quot;2019-Datacenter-Core-with-Containers-smalldisk&quot;,<br>        &quot;2019-datacenter-core-with-containers-smalldisk-g2&quot;,<br>        &quot;2019-datacenter-gensecond&quot;,<br>        &quot;2019-datacenter-gs&quot;,<br>        &quot;2019-Datacenter-smalldisk&quot;,<br>        &quot;2019-datacenter-smalldisk-g2&quot;,<br>        &quot;2019-Datacenter-with-Containers&quot;,<br>        &quot;2019-datacenter-with-containers-g2&quot;,<br>        &quot;2019-datacenter-with-containers-gs&quot;,<br>        &quot;2019-Datacenter-with-Containers-smalldisk&quot;,<br>        &quot;2019-datacenter-with-containers-smalldisk-g2&quot;,<br>        &quot;2019-Datacenter-zhcn&quot;,<br>        &quot;2019-datacenter-zhcn-g2&quot;,<br>        &quot;2022-datacenter&quot;,<br>        &quot;2022-datacenter-azure-edition&quot;,<br>        &quot;2022-datacenter-azure-edition-core&quot;,<br>        &quot;2022-datacenter-azure-edition-core-smalldisk&quot;,<br>        &quot;2022-datacenter-azure-edition-smalldisk&quot;,<br>        &quot;2022-datacenter-core&quot;,<br>        &quot;2022-datacenter-core-g2&quot;,<br>        &quot;2022-datacenter-core-smalldisk&quot;,<br>        &quot;2022-datacenter-core-smalldisk-g2&quot;,<br>        &quot;2022-datacenter-g2&quot;,<br>        &quot;2022-datacenter-smalldisk&quot;,<br>        &quot;2022-datacenter-smalldisk-g2&quot;<br>      ],<br>      &quot;metadata&quot;: {<br>        &quot;description&quot;: &quot;The Windows version for the VM. This will pick a fully patched image of this given Windows version.&quot;<br>      }<br>    },<br>    &quot;vmSize&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;defaultValue&quot;: &quot;Standard_D2s_v5&quot;,<br>      &quot;metadata&quot;: {<br>        &quot;description&quot;: &quot;Size of the virtual machine.&quot;<br>      }<br>    },<br>    &quot;location&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;defaultValue&quot;: &quot;[resourceGroup().location]&quot;,<br>      &quot;metadata&quot;: {<br>        &quot;description&quot;: &quot;Location for all resources.&quot;<br>      }<br>    },<br>    &quot;vmName&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;defaultValue&quot;: &quot;simple-vm&quot;,<br>      &quot;metadata&quot;: {<br>        &quot;description&quot;: &quot;Name of the virtual machine.&quot;<br>      }<br>    }<br>  },<br>  &quot;variables&quot;: {<br>    &quot;storageAccountName&quot;: &quot;[format(&#39;bootdiags{0}&#39;, uniqueString(resourceGroup().id))]&quot;,<br>    &quot;nicName&quot;: &quot;myVMNic&quot;,<br>    &quot;addressPrefix&quot;: &quot;10.0.0.0/16&quot;,<br>    &quot;subnetName&quot;: &quot;Subnet&quot;,<br>    &quot;subnetPrefix&quot;: &quot;10.0.0.0/24&quot;,<br>    &quot;virtualNetworkName&quot;: &quot;MyVNET&quot;,<br>    &quot;networkSecurityGroupName&quot;: &quot;default-NSG&quot;<br>  },<br>  &quot;resources&quot;: [<br>    {<br>      &quot;type&quot;: &quot;Microsoft.Storage/storageAccounts&quot;,<br>      &quot;apiVersion&quot;: &quot;2021-04-01&quot;,<br>      &quot;name&quot;: &quot;[variables(&#39;storageAccountName&#39;)]&quot;,<br>      &quot;location&quot;: &quot;[parameters(&#39;location&#39;)]&quot;,<br>      &quot;sku&quot;: {<br>        &quot;name&quot;: &quot;Standard_LRS&quot;<br>      },<br>      &quot;kind&quot;: &quot;Storage&quot;<br>    },<br>    {<br>      &quot;type&quot;: &quot;Microsoft.Network/publicIPAddresses&quot;,<br>      &quot;apiVersion&quot;: &quot;2021-02-01&quot;,<br>      &quot;name&quot;: &quot;[parameters(&#39;publicIpName&#39;)]&quot;,<br>      &quot;location&quot;: &quot;[parameters(&#39;location&#39;)]&quot;,<br>      &quot;sku&quot;: {<br>        &quot;name&quot;: &quot;[parameters(&#39;publicIpSku&#39;)]&quot;<br>      },<br>      &quot;properties&quot;: {<br>        &quot;publicIPAllocationMethod&quot;: &quot;[parameters(&#39;publicIPAllocationMethod&#39;)]&quot;,<br>        &quot;dnsSettings&quot;: {<br>          &quot;domainNameLabel&quot;: &quot;[parameters(&#39;dnsLabelPrefix&#39;)]&quot;<br>        }<br>      }<br>    },<br>    {<br>      &quot;type&quot;: &quot;Microsoft.Network/networkSecurityGroups&quot;,<br>      &quot;apiVersion&quot;: &quot;2021-02-01&quot;,<br>      &quot;name&quot;: &quot;[variables(&#39;networkSecurityGroupName&#39;)]&quot;,<br>      &quot;location&quot;: &quot;[parameters(&#39;location&#39;)]&quot;,<br>      &quot;properties&quot;: {<br>        &quot;securityRules&quot;: [<br>          {<br>            &quot;name&quot;: &quot;default-allow-3389&quot;,<br>            &quot;properties&quot;: {<br>              &quot;priority&quot;: 1000,<br>              &quot;access&quot;: &quot;Allow&quot;,<br>              &quot;direction&quot;: &quot;Inbound&quot;,<br>              &quot;destinationPortRange&quot;: &quot;3389&quot;,<br>              &quot;protocol&quot;: &quot;Tcp&quot;,<br>              &quot;sourcePortRange&quot;: &quot;*&quot;,<br>              &quot;sourceAddressPrefix&quot;: &quot;*&quot;,<br>              &quot;destinationAddressPrefix&quot;: &quot;*&quot;<br>            }<br>          }<br>        ]<br>      }<br>    },<br>    {<br>      &quot;type&quot;: &quot;Microsoft.Network/virtualNetworks&quot;,<br>      &quot;apiVersion&quot;: &quot;2021-02-01&quot;,<br>      &quot;name&quot;: &quot;[variables(&#39;virtualNetworkName&#39;)]&quot;,<br>      &quot;location&quot;: &quot;[parameters(&#39;location&#39;)]&quot;,<br>      &quot;properties&quot;: {<br>        &quot;addressSpace&quot;: {<br>          &quot;addressPrefixes&quot;: [<br>            &quot;[variables(&#39;addressPrefix&#39;)]&quot;<br>          ]<br>        },<br>        &quot;subnets&quot;: [<br>          {<br>            &quot;name&quot;: &quot;[variables(&#39;subnetName&#39;)]&quot;,<br>            &quot;properties&quot;: {<br>              &quot;addressPrefix&quot;: &quot;[variables(&#39;subnetPrefix&#39;)]&quot;,<br>              &quot;networkSecurityGroup&quot;: {<br>                &quot;id&quot;: &quot;[resourceId(&#39;Microsoft.Network/networkSecurityGroups&#39;, variables(&#39;networkSecurityGroupName&#39;))]&quot;<br>              }<br>            }<br>          }<br>        ]<br>      },<br>      &quot;dependsOn&quot;: [<br>        &quot;[resourceId(&#39;Microsoft.Network/networkSecurityGroups&#39;, variables(&#39;networkSecurityGroupName&#39;))]&quot;<br>      ]<br>    },<br>    {<br>      &quot;type&quot;: &quot;Microsoft.Network/networkInterfaces&quot;,<br>      &quot;apiVersion&quot;: &quot;2021-02-01&quot;,<br>      &quot;name&quot;: &quot;[variables(&#39;nicName&#39;)]&quot;,<br>      &quot;location&quot;: &quot;[parameters(&#39;location&#39;)]&quot;,<br>      &quot;properties&quot;: {<br>        &quot;ipConfigurations&quot;: [<br>          {<br>            &quot;name&quot;: &quot;ipconfig1&quot;,<br>            &quot;properties&quot;: {<br>              &quot;privateIPAllocationMethod&quot;: &quot;Dynamic&quot;,<br>              &quot;publicIPAddress&quot;: {<br>                &quot;id&quot;: &quot;[resourceId(&#39;Microsoft.Network/publicIPAddresses&#39;, parameters(&#39;publicIpName&#39;))]&quot;<br>              },<br>              &quot;subnet&quot;: {<br>                &quot;id&quot;: &quot;[resourceId(&#39;Microsoft.Network/virtualNetworks/subnets&#39;, variables(&#39;virtualNetworkName&#39;), variables(&#39;subnetName&#39;))]&quot;<br>              }<br>            }<br>          }<br>        ]<br>      },<br>      &quot;dependsOn&quot;: [<br>        &quot;[resourceId(&#39;Microsoft.Network/publicIPAddresses&#39;, parameters(&#39;publicIpName&#39;))]&quot;,<br>        &quot;[resourceId(&#39;Microsoft.Network/virtualNetworks&#39;, variables(&#39;virtualNetworkName&#39;))]&quot;<br>      ]<br>    },<br>    {<br>      &quot;type&quot;: &quot;Microsoft.Compute/virtualMachines&quot;,<br>      &quot;apiVersion&quot;: &quot;2021-03-01&quot;,<br>      &quot;name&quot;: &quot;[parameters(&#39;vmName&#39;)]&quot;,<br>      &quot;location&quot;: &quot;[parameters(&#39;location&#39;)]&quot;,<br>      &quot;properties&quot;: {<br>        &quot;hardwareProfile&quot;: {<br>          &quot;vmSize&quot;: &quot;[parameters(&#39;vmSize&#39;)]&quot;<br>        },<br>        &quot;osProfile&quot;: {<br>          &quot;computerName&quot;: &quot;[parameters(&#39;vmName&#39;)]&quot;,<br>          &quot;adminUsername&quot;: &quot;[parameters(&#39;adminUsername&#39;)]&quot;,<br>          &quot;adminPassword&quot;: &quot;[parameters(&#39;adminPassword&#39;)]&quot;<br>        },<br>        &quot;storageProfile&quot;: {<br>          &quot;imageReference&quot;: {<br>            &quot;publisher&quot;: &quot;MicrosoftWindowsServer&quot;,<br>            &quot;offer&quot;: &quot;WindowsServer&quot;,<br>            &quot;sku&quot;: &quot;[parameters(&#39;OSVersion&#39;)]&quot;,<br>            &quot;version&quot;: &quot;latest&quot;<br>          },<br>          &quot;osDisk&quot;: {<br>            &quot;createOption&quot;: &quot;FromImage&quot;,<br>            &quot;managedDisk&quot;: {<br>              &quot;storageAccountType&quot;: &quot;StandardSSD_LRS&quot;<br>            }<br>          },<br>          &quot;dataDisks&quot;: [<br>            {<br>              &quot;diskSizeGB&quot;: 1023,<br>              &quot;lun&quot;: 0,<br>              &quot;createOption&quot;: &quot;Empty&quot;<br>            }<br>          ]<br>        },<br>        &quot;networkProfile&quot;: {<br>          &quot;networkInterfaces&quot;: [<br>            {<br>              &quot;id&quot;: &quot;[resourceId(&#39;Microsoft.Network/networkInterfaces&#39;, variables(&#39;nicName&#39;))]&quot;<br>            }<br>          ]<br>        },<br>        &quot;diagnosticsProfile&quot;: {<br>          &quot;bootDiagnostics&quot;: {<br>            &quot;enabled&quot;: true,<br>            &quot;storageUri&quot;: &quot;[reference(resourceId(&#39;Microsoft.Storage/storageAccounts&#39;, variables(&#39;storageAccountName&#39;))).primaryEndpoints.blob]&quot;<br>          }<br>        }<br>      },<br>      &quot;dependsOn&quot;: [<br>        &quot;[resourceId(&#39;Microsoft.Network/networkInterfaces&#39;, variables(&#39;nicName&#39;))]&quot;,<br>        &quot;[resourceId(&#39;Microsoft.Storage/storageAccounts&#39;, variables(&#39;storageAccountName&#39;))]&quot;<br>      ]<br>    }<br>  ],<br>  &quot;outputs&quot;: {<br>    &quot;hostname&quot;: {<br>      &quot;type&quot;: &quot;string&quot;,<br>      &quot;value&quot;: &quot;[reference(resourceId(&#39;Microsoft.Network/publicIPAddresses&#39;, parameters(&#39;publicIpName&#39;))).dnsSettings.fqdn]&quot;<br>    }<br>  }<br>}</pre><p>References:<br><a href="https://learn.microsoft.com/en-us/azure/devtest-labs/devtest-lab-use-resource-manager-template#store-arm-templates-in-git-repositories">https://learn.microsoft.com/en-us/azure/devtest-labs/devtest-lab-use-resource-manager-template#store-arm-templates-in-git-repositories</a></p><p><a href="https://learn.microsoft.com/en-us/azure/virtual-machines/windows/ps-template">https://learn.microsoft.com/en-us/azure/virtual-machines/windows/ps-template</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab7c0da1ad97" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/azure-resource-manager-arm-templates-ab7c0da1ad97">Azure Resource Manager (ARM) Templates</a> was originally published in <a href="https://awstip.com/">AWS Tip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hosting a SAS (Software as a Service) application on Kubernetes Part-II]]></title>
            <link>https://medium.com/@101awscloud/hosting-a-sas-software-as-a-service-application-on-kubernetes-part-ii-b47788404044?source=rss-696bb91d1630------2</link>
            <guid isPermaLink="false">https://medium.com/p/b47788404044</guid>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[hosting]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[sass]]></category>
            <dc:creator><![CDATA[CloudSewa]]></dc:creator>
            <pubDate>Thu, 26 Jan 2023 03:24:56 GMT</pubDate>
            <atom:updated>2023-01-26T03:24:56.194Z</atom:updated>
            <content:encoded><![CDATA[<p>To create a Kubernetes cluster on GCP using Google Kubernetes Engine (GKE), you can follow these steps:</p><ol><li>Go to the GCP Console and navigate to the Kubernetes Engine page.</li><li>Click the “Create Cluster” button.</li><li>Select the desired settings for your cluster, such as the number of nodes, the machine type, and the zone or region.</li><li>Configure any additional settings, such as the Kubernetes version, the network and subnet, and the node pool settings.</li><li>Choose if you want to enable stackdriver monitoring, logging and Kubernetes addons.</li><li>Click the “Create” button to create the cluster.</li><li>Once the cluster is created, you can use the gcloud command-line tool or the GCP Console to interact with your cluster and deploy resources to it.</li><li>To connect to the cluster you can use gcloud container clusters get-credentials &lt;cluster-name&gt;</li><li>You can also enable the Kubernetes dashboard to visualize and manage the resources in your cluster through the GKE dashboard.</li><li>Keep in mind that you will be charged for the resources you use on GCP, including the nodes and resources in your GKE cluster. You can monitor your costs and usage in the GCP Console.</li></ol><p>Also, you can use other GCP services such as Cloud Run, App Engine Flexible Environment, or Cloud Functions to deploy and manage your Kubernetes applications on GCP, depending on your specific use case and requirements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b47788404044" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hosting a SAS (Software as a Service) application on Kubernetes Part-I]]></title>
            <link>https://medium.com/@101awscloud/hosting-a-sas-software-as-a-service-application-on-kubernetes-90532a8ea5c6?source=rss-696bb91d1630------2</link>
            <guid isPermaLink="false">https://medium.com/p/90532a8ea5c6</guid>
            <category><![CDATA[hosting]]></category>
            <category><![CDATA[application]]></category>
            <category><![CDATA[sass]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[CloudSewa]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 17:20:57 GMT</pubDate>
            <atom:updated>2023-01-25T17:32:36.208Z</atom:updated>
            <content:encoded><![CDATA[<p>Hosting a SAS (Software as a Service) application on Kubernetes can be a great way to take advantage of the platform’s powerful features for scaling, self-healing, and rolling updates.</p><p>Here are the general steps to host a SAS application on Kubernetes:</p><ol><li>Package your application as a container image. You can use a containerization tool such as Docker to create a container image of your application.</li><li>Push the container image to a container registry. You can use Google Container Registry (GCR) to host your container images.</li><li>Create a Kubernetes cluster on GCP. You can use Google Kubernetes Engine (GKE) to create and manage your Kubernetes cluster on GCP.</li><li>Create a Kubernetes Deployment for your application. This defines the desired state for your application, such as the number of replicas and the container image to use. You can use kubectl create command to create the Deployment in your cluster.</li><li>Create a Kubernetes Service to expose the application to external traffic. This creates a stable endpoint for external clients to access your application. You can use kubectl create command to create the Service in your cluster.</li><li>Create Kubernetes Ingress to route external traffic to the service. It is a way to route the traffic based on the domain name or path.</li><li>Create External Load Balancer to expose the ingress to external traffic. With GCP you can leverage the Kubernetes Ingress to create a LoadBalancer that forwards traffic to the ingress.</li><li>Monitor your application and make updates as needed. You can use Kubernetes features such as rolling updates and self-healing to update your application and ensure that it is running smoothly.</li><li>Secure your application with GCP Security features. You can use GCP security features such as firewall rules, Identity-Aware Proxy, and Kubernetes Network Policies to secure your application.</li><li>Consider using GCP services to enhance your application functionality. You can use GCP services such as Cloud SQL, Cloud Memorystore, and Cloud Spanner to enhance your application functionality.</li></ol><p>It is important to consider the requirements of your SAS application when deploying it on GCP Kubernetes. For example, if your application requires a database, you should also deploy a Kubernetes StatefulSet or a Deployment with a Persistent Volume for the database.</p><p>It is also recommended to consider the security and compliance requirements for your SAS application and to configure GCP and Kubernetes accordingly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90532a8ea5c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Kubernetes ?]]></title>
            <link>https://medium.com/@101awscloud/what-is-kubernetes-f60ff2ef6b53?source=rss-696bb91d1630------2</link>
            <guid isPermaLink="false">https://medium.com/p/f60ff2ef6b53</guid>
            <category><![CDATA[yaml]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[CloudSewa]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 16:18:33 GMT</pubDate>
            <atom:updated>2023-01-25T16:19:08.686Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is Kubernetes with Real World Example?</h3><p>Kubernetes is an open-source platform for automating deployment, scaling, and management of containerized applications. It is designed to work with a variety of container technologies, such as Docker. Some common use cases for Kubernetes include:</p><ul><li>Deploying and scaling web applications</li><li>Automating the roll-out and roll-back of new features and updates</li><li>Managing and scaling batch jobs and background tasks</li><li>Running and scaling stateful services such as databases</li></ul><p>Kubernetes can be used in a variety of environments, including on-premises, in the cloud, or in hybrid environments. Some popular cloud providers that offer managed Kubernetes services include Google Kubernetes Engine (GKE), Amazon Elastic Container Service for Kubernetes (EKS), and Azure Kubernetes Service (AKS).</p><p>Here’s an example of a Kubernetes Deployment configuration file, written in YAML, that deploys a simple web application:</p><pre>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: web-app<br>  labels:<br>    app: web-app<br>spec:<br>  replicas: 3<br>  selector:<br>    matchLabels:<br>      app: web-app<br>  template:<br>    metadata:<br>      labels:<br>        app: web-app<br>    spec:<br>      containers:<br>      - name: web-app<br>        image: gcr.io/my-project/web-app:latest<br>        ports:<br>        - containerPort: 80</pre><p>This configuration file creates a Deployment named “web-app” that runs 3 replicas of a containerized web application. The image for the container is pulled from a Google Container Registry (GCR) repository. The container listens on port 80.</p><p>Here’s an example of a Kubernetes Service configuration file that exposes the web application to external traffic:</p><pre>apiVersion: v1<br>kind: Service<br>metadata:<br>  name: web-app-svc<br>  labels:<br>    app: web-app<br>spec:<br>  selector:<br>    app: web-app<br>  ports:<br>  - name: http<br>    port: 80<br>    targetPort: 80<br>  type: ClusterIP</pre><p>This configuration file creates a Service named “web-app-svc” that routes external traffic to the pods running the web application, based on the pod labels. The service listens on port 80 and sends the traffic to the target port 80.</p><p>You can use these code snippets as a starting point for your own Kubernetes configurations. Remember that you need to adjust the code to fit your specific use case and environment.</p><p>You can use kubectl command to create, update and delete the resources in kubernetes, also you can use kubectl to see the current status of the resources in your cluster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f60ff2ef6b53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[S3 Bucket Access Policy script]]></title>
            <link>https://medium.com/@101awscloud/s3-bucket-access-policy-script-1dce00af958c?source=rss-696bb91d1630------2</link>
            <guid isPermaLink="false">https://medium.com/p/1dce00af958c</guid>
            <category><![CDATA[policy]]></category>
            <category><![CDATA[bucket-policy]]></category>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[script]]></category>
            <dc:creator><![CDATA[CloudSewa]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 08:50:30 GMT</pubDate>
            <atom:updated>2023-01-25T08:50:30.014Z</atom:updated>
            <content:encoded><![CDATA[<p>An S3 Bucket Access Policy script is a program that automates the process of creating and managing S3 bucket access policies. These scripts can be written in various programming languages such as Python, Java, and JavaScript, and can be used to perform tasks such as:</p><ul><li>Creating new buckets and setting their access policies</li><li>Adding or removing permissions for specific users or groups</li><li>Changing the permissions on existing objects or folders</li><li>Granting or revoking access to specific IP addresses or ranges</li><li>Logging access attempts and monitoring usage</li></ul><p>Here is an example of a Python script that creates an S3 bucket and sets its access policy to allow public read access:</p><pre>import boto3<br><br># Create an S3 client<br>s3 = boto3.client(&#39;s3&#39;)<br><br># Set the name of the bucket<br>bucket_name = &#39;my-new-bucket&#39;<br><br># Create the bucket<br>s3.create_bucket(Bucket=bucket_name)<br><br># Set the access policy for the bucket to allow public read access<br>policy = {<br>    &#39;Version&#39;: &#39;2012-10-17&#39;,<br>    &#39;Statement&#39;: [{<br>        &#39;Sid&#39;: &#39;AddPerm&#39;,<br>        &#39;Effect&#39;: &#39;Allow&#39;,<br>        &#39;Principal&#39;: &#39;*&#39;,<br>        &#39;Action&#39;: [&#39;s3:GetObject&#39;],<br>        &#39;Resource&#39;: f&#39;arn:aws:s3:::{bucket_name}/*&#39;<br>    }]<br>}<br>s3.put_bucket_policy(Bucket=bucket_name, Policy=json.dumps(policy))</pre><p>This script uses the boto3 library, which is the Amazon Web Services (AWS) SDK for Python, to interact with the S3 service. You can use similar script for other languages, like AWS Java SDK or AWS JavaScript SDK.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1dce00af958c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nginx Load Balancer with Failover]]></title>
            <link>https://medium.com/@101awscloud/nginx-load-balancer-with-failover-676f02f370b?source=rss-696bb91d1630------2</link>
            <guid isPermaLink="false">https://medium.com/p/676f02f370b</guid>
            <category><![CDATA[failover]]></category>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[load-balancer]]></category>
            <dc:creator><![CDATA[CloudSewa]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 05:49:56 GMT</pubDate>
            <atom:updated>2023-01-25T05:59:34.108Z</atom:updated>
            <content:encoded><![CDATA[<p>An Nginx load balancer with failover can be configured by following these steps:</p><ol><li>Install Nginx on the load balancer server: This can be done by downloading the Nginx package from the official website and installing it using the package manager of your operating system.</li><li>Create a configuration file for the load balancer: This file should include the list of backend servers that Nginx should forward requests to. It should also include any additional settings, such as the load balancing algorithm to use.</li><li>Configure health checks: Nginx can be configured to perform health checks on the backend servers to determine if they are available. This can be done by using the health_check module. In this example, we will check the status of the /health endpoint every 5 seconds.</li></ol><pre>http {<br>    upstream backend {<br>        server backend1.example.com;<br>        server backend2.example.com;<br>        health_check interval=5s uri=/health;<br>    }<br><br>    server {<br>        listen 80;<br>        location / {<br>            proxy_pass http://backend;<br>        }<br>    }<br>}</pre><p>4.Configure failover: Nginx can be configured to failover to a backup server if the primary server is not available. This can be done by using the backup directive. In this example, we will failover to backend3.example.com if backend1.example.com is not available.</p><pre>http {<br>    upstream backend {<br>        server backend1.example.com;<br>        server backend2.example.com;<br>        server backend3.example.com backup;<br>        health_check interval=5s uri=/health;<br>    }<br><br>    server {<br>        listen 80;<br>        location / {<br>            proxy_pass http://backend;<br>        }<br>    }<br>}</pre><p>5. Start the Nginx service: Once the configuration file is created, start the Nginx service by running the appropriate command for your operating system.</p><p>6. Monitor the Load balancer: Regularly monitor the load balancer to ensure that it is working as expected and that requests are being forwarded to the correct backend servers.</p><p>Please note that this is a basic example, you may have to add more configurations to suit your specific use case and environment.</p><blockquote>Here is an complete example configuration for an Nginx load balancer with failover:</blockquote><pre>http {<br>    upstream backend {<br>        server backend1.example.com weight=3;<br>        server backend2.example.com weight=2;<br>        server backend3.example.com weight=1;<br>        server backup.example.com backup;<br>    }<br><br>    server {<br>        listen 80;<br><br>        location / {<br>            proxy_pass http://backend;<br>            proxy_next_upstream error timeout invalid_header http_500;<br>            proxy_set_header Host $host;<br>            proxy_set_header X-Real-IP $remote_addr;<br>        }<br>    }<br>}</pre><p>In this configuration, the upstream block defines three backend servers (backend1, backend2, and backend3) and one backup server (backup). The weight parameter is used to specify the relative weight of each server, which determines how many requests will be sent to each server. In this example, backend1 will receive 3 times as many requests as backend2, and backend2 will receive twice as many requests as backend3.</p><p>The server block listens on port 80 and forwards all requests to the backend upstream. The proxy_next_upstream directive is used to specify that Nginx should try the next server in the upstream if an error occurs. The error, timeout, invalid_header, and http_500 parameters specify the types of errors that should trigger a failover to the next server.</p><p>The proxy_set_header directives are used to set the Host and X-Real-IP headers to the original values of the request.</p><p>It’s important to note that this is a basic example and you should adjust this configuration to meet your specific requirements. Also, it’s recommended to use health checks and monitoring to check the health of your servers and update the configuration accordingly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=676f02f370b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bussiness Plan for a Cloud Service Company]]></title>
            <link>https://medium.com/@101awscloud/bussiness-plan-for-a-cloud-service-company-d7cc59de7219?source=rss-696bb91d1630------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7cc59de7219</guid>
            <category><![CDATA[strategic-planning]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[plans]]></category>
            <category><![CDATA[bussiness]]></category>
            <category><![CDATA[cloud-services]]></category>
            <dc:creator><![CDATA[CloudSewa]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 04:28:26 GMT</pubDate>
            <atom:updated>2023-01-25T04:28:26.018Z</atom:updated>
            <content:encoded><![CDATA[<p>A business plan for a cloud services company should include the following key elements:</p><ol><li><strong>Executive Summary: </strong>A brief overview of the company, its services and goals.</li><li><strong>Industry Analysis:</strong> An analysis of the cloud services industry, including market size, trends, and major players.</li><li><strong>Market Segmentation: </strong>A breakdown of the target market for the company’s services, including demographics, psychographics, and geographics.</li><li><strong>Competitive Analysis:</strong> An analysis of the company’s major competitors and their strengths and weaknesses.</li><li><strong>Service Offerings:</strong> A detailed description of the company’s services, including pricing and packaging options.</li><li><strong>Marketing and Sales Strategy:</strong> A plan for promoting and selling the company’s services, including advertising, public relations, and sales techniques.</li><li><strong>Operations and Management:</strong> A description of the company’s operations, including the organizational structure, key personnel, and management processes.</li><li><strong>Financial Projections:</strong> Financial projections, including projected income statements, balance sheets, and cash flow statements.</li><li><strong>Conclusion: </strong>A summary of the key points covered in the business plan, and the company’s future prospects.</li></ol><p>The plan should also include any supporting documents, such as resumes of key personnel, sample contracts, and financial statements. It’s important to be as detailed as possible in the plan, especially for the financial projections, as these will be crucial for convincing investors or lenders to provide funding for the business.</p><p>It’s also important to be realistic when creating the business plan, and to be aware of the potential challenges and risks that the company may face. The plan should include strategies for mitigating these risks and addressing challenges, as well as a clear vision for how the company will grow and evolve over time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7cc59de7219" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lambda Script to Identify and Delete Infrequently Objects & Resources of AWS]]></title>
            <link>https://medium.com/@101awscloud/lambda-script-to-identify-and-delete-infrequently-objects-resources-of-aws-fe3c86ce06c6?source=rss-696bb91d1630------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe3c86ce06c6</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[resources]]></category>
            <category><![CDATA[delete]]></category>
            <category><![CDATA[identify]]></category>
            <category><![CDATA[lambda]]></category>
            <dc:creator><![CDATA[CloudSewa]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 04:19:30 GMT</pubDate>
            <atom:updated>2023-01-25T04:19:30.569Z</atom:updated>
            <content:encoded><![CDATA[<p>Here is an example of a Python script that can be used to identify and delete infrequently accessed objects in an Amazon Simple Storage Service (S3) bucket and stop or terminate underutilized Amazon Elastic Compute Cloud (EC2) instances and Amazon Relational Database Service (RDS) instances on AWS:</p><pre>import boto3<br>from datetime import datetime, timedelta<br><br>def get_underutilized_instances(client, days):<br>    &quot;&quot;&quot;<br>    Returns a list of underutilized EC2 instances<br>    &quot;&quot;&quot;<br>    instances = []<br>    reservations = client.describe_instances()[&quot;Reservations&quot;]<br>    for reservation in reservations:<br>        for instance in reservation[&quot;Instances&quot;]:<br>            # Check if the instance is running<br>            if instance[&quot;State&quot;][&quot;Name&quot;] == &quot;running&quot;:<br>                # Get the instance&#39;s launch time<br>                launch_time = instance[&quot;LaunchTime&quot;]<br>                # Check if the instance has been running for more than the specified number of days<br>                if (datetime.now(launch_time.tzinfo) - launch_time).days &gt;= days:<br>                    # Get the instance&#39;s CPU usage<br>                    cloudwatch = boto3.client(&#39;cloudwatch&#39;)<br>                    metric_name = &#39;CPUUtilization&#39;<br>                    namespace = &#39;AWS/EC2&#39;<br>                    statistic = &#39;Average&#39;<br>                    period = 86400<br>                    cpu_usage = cloudwatch.get_metric_data(<br>                        MetricDataQueries=[<br>                            {<br>                                &#39;Id&#39;: &#39;m1&#39;,<br>                                &#39;MetricStat&#39;: {<br>                                    &#39;Metric&#39;: {<br>                                        &#39;Namespace&#39;: namespace,<br>                                        &#39;MetricName&#39;: metric_name,<br>                                        &#39;Dimensions&#39;: [<br>                                            {<br>                                                &#39;Name&#39;: &#39;InstanceId&#39;,<br>                                                &#39;Value&#39;: instance[&quot;InstanceId&quot;]<br>                                            },<br>                                        ]<br>                                    },<br>                                    &#39;Period&#39;: period,<br>                                    &#39;Stat&#39;: statistic<br>                                },<br>                                &#39;ReturnData&#39;: True<br>                            },<br>                        ],<br>                        StartTime=&#39;{}&#39;.format((datetime.now() - timedelta(days=days)).strftime(&#39;%Y-%m-%d %H:%M:%S&#39;)),<br>                        EndTime=&#39;{}&#39;.format((datetime.now()).strftime(&#39;%Y-%m-%d %H:%M:%S&#39;)),<br>                    )<br>                    # Check if the instance&#39;s CPU usage is below a certain threshold<br>                    if cpu_usage[&quot;MetricDataResults&quot;][0][&quot;Values&quot;][0] &lt; 10.0:<br>                        instances.append(instance[&quot;InstanceId&quot;])<br>    return instances<br><br>def remove_infrequent_objects(client, bucket_name, days):<br>    &quot;&quot;&quot;<br>    Removes infrequently accessed objects from an S3 bucket<br>    &quot;&quot;&quot;<br>    objects_to_delete = []<br>    # Get a list of objects in the S3 bucket<br>    objects = client.list_objects_v2(Bucket=bucket_name)[&quot;Contents&quot;]<br>    for obj in objects:<br>        # Check if the object was last accessed more than the specified number of days ago<br>        if (datetime.now() - obj[&quot;LastModified&quot;]).days &gt;= days:<br>            objects_to_delete.append({&quot;Key&quot;: obj[&quot;Key&quot;]})</pre><blockquote>This is not used in Production Environment. Only tested in Test Environment.Dont use it in your production account. Create a seperate test AWS Account and use it.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe3c86ce06c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>