<?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 Dharani Sowndharya on Medium]]></title>
        <description><![CDATA[Stories by Dharani Sowndharya on Medium]]></description>
        <link>https://medium.com/@dharanisowndharya?source=rss-f52a9f6ba5cb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4h7DATVznsvxlq5V3E6MDw.jpeg</url>
            <title>Stories by Dharani Sowndharya on Medium</title>
            <link>https://medium.com/@dharanisowndharya?source=rss-f52a9f6ba5cb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:55:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dharanisowndharya/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[Moving non-tech posts to Substack]]></title>
            <link>https://dharanisowndharya.medium.com/moving-non-tech-posts-to-substack-3c34160db560?source=rss-f52a9f6ba5cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c34160db560</guid>
            <dc:creator><![CDATA[Dharani Sowndharya]]></dc:creator>
            <pubDate>Sat, 08 Nov 2025 07:33:06 GMT</pubDate>
            <atom:updated>2025-11-08T07:33:06.906Z</atom:updated>
            <content:encoded><![CDATA[<h4>A New Home for My Non-Tech Posts!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c4AVzFIE5KoISDeU" /><figcaption>Photo by <a href="https://unsplash.com/@mikbutcher?utm_source=medium&amp;utm_medium=referral">Michal Balog</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hello everyone!</p><p>I’m making a small but helpful change to how I share my posts, and I wanted to let my fantastic followers know what’s happening.</p><h4>Why the Change?</h4><p>It’s all about making things <strong>easier for you</strong> to follow the content you love! I’ve been posting both my deep-dive <strong>tech articles</strong> and my <strong>non-tech posts</strong> (like personal reflections, creative writing, or anything else) right here on Medium.</p><p>Moving forward, I’m creating a clear separation:</p><ol><li><strong>Tech Content Stays Here (Medium):</strong> All the posts you’ve come to expect about programming, gadgets, industry news, and tutorials will <strong>remain right here on Medium</strong>. Nothing changes!</li><li><strong>Non-Tech Content is Moving (Substack):</strong> All my posts that <em>aren’t</em> about tech — the more personal stuff, creative pieces, or general life thoughts — will now live on my <a href="https://dharanisowndharya.substack.com/"><strong>Substack newsletter</strong></a>.</li></ol><blockquote><strong>Substack link </strong>: <a href="https://dharanisowndharya.substack.com/"><strong>https://dharanisowndharya.substack.com/</strong></a></blockquote><h3>Where to Find Me</h3><p>This split gives me a clear focus and makes sure you only get the content you’re most interested in.</p><ul><li><strong>For Tech Posts:</strong> Keep following me <strong>right here on Medium</strong>.</li><li><strong>For Non-Tech Posts:</strong> Please subscribe to my new home on <strong>Substack</strong>!</li></ul><p>I appreciate every single one of you following along. This move will help both of us — it gives me a clear structure for writing and gives you an easier way to consume my content!</p><p>Thanks for your understanding and support! See you either here or on Substack!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c34160db560" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best way to structure your Terraform projects — Part 2!]]></title>
            <link>https://awstip.com/best-way-to-structure-your-terraform-projects-part-2-beeb8bd35bac?source=rss-f52a9f6ba5cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/beeb8bd35bac</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[iac]]></category>
            <dc:creator><![CDATA[Dharani Sowndharya]]></dc:creator>
            <pubDate>Thu, 09 Nov 2023 09:23:52 GMT</pubDate>
            <atom:updated>2023-11-13T19:07:18.067Z</atom:updated>
            <content:encoded><![CDATA[<h3>Best way to structure your Terraform projects — Part 2!</h3><p>Part 2 on answers to the most asked questions to a DevOps Specialist!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rDnQ0o4ZENC_xwD_" /><figcaption>Photo by <a href="https://unsplash.com/@martinshreder?utm_source=medium&amp;utm_medium=referral">Martin Shreder</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Please refer to Part 1 of this blog <a href="https://medium.com/aws-tip/best-way-to-structure-your-terraform-projects-part-1-915bab2791b8">here</a>.</p><p>As mentioned in Part 1, the opinions provided in the blog are subjective and I wanted to write this article as an open discussion to not only share some of the approaches that I followed but also to invite people to suggest and discuss any other options and to get more feedback on the pros and cons listed.</p><h3>Should I use a pipeline for Terraform deployments?</h3><p>Definitely yes.</p><p>Create a pipeline with roles having the least access privileges. Restrict access to the pipeline as well. No manual updates should be allowed apart from this. This might make development slow, but eventually, this will ensure consistency. Enable auditability for this pipeline so that the changes can be traced.</p><h3>How should I design the pipeline for deployment in Terraform?</h3><p>One common complaint we get when we try this approach is that the pipeline quickly becomes bulky and that it becomes slower. To solve this, separate the Terraform code deployments into logical blocks and deploy them separately with a different pipeline. This will make the changes smaller, quicker and will make them easily testable.</p><p>The output of the smaller pipelines can be stored in a central repository or AWS SSM param and the integration pipeline should be built in such a way that it can refer to the output of the previous pipeline . For example, we can use the ‘data’ resource in the code to refer to these dependencies while creating the resources in the integration pipeline.</p><p>This is an oversimplified diagram depicting the above theory. Feel free to separate the pipelines in a logical approach that makes sense for the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Czj10tljMaezjBZfyObzQ.png" /></figure><p>Create a pipeline separately for dev folks that they can use for their local testing. Encourage testing via code to make it a practice. <br><strong>Pros</strong>:</p><p>No need to run a big pipeline with the whole environment changes to make small changes like renaming the tags.</p><p>Quicker feedback loops and the issues in the code can be identified earlier.</p><p>Testing becomes simple.</p><p><strong>Cons</strong>:</p><p>Makes the whole setup complicated and can cause mismatches in the logic chosen to separate the pipelines.</p><ul><li>For example, a team mate might choose to run vpc, subnets, gateways etc in a single pipeline and a new joiner to the team could create a separate pipeline for just creating route tables, which might get complicated in the long run.</li><li>Need clear documentation that explains the logical approach chosen</li></ul><h3>How to effectively test my Terraform setup?</h3><p>I have written two blogs on testing using <a href="https://awstip.com/testing-your-terraform-code-part-1-d55fbbd15784">Terratest</a> and <a href="https://awstip.com/testing-your-terraform-code-part-2-525de5384b75">Checkov</a>. Please refer to them for information on tools used and how to use them.</p><p>Yet another resource I constantly refer to for testing Terraform is this excellent<a href="https://www.youtube.com/watch?v=xhHOW0EF5u8"> video by Yevgeniy Brikman</a>. It talks about different types of ways in which we can test Terraform and the tools that can be used for them.</p><p><strong>Other recommended tools for testing:</strong></p><ol><li><a href="https://www.openpolicyagent.org/docs/latest/terraform/">OPA</a> to use pre-defined or custom policies to check your Terraform code against</li><li><a href="https://github.com/terraform-linters/tflint">Tflint</a> or <a href="https://www.checkov.io/">Checkov</a> for static testing</li><li>Use Variable validation that comes in-built with Terraform for contract testing</li></ol><ul><li><strong><em>Important Note</em></strong><em>:</em> One thing that stops a lot of people from adding tests to their setup is that they might have to learn a new programming language like Go or Ruby. With Terraform 1.6(Released on October 4,2023) , Hashicorp has introduced testing using HCL itself, which makes the unit and integration testing very easy. I am currently experimenting with it and will post the process and setup in my upcoming blog and link it here.</li></ul><p>5. Use <a href="https://terratest.gruntwork.io/">Terratest</a> for Integration and End to End testing</p><p>There are n number of tools to perform these tasks and I would suggest the reader to choose a tool that works for them based on their own deciding factors.</p><h3>What are the recommended tools to be used alongside Terraform?</h3><p>Apart from the above-mentioned testing tools, I’ve also used/come across these tools for various use cases</p><ol><li><a href="https://github.com/awslabs/git-secrets">Git-Secret</a> or <a href="https://github.com/thoughtworks/talisman">Talisman</a> to not commit sensitive data to a repository</li><li><a href="https://github.com/infracost/infracost">Infracost</a> for getting an approximate break down on the costs that your Terraform setup might incur</li><li><a href="https://github.com/terraform-docs/terraform-docs">Terraform-docs</a> to overcome the pesky work of writing documentation for your code</li><li><a href="https://terragrunt.gruntwork.io/">Terragrunt</a> for keeping your code DRY</li></ol><h3>Hearing a lot of news on Terraform licensing but I do not understand it fully. Can you explain how this would affect me?</h3><p>There are two scenarios for this and I’ll try to explain them in simple terms.</p><p>If you are a DevOps Engineer or Infra Engineer in your company and you use Terraform to build your resources, the good news is, nothing is changed. You can continue doing so!</p><p>If you are working on a product using Terraform’s source code and created a wrapper on top of it and have monetized this product or planning to monetize it, you need to get the license from Terraform. This might affect the ecosystem of the tools surrounding Terraform and there could be changes in how you use them going forward.</p><h3><strong>Will the advent of AI create an impact in DevOps? Is there a chance of losing jobs in the future?</strong></h3><p>The answers are both ‘Yes’ and ‘No’. I’m working on a blog explaining the way in which we can use AI to our advantage in DevOps. Will be linking it once its done. There are use cases popping up everyday about how we can use AI in DevOps and I would suggest folks to subscribe to newsletters to learn further.</p><h3>How to keep myself updated on what is happening in Tech? I am overwhelmed by the news around.</h3><p>It is difficult but the following points could help</p><ol><li>Follow newsletters and subscriptions that resonates with you.</li></ol><ul><li>Some of the newsletters I’ve subscribed as a DevOps Specialist are <a href="https://bytebytego.com/">ByteByteGo</a>, <a href="https://www.weekly.tf/">weekly.tf</a>,<a href="https://newsletter.systemdesign.one/"> System Design Newsletter by NK</a>,Medium digests on the relevant topics, <a href="https://letsmakecloud.beehiiv.com/">Let’s make cloud</a></li></ul><p>For newbies, it is understandable that it might get overwhelming despite having these resources. The only way to step over that feeling is to take one step at a time. If all you could do that day is read one tweet by a tech person, stick to it. The information might help someday when you are coming up with a solution</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=beeb8bd35bac" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/best-way-to-structure-your-terraform-projects-part-2-beeb8bd35bac">Best way to structure your Terraform projects — Part 2!</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[Best Way to structure your Terraform projects — Part 1!]]></title>
            <link>https://awstip.com/best-way-to-structure-your-terraform-projects-part-1-915bab2791b8?source=rss-f52a9f6ba5cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/915bab2791b8</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Dharani Sowndharya]]></dc:creator>
            <pubDate>Sat, 28 Oct 2023 04:23:17 GMT</pubDate>
            <atom:updated>2024-01-09T10:57:04.125Z</atom:updated>
            <content:encoded><![CDATA[<h3>Best Way to structure your Terraform projects — Part 1!</h3><p>Answers to the most asked questions to a DevOps Specialist!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GZ52Gif8h0IszEoB" /><figcaption>Photo by <a href="https://unsplash.com/@kaleidico?utm_source=medium&amp;utm_medium=referral">Kaleidico</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Often times, one of the common questions that get asked by folks who are starting their IAC automation using Terraform is:</p><blockquote>What are the best practices to be followed in structuring my Terraform project?</blockquote><p>The answer often is “It depends..”</p><p>There is no single solution which will work for all kinds of use-cases and there are pros and cons for each approach. The opinions provided in the blog are subjective and I wanted to write this article as an open discussion to not only share some of the approaches that I followed but also to invite people to suggest and discuss any other options and to get more feedback on the pros and cons listed. The solutions will have references to AWS services. Choose equivalent services in other cloud providers as needed.</p><p>I’ve divided this blog into multiple parts to provide as a collection of best practices that will evolve over time.</p><h3><strong>When should I use modules and when should I opt to use resources directly?</strong></h3><p>Modules are reusable functions in Terraform that you can call multiple times to keep your code DRY</p><p>If your automation is simple, you can skip writing modules and add the resources in your tf files directly. But, if its complex and if you foresee calling specific resources repeatedly, write modules and call them from your main.tf</p><p><strong>Pros</strong>:</p><p>Reduces code duplication</p><p><strong>Cons</strong>:</p><p>Makes testing complicated</p><p>Reduces visibility on the flow of the code</p><h3>Can I club resources together like module “networking”(Contains vpc, subnet etc) module “compute” (Contains ec2, lambda) ?</h3><p>Go for resource specific modules.</p><p>Reason: Clubbing them together will often create monoliths that will become difficult to find and handle. For example, networking as a module can have vpc, subnet, route table, route table associations, internet gateway, nat gateway, transit gateway, vpc peering, vpn etc</p><p>If there are no clearly defined definitions for each logically grouped modules, there is a chance that someone else from the team accidentally creating duplicates or move a resource block to a different folder structure. For example, a new team member might think that Lambda belongs to a serverless module instead of a compute module and might move it there.</p><p><strong>Pros:</strong></p><p>Makes debugging easier</p><p>Easier to navigate and find the respective module</p><p><strong>Cons</strong>:</p><p>For a simple project, having too many modules could become tedious to create and test</p><p>Maintenance gets complicated</p><h3>Can I store the terraform code in the same repository as our application code?</h3><p>Store the modules/terraform code in a separate repository. Having the code close to the app repository might look simple in the short run, but with each new microservice, maintenance becomes complicated. And if you need to introduce any change, you need to change a lot of repositories and the team needs to make sure that it is reflected in all of them correctly. It also provides a single point of control in approving and merging PRs to the DevOps team</p><h3>Can I store the modules in the same repo as the main terraform repos or should I create a separate repo for modules?</h3><p>Create two repos. One where all the terraform modules are stored and one repository containing the main terraform file which refers the modules repo. Refer to this module repo using the source variable and point to a specific branch or tag.</p><pre># select a specific tag<br>module &quot;vpc&quot; {<br>  source = &quot;git::https://example.com/vpc.git?ref=v1.2.0&quot;<br>}</pre><p>Using this approach, we can control the version of the dependant resource which is referencing the module and this will allow ease in testing and providing updates.</p><p>You can also use some form of PR request based approval to change anything in the modules repo. Since modules are common functions that will impact all the dependant resources, stringent measures could be taken specifically to avoid manual errors.</p><p><strong>Cons</strong>:</p><p>Reduced visibility and control</p><h3><strong>Can we use the public modules available in terraform registry or do we need to write our own modules?</strong></h3><p>If you are not looking for a quick automation, please consider writing your own modules and maintaining them. You can copy parts of the remote modules and use it as per your use case to not reinvent the wheel again.</p><p><strong>Pros</strong>:</p><ol><li>The public module will have a lot of configurable use cases that might not apply to our setup</li><li>Debugging becomes very difficult as the code in public modules tend to be complex</li><li>Moving to a newer version or tag needs extensive testing and good understanding of the code</li></ol><p><strong>Cons</strong>:</p><ol><li>It is time consuming</li><li>You might not follow the industry standard best practices if you choose to write your own code</li><li>Your own code will not be battle tested and there are chances of getting errors</li></ol><h3>What are the best practices of storing the terraform state?</h3><ol><li>Store the terraform state in an object storage like S3</li><li>Use Dynamo DB to lock the terraform state to prevent concurrent writes to state file</li><li>Split the terraform state logically based on accounts, environments and stacks as well and store them in respective folders separately in S3<br>– This will reduce the blast radius in case of any issues in your setup</li><li>Use consistent naming to find the state files and their location</li></ol><p>Please refer to Part 2 of this blog <a href="https://medium.com/p/beeb8bd35bac">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=915bab2791b8" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/best-way-to-structure-your-terraform-projects-part-1-915bab2791b8">Best Way to structure your Terraform projects — Part 1!</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[Testing your Terraform code — Part 2]]></title>
            <link>https://awstip.com/testing-your-terraform-code-part-2-525de5384b75?source=rss-f52a9f6ba5cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/525de5384b75</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[iac]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[terraform-testing]]></category>
            <dc:creator><![CDATA[Dharani Sowndharya]]></dc:creator>
            <pubDate>Fri, 21 May 2021 10:28:07 GMT</pubDate>
            <atom:updated>2023-10-30T19:09:53.693Z</atom:updated>
            <content:encoded><![CDATA[<h3>Testing your Terraform code — Part 2</h3><p>Exploring Checkov</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zxscF72WxXse7oDW" /><figcaption>Photo by <a href="https://unsplash.com/@heylagostechie?utm_source=medium&amp;utm_medium=referral">heylagostechie</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In <a href="https://dharanisowndharya.medium.com/testing-your-terraform-code-part-1-d55fbbd15784">part 1 </a>of this series, we looked into how we can use Terratest for testing our Infrastructure as a code setup. While Terratest can be used as part of our integration testing pipeline to check if the infrastructure stack gets created as we expected it to, we can use checkov for checking if our code is following the compliance and is free from known security issues.</p><p>From their docs[1]:</p><blockquote>Checkov is a static code analysis tool for infrastructure-as-code.</blockquote><blockquote>It scans cloud infrastructure provisioned using <a href="https://terraform.io/">Terraform</a>, Terraform plan, <a href="https://aws.amazon.com/cloudformation/">Cloudformation</a>, <a href="https://kubernetes.io/">Kubernetes</a>, <a href="https://www.docker.com/">Dockerfile</a>, <a href="https://www.serverless.com/">Serverless</a> or <a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/overview">ARM Templates</a> and detects security and compliance misconfigurations using graph-based scanning.</blockquote><p>It is one of the most popular tools for running static analysis in Terraform as of publishing this article. The tool has been downloaded more than a million times and has more than 2.5k stars on its Github page. It is backed by Bridgecrew which was recently acquired by Palo Alto Networks. So rest assured, this tool is going to stay in the field for a while.</p><p>They have more than 1000 inbuilt policies to perform compliance checks on AWS, Azure and Google cloud. We can check for misconfigured credentials in the code, check for security vulnerabilities like having an IAM resource opened wide or having a security group with wide-open permissions, we can get insights on the absence of encryption and a lot more is available with the code and the policies updated almost every single day.</p><p>The prerequisites for installing it are</p><blockquote>Python ≥ 3.7</blockquote><blockquote>Terraform ≥ 0.12</blockquote><p>Setting it up is pretty straightforward. Follow the steps to install Checkov on a Linux machine. Use a virtual environment for python installation if you do not have the required python version in your machine.</p><p><em>pip3 install checkov</em></p><p>On Mac, we can also install it via brew</p><p><em>brew install checkov</em></p><p>If its already installed, we can upgrade it using</p><p><em>pip3 install -U checkov</em></p><p>or</p><p><em>brew upgrade checkov</em></p><p>Installation is as simple as that. Once it’s installed we can run it against a single file or against directories.</p><p>For running against a directory</p><p><em>checkov -d &lt;directory_containing_tf_files&gt;</em></p><p>For running against a single file</p><p><em>checkov -f /location/test.tf</em></p><p>The output of the checkov scan would look like this. It would show the result of passed checks and if there are failures, it’ll show them with valid reasons</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wa-402XaMazKRBCmAFVEWw.png" /></figure><p>We can integrate this as part of our pre-commit hook or in our merge criteria for pull requests or as part of the CI pipeline in launching our Infrastructure using Terraform. We can also write custom checks for implementation in our setup.</p><p>There could be scenarios where we might think that it needs to skip certain checks to avoid failing the pipeline. In that case, we can add skip to that part of the compliance check.</p><p>For example, in my code for launching RDS, I got a compliance issue for not enabling Multi-AZ. This check can be skipped by adding the skip comment in the following manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*llJt86dBrB6xHIjheXuOHw.png" /></figure><p>The format for the skip comment is :</p><p><em>checkov:skip=&lt;check_id&gt;:&lt;suppression_comment&gt;</em></p><p>We can get the CKV code while running the check or from the GitHub docs location.</p><p>A specific check can be skipped from the command line as well.</p><p><em>checkov -d . — skip-check CKV_AWS_157</em></p><p>The output of a skipped check would look like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R8EFvj_LgdkQtZdhfeJX4w.png" /></figure><p>We can also integrate it with our IDE. If you are using VSCode, checkov can be installed as a plugin.[2] By adding it to the IDE, we can run tests as we are typing and fix issues in the development phase itself. However, the plugin is not up to date with the Checkov releases and we might miss a few checks if we just rely on the plugin. So, it’s recommended to use Chekov from the plugin and also from the CLI set-up.</p><p>Happy coding folks :)</p><p>Testing terraform code series:</p><p>Part 1 : <a href="https://dharanisowndharya.medium.com/testing-your-terraform-code-part-1-d55fbbd15784">https://dharanisowndharya.medium.com/testing-your-terraform-code-part-1-d55fbbd15784</a></p><p>References:</p><ol><li><a href="https://github.com/bridgecrewio/checkov">https://github.com/bridgecrewio/checkov</a></li><li><a href="https://github.com/bridgecrewio/checkov-vscode">https://github.com/bridgecrewio/checkov-vscode</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=525de5384b75" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/testing-your-terraform-code-part-2-525de5384b75">Testing your Terraform code — Part 2</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[Testing your Terraform code — Part 1]]></title>
            <link>https://awstip.com/testing-your-terraform-code-part-1-d55fbbd15784?source=rss-f52a9f6ba5cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d55fbbd15784</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[terratest]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Dharani Sowndharya]]></dc:creator>
            <pubDate>Tue, 30 Mar 2021 12:20:35 GMT</pubDate>
            <atom:updated>2023-10-30T19:09:48.835Z</atom:updated>
            <content:encoded><![CDATA[<h3>Testing your Terraform code — Part 1</h3><p>Exploring Terratest for Terraform</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*85OYGM-gzcsh6DKI" /><figcaption>Photo by <a href="https://unsplash.com/@scienceinhd?utm_source=medium&amp;utm_medium=referral">Science in HD</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>But before we jump, let’s start with a quick introduction on the need for a testing tool/framework for Terraform with a quick blast from the past on how it all started.</p><p>Do you remember the time when cloud became a buzzword everywhere and companies started experimenting with it? It felt like we were entering a new era where everything became elastic. We could launch the servers with a small touch of our finger on the mouse and voila, like magic, all the resources we wanted got created. We didn’t have to wait for months for the server to get provisioned and we could deploy everything to production in a couple of days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yiPqw2Q4m-6X6p4Y" /></figure><p>A few of us sprouted out of our normal work to look into this new and shiny discovery named cloud, went through a couple of certifications and named ourselves as Cloud Engineers which actually sounded far cooler than the name systems administrator or ops that we were used to being called.</p><p>It was all cool in the beginning(like everything is), but when everyone started using it, it put a lot of pressure on the consistency in which the servers were spun. We would have spun up a server just a week before for our tester to test their code and when they asked us a week later, we would have comfortably forgotten about the various configurations that went in and spent hours trying to replicate it and went on to create another server which soon went unused and added its own share of bills that boggled us at the monthly billing cycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*DpxwhIwcXEhyUyEE" /></figure><p>Ofcourse, providers like AWS had their own version of IAC, but with new cloud providers getting into the market every single day, we wanted something common that we could use across the board.</p><p>That’s when Terraform jumped in and transformed the whole IAC scene and made our lives so much easier. We were able to create consistent resources, maintain the state to avoid duplications and to top it all off, the language was very simple that you can learn and start using it within a day!</p><p>But, wherever code is present, we should add test cases to verify the working of it. Particularly in case of infrastructure, where a small manual error could destroy everything in a matter of seconds. It is high time that we start to test our IAC and make it a norm everywhere</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bd5BMqyf9LHdfU1B" /></figure><p>Enter <strong>Terratest</strong>. There are plenty of tools that are mushrooming in this space, but terratest seems to be leading the pack for now. From their own words:</p><blockquote>You can think of Terratest as a way to do end-to-end, acceptance or integration testing, whereas most other tools are focused on unit or functional testing.<a href="https://terratest.gruntwork.io/docs/">[1]</a></blockquote><p>Instead of us eyeballing every line of terraform plan or output, we can automate using terratest to test our code and to make it do that work for us. Let’s say we want to create a VPC with subnets which are private only, instead of depending on someone to go through the console or aws cli to check this at the end of the Infrastructure pipeline, we can make use of Terratest to make this check for us.</p><h4>A little bit more on Terratest</h4><p>Terratest is written in Go and is developed by Gruntwork. But, this tutorial does not go deep into golang or give explanations on how to write it or expect the reader to know much about Go. There are plenty of tutorials that give that information. Rather, we are going to look into a simple example on how we can leverage terratest to test our infrastructure and maybe help you in demystifying any hesitation that you might have (like I did before I started) to start experimenting with it. I (with a smiling face) would like to say that no prior knowledge in Go is required to understand the rest of this article and I hope this helps anyone who is scouring the internet to understand Terratest.</p><h4>Prerequisites:</h4><ol><li>Install Go — <a href="https://golang.org/">https://golang.org/</a></li><li>Install Terraform — <a href="https://learn.hashicorp.com/tutorials/terraform/install-cli">https://learn.hashicorp.com/tutorials/terraform/install-cli</a></li><li>Set up a simple terraform module. You can use the code present in this link or any link which creates a VPC and a couple of subnets→ <a href="https://www.bogotobogo.com/DevOps/Terraform/Terraform-VPC-Subnet-ELB-RouteTable-SecurityGroup-Apache-Server-1.php">https://www.bogotobogo.com/DevOps/Terraform/Terraform-VPC-Subnet-ELB-RouteTable-SecurityGroup-Apache-Server-1.php</a></li><li>An AWS account with credentials to spin up the resources</li></ol><p>Let’s get our hands dirty with the following example. I’ll explain each and every line in the code through the comments on top of it (Being a Go novice, any comments on information that I might have misunderstood and added in the explanation is highly appreciated)</p><p>This is a sample code that we are using to test if a VPC got created as we expected it to, with two subnets and having both of them as private</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0ffc784bdae0aec289999125eb87ac34/href">https://medium.com/media/0ffc784bdae0aec289999125eb87ac34/href</a></iframe><p>Let’s say if one of them is private and one of them is public, we would get the following line in the output.</p><p>It will create the stack mentioned using the terraform script files mentioned in the directory and will destroy it. The output is parsed to make the assertion in Go test</p><blockquote>terraform_aws_vpc_test.go:35:</blockquote><blockquote>Error Trace: terraform_aws_vpc_test.go:35</blockquote><blockquote>Error: Should be true</blockquote><blockquote>Test: TestNetworkForRDS</blockquote><p>We would get the following error in the console once the test is over</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k0r-LPe1ypXIdqfZ" /></figure><p>You can execute the above file using the command</p><blockquote>go test terraform_aws_vpc_test.go -timeout 30m -v</blockquote><p>Deciphering the above command:</p><p>go → Since its a Go file</p><p>test → <a href="https://golang.org/pkg/cmd/go/internal/test/">We are using the ‘test’ feature of Go</a></p><p>terraform_aws_vpc_test.go → Name of our file. Note: It should end with _test.go</p><p>-timeout 30m → By default its 10m. <a href="https://terratest.gruntwork.io/docs/testing-best-practices/timeouts-and-logging/">Terratest developers recommend to go with the highest possible values.</a></p><ul><li>v → Verbose</li></ul><p>You can use any pre written Go functions that Terratest team have written already. They have a collection of modules in their Git repo for different cloud providers. For example if you want to write test cases for EC2, you can refer to this <a href="https://github.com/gruntwork-io/terratest/tree/master/modules/aws">link</a> where there is a Go file for EC2 and take up any of the functions that they’ve written and add it to your code.</p><p><strong>Reiterating the points to note while running Terratest :</strong></p><ol><li>The function name for the Terratest module should start with Test</li><li>terraformOptions is where we point to the folder containing terraform files and whatever variable that we would like to pass to the files in the tf dir for testing purposes while doing InitApply</li><li>defer is used to destroy once we’ve created the stack</li><li>We should pass the terraformOptions as a variable to both defer and InitAndApply</li><li>We can query the output of terraform with terraform.Output(t, terraformOptions, “whatever the output name we’ve given”</li><li>You create a file ending in _test.go and run tests with the go test command. E.g., go test my_test.go.</li><li>terraformOptions := terraform.WithDefaultRetryableErrors → Construct the terraform options with default retryable errors to handle the most common retryable errors in terraform testing</li><li>go test -v -run TestTerraformAwsHelloWorldExample -timeout 30m. This is because Go sets a default test time out of 10 minutes, and if your test take longer than that to run, Go will panic, and kill the test code part way through. This prevents the clean up code from running (the terraform destroy), leaving you with lots of resources hanging in your AWS account. To prevent this, we always recommend setting a high test timeout; the test above doesn’t actually take anywhere near 30 minutes (typical runtime is ~3 minutes), but we give lots of extra buffer to be extra sure that the test always has a chance to finish cleanly.</li></ol><p><strong>Recommendations: </strong><a href="https://terratest.gruntwork.io/docs/#testing-best-practices">Please refer to the documentation for more detailed explanations for each of these points</a>. Some of them could be repeated. But, I added it so that we can know about the recommendations that the terratest team mentioned specifically</p><ol><li>Run the Terratest in a different environment than that of prod if we are using it to create resources to avoid confusions</li><li>Use unique ID to generate unique names for the resources being created to avoid destroying the existing resource by accident. You can use Terratest’s random.UniqueId() function to generate identifiers that are short enough to use in resource names (just 6 characters) but random enough to make it unlikely that you’ll have a conflict.</li></ol><blockquote>uniqueId := random.UniqueId()</blockquote><blockquote>instanceName := fmt.Sprintf(“terratest-http-example-%s”, uniqueId)</blockquote><blockquote>terraformOptions := &amp;terraform.Options {</blockquote><blockquote>TerraformDir: “../examples/terraform-http-example”,</blockquote><blockquote>Vars: map[string]interface{} {</blockquote><blockquote>“instance_name”: instanceName,</blockquote><blockquote>},</blockquote><blockquote>}</blockquote><blockquote>terraform.Apply(t, terraformOptions)</blockquote><p>4. Clean up code using defer all the time.If by any chance, it was interrupted through poor network connection or timeout, use a tool that would destroy everything in the test account every night : Refer : <a href="https://github.com/gruntwork-io/cloud-nuke">cloud-nuke</a> by terratest team</p><p>5. Always use a timeout with a maximum timeout value. Default is 10 mins: If the code timeouts, defer will not happen which will leave orphaned resources in the account. So go for the maximum value possible</p><blockquote>go test -timeout 30m</blockquote><p>6. Use Terratest’s logger.Log and logger.Logf functions, which will log to stdout immediately</p><blockquote>func TestFoo(t *testing.T) {</blockquote><blockquote>logger.Log(t, “This will show up in stdout immediately”)</blockquote><blockquote>}</blockquote><p>7. Execute each package sequentially using the -p 1 flag in the go test command so that the logs are printed then and there for that package rather than printing all the logs once the test is complete for all the packages</p><p>8. Parsing through the output of the terratest log could be tedious and to show the results in the Jenkins pipeline effectively, we can use the external binary terratest_log_parser. — <a href="https://terratest.gruntwork.io/docs/testing-best-practices/debugging-interleaved-test-output/">https://terratest.gruntwork.io/docs/testing-best-practices/debugging-interleaved-test-output/</a></p><p>9. Tests should run everytime we run go test as it might take the results from the cache and might not execute go test since there won’t be any change in the testing code whereas there could be changes in the Terraform code. This can be rectified by -count 1 flag</p><blockquote>go test -count=1 -timeout 30m -p 1</blockquote><p>10. If you are expecting an error and don’t want it to cause a test failure, use the method name that ends with a capital E where we can handle the exceptions in a better way</p><blockquote>if _, err := terraform.InitE(t, terraformOptions); err != nil {</blockquote><blockquote>// Do something with err</blockquote><blockquote>}</blockquote><p>— — — — — — — — — — — —</p><p><strong>References</strong> :</p><p>[1] <a href="https://terratest.gruntwork.io/docs/">https://terratest.gruntwork.io/docs/</a></p><p>[2] <a href="https://golang.org/pkg/testing/">https://golang.org/pkg/testing/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d55fbbd15784" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/testing-your-terraform-code-part-1-d55fbbd15784">Testing your Terraform code — Part 1</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[Why you should intentionally break your perfectly working servers often?]]></title>
            <link>https://dharanisowndharya.medium.com/why-you-should-intentionally-break-your-perfectly-working-servers-often-37a6c08d36ef?source=rss-f52a9f6ba5cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/37a6c08d36ef</guid>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[chaos-theory]]></category>
            <category><![CDATA[chaos-monkey]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[chaos-engineering]]></category>
            <dc:creator><![CDATA[Dharani Sowndharya]]></dc:creator>
            <pubDate>Wed, 03 Mar 2021 13:19:17 GMT</pubDate>
            <atom:updated>2021-03-09T06:07:54.640Z</atom:updated>
            <content:encoded><![CDATA[<h4>A quick introduction to Chaos Engineering</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RbmaYa8_1HZmRxjd" /><figcaption>Photo by <a href="https://unsplash.com/@brett_jordan?utm_source=medium&amp;utm_medium=referral">Brett Jordan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You are working on a very critical release a few days before your much awaited vacation. Surprisingly, everything went according to plan. That junior developer whom you thought would definitely mess up didn’t. You’ve checked everything that could go wrong in your system and you are looking forward to a fun filled trip with your friends and leave early that day.</p><p>Just when you are packing, you get a call from your Ops team. You immediately know that there is some issue. You attend the call with a groan and you hear that the team is facing a downtime because of a failed region in the cloud provider that you have hosted your servers on. One of the cloud services are down and hence all of them that depend on it are showing the dreaded red status in the cloud provider’s status page.</p><p>You realize with a panic that, even though you’ve tested for the high availability option, you didn’t check the high availability in the scale of a region.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*eQcQFBUMpG7PvY1NmvBtqQ.gif" /></figure><p>As a systems administrator or a lead, is this scenario relatable? Often times, the system goes down with a completely new reason that you’ve not come across before and you are put in a situation where you have to be quick on your feet and cool in your head to learn on the spot and rectify it.</p><p>Chaos engineering is a practice to help you in a situation like this.</p><p>As per official documentation,</p><blockquote>Chaos Engineering is the discipline of experimenting on a distributed system in order to build confidence in the system’s capability to withstand turbulent conditions in production.</blockquote><p>Google, Microsoft, Facebook, Amazon have been using some variation of this set up to test their resiliency from the early 2000s</p><p>Despite the concept’s presence in the tech industry from long ago, Netflix introduced the discipline of chaos engineering to the wide world. To safeguard their multi million dollar business which was completely dependant and operated on cloud, they introduced a tool named Chaos monkey all the way back in 2011. It is part of a bunch of tools named Simian Army(now deprecated) in which each of them can cause various levels of destruction to your infrastructure set up. Some of them are:</p><p><strong>Chaos Monkey — </strong>Causing destruction to random servers in the infra<br><strong>Chaos Gorilla — </strong>It simulates disabling a full AZ / Data center<br><strong>Chaos Kongs — </strong>It simulates disabling a complete region<br><strong>Latency monkey — </strong>Introduces delays in communication that we commonly face during outages</p><p>They named it after monkeys because, they wanted to simulate a behavior like that of a destruction that a real monkey could cause in a datacenter by pulling all the cables and destroying everything in sight.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FKrLqtbe8PGEDe%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fmeme-ahora-no-por-favor-porfavor-KrLqtbe8PGEDe&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2FKrLqtbe8PGEDe%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="296" frameborder="0" scrolling="no"><a href="https://medium.com/media/e299c4f494b6b49264d58e952149bbb8/href">https://medium.com/media/e299c4f494b6b49264d58e952149bbb8/href</a></iframe><p>As recognition for this discipline grew, a lot of other vendors came into picture to provide this as a service.</p><p>Some of the products in the market are <a href="https://www.gremlin.com/"><strong>Gremlin</strong></a><strong>, </strong><a href="https://chaostoolkit.org/"><strong>Chaos toolkit</strong></a><strong>, </strong><a href="https://github.com/Shopify/toxiproxy"><strong>Toxi Proxy</strong></a><strong>, </strong><a href="https://github.com/alexei-led/pumba"><strong>Pumba</strong></a><strong> </strong>etc</p><p>A practice named Game day is followed in which the teams tested their resiliency to prove their hypothesis on the behaviour of their system. In this practice, teams and the respectice stake holders sit together to execute disruptive experiments in a safe and controlled manner. They can then work on their recovery procedures and validate their system performance.</p><p>The game days need not be very complicated. You can conduct a game day and check if the Ops team is able to handle issues based on the steps provided in your runbook, or you can see if all your alerts are working as expected or an experiment to see if your DNS service is able to route to a different region in case of a simulation in regional failover</p><p>You need not depend on external vendors to conduct this. You can create your own chaos engineering set up. For example, if you are using AWS, you can write code in boto3 to shut down instances of an ASG at regular periods of time and monitor how it affects your system by running a load test.</p><p>As per the Principles of Chaos Engineering: (<a href="https://principlesofchaos.org/">https://principlesofchaos.org</a>) there are few steps that you have to keep in mind before starting with your own chaos set up</p><ol><li>There should be a clear definition of steady state which you wish to accomplish and you have to define this before starting your experiment. In simple terms, it could be that you want your website to always show 200 as status despite failures in certain targeted servers. Resiliency can be acheived by a simple set up by having multiple instances of your server in an Auto scaling group spanning over multiple availability zones and you can see if this set up allows you to get a steady state.</li><li>Consider and note the measurable outputs of the system that you are going to monitor. It can be your latency, error rates, throughput etc. This will give a clear picture on how your system gets affected by these experiments</li><li>Simulate issues that closely resemble real life events. Bring in to your mind on the last 5 or 6 real time issues that you faced. Maybe, the SSL cert got expired, a sudden increase in users, surge in the usage of memory or cpu or the cloud provider had an outage that made your set up unstable. Use these scenarios and try to simulate them either with the help of existing tools or with your own code</li><li>If you are conducting this in Production, make sure that the destruction that you try to introduce could be contained in some way possible with a kill switch that would stop the experiment after a certain duration or after a certain scope. Make sure that there is always a recovery plan to mitigate issues caused by this experiment</li><li>If possible, automate this whole process</li></ol><p>This process will allow us to learn more about our system. You could be doing a load test, but you’ll know that the application unexpectedly crashes when the count of instances reach a certain limit. This would be something that you wouldn’t have expected, but scenarios like this will prompt us to understand more about our system and why certain issues occur.</p><p>End the whole exercise with retrospection to understand what went well and what could have gone better. Maybe it could be better communication to the stake holders, rewriting your runbook to handle incidents with more details or just making changes to accommodate more resources in your system.</p><p>Is there someone in your team, maybe that junior developer who has a flair for breaking stuff, you can assign him this job to intentionally break your servers to his heart’s content and learn as a team from the experiments about the observations on the system behaviour</p><p>— — — — — — — —</p><p><strong>References</strong>:</p><p><a href="https://github.com/dastergon/awesome-chaos-engineering">GitHub - dastergon/awesome-chaos-engineering: A curated list of Chaos Engineering resources.</a></p><p>https://principlesofchaos.org</p><p>Inspired from discussions with:<a href="https://www.linkedin.com/in/ssivakumar"> Siva S, Distinguished Engineer, Trimble Inc, Chennai</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37a6c08d36ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Useful links that I refer to often in my DevOps day to day work]]></title>
            <link>https://dharanisowndharya.medium.com/useful-links-that-i-refer-to-often-in-my-devops-day-to-day-work-df9763644fde?source=rss-f52a9f6ba5cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/df9763644fde</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Dharani Sowndharya]]></dc:creator>
            <pubDate>Wed, 04 Nov 2020 13:56:09 GMT</pubDate>
            <atom:updated>2020-12-11T10:41:55.683Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Collection of articles for day to day DevOps work</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RCzVDwxZ4Ss3mwdp" /><figcaption>Photo by <a href="https://unsplash.com/@anniespratt?utm_source=medium&amp;utm_medium=referral">Annie Spratt</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote><strong>DevOps:</strong></blockquote><p><strong>Roadmap:</strong></p><p>Very useful representation to understand tools and technologies used in DevOps : <a href="https://roadmap.sh/devops">https://roadmap.sh/devops</a></p><p><strong>Terminologies that every DevOps professional should be aware:</strong></p><p><a href="https://dzone.com/articles/100-devops-terms-or-what-does-your-devops-say">100 DevOps Terms, or, What Does Your DevOps Say? - DZone DevOps</a></p><p><strong>Curated list of 100-best-devops-stories-of-2019:</strong></p><p><a href="https://medium.com/faun/100-best-devops-stories-of-2019-faun-11d0c395cd75">https://medium.com/faun/100-best-devops-stories-of-2019-faun-11d0c395cd75</a></p><blockquote><strong>Internet and DNS</strong></blockquote><p><strong>How does Internet work:</strong></p><p><a href="https://www.youtube.com/watch?v=Dxcc6ycZ73M&amp;list=PLkZYeFmDuaN21nQjzE4RLLNccK_YP0P0_">https://www.youtube.com/watch?v=Dxcc6ycZ73M&amp;list=PLkZYeFmDuaN21nQjzE4RLLNccK_YP0P0_</a></p><p><strong>Loading a webpage might take less than a second but these are the steps that happen underneath: <br></strong><a href="https://medium.com/@maneesha.wijesinghe1/what-happens-when-you-type-an-url-in-the-browser-and-press-enter-bb0aa2449c1a">https://medium.com/@maneesha.wijesinghe1/what-happens-when-you-type-an-url-in-the-browser-and-press-enter-bb0aa2449c1a</a></p><p><strong>How DNS works:</strong></p><p><a href="https://medium.com/faun/how-dns-works-and-how-to-create-your-own-nameservers-c1b1aab86248">How DNS Works and How to Create Your Own Nameservers</a></p><p><strong>Really useful article to understand Route 53 better:</strong></p><ul><li><a href="https://www.bluematador.com/blog/how-to-deploy-an-app-to-aws-route-53-and-dns-explained">How to deploy an app to AWS: Route 53 and DNS explained</a></li><li><a href="https://medium.com/@devopslearning/21-days-of-aws-using-terraform-day-9-introduction-to-route53-using-terraform-deb99c9990ec">21 Days of AWS using Terraform — Day 9- Introduction to Route53 using Terraform</a></li></ul><p><strong>Difference between CNAME and Alias record:</strong></p><p><a href="https://help.ns1.com/hc/en-us/articles/360017511293-What-is-the-difference-between-CNAME-and-ALIAS-records-">https://help.ns1.com/hc/en-us/articles/360017511293-What-is-the-difference-between-CNAME-and-ALIAS-records-</a></p><blockquote><strong>Terraform</strong></blockquote><p><strong>Terraform testing tools:</strong></p><p><a href="https://medium.com/@mschirbel/testing-iac-how-could-we-do-it-b4187f6c1145">Testing IaC — How could we do it</a></p><p><a href="https://terratest.gruntwork.io/docs/getting-started/quick-start/">https://terratest.gruntwork.io/docs/getting-started/quick-start/</a></p><p><a href="https://github.com/k1LoW/awspec">https://github.com/k1LoW/awspec</a></p><p><a href="https://medium.com/@pb8226/running-terraform-with-jenkins-pipelines-f29a8cb861d4">https://medium.com/@pb8226/running-terraform-with-jenkins-pipelines-f29a8cb861d4</a></p><p><a href="https://www.terraform.io/docs/cloud/sentinel/mock.html">https://www.terraform.io/docs/cloud/sentinel/mock.html</a></p><p><a href="https://newcontext-oss.github.io/kitchen-terraform/">https://newcontext-oss.github.io/kitchen-terraform/</a></p><p><a href="https://kitchen.ci/">https://kitchen.ci/</a></p><p><a href="https://cloudskiff.com/terraform-code-testing/">Terraform code testing - Tips to help you start now! - CloudSkiff</a></p><p><strong>Terrascan:</strong></p><p><a href="https://www.cloudsecuritymusings.com/blog/using-terrascan-for-static-code-analysis-of-your-infrastructure-code-part-2">https://www.cloudsecuritymusings.com/blog/using-terrascan-for-static-code-analysis-of-your-infrastructure-code-part-2</a></p><p><a href="https://www.helpnetsecurity.com/2020/08/18/terrascan-open-source-software/">https://www.helpnetsecurity.com/2020/08/18/terrascan-open-source-software/</a></p><p><a href="https://github.com/accurics/terrascan">https://github.com/accurics/terrascan</a></p><p><a href="https://docs.accurics.com/projects/accurics-terrascan/en/latest/getting-started/">https://docs.accurics.com/projects/accurics-terrascan/en/latest/getting-started/</a></p><p><a href="https://github.com/accurics/terrascan">accurics/terrascan</a></p><p><a href="https://devops.stackexchange.com/questions/863/how-to-test-a-terraform-configuration">https://devops.stackexchange.com/questions/863/how-to-test-a-terraform-configuration</a></p><p><strong>Example git hub project using terratest :</strong></p><p><a href="https://github.com/mongodb/terraform-aws-ecs-task-definition">https://github.com/mongodb/terraform-aws-ecs-task-definition</a></p><p><strong>Types of terraform testing that we can perform:</strong></p><p><a href="https://medium.com/swlh/a-jump-start-on-terraform-testing-295522cdb407">A Jump Start on Terraform Testing</a></p><p><strong>Making terraform more DRYer:</strong></p><p><a href="https://medium.com/dev-genius/terraform-staying-dry-when-using-count-conditionals-2c4f6c15a4ac">Terraform: Staying DRY when using count conditionals</a></p><p><strong>The terraform should have code for pre installed plugins so that there is no change</strong><br><a href="https://learn.hashicorp.com/tutorials/terraform/automate-terraform">https://learn.hashicorp.com/tutorials/terraform/automate-terraform</a><br><strong>Creating and using terraform workspaces</strong><br><a href="https://medium.com/better-programming/managing-multiple-environments-in-terraform-5b389da3a2ef">https://medium.com/better-programming/managing-multiple-environments-in-terraform-5b389da3a2ef</a></p><blockquote><strong>Pipeline automation</strong></blockquote><p><strong>DevSecops tools that every devops should be aware of:</strong></p><p><a href="https://medium.com/faun/devsecops-tools-a-list-of-the-31-most-used-tools-7ef561316151">https://medium.com/faun/devsecops-tools-a-list-of-the-31-most-used-tools-7ef561316151</a></p><p><strong>Immutable infrastructure:</strong></p><p>This will eliminate issues caused by a hundred moving components that will give us the issue of it working in lower environment but not working in higher environment<br><a href="https://medium.com/faun/immutable-infrastructure-and-image-factories-for-fun-and-profit-a25c0464be66">https://medium.com/faun/immutable-infrastructure-and-image-factories-for-fun-and-profit-a25c0464be66</a></p><p><strong>DevSecOps pipelines setup:</strong></p><p>Good representation on setting up your CICD pipeline with Security steps — DevSecOps</p><p><a href="https://medium.com/faun/devsecops-automation-framework-b6ebc9ba31a4">DevSecOps Automation Framework</a></p><p><strong>Automation with terraform using Jenkins:</strong></p><ul><li><a href="https://learn.hashicorp.com/tutorials/terraform/automate-terraform">Running Terraform in Automation | Terraform - HashiCorp Learn</a></li><li><a href="https://learn.hashicorp.com/tutorials/terraform/automate-terraform">Running Terraform in Automation | Terraform - HashiCorp Learn</a></li></ul><p><strong>Deployment using terraform and code pipeline aws</strong></p><p><a href="https://medium.com/faun/terraform-deployments-with-aws-codepipeline-342074248843">https://medium.com/faun/terraform-deployments-with-aws-codepipeline-342074248843</a></p><p><strong>Deployment using cloud formation:</strong></p><p><a href="https://medium.com/swlh/aws-cloudformation-managed-complete-ecs-infrastructure-including-ci-cd-pipeline-from-github-to-ecs-b833bb44e01c">https://medium.com/swlh/aws-cloudformation-managed-complete-ecs-infrastructure-including-ci-cd-pipeline-from-github-to-ecs-b833bb44e01c</a></p><p><strong>Deployment using jenkins file in ECS:</strong></p><p><strong>Good example to test the deployment:</strong></p><p><a href="https://github.com/lavaliere/game-of-life/blob/master/Jenkinsfile">https://github.com/lavaliere/game-of-life/blob/master/Jenkinsfile</a></p><p><a href="https://abakonski.com/creating-a-continuous-deployment-pipeline-using-bitbucket-jenkins-and-amazon-ecs-part-2-of-2/">https://abakonski.com/creating-a-continuous-deployment-pipeline-using-bitbucket-jenkins-and-amazon-ecs-part-2-of-2/</a></p><p><strong>ECS automation using Jenkins + Ansible :</strong></p><p><a href="https://medium.com/faun/building-repeatable-infrastructure-with-terraform-and-ansible-on-aws-3f082cd398ad">Building Repeatable Infrastructure with Terraform and Ansible on AWS</a></p><p><strong>Jenkins file for terraform plan and apply:</strong><br><a href="https://github.com/andreistefanciprian/terraform-jenkins-pipeline/blob/master/Jenkinsfile.static">https://github.com/andreistefanciprian/terraform-jenkins-pipeline/blob/master/Jenkinsfile.static</a></p><p><a href="https://medium.com/@timhberry/terraform-pipelines-in-jenkins-47267129ff06">https://medium.com/@timhberry/terraform-pipelines-in-jenkins-47267129ff06</a></p><p><a href="https://objectpartners.com/2016/06/01/automating-terraform-projects-with-jenkins/">https://objectpartners.com/2016/06/01/automating-terraform-projects-with-jenkins/</a></p><p><a href="https://learn.hashicorp.com/terraform/development/running-terraform-in-automation">https://learn.hashicorp.com/terraform/development/running-terraform-in-automation</a></p><p><strong>Very neat pipleline examples :</strong></p><p><a href="https://dzone.com/articles/immutable-infrastructure-cicd-using-hashicorp-terr">https://dzone.com/articles/immutable-infrastructure-cicd-using-hashicorp-terr</a></p><p><a href="https://gist.github.com/gazoakley/87dcc16d28fd05acda4ba0a4be5ac387">https://gist.github.com/gazoakley/87dcc16d28fd05acda4ba0a4be5ac387</a></p><p><a href="https://github.com/TedSpinks/jenkins-tfe-examples/blob/master/terraform-cmd/Jenkinsfile">https://github.com/TedSpinks/jenkins-tfe-examples/blob/master/terraform-cmd/Jenkinsfile</a></p><p><strong>Add manual changes to terraform code:</strong></p><p><a href="https://medium.com/faun/3-tips-to-manage-drift-from-manual-changes-in-terraform-91b3395cfb5c">https://medium.com/faun/3-tips-to-manage-drift-from-manual-changes-in-terraform-91b3395cfb5c</a></p><p><strong>Ideas for different CICD pipelines:</strong></p><p><a href="https://medium.com/avmconsulting-blog/how-to-build-your-first-aws-codepipeline-ci-cd-pipeline-c4127dab6394">https://medium.com/avmconsulting-blog/how-to-build-your-first-a#Cloudws-codepipeline-ci-cd-pipeline-c4127dab6394</a></p><p><strong>Storing secrets:</strong></p><p><a href="https://blog.gruntwork.io/a-comprehensive-guide-to-managing-secrets-in-your-terraform-code-1d586955ace1">https://blog.gruntwork.io/a-comprehensive-guide-to-managing-secrets-in-your-terraform-code-1d586955ace1</a></p><p><strong>Deployment using code build /deploy:</strong></p><p><a href="https://medium.com/polarsquad/continuous-deployments-for-aws-infrastructure-without-trusting-a-third-party-ci-c6b140043bb6">https://medium.com/polarsquad/continuous-deployments-for-aws-infrastructure-without-trusting-a-third-party-ci-c6b140043bb6</a></p><p><strong>Declarative terraform Jenkins pipeline</strong><br><strong>Has good examples on handling exception and user prompt :</strong><br><a href="https://github.com/andnreistefanciprian/terraform-jenkins-pipeline/blob/master/Jenkinsfile.static">https://github.com/andnreistefanciprian/terraform-jenkins-pipeline/blob/master/Jenkinsfile.static</a><br><a href="https://medium.com/@timhberry/terraform-pipelines-in-jenkins-47267129ff06">https://medium.com/@timhberry/terraform-pipelines-in-jenkins-47267129ff06</a></p><p><strong>This shows cloud bees integration in Jenkins UI as well<br>Has better user prompt</strong><br><a href="https://gist.github.com/gazoakley/87dcc16d28fd05acda4ba0a4be5ac387">https://gist.github.com/gazoakley/87dcc16d28fd05acda4ba0a4be5ac387</a><br><a href="https://github.com/TedSpinks/jenkins-tfe-examples/blob/master/terraform-cmd/Jenkinsfile">https://github.com/TedSpinks/jenkins-tfe-examples/blob/master/terraform-cmd/Jenkinsfile</a>Flow diagram for the Jenkins pipeline to IAC set up <br><a href="https://objectpartners.com/2016/06/01/automating-terraform-projects-with-jenkins/">https://objectpartners.com/2016/06/01/automating-terraform-projects-with-jenkins/</a><br><strong>Good error handling<br>Sending messages to slack on success and failure</strong><br><strong>Uses scripted pipeline</strong><br><a href="https://dzone.com/articles/immutable-infrastructure-cicd-using-hashicorp-terr">https://dzone.com/articles/immutable-infrastructure-cicd-using-hashicorp-terr</a></p><p><strong>Jenkins certified engineer certification details:</strong></p><p><a href="https://medium.com/@devopslearning/my-road-to-certified-jenkins-engineer-807ae52409a0">https://medium.com/@devopslearning/my-road-to-certified-jenkins-engineer-807ae52409a0</a></p><blockquote><strong>Linux CLI</strong></blockquote><p><strong>Useful commands with CURL:</strong></p><p><a href="https://medium.com/100-days-of-linux/10-curl-commands-that-you-should-know-ee3d032eb351">10 Curl Commands that you should know</a></p><p><strong>Essential Linux commands:</strong></p><p><a href="https://medium.com/better-programming/15-essential-linux-command-line-tips-and-tricks-95e2bfa2890f">15 Essential Linux Command Line Tips and Tricks</a></p><p><strong>PYENV set up for handling multiple Python versions:</strong></p><p><a href="https://realpython.com/intro-to-pyenv/">Managing Multiple Python Versions With pyenv - Real Python</a></p><p><strong>Useful videos on SysAdmin tasks in Linux:</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLtK75qxsQaMKLUENMaPlD_O2qS8ZBGjuy&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dls5cGi12kGw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fls5cGi12kGw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/13528a9602789d9bc6b6aec03e91752d/href">https://medium.com/media/13528a9602789d9bc6b6aec03e91752d/href</a></iframe><p><strong>Making sense of memory usage in Linux:</strong></p><p><a href="https://www.networkworld.com/article/2722141/making-sense-of-memory-usage-on-linux.html">Making sense of memory usage on Linux</a></p><p><strong>Installing Java:</strong></p><p><a href="https://computingforgeeks.com/how-to-install-java-11-on-centos-7-fedora-29-fedora-28/">https://computingforgeeks.com/how-to-install-java-11-on-centos-7-fedora-29-fedora-28/</a></p><p><strong>How SSH works:</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLtK75qxsQaMII75AbcuIruao1k2qdxwjg&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrfYZR6opTVg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrfYZR6opTVg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3faeb95fde93d0a6328491ea8aebc4a6/href">https://medium.com/media/3faeb95fde93d0a6328491ea8aebc4a6/href</a></iframe><blockquote><strong>SSL :</strong></blockquote><p><strong>How SSL certs are submitted for CA verification</strong></p><p><a href="https://dzone.com/articles/tlsssl-certificates-part-4">TLS/SSL Explained: TLS/SSL Certificates, Part 3 - DZone Security</a></p><p><strong>One way and Mutual TLS explained:</strong></p><p><a href="https://dzone.com/articles/implementing-one-way-and-two-way-ssl-mutual-authen">https://dzone.com/articles/implementing-one-way-and-two-way-ssl-mutual-authen</a></p><blockquote><strong>AWS</strong></blockquote><p><strong>Protecting AWS set up:</strong></p><p><a href="https://medium.com/faun/aws-cloud-security-in-a-nutshell-f9e53907f41d">AWS Cloud Security in a Nutshell</a></p><p><strong>Various ways to login to your AWS account:</strong></p><p><a href="https://medium.com/faun/how-to-access-your-aws-account-de2313542a63">https://medium.com/faun/how-to-access-your-aws-account-de2313542a63</a></p><p><strong>IAM Cross account roles explained:</strong></p><p><a href="https://medium.com/adobetech/working-with-cross-account-roles-in-aws-b4f21dd72f4a">Working with Cross Account Roles in AWS</a></p><p><strong>Validate Lambda Events:</strong></p><p><a href="https://medium.com/cyberark-engineering/aws-lambda-event-validation-from-zero-to-hero-2ca950acd2ea">https://medium.com/cyberark-engineering/aws-lambda-event-validation-from-zero-to-hero-2ca950acd2ea</a></p><p><strong>RDS MySQL or Aurora MySql:</strong></p><p><a href="https://blog.shikisoft.com/why-choose-aurora-over-regular-rds/">Why Choose Amazon Aurora Over Regular RDS?</a></p><p><strong>Install AWS CLI:</strong></p><p><a href="https://docs.aws.amazon.com/cli/latest/userguide/">AWS Command Line Interface</a></p><p><strong>SSH password authentication to EC2:</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLQP5dDPLts66eWDopxxCRjbu6QemVYhSC&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DbwXjaSQ1KwE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FbwXjaSQ1KwE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/624e5f090fc7f864263cd06561b2d3dc/href">https://medium.com/media/624e5f090fc7f864263cd06561b2d3dc/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FRYPosRx7lT0&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DRYPosRx7lT0&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d83b1ecb8b448cf75dfe71b3af63ccf9/href">https://medium.com/media/d83b1ecb8b448cf75dfe71b3af63ccf9/href</a></iframe><p><strong>ECS deployments:</strong></p><p><a href="https://medium.com/@aaron.kaz.music/monitoring-the-health-of-ecs-service-deployments-baeea41ae737">https://medium.com/@aaron.kaz.music/monitoring-the-health-of-ecs-service-deployments-baeea41ae737</a></p><p><a href="https://medium.com/twodigits/ci-cd-pipeline-for-aws-ecs-fargate-958d5c29205d">https://medium.com/twodigits/ci-cd-pipeline-for-aws-ecs-fargate-958d5c29205d</a></p><p><strong>Getting secrets for task def from secrets manager:</strong></p><p><a href="https://medium.com/swlh/how-to-securely-use-aws-secrets-manager-to-inject-secrets-into-ecs-using-infrastructure-as-code-ff2b39b420b6">https://medium.com/swlh/how-to-securely-use-aws-secrets-manager-to-inject-secrets-into-ecs-using-infrastructure-as-code-ff2b39b420b6</a></p><p><strong>Montitoring ecs deployment :</strong></p><p><a href="https://levelup.gitconnected.com/a-practical-guide-to-deploying-microservices-on-aws-6a8ddd298f7e">https://levelup.gitconnected.com/a-practical-guide-to-deploying-microservices-on-aws-6a8ddd298f7e</a></p><p><strong>ECS- capacity provider eg:</strong></p><p><a href="https://stackoverflow.com/questions/60056801/aws-ecs-capacity-provider-using-terraform">https://stackoverflow.com/questions/60056801/aws-ecs-capacity-provider-using-terraform</a></p><p><strong>Scanning of container images in pipeline:</strong></p><p><a href="https://medium.com/faun/container-security-101-scanning-images-for-vulnerabilities-8030af2441ba">https://medium.com/faun/container-security-101-scanning-images-for-vulnerabilities-8030af2441ba</a></p><p><strong>Secret manager for storing secrets </strong>:</p><p><a href="https://codeburst.io/how-to-securely-use-aws-secrets-manager-to-inject-secrets-into-ecs-using-infrastructure-as-code-ff2b39b420b6">https://codeburst.io/how-to-securely-use-aws-secrets-manager-to-inject-secrets-into-ecs-using-infrastructure-as-code-ff2b39b420b6</a></p><blockquote><strong>Ansible</strong></blockquote><p><strong>Simple and clear explanation:</strong></p><p><a href="https://medium.com/swlh/getting-started-with-ansible-ee31be8c6a75">Getting Started With Ansible</a></p><blockquote><strong>Kubernetes</strong></blockquote><p><strong>CKA/CKAD exam preparation:</strong></p><p><a href="https://medium.com/swlh/my-take-towards-cka-ckad-september-curriculum-update-tips-ff38e7585447">My Take Towards CKA &amp; CKAD + September Curriculum Update Tips</a></p><p><strong>When do you need to go for Kubernetes:</strong></p><p><a href="https://thechief.io/c/cloudplex/when-do-you-need-use-kubernetes/">When do you need to use Kubernetes?</a></p><p><strong>Pictorial explanation of Kubernetes:</strong></p><p><a href="https://medium.com/tarkalabs/know-kubernetes-pictorially-f6e6a0052dd0">Know Kubernetes — Pictorially</a></p><p><strong>Curated list of 70 best Kubernetes tutorials</strong></p><p><a href="https://wiki.aquasec.com/display/containers/70+Best+Kubernetes+Tutorials?utm_source=DevOps%27ish&amp;utm_campaign=c49ef46bf7-DEVOPSISH_132&amp;utm_medium=email&amp;utm_term=0_eab566bc9f-c49ef46bf7-46461675">70 Best Kubernetes Tutorials</a></p><blockquote><strong>Nginx</strong></blockquote><p><strong>Very clear intro to Nginx:</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fv2FZGyot5ic&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dv2FZGyot5ic&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/44a550171385ab53a086e0c7a0864d93/href">https://medium.com/media/44a550171385ab53a086e0c7a0864d93/href</a></iframe><p><strong>Optimizing Nginx configurations:</strong></p><p><a href="https://blog.martinfjordvald.com/2011/04/optimizing-nginx-for-high-traffic-loads/">https://blog.martinfjordvald.com/2011/04/optimizing-nginx-for-high-traffic-loads/</a><br><a href="https://www.nginx.com/blog/thread-pools-boost-performance-9x/">https://www.nginx.com/blog/thread-pools-boost-performance-9x/</a><br><a href="https://www.revsys.com/12days/nginx-tuning/">https://www.revsys.com/12days/nginx-tuning/</a></p><p><strong>Understanding contexts in Nginx:</strong></p><p><a href="https://www.digitalocean.com/community/tutorials/understanding-the-nginx-configuration-file-structure-and-configuration-contexts">Understanding the Nginx Configuration File Structure and Configuration Contexts | DigitalOcean</a></p><p><strong>Best practices:</strong></p><p><a href="https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/">Pitfalls and Common Mistakes</a></p><p><strong>Rewrite rules in Nginx:<br></strong><a href="https://www.journaldev.com/26864/nginx-rewrite-url-rules">https://www.journaldev.com/26864/nginx-rewrite-url-rules</a></p><p><strong>Understanding proxy pass:</strong></p><ul><li><a href="https://www.digitalocean.com/community/tutorials/understanding-nginx-http-proxying-load-balancing-buffering-and-caching">Understanding Nginx HTTP Proxying, Load Balancing, Buffering, and Caching | DigitalOcean</a></li><li><a href="https://www.liaohuqiu.net/posts/nginx-proxy-pass/">Nginx proxy_pass: examples for how does nginx proxy_pass map the request | Yet Another Summer Rain</a></li></ul><p><strong>JWT based validations in Nginx:</strong></p><p><a href="https://dzone.com/articles/authenticating-api-clients-with-jwt-and-nginx-plus">https://dzone.com/articles/authenticating-api-clients-with-jwt-and-nginx-plus</a></p><p><a href="https://www.nginx.com/blog/authenticating-api-clients-jwt-nginx-plus/?_ga=2.230276828.1397636340.1563439723-792238633.1548125240">https://www.nginx.com/blog/authenticating-api-clients-jwt-nginx-plus/?_ga=2.230276828.1397636340.1563439723-792238633.1548125240</a></p><p><a href="http://nginx.org/en/docs/http/ngx_http_auth_jwt_module.html?utm_source=authenticating-api-clients-jwt-nginx-plus&amp;utm_medium=blog#variables">http://nginx.org/en/docs/http/ngx_http_auth_jwt_module.html?utm_source=authenticating-api-clients-jwt-nginx-plus&amp;utm_medium=blog#variables</a></p><p><strong>Using an external end point to validate jwt:</strong></p><p><a href="http://nginx.org/en/docs/http/ngx_http_auth_jwt_module.html">http://nginx.org/en/docs/http/ngx_http_auth_jwt_module.html</a></p><p><strong>Validation based on a username and password:</strong></p><p><a href="http://nginx.org/en/docs/http/ngx_http_auth_basic_module.html">http://nginx.org/en/docs/http/ngx_http_auth_basic_module.html</a></p><p><strong>Validation based on IP:</strong></p><p><a href="http://nginx.org/en/docs/http/ngx_http_access_module.html">http://nginx.org/en/docs/http/ngx_http_access_module.html</a></p><blockquote><strong>Encryption</strong></blockquote><p><strong>Difference between HS256 and SHA-256 :</strong></p><p><a href="https://stackoverflow.com/questions/39239051/rs256-vs-hs256-whats-the-difference?source=post_page---------------------------">RS256 vs HS256: What&#39;s the difference?</a></p><p><strong>Understanding JWT tokens :</strong><br><a href="https://medium.com/vandium-software/5-easy-steps-to-understanding-json-web-tokens-jwt-1164c0adfcec">https://medium.com/vandium-software/5-easy-steps-to-understanding-json-web-tokens-jwt-1164c0adfcec</a></p><p><a href="https://blog.angular-university.io/angular-jwt/">JWT: The Complete Guide to JSON Web Tokens</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df9763644fde" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>