<?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 CloudandDevOpsAdmin on Medium]]></title>
        <description><![CDATA[Stories by CloudandDevOpsAdmin on Medium]]></description>
        <link>https://medium.com/@bincysjames?source=rss-3e7b5d7aa194------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*jn68O9JO5HsIh0tK</url>
            <title>Stories by CloudandDevOpsAdmin on Medium</title>
            <link>https://medium.com/@bincysjames?source=rss-3e7b5d7aa194------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 16:33:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bincysjames/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[Terraforming with ease]]></title>
            <link>https://medium.com/cloud-devops/terraforming-with-ease-4a5d93c1333?source=rss-3e7b5d7aa194------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a5d93c1333</guid>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[CloudandDevOpsAdmin]]></dc:creator>
            <pubDate>Tue, 30 Jun 2020 11:09:09 GMT</pubDate>
            <atom:updated>2020-06-30T11:10:02.611Z</atom:updated>
            <content:encoded><![CDATA[<h3>Terraforming best practices-part1</h3><p>While you are making some terraform scripts for the tasks, these few tricks will help you to excel in the same.This is followed in most of the organisations as a best practice as well.</p><p>As we know module is a container for multiple resources that are used together . We can create a module for single resource as well will all the best practices your company follows in the resource creation.</p><p>The common files present in a terraform resource creation scripts are main.tf, variable.tf, output.tf, provider.tf and backend.tf and locals.tf.</p><ol><li>Create a container registry using terraform along with a resource group and use datasources to get the existing resource information</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DpljbpIB30mJa_a2BP1YjA.png" /><figcaption>image 1</figcaption></figure><p>As in image1 we can see that in line 7 &amp;8 we are getting the resource group name and location using output or azurerm_resource_group.rg.name.</p><p>If we need some existing resource information we can use datasource and check the terraform documentation of <strong>datasource:resource </strong>and check <strong>attribute reference section </strong>on what can be exported as output.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*CzXsW2YuY-V3Pr421Ls4WQ.png" /><figcaption>data in terraform</figcaption></figure><p>Lets check the acr documentation and export all the attributes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k5qP5g7dgSddzWYO6XObOA.png" /><figcaption>datasources:acr</figcaption></figure><p>2. using input variable values</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IXmECmaZNxfyenKNaL3xpQ.png" /><figcaption>input variables</figcaption></figure><p>These variables should be declared using a variable block.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*SRqE9qTXlc6A9q_cLyaNTg.png" /><figcaption>variable declaration</figcaption></figure><p>We can add <strong>type</strong> constraints in variable block and supported keywords are string,number,bool,list,map,set,tuple etc.</p><p>Sample VM creation script</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b67-yWrsd9BDCrbNlCRxlw.png" /><figcaption>Google compute engine terraform</figcaption></figure><p><a href="https://www.terraform.io/docs/providers/google/r/compute_instance.html">https://www.terraform.io/docs/providers/google/r/compute_instance.html</a></p><p>Once the VM is created , tasks needs to be done we can use provisioner option in terraform.</p><p>main provisioner in terraform are local-exec, remote-exec, file provisioner</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YtuhrnEdo9EWS24_6GCrUQ.png" /><figcaption>Local and remote exec provisioner example</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*G4iNpY9ZAOPQyq97oahnYg.png" /><figcaption>file provisioner</figcaption></figure><p>Another option is there to use scripts in Google Compute Engine Instance \Template creation is to use <strong>template_file. “template_file” datasource renders a template from an external file</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*ig1AM9tVogbIG6hlNP1G3w.png" /><figcaption>datasource:template_file</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VEITJmLJnp-KZjHKpdhIaw.png" /><figcaption>use the code in metadata section</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a5d93c1333" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloud-devops/terraforming-with-ease-4a5d93c1333">Terraforming with ease</a> was originally published in <a href="https://medium.com/cloud-devops">Cloud&amp;DevOps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sample case study: Mountkirk Games]]></title>
            <link>https://medium.com/@bincysjames/sample-case-study-mountkirk-games-6baa19dcf2af?source=rss-3e7b5d7aa194------2</link>
            <guid isPermaLink="false">https://medium.com/p/6baa19dcf2af</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[google-cloud-architect]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[exam-preparation]]></category>
            <dc:creator><![CDATA[CloudandDevOpsAdmin]]></dc:creator>
            <pubDate>Wed, 06 Nov 2019 16:55:33 GMT</pubDate>
            <atom:updated>2019-11-06T16:57:09.802Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a sample case study , that may be used on the Professional Cloud Architect exam. It describes a fictitious business and solution concept to provide additional context to exam questions.</p><p>Mountkirk Games makes online, session-based, multiplayer games for mobile platforms. They build all of their games using some server-side integration. Historically, they have used cloud providers to lease physical servers.</p><p>Due to the unexpected popularity of some of their games, they have had problems scaling their global audience, application servers, MySQL databases, and analytics tools.</p><p>Their current model is to <strong>write game statistics to files</strong> and <strong>send them through an ETL tool</strong> that <strong>loads them into a centralized MySQL database for reporting</strong>.</p><h3>1. Solution concept</h3><p>Mountkirk Games is building a new game, which they expect to be very popular. They plan to deploy the game’s backend on <strong>Compute Engine</strong> so they can <strong>capture</strong> <strong>streaming metrics</strong>, <strong>run intensive analytics</strong>, and take advantage of its <strong>autoscaling server</strong> environment and integrate with a <strong>managed NoSQL database.</strong></p><h3>2. Business requirements</h3><p>· <strong>Increase to a global footprint</strong></p><p>· Improve uptime — downtime is loss of players</p><p>· Increase efficiency of the cloud resources we use</p><p>· Reduce latency to all customers</p><h3>3. Technical requirements</h3><p>Requirements for game backend platform</p><p>· Dynamically scale up or down based on game activity</p><p>· <strong>Connect to a transactional database service to manage user profiles and game state</strong></p><p>· Store game activity in a timeseries database service for future analysis</p><p>· As the system scales, ensure that data is not lost due to processing backlogs</p><p>· Run hardened Linux distr.</p><p>Requirements for game analytics platform</p><p>· Dynamically scale up or down based on game activity</p><p>· Process incoming data on the fly directly from the game servers</p><p>· Process data that arrives late because of slow mobile networks</p><p>· Allow queries to access at least 10 TB of historical data</p><p>· Process files that are regularly uploaded by users’ mobile devices</p><h3>4. Executive statement</h3><p>Our last successful game did not scale well with our previous cloud provider, resulting in lower user adoption and affecting the game’s reputation. Our investors want more key performance indicators (KPIs) to evaluate the speed and stability of the game, as well as other metrics that provide deeper insight into usage patterns so we can adapt the game to target users. Additionally, our current technology stack cannot provide the scale we need, so we want to replace MySQL and move to an environment that provides autoscaling and low latency load balancing and frees us up from managing physical servers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L5C4F_a4RcNrupufEQzDeg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*crXnKDaF5C5Fhbx90AdEow.png" /><figcaption>Reference Architecture</figcaption></figure><p><a href="https://cloud.google.com/solutions/mobile/mobile-gaming-analysis-telemetry">https://cloud.google.com/solutions/mobile/mobile-gaming-analysis-telemetry</a></p><p>Happy Learning !!!!!!!!!!!!!!!!!!!!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6baa19dcf2af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dress4win- Sample case study explained]]></title>
            <link>https://medium.com/@bincysjames/dress4win-sample-case-study-explained-9247979ee742?source=rss-3e7b5d7aa194------2</link>
            <guid isPermaLink="false">https://medium.com/p/9247979ee742</guid>
            <category><![CDATA[gcp-certification]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[google-cloud-architect]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[CloudandDevOpsAdmin]]></dc:creator>
            <pubDate>Sun, 03 Nov 2019 16:01:48 GMT</pubDate>
            <atom:updated>2020-03-11T08:58:42.643Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a sample case study that may be used on the Professional Cloud Architect exam. It describes a fictitious business and solution concept to provide additional context to exam questions.</p><p>Dress4Win is a web-based company that helps their users organize and manage their personal wardrobe using a web app and mobile application. The company also cultivates an active social network that connects their users with designers and retailers. They monetize their services through advertising, ecommerce, referrals, and a freemium app model. The application has grown from a few servers in the founder’s garage to several hundred servers and appliances in a colocated data center. However, the capacity of their infrastructure is now insufficient for the application’s rapid growth. Because of this growth and the company’s desire to innovate faster, Dress4Win is committing to a full migration to a public cloud.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>1. Solution concept</p><p>For the first phase of their migration to the cloud, Dress4Win is moving their development and test environments. They are also building a disaster recovery site, because their current infrastructure is at a single location. They are not sure which components of their architecture <strong>they can migrate as is</strong> and <strong>which components they need to change </strong>before migrating them.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -</p><p>2. Existing technical environment</p><p>The Dress4Win application is served out of a single data center location.</p><p><strong>All servers run Ubuntu LTS v16.04. — — -&gt;can map to Compute Engine</strong></p><p>Databases:</p><p>· MySQL. One server for user data, inventory, static data, — — → <strong>can map to Cloud SQL (managed service)</strong></p><p>· MySQL 5.7</p><p>· 8 core CPUs</p><p>· 128 GB of RAM →<strong> for 128 GB memory need to utilize high memory machine or use compute engine with MYSQL Installed.</strong></p><p>· 2x 5 TB HDD (RAID 1)</p><p>Compute:</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p><strong>40 web application servers providing micro-services based APIs and static content</strong></p><p>· Tomcat — Java</p><p>· Nginx</p><p>· Four core CPUs</p><p>· 32 GB of RAM</p><p><strong>Solution: Can use Managed Instance Group with Autoscaling enabled and Global HTTP(s) Load Balancer.</strong></p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p><strong>20 Apache Hadoop/Spark servers:</strong></p><p>· Data analysis</p><p>· Real-time trending calculations</p><p>· Eight core CPUs</p><p>· 128 GB of RAM</p><p>· 4x 5 TB HDD (RAID 1)</p><p><strong>Solution: Data Proc : Cloud Dataproc is a fast, easy-to-use, fully managed cloud service for running Apache Spark and Apache Hadoop clusters in a simpler, more cost-efficient way</strong></p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p><strong>Three RabbitMQ servers for messaging, social notifications, and events:</strong></p><p>· Eight core CPUs</p><p>· 32GB of RAM</p><p><strong>Solution: Can use Cloud pubsub, may need to refactor the code. Can do as is migration to a compute engine with RabbitMQ installed with custom machine type.</strong></p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>· Miscellaneous servers:</p><p>· Jenkins, monitoring, bastion hosts, security scanners</p><p><strong>Solution: Can use Marketplace Jenkins , Monitoring we use stackdriver monitoring ,Bastion host in compute engine, for security scanner use Cloud Web security scanner in compute option.</strong></p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>· Eight core CPUs</p><p>· 32GB of RAM</p><p>Storage appliances:</p><p>· iSCSI for VM hosts <strong>→ can use Block storage (persistent disk)</strong></p><p>· Fibre channel SAN — MySQL databases → <strong>can use</strong> <strong>clusters of persisitent disk for cloudsql</strong></p><p>· 1 PB total storage; 400 TB available</p><p>· NAS — image storage, logs, backups <strong>— -&gt; can use Blob storage</strong></p><p>· 100 TB total storage; 35 TB available</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>3. Business requirements</p><p>· Build a reliable and reproducible environment with scaled parity of production</p><p>· Improve security by defining and adhering to a set of security and identity and access management (IAM) best practices for cloud</p><p>· Improve business agility and speed of innovation through rapid provisioning of new resources →<strong>Deployment manager or Terraform</strong></p><p>· Analyze and optimize architecture for performance in the cloud → <strong>Stackdriver products</strong></p><p>4. Technical requirements</p><p>· Easily create non-production environments in the cloud</p><p>· Implement an automation framework for provisioning resources in cloud → <strong>Cloud deployment manager</strong></p><p>· Implement a continuous deployment process for deploying applications to the on-premises data center or cloud <strong>→Jenkins from marketplace</strong></p><p>· Support failover of the production environment to cloud during an emergency →<strong>Cloud DNS</strong></p><p>· Encrypt data on the wire and at rest →<strong>CSEK</strong></p><p>· Support multiple private connections between the production data center and cloud environment. →<strong>Cloud VPN</strong></p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>5. Executive statement</p><p>Our investors are concerned about our ability to scale and contain costs with our current infrastructure. They are also concerned that a competitor could use a public cloud platform to offset their up-front investment and free them to focus on developing better features. Our traffic patterns are highest in the mornings and weekend evenings; during other times, 80% of our capacity is sitting idle.</p><p>Our capital expenditure is now exceeding our quarterly projections. Migrating to the cloud will likely cause an initial increase in spending, but we expect to fully transition before our next hardware refresh cycle. Our total cost of ownership (TCO) analysis over the next five years for a public cloud strategy achieves a cost reduction between 30% and 50% over our current model.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Technical Evaluation:</p><p><strong>Multiple solutions are possible and a sample solution is provided and other solutions can be better.</strong></p><p>1. <strong>Cloud SQL</strong> as replacement for MySQL</p><p>2. <strong>Cloud Datastore</strong> for mobile backend</p><p>3. <strong>Compute Engine </strong>for VMs</p><p>4. <strong>Batch Processing </strong>using Dataflow</p><p>5. <strong>Load Balancer </strong>for High availability/traffic routing</p><p>6. <strong>Local SSD </strong>for VM hosts</p><p>7. <strong>SSD Persistent disks </strong>for db compute engine VM if Cloud SQL is not opted</p><p>8. <strong>Cloud Storage </strong>for backups</p><p>9. <strong>Stackdriver </strong>for logs</p><p>10. <strong>Cloud Dataproc </strong>for Hadoop/Spark workloads</p><p>11. <strong>Bigquery </strong>for realtime trending analysis</p><p>12. <strong>Cloud Pub/sub </strong>for messaging and notification</p><p>13. <strong>Cloud functions </strong>for event triggers</p><p>14. <strong>Cloud VPN</strong> for multiple private connections between prod data center and cloud</p><p>15. <strong>CSEK </strong>for encryption</p><p>16. <strong>Cloud Marketplace for</strong> Jenkins and Nginx</p><p>Happy Learning !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9247979ee742" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AZ-300-A2: Deploying and Configuring Infrastructure]]></title>
            <link>https://medium.com/@bincysjames/az-300-a2-deploying-and-configuring-infrastructure-ed2010b43c7e?source=rss-3e7b5d7aa194------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed2010b43c7e</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[az-300-study-material]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[CloudandDevOpsAdmin]]></dc:creator>
            <pubDate>Wed, 16 Oct 2019 09:07:37 GMT</pubDate>
            <atom:updated>2019-10-16T09:07:37.899Z</atom:updated>
            <content:encoded><![CDATA[<p>Page 2</p><p>Lets start with some basics on Azure and the definition is added to understand the other topics . How can we do will be included in upcoming sessions.</p><p>What is the difference between Datacenter model,IAAS , PAAS &amp; SAAS ?</p><p>What is shared responsibility model in Azure?</p><p>Azure tenant vs subscription</p><p>Azure availability zone vs Availability set vs Scaleset</p><p>Azure Networking Vnets ,subnets, load balancer , Application gateway, service end points, Network security groups, IP Addressing , Vnet Peering</p><p>VM Storage:storage account network access, type , access tier, performance tiers, replication options, securing storage account , access keys and shared access signature.</p><p>Hybrid connectivity :VPN Gateway, P2S , S2S, vnet-vnet, Express Route</p><p><strong>Please skip this if you are aware of these topics.</strong></p><ol><li><strong>What is the difference between Datacenter model,IAAS , PAAS &amp; SAAS ?</strong></li></ol><p>As we know in traditional datacenter model we owe everything including datacenter building , power, racks , servers , OS , virtualization etc.and it comes with more upfront cost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*hajmQ1M9b7pg2xbefokkHQ.png" /></figure><p>In IAAS model from operation system all that up we needs to manage and the servers, storage , networking and virtualization will be managed by azure.</p><p>In PAAS model we need to manage only the data and application.</p><p>In SAAS everything will be managed by Azure and we just need to utilize that as customer.</p><p><strong>2. What is shared responsibility model in Azure?</strong></p><p>In Shared responsibility model we need to manage certain things for keeping our cloud safe and few things will be managed by Azure including hardware , Virtualization and network Infrastructure etc.</p><p>Our responsibility Includes:</p><p>VM , Patching , Applications, NSG , Data, Keys , Password, credentials etc.</p><p><strong>3. Azure tenant vs directory vs subscription</strong></p><p>A <strong>tenant</strong> is a representation of an organization. It’s a dedicated instance of <strong>Azure</strong> AD that an organization or app developer receives when the organization or app developer creates a relationship with Microsoft.A <strong>directory</strong> is the <strong>Azure</strong> AD service.</p><p>Each <strong>directory</strong> has one <strong>or</strong> more domains. A <strong>directory</strong> can have many <strong>subscriptions</strong> associated with it, but only one <strong>tenant</strong>.</p><p>A subscription is an agreement with Microsoft to use one or more Microsoft cloud platforms or services, for which charges accrue based on either a per-user license fee or on cloud-based resource consumption.In your <strong>subscription</strong>(s) you can manage resources in resources groups.</p><p><strong>4. Azure availability zone vs Availability set vs Scaleset</strong></p><p><strong>Availability Zones</strong> are physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking</p><p><strong>An Availability Se</strong>t is a logical grouping capability for isolating VM resources from each other when they’re deployed. Azure makes sure that the VMs you place within an Availability Set run across multiple physical servers, compute racks, storage units, and network switches. The hardware in a location is divided in to multiple update domains and fault domains. An <strong>update domain</strong> is a group of VMs and underlying physical hardware that can be rebooted at the same time. VMs in the same <strong>fault domain</strong> share common storage as well as a common power source and network switch.</p><p>Azure<strong> virtual machine scale sets</strong> let you create and manage a group of identical, load balanced VMs. The number of VM instances can automatically increase or decrease in response to demand or a defined schedule.</p><p><strong>5. Azure Networking basics: Vnets ,subnets,Network security groups, load balancer , Application gateway, service end points,Vnet Peering.</strong></p><p><strong>Azure Virtual Network</strong> (<strong>VNet</strong>) is the fundamental building block for private network in <strong>Azure</strong>. <strong>VNet</strong> enables many types of <strong>Azure</strong> resources, such as <strong>Azure</strong> Virtual Machines (VM), to securely communicate with each other, the internet, and on-premises networks.</p><p><strong>Subnets </strong>enable you to segment the virtual network into one or more sub-networks and allocate a portion of the virtual network’s address space to each subnet.You can secure resources within subnets using <strong>Network Security Groups.</strong>You can connect virtual networks to each other, enabling resources in either virtual network to communicate with each other, using <strong>virtual network peering.E</strong>xtend our virtual network private address space and the identity of our virtual network to Azure service resources, such as Azure Storage accounts and Azure SQL databases, over a direct connection.<strong> Service endpoints </strong>allows us to secure our critical Azure service resources to only a virtual network.<strong>Azure Application Gateway</strong> is a web traffic load balancer that enables us to manage traffic to our web applications.We can route traffic based on the incoming URL using AppGW. So if /images is in the incoming URL, we can route traffic to a specific set of servers (known as a pool) configured for images. If /video is in the URL, that traffic is routed to another pool that&#39;s optimized for videos.<strong>With Azure Load Balancer</strong>, we can scale our applications and create high availability for your services. Load Balancer supports inbound and outbound scenarios, provides low latency and high throughput, and scales up to millions of flows for all TCP and UDP applications.</p><p><strong>7. VM Storage:storage account network access, type , access tier, performance tiers, replication options, access keys and shared access signature.</strong></p><p>An<strong> Azure storage account </strong>contains all of your Azure Storage data objects: blobs, files, queues, tables, and disks.</p><p>Types of storage accounts: <strong>General-purpose v2 accounts</strong>: Basic storage account type for blobs, files, queues, and tables. Recommended for most scenarios using Azure Storage.</p><ul><li><strong>General-purpose v1 accounts</strong>: Legacy account type for blobs, files, queues, and tables. Use general-purpose v2 accounts instead when possible.</li><li><strong>Block blob storage accounts</strong>: Blob-only storage accounts with premium performance characteristics. Recommended for scenarios with high transactions rates, using smaller objects, or requiring consistently low storage latency.</li><li><strong>FileStorage storage accounts</strong>: Files-only storage accounts with premium performance characteristics. Recommended for enterprise or high performance scale applications.</li><li><strong>Blob storage accounts</strong>: Blob-only storage accounts. Use general-purpose v2 accounts instead when possible.</li></ul><p>Performance tier</p><ul><li>A standard performance tier for storing blobs, files, tables, queues, and Azure virtual machine disks.</li><li>A premium performance tier for storing unmanaged virtual machine disks only.</li></ul><p>Access tiers for block blob data</p><ul><li>The <strong>Hot</strong> access tier, which is optimized for frequent access of objects in the storage account. . New storage accounts are created in the hot tier by default.</li><li>The <strong>Cool</strong> access tier, which is optimized for storing large amounts of data that is infrequently accessed and stored for at least 30 days.</li><li>The <strong>Archive</strong> tier, which is available only for individual block blobs. The archive tier is optimized for data that can tolerate several hours of retrieval latency and will remain in the Archive tier for at least 180 days.</li></ul><p>Replication Types</p><p>Replication options for a storage account include:</p><ul><li>Locally-redundant storage (LRS): A simple, low-cost replication strategy. Data is replicated synchronously three times within the primary region.</li><li>Zone-redundant storage (ZRS): Replication for scenarios requiring high availability. Data is replicated synchronously across three Azure availability zones in the primary region.</li><li>Geo-redundant storage (GRS): Cross-regional replication to protect against regional outages. Data is replicated synchronously three times in the primary region, then replicated asynchronously to the secondary region. For read access to data in the secondary region, enable read-access geo-redundant storage (RA-GRS).</li><li>Geo-zone-redundant storage (GZRS) : Replication for scenarios requiring both high availability and maximum durability. Data is replicated synchronously across three Azure availability zones in the primary region, then replicated asynchronously to the secondary region.</li></ul><p><strong>A shared access signature (SAS)</strong> provides secure delegated access to resources in our storage account without compromising the security of our data. With a SAS, we have granular control over how a client can access our data. We can control what resources the client may access, what permissions they have on those resources, and how long the SAS is valid, among other parameters.</p><p>When we create a storage account, Azure generates two 512-bit storage <strong>account access keys</strong>. These keys can be used to authorize access to our storage account via Shared Key.</p><p><strong>8. Hybrid connectivity :VPN Gateway, P2S , S2S, vnet-vnet, Express Route</strong></p><p><strong>A VPN gateway </strong>is a specific type of virtual network gateway that is used to send encrypted traffic between an Azure virtual network and an on-premises location <strong>over the public Internet</strong>.We can also use a VPN gateway to send encrypted traffic between Azure virtual networks <strong>over the Microsoft network</strong>. Each virtual network can have only one VPN gateway.However, we can create multiple connections to the same VPN gateway</p><p>A <strong>Site-to-Site (S2S) VPN gateway </strong>connection is a connection over IPsec/IKE (IKEv1 or IKEv2) VPN tunnel. S2S connections can be used for cross-premises and hybrid configurations. A S2S connection requires a VPN device located on-premises that has a public IP address assigned to it and is not located behind a NAT.</p><p>A<strong> Point-to-Site (P2S) VPN gateway</strong> connection lets you create a secure connection to your virtual network from an individual client computer. A P2S connection is established by starting it from the client computer.</p><p>Connecting a <strong>virtual network to another virtual network (VNet-to-VNet)</strong> is similar to connecting a VNet to an on-premises site location. Both connectivity types use a VPN gateway to provide a secure tunnel using IPsec/IKE.</p><p><strong>ExpressRoute</strong> lets us extend our on-premises networks into the Microsoft cloud over a private connection facilitated by a connectivity provider. ExpressRoute connections do not go over the public Internet.</p><p>A <strong>virtual network gateway</strong> is composed of two or more virtual machines that are deployed to a specific subnet you create, which is called the <em>gateway subnet</em>. The VMs that are located in the gateway subnet are created when you create the virtual network gateway.Virtual network gateway VMs are configured to contain routing tables and gateway services specific to the gateway.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed2010b43c7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AZ-300-A1: Deploying and Configuring Infrastructure]]></title>
            <link>https://medium.com/@bincysjames/https-medium-com-bincysjames-az-300-a-deploying-and-configuring-infrastructure-1-ac425302e0f5?source=rss-3e7b5d7aa194------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac425302e0f5</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[az-300-study-material]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[CloudandDevOpsAdmin]]></dc:creator>
            <pubDate>Tue, 15 Oct 2019 05:44:36 GMT</pubDate>
            <atom:updated>2019-10-15T05:44:36.880Z</atom:updated>
            <content:encoded><![CDATA[<p>Page 1</p><p>This explains how to manage Azure resources, including deployment and configuration of virtual machines, virtual networks, storage accounts, and Azure AD ,implementing and managing hybrid identities, how cloud resources are managed in Azure through user and group accounts, and how to grant access to Azure AD users, groups, and services using Role-based access control (RBAC).</p><p>You need to learn about the different storage accounts and services as well as basic data replication concepts and available replication schemes. How to work with Storage Explorer as a convenient way to work with Azure storage data. Need to learn the types of storage and how to work with managed and custom disks.</p><p>Azure blob storage is how Azure stores unstructured data in the cloud, and we will work with blobs and blob containers also Table and Queue storage as storage options for structured data.</p><p>You will learn how to create and deploy virtual machines in Azure, using the Azure portal, PowerShell, and ARM templates. Understand how to deploy custom images and Linux virtual machines. We will see how to configure the networking and storage components of virtual machines. Deploying highly available virtual machines is critical for planned and unplanned events, and we need to learn how to use availability sets to ensure that virtual machine resources are available during downtime.</p><p>We need to learn the monitoring tools and capabilities provided by Azure, including Azure Alerts and Activity Log. In addition to alerts and logs, we will be introduced to Log Analytics as an effective data analytics solution for understanding our system status and health. And perhaps the most exciting thing we will learn is how to use the Azure Resource Manager deployment model to work with resources, resource groups, and ARM templates.</p><p>Because this course is the first course in the series for the Azure Solutions Architect exams, there is a sizeable amount of introductory content presented to prepare us for the remaining courses.</p><p><strong>Key Learning Areas</strong></p><p>· Managing Azure Subscriptions and Resources</p><p>· Implementing and Managing Storage</p><p>· Deploying and Managing VMs</p><p>· Configuring and Managing Virtual Networks</p><p>· Managing Identities using Azure Active Directory</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac425302e0f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exam AZ-300: Microsoft Azure Architect Technologies]]></title>
            <link>https://medium.com/@bincysjames/exam-az-300-microsoft-azure-architect-technologies-51b53402ee9f?source=rss-3e7b5d7aa194------2</link>
            <guid isPermaLink="false">https://medium.com/p/51b53402ee9f</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[az-300-study-material]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[CloudandDevOpsAdmin]]></dc:creator>
            <pubDate>Tue, 15 Oct 2019 05:43:58 GMT</pubDate>
            <atom:updated>2019-10-15T05:43:58.601Z</atom:updated>
            <content:encoded><![CDATA[<p>This exam measures your ability to accomplish the following technical tasks: deploy and configure infrastructure; implement workloads and security; create and deploy apps; implement authentication and secure data; and develop for the cloud and Azure storage. The topics are as follows:</p><p><strong>1.</strong> <strong>Deploy and configure infrastructure (25–30%)</strong></p><p><strong>1.1.</strong> <strong>Analyze resource utilization and consumption</strong></p><p>· configure diagnostic settings on resources</p><p>· create baseline for resources</p><p>· create and rest alerts</p><p>· analyze alerts across subscription</p><p>· analyze metrics across subscription</p><p>· create action groups</p><p>· monitor for unused resources</p><p>· monitor spend</p><p>· report on spend</p><p>· utilize Log Search query functions</p><p>· view alerts in Azure Monitor logs</p><p><strong>1.2</strong> <strong>Create and configure storage accounts</strong></p><p>· configure network access to the storage account</p><p>· create and configure storage account</p><p>· generate shared access signature</p><p>· install and use Azure Storage Explorer</p><p>· manage access keys</p><p>· monitor activity log by using Azure Monitor logs</p><p>· implement Azure storage replication</p><p><strong>1.3</strong> <strong>Create and configure a Virtual Machine (VM) for Windows and Linux</strong></p><p>· configure high availability</p><p>· configure monitoring, networking, storage, and virtual machine size</p><p>· deploy and configure scale sets</p><p><strong>1.4</strong> <strong>Automate deployment of Virtual Machines (VMs)</strong></p><p>· Modify Azure Resource Manager template</p><p>· configure location of new VMs</p><p>· configure VHD template</p><p>· deploy from template</p><p>· save a deployment as an Azure Resource Manager template</p><p>· deploy Windows and Linux VMs</p><p><strong>1.5</strong> <strong>Implement solutions that use virtual machines (VM)</strong></p><p>· provision VMs</p><p>· create Azure Resource Manager templates</p><p>· configure Azure Disk Encryption for VMs</p><p><strong>1.6</strong> <strong>Create connectivity between virtual networks</strong></p><p>· create and configure VNET peering</p><p>· create and configure VNET to VNET</p><p>· verify virtual network connectivity</p><p>· create virtual network gateway</p><p><strong>1.7</strong> <strong>Implement and manage virtual networking</strong></p><p>· configure private and public IP addresses, network routes, network interface, subnets, and virtual network</p><p><strong>1.8</strong> <strong>Manage Azure Active Directory (AD)</strong></p><p>· add custom domains</p><p>· configure Azure AD Identity Protection, Azure AD Join, and Enterprise State Roaming</p><p>· configure self-service password reset</p><p>· implement conditional access policies</p><p>· manage multiple directories</p><p>· perform an access review</p><p><strong>1.9</strong> <strong>Implement and manage hybrid identities</strong></p><p>· install and configure Azure AD Connect</p><p>· configure federation and single sign-on</p><p>· manage Azure AD Connect</p><p>· manage password sync and writeback</p><p><strong>2.</strong> <strong>Implement workloads and security (20–25%)</strong></p><p><strong>2.1</strong> <strong>Migrate servers to Azure</strong></p><p>· migrate by using Azure Site Recovery</p><p>· migrate using P2V</p><p>· configure storage</p><p>· create a backup vault</p><p>· prepare source and target environments</p><p>· backup and restore data</p><p>· deploy Azure Site Recovery agent</p><p>· prepare virtual network</p><p><strong>2.2</strong> <strong>Configure serverless computing</strong></p><p>· manage a Logic App resource</p><p>· manage Azure Function app settings</p><p>· manage Event Grid</p><p>· manage Service Bus</p><p><strong>2.3</strong> <strong>Implement application load balancing</strong></p><p>· configure application gateway and load balancing rules</p><p>· implement front end IP configurations</p><p>· manage application load balancing</p><p><strong>2.4</strong> <strong>Integrate on-premises network with Azure virtual network</strong></p><p>· create and configure Azure VPN Gateway</p><p>· create and configure site to site VPN</p><p>· configure Express Route</p><p>· verify on-premises connectivity</p><p>· manage on-premises connectivity with Azure</p><p><strong>2.5</strong> <strong>Manage role-based access control (RBAC)</strong></p><p>· create a custom role</p><p>· configure access to Azure resources by assigning roles</p><p>· configure management access to Azure</p><p>· troubleshoot RBAC</p><p>· implement RBAC policies</p><p>· assign RBAC roles</p><p><strong>2.6</strong> <strong>Implement Multi-Factor Authentication (MFA)</strong></p><p>· enable MFA for an Azure tenant</p><p>· configure user accounts for MFA</p><p>· configure fraud alerts</p><p>· configure bypass options</p><p>· configure trusted IPs</p><p>· configure verification methods</p><p>· manage role-based access control (RBAC)</p><p>· implement RBAC policies</p><p>· assign RBAC Roles</p><p>· create a custom role</p><p>· configure access to Azure resources by assigning roles</p><p>· configure management access to Azure</p><p><strong>3.</strong> <strong>Create and deploy apps (5–10%)</strong></p><p><strong>3.1.</strong> <strong>Create web apps by using PaaS</strong></p><p>· create an Azure App Service Web App</p><p>· create documentation for the API</p><p>· create an App Service Web App for containers</p><p>· create an App Service background task by using WebJobs</p><p>· enable diagnostics logging</p><p><strong>3.2</strong> <strong>Design and develop apps that run in containers</strong></p><p>· configure diagnostic settings on resources</p><p>· create a container image by using a Docker file</p><p>· create an Azure Kubernetes Service</p><p>· publish an image to the Azure Container Registry</p><p>· implement an application that runs on an Azure Container Instance</p><p>· manage container settings by using code</p><p><strong>4.</strong> <strong>Implement authentication and secure data (5–10%)</strong></p><p><strong>4.1</strong> <strong>Implement authentication</strong></p><p>· implement authentication by using certificates, forms-based authentication, tokens, or Windows-integrated authentication</p><p>· implement multi-factor authentication by using Azure AD</p><p>· implement OAuth2 authentication</p><p>· implement Managed identities for Azure resources Service Principal authentication</p><p><strong>4.2</strong> <strong>Implement secure data solutions</strong></p><p>· encrypt and decrypt data at rest and in transit</p><p>· encrypt data with Always Encrypted</p><p>· implement Azure Confidential Compute and SSL/TLS communications</p><p>· create, read, update, and delete keys, secrets, and certificates by using the KeyVault API</p><p><strong>5.</strong> <strong>Develop for the cloud and for Azure storage (20–25%)</strong></p><p><strong>5.1</strong> <strong>Develop solutions that use Cosmos DB storage</strong></p><p>· create, read, update, and delete data by using appropriate APIs</p><p>· implement partitioning schemes</p><p>· set the appropriate consistency level for operations</p><p><strong>5.2</strong> <strong>Develop solutions that use a relational database</strong></p><p>· provision and configure relational databases</p><p>· configure elastic pools for Azure SQL Database</p><p>· create, read, update, and delete data tables by using code</p><p><strong>5.3</strong> <strong>Configure a message-based integration architecture</strong></p><p>· configure an app or service to send emails, Event Grid, and the Azure Relay Service</p><p>· create and configure Notification Hub, Event Hub, and Service Bus</p><p>· configure queries across multiple products</p><p><strong>5.4</strong> <strong>Develop for autoscaling</strong></p><p>· implement autoscaling rules and patterns (schedule, operational/system metrics, code that addresses singleton application instances)</p><p>· implement code that addresses transient state</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51b53402ee9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vault -Dynamic Secrets on Azure]]></title>
            <link>https://medium.com/cloud-devops/vault-dynamic-secrets-on-azure-dbf9a2056c47?source=rss-3e7b5d7aa194------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbf9a2056c47</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[hashicorp-vault]]></category>
            <category><![CDATA[dynamic-secrets]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[CloudandDevOpsAdmin]]></dc:creator>
            <pubDate>Wed, 09 Oct 2019 09:29:18 GMT</pubDate>
            <atom:updated>2019-10-09T09:29:18.649Z</atom:updated>
            <content:encoded><![CDATA[<p>Vault secures, stores, and tightly controls access to tokens, passwords, certificates, API keys, and other secrets in modern computing.This document discusses on how dynamic secrets are configured in Azure using vault and how it is retrieved while using in scripts or in API calls.</p><p><strong>1.</strong> <strong>Azure Secrets Engine</strong></p><p>The Azure secrets engine dynamically generates Azure service principals and role assignments. Vault roles can be mapped to one or more Azure roles, providing a simple, flexible way to manage the permissions granted to generated service principals.</p><p>Each service principal is associated with a Vault lease. When the lease expires (either during normal revocation or through early revocation), the service principal is automatically deleted.</p><p><strong>1.1</strong> <strong>Secret Engine Configuration using commands</strong></p><p>· Connect to Vault server</p><p>· Enable the Azure secrets engine</p><p>· Configure the secrets engine with account credentials</p><p>· Configure a role</p><p>· Generate dynamic credentials from role</p><pre><strong>$ vault secrets enable azure</strong></pre><pre>Success! Enabled the azure secrets engine at: azure/</pre><pre>$ <strong>vault write azure/config \</strong></pre><pre><strong>subscription_id=$AZURE_SUBSCRIPTION_ID \</strong></pre><pre><strong>tenant_id=$AZURE_TENANT_ID \</strong></pre><pre><strong>client_id=$AZURE_CLIENT_ID \</strong></pre><pre><strong>client_secret=$AZURE_CLIENT_SECRET</strong></pre><pre>Success! Data written to: azure/config</pre><pre><strong>$ vault write azure/roles/my-role ttl=1h azure_roles=-&lt;&lt;EOF</strong></pre><pre><strong>[{</strong></pre><pre><strong>&quot;role_name&quot;: &quot;Contributor&quot;,</strong></pre><pre><strong>&quot;scope&quot;:  &quot;/subscriptions/&lt;uuid&gt;/resourceGroups/Website&quot;</strong></pre><pre><strong>}]</strong></pre><pre><strong>EOF</strong></pre><pre><strong>$ vault read azure/creds/my-role</strong></pre><pre>Key                Value</pre><pre>---                -----</pre><pre>lease_id               azure/creds/sp_role/1xxxxxx-xxxxxx-xxxxxx-xxxxxx</pre><pre>lease_duration         60m</pre><pre>lease_renewable        true</pre><pre>client_id              xxxxxxxx-xxx-x-xx-xxxxxxxxxxxxx</pre><pre>client_secret          xxxxxxx-xxx-x-xx-xxxxxxxxxxxxx</pre><ol><li><strong>1</strong> <strong>Secret Engine Configuration using Terraform</strong></li></ol><p>The secret engine configuration and generating dynamic credentials can be done using terraform and this can be automated using pipelines as well. Below is the sample terraform script.</p><pre>resource &quot;vault_azure_secret_backend&quot; &quot;azure&quot; {</pre><pre>subscription_id = &quot;${var.subscription_id}&quot;</pre><pre>tenant_id       = &quot;${var.tenant_id}&quot;</pre><pre>client_secret   = &quot;${var.client_secret}&quot;</pre><pre>client_id       = &quot;${var.client_id}&quot;</pre><pre>environment     = &quot;${var.vault_environment}&quot;</pre><pre>}</pre><pre>resource &quot;vault_azure_secret_backend_role&quot; &quot;generated_role&quot; {</pre><pre>backend    = &quot;${vault_azure_secret_backend.azure.path}&quot;</pre><pre>role       = &quot;rolename&quot;</pre><pre>ttl        = 300</pre><pre>max_ttl    = 600</pre><pre>azure_roles {</pre><pre>role_name = &quot;Reader&quot;<br>scope =  &quot;/subscriptions/${var.subscription_id}/resourceGroups/${var.resource_group_name}&quot;</pre><pre>}}</pre><pre>resource &quot;vault_policy&quot; &quot;example&quot; {</pre><pre>name = &quot;policyforazuresecretengine&quot;</pre><pre>policy = &lt;&lt;EOT</pre><pre>path &quot;secret/azurepath&quot; {</pre><pre>policy = &quot;write&quot;</pre><pre>}</pre><pre>EOT</pre><pre>}</pre><pre>data &quot;vault_generic_secret&quot; &quot;login&quot; {</pre><pre>path = &quot;azure/creds/rolename&quot;</pre><pre>}</pre><p>The output is the client_id and client_secret which can be used to automate azure IAC using terraform.</p><pre>provider &quot;azurerm&quot; {</pre><pre>client_id   = &quot;${data.vault_generic_secret.login.data[&quot;client_id&quot;]}&quot;</pre><pre>client_secret = &quot;${data.vault_generic_secret.login.data[&quot;client_secret&quot;]}&quot;</pre><pre>}</pre><p>For generating dynamic credentials while running terraform scripts, can use provider.tf as below.</p><pre>provider &quot;vault&quot; {</pre><pre>address = &quot;${var.address}&quot;</pre><pre>address = &quot;http://x.x.x.x:8200&quot;</pre><pre>token = &quot;s.xxxxxxxxxxxxxxxxxx&quot;</pre><pre>}</pre><pre>provider &quot;azurerm&quot; {</pre><pre>subscription_id = &quot;xxxxxxxx-xxxx-xxxxx-xxxx-xxxxxxxxxxx&quot;</pre><pre>tenant_id = &quot;xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx&quot;</pre><pre>client_secret = &quot;${data.vault_generic_secret.azure_jwt.data[&quot;client_secret&quot;]}&quot;</pre><pre>client_id = &quot;${data.vault_generic_secret.azure_jwt.data[&quot;client_id&quot;]}&quot;</pre><pre>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*FI5JzOu9ko2yWGuFshtmAg.png" /></figure><h3><a href="https://medium.com/@bincysjames/https-medium-com-bincysjames-vault-manage-secrets-and-protect-sensitive-data-part-1-87bde7b3d0c7">Vault -Manage Secrets and Protect Sensitive Data -Part 1</a></h3><h3><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-2-e7088692ede3">Vault -Manage Secrets and Protect Sensitive Data -Part 2</a></h3><h3><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-3-17b53b73a49e">Vault -Manage Secrets and Protect Sensitive Data -Part 3</a></h3><h3><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-4-6e0f8da4ec20">Vault -Manage Secrets and Protect Sensitive Data -Part 4</a></h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbf9a2056c47" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloud-devops/vault-dynamic-secrets-on-azure-dbf9a2056c47">Vault -Dynamic Secrets on Azure</a> was originally published in <a href="https://medium.com/cloud-devops">Cloud&amp;DevOps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vault -Manage Secrets and Protect Sensitive Data -Part 6]]></title>
            <link>https://medium.com/cloud-devops/vault-manage-secrets-and-protect-sensitive-data-part-6-93a0a19ac195?source=rss-3e7b5d7aa194------2</link>
            <guid isPermaLink="false">https://medium.com/p/93a0a19ac195</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[hashicorp-vault]]></category>
            <category><![CDATA[vault]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[CloudandDevOpsAdmin]]></dc:creator>
            <pubDate>Thu, 11 Jul 2019 10:26:45 GMT</pubDate>
            <atom:updated>2019-07-11T10:35:11.963Z</atom:updated>
            <content:encoded><![CDATA[<p>Terraforming vault configurations — gcp</p><ol><li>Create a service account, give permission in GCP, create a GCP Secrets Engine.</li></ol><pre>resource &quot;google_service_account&quot; &quot;vault&quot; {<br> <strong># Account ID must be at least 6 characters. Therefore using vault-admininstead of vault.</strong><br>account_id = &quot;vault-admin&quot;<br>display_name = &quot;Vault Admin Account for GCP&quot;<br>project = &quot;projectid&quot;}</pre><pre><strong># create a google service account key</strong></pre><pre>resource &quot;google_service_account_key&quot; &quot;vault_key&quot; {<br>service_account_id = &quot;${google_service_account.vault.name}&quot;<br>}<br>locals {<br>vault_iam_roles = [<br>&quot;roles/iam.serviceAccountAdmin&quot;,<br>&quot;roles/iam.serviceAccountKeyAdmin&quot;,<br>&quot;roles/iam.serviceAccountUser&quot;,<br>]<br>}<br><strong># give permission to service account</strong></pre><pre>resource &quot;google_project_iam_member&quot; &quot;project_iam_member_vault_service_account&quot; {<br>count = &quot;${length(local.vault_iam_roles)}&quot;<br>project = &quot;projectid&quot;<br>role = &quot;${element(local.vault_iam_roles, count.index)}&quot;<br>member = &quot;serviceAccount:${google_service_account.vault.email}&quot;<br>}</pre><pre><strong># Create a GCP secret backend</strong></pre><pre>resource &quot;vault_gcp_secret_backend&quot; &quot;gcp_secret_backend&quot; {<br>depends_on = [&quot;google_project_iam_member.project_iam_member_vault_service_account&quot;,<br>]<br>credentials = &quot;${base64decode(google_service_account_key.vault_key.private_key)}&quot;<br>path = &quot;pathname&quot;</pre><pre>default_lease_ttl_seconds = &quot;3600&quot; <strong># Set default value explicitly for reference</strong><br>max_lease_ttl_seconds = &quot;86400&quot; <strong># Set default value explicitly for reference</strong><br>}</pre><p>2. Create a roleset for Compute Engine Admin</p><pre><strong>#Creating Vault rolesets for the project- Compute Engine-Admin</strong></pre><pre>resource &quot;vault_gcp_secret_roleset&quot; &quot;rolesetname&quot; {<br>backend = &quot;give the backend path or get as data from above script&quot;<br>roleset = &quot;ComputeEngine_Admin_vault&quot;<br>secret_type  = &quot;access_token&quot;<br>project      = &quot;projectid&quot;<br>token_scopes = [&quot;https://www.googleapis.com/auth/cloud-platform&quot;]binding {<br>resource = &quot;//cloudresourcemanager.googleapis.com/projects/${projectid}&quot;<br>roles = [<br>&quot;roles/compute.appAdmin&quot;,<br>]<br>}<br>}</pre><p>3. Create a policy in Vault for providing read write access to the GCP Secrets Engine path.</p><pre>resource &quot;vault_policy&quot; &quot;policyname&quot; {<br>name = &quot;projectname&quot;<br>policy {<br>path = &quot;secretenginepath/token/rolesetname&quot; {<br>capabilities = [&quot;read&quot;, &quot;write&quot;]<br>}<br>path &quot;auth/token/*&quot; {<br>capabilities = [&quot;read&quot;]<br>}<br>}<br>}</pre><p>4. Create a token with the created policy , so that token has access to the secrets engine path and the roleset.</p><pre>resource &quot;vault_token&quot; &quot;tokenname&quot; {<br>role_name = &quot;rolename&quot;<br>policies = &quot;policyname&quot;<br>renewable = true<br>ttl = &quot;24h&quot;<br>renew_min_lease = 43200<br>renew_increment = 86400<br>}<br>output &quot;vault_token&quot; {value = &quot;${data.vault_generic_secret.tokenname.data[&quot;value&quot;]}&quot;<br>}</pre><p>5. Copy the generated token and the team members can use this token in terraform script for resource creation</p><pre><strong>provider &quot;vault&quot; {<br>address = &quot;vault server address&quot;<br>token = &quot;provide the generated token&quot;<br>}<br>data &quot;vault_generic_secret&quot; &quot;gcp_jwt&quot; {<br>path = &quot;pathname/token/rolesetname&quot;<br>}<br></strong>provider &quot;google&quot; {<br><strong>access_token = &quot;${data.vault_generic_secret.gcp_jwt.data[&quot;token&quot;]}&quot;<br></strong>project = &quot;projectname&quot;<br>region = &quot;region&quot;<br>}</pre><pre>resource &quot;google_compute_instance&quot; &quot;vm_instance&quot; <br> and your terraform code for VM creation</pre><h4><a href="https://medium.com/@bincysjames/https-medium-com-bincysjames-vault-manage-secrets-and-protect-sensitive-data-part-1-87bde7b3d0c7">Vault -Manage Secrets and Protect Sensitive Data -Part 1</a></h4><h4><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-2-e7088692ede3">Vault -Manage Secrets and Protect Sensitive Data -Part 2</a></h4><h4><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-3-17b53b73a49e">Vault -Manage Secrets and Protect Sensitive Data -Part 3</a></h4><h4><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-4-6e0f8da4ec20">Vault -Manage Secrets and Protect Sensitive Data -Part 4</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93a0a19ac195" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloud-devops/vault-manage-secrets-and-protect-sensitive-data-part-6-93a0a19ac195">Vault -Manage Secrets and Protect Sensitive Data -Part 6</a> was originally published in <a href="https://medium.com/cloud-devops">Cloud&amp;DevOps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vault -Manage Secrets and Protect Sensitive Data -Part 5]]></title>
            <link>https://medium.com/cloud-devops/vault-manage-secrets-and-protect-sensitive-data-part-5-fccccfdbbc27?source=rss-3e7b5d7aa194------2</link>
            <guid isPermaLink="false">https://medium.com/p/fccccfdbbc27</guid>
            <category><![CDATA[vault]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[hashicorp-vault]]></category>
            <dc:creator><![CDATA[CloudandDevOpsAdmin]]></dc:creator>
            <pubDate>Thu, 11 Jul 2019 07:49:46 GMT</pubDate>
            <atom:updated>2019-07-11T08:12:37.837Z</atom:updated>
            <content:encoded><![CDATA[<p>Dynamic secrets</p><p>In our previous discussion, we implemented a standalone vault, implemented Vault with Consul backend, discussed about rotating and rekeying concepts. We will discuss some of the vault basic ideas and in the next session we will automate the same using terraform scripting.</p><h4><strong>Secrets Engines</strong></h4><p>Secrets engines are components which store, generate, or encrypt data.Some secrets engines like kv simply store the data and read the same .Other secrets engines connect to other services and generate dynamic credentials on demand like azure and gcp secrets engine.Secrets engines are enabled at a “path” in Vault.When a request comes to Vault, the router automatically routes anything with the route prefix to the secrets engine. We will provide access to read the path of the secrets engine using policies. For example if a token or a user-account needs to read\write from a particular secrets engine path , we will create policies and create a token out of the policy and in policy we can mention the path and the capabilities.We will discuss the same later in detail.</p><p><strong>1. Azure Secrets Engine</strong></p><p>The Azure secrets engine dynamically generates Azure service principals and role assignments.Each service principal is associated with a Vault lease. When the lease expires, the service principal is automatically deleted.</p><ol><li><strong>1 Enable the Azure secrets engine:</strong></li></ol><p>vault secrets enable azure -path azure</p><p><strong>1.2. Configure the secrets engine with account credentials:</strong></p><p>vault write azure/config \<br>subscription_id=$AZURE_SUBSCRIPTION_ID \<br>tenant_id=$AZURE_TENANT_ID \<br>client_id=$AZURE_CLIENT_ID \<br>client_secret=$AZURE_CLIENT_SECRET</p><p>Provide the environment variables $AZURE_SUBSCRIPTION_ID, $AZURE_TENANT_ID , $AZURE_CLIENT_ID, $AZURE_CLIENT_SECRET.</p><p>Now we can see that the vault is connected to our azure account, this spn credentials needs to have required permission in our account, so that vault can create and delete dynamic spn and role assignments.</p><p><strong>1.3. Configure a role.</strong></p><p>A role may be set up with either an existing service principal, or a set of Azure roles that will be assigned to a dynamically created service principal.</p><p>To configure a role called “role1” with an existing service principal spn1:</p><pre>vault write azure/roles/role1 application_object_id=&lt;spn1_app_obj_id&gt; ttl=1h</pre><p>To configure the role to create a new service principal with Azure roles:</p><pre>vault write azure/roles/role1 ttl=1h azure_roles=-&lt;&lt;EOF<br>     [<br>         {<br>             &quot;role_name&quot;: &quot;Contributor&quot;,<br>             &quot;scope&quot;:  &quot;/subscriptions/&lt;uuid&gt;/resourceGroups/Database&quot;<br>         }<br>     ]<br> EOF</pre><p>The scope must be provided for every role assignment.</p><p>After the secrets engine is configured and a user/machine has a Vault token with the proper permissions, it can generate credentials.</p><pre>vault read azure/creds/role1</pre><p>This endpoint generates a renewable set of credentials. The application can login using the client_id/client_secret</p><p><strong>2. GCP Secrets Engine</strong></p><p>The Google Cloud Vault secrets engine dynamically generates Google Cloud service account keys and OAuth tokens based on IAM policies. This enables users to gain access to Google Cloud resources without needing to create or manage a dedicated service account.</p><p><strong>2.1 Enable the Google Cloud secrets engine:</strong></p><pre>vault secrets enable gcp</pre><p><strong>2.2 Configure the secrets engine with account credentials:</strong></p><pre>vault write gcp/config credentials=@my-credentials.json</pre><p>The service account we are giving as credentials should have minimum permissions for the vault to perform token generation and key generation.</p><p>Assign the set of roles required to get resource-specific getIamPolicy/setIamPolicy permissions. At a minimum you will need to assign roles/iam.serviceAccountAdmin and roles/iam.serviceAccountKeyAdmin so Vault can manage service accounts and keys.</p><p><strong>2.3 Configure a roleset:</strong></p><p>Rolesets determine the permissions that Service Account credentials generated by Vault will have on GCP resources.Roleset can be configured to generate OAuth2 access tokens ( preferred method)or GCP Service Account keys.Service Accounts are created when the roleset is created (or updated) rather than each time a secret is generated.</p><p>To configure a roleset that generates OAuth2 access tokens</p><pre>vault write gcp/roleset/rolesetname \<br>     project=&quot;projectname&quot; \<br>     secret_type=&quot;access_token&quot;  \<br>     token_scopes=&quot;https://www.googleapis.com/auth/cloud-platform&quot; \<br>     bindings=-&lt;&lt;EOF<br>       resource &quot;//cloudresourcemanager.googleapis.com/projects/projectname&quot; {<br>         roles = [&quot;roles/editor&quot;]<br>       }<br>     EOF</pre><p>To configure a roleset that generates GCP Service Account keys:</p><pre>vault write gcp/roleset/rolesetname \<br>     project=&quot;projectname&quot; \<br>     secret_type=&quot;service_account_key&quot;  \<br>     bindings=-&lt;&lt;EOF<br>       resource &quot;//cloudresourcemanager.googleapis.com/projects/my-project&quot; {<br>         roles = [&quot;roles/viewer&quot;]<br>       }<br>     EOF</pre><p>After the secrets engine is configured and a user/machine has a Vault token with the proper permission, it can generate credentials.</p><p>To generate OAuth2 tokens</p><pre>vault read gcp/token/rolesetname</pre><p>This will generate a token value and the token value then can be used as a HTTP Authorization Bearer token in requests to GCP APIs.</p><pre>curl -H &quot;Authorization: Bearer tokenvalue&quot;</pre><p>To generate service account keys</p><pre>vault read gcp/key/rolesetname</pre><p>In the next session we will discuss on how to do this via terraform scripts and how the generated token can be used in a terraform script for creating resources in Azure and GCP.</p><h4><a href="https://medium.com/@bincysjames/https-medium-com-bincysjames-vault-manage-secrets-and-protect-sensitive-data-part-1-87bde7b3d0c7">Vault -Manage Secrets and Protect Sensitive Data -Part 1</a></h4><h4><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-2-e7088692ede3">Vault -Manage Secrets and Protect Sensitive Data -Part 2</a></h4><h4><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-3-17b53b73a49e">Vault -Manage Secrets and Protect Sensitive Data -Part 3</a></h4><h4><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-4-6e0f8da4ec20">Vault -Manage Secrets and Protect Sensitive Data -Part 4</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fccccfdbbc27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloud-devops/vault-manage-secrets-and-protect-sensitive-data-part-5-fccccfdbbc27">Vault -Manage Secrets and Protect Sensitive Data -Part 5</a> was originally published in <a href="https://medium.com/cloud-devops">Cloud&amp;DevOps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vault -Manage Secrets and Protect Sensitive Data -Part 4]]></title>
            <link>https://medium.com/cloud-devops/vault-manage-secrets-and-protect-sensitive-data-part-4-6e0f8da4ec20?source=rss-3e7b5d7aa194------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e0f8da4ec20</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[vault]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[CloudandDevOpsAdmin]]></dc:creator>
            <pubDate>Wed, 10 Jul 2019 16:26:38 GMT</pubDate>
            <atom:updated>2019-07-11T07:59:36.171Z</atom:updated>
            <content:encoded><![CDATA[<p>Rekeying and Rotating Vault</p><p>As discussed already , vault uses <strong>Shamir’s Secret Sharing Algorithm </strong>to prevent individual access to the system. A secret is divided into many parts and those parts are needed to reconstruct the original secret.When a Vault server is initialized , Vault generated a master key and this master key is splitted into key shares (default is 5).Vault wont share the master key and the only way to generate the master key is by providing the unseal keys.This generated master key is used to decrypt the encryption key( we generated as part of vault installation).</p><p>If your organization has a policy to regenerate the master key for any security or compliance and to rotate the encryption keys.In Vault rekeying and rotating are two separate operations . The process for generating a new master key and applying Shamir’s algorithm is called “rekeying”. The process for generating a new encryption key for Vault to encrypt data at rest is called “rotating”. Vault will continue to service requests uninterrupted during these processes.</p><p>Lets get into the steps</p><ol><li>Rekeying Vault</li></ol><p>Before proceeding with rekey , discuss on the number of key-shares and the key-threshold. Enter operator rekey and provide the token , do the step 3 times and rekeying will be complete.</p><p>vault operator rekey -init -key-shares=7 -key-threshold=4<br>vault operator rekey -init -status<br>vault operator rekey</p><p>Check the rekey progress and once the rekeying completes you will get 7 new unseal keys as we have mentioned -key-shares=7 .</p><p>2. Rotating the encryption key in Vault</p><p>Rotating Vault’s encryption key does not require the unseal keys, just require the correct permission.</p><p>To trigger a key rotation, execute the command:</p><p>vault operator rotate</p><p>This will output the key version and installation time and all new values written to the storage backend will be encrypted with this new key.</p><h4><a href="https://medium.com/@bincysjames/https-medium-com-bincysjames-vault-manage-secrets-and-protect-sensitive-data-part-1-87bde7b3d0c7">Vault -Manage Secrets and Protect Sensitive Data -Part 1</a></h4><h4><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-2-e7088692ede3">Vault -Manage Secrets and Protect Sensitive Data -Part 2</a></h4><h4><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-3-17b53b73a49e">Vault -Manage Secrets and Protect Sensitive Data -Part 3</a></h4><h4><a href="https://medium.com/@bincysjames/vault-manage-secrets-and-protect-sensitive-data-part-5-fccccfdbbc27">Vault -Manage Secrets and Protect Sensitive Data -Part 5</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e0f8da4ec20" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloud-devops/vault-manage-secrets-and-protect-sensitive-data-part-4-6e0f8da4ec20">Vault -Manage Secrets and Protect Sensitive Data -Part 4</a> was originally published in <a href="https://medium.com/cloud-devops">Cloud&amp;DevOps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>