<?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 Andy Scott on Medium]]></title>
        <description><![CDATA[Stories by Andy Scott on Medium]]></description>
        <link>https://medium.com/@Andy-scott?source=rss-f66cef87d2dd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QVIXV7PuQgRGQffxZYO_rw@2x.jpeg</url>
            <title>Stories by Andy Scott on Medium</title>
            <link>https://medium.com/@Andy-scott?source=rss-f66cef87d2dd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:03:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Andy-scott/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[DevOps Engineer Interview Preparation]]></title>
            <link>https://medium.com/@Andy-scott/devops-engineer-interview-preparation-b1240ce9010b?source=rss-f66cef87d2dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1240ce9010b</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[sdlc]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[sre]]></category>
            <dc:creator><![CDATA[Andy Scott]]></dc:creator>
            <pubDate>Fri, 28 Oct 2022 12:25:33 GMT</pubDate>
            <atom:updated>2022-10-28T16:07:57.855Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tk7qpzQwesB7ae-3" /><figcaption>The first hurdle is knowing what you don’t know</figcaption></figure><p>This list is designed to assist any DevOps engineers preparing for an interview. I have tried to keep the questions as foundational and cloud agnostic as possible however the links and rationals may be more focused towards AWS technologies.</p><p>Each question may include a short summary and links to further reading, I strongly recommend being able to fully discuss these points and get to a much deeper depth than the answer I have given in this article.</p><p><strong>What is DevOps? </strong><br><em>DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. This speed enables organizations to better serve their customers and compete more effectively in the market.</em></p><p><a href="https://aws.amazon.com/devops/what-is-devops/">What is DevOps? - DevOps Models Explained - Amazon Web Services (AWS)</a></p><p><strong>What are the principles of DevOps?</strong></p><ul><li><a href="https://aws.amazon.com/devops/what-is-devops/?trk=c5f58b77-8784-4fca-8a32-6c80ab18ac48&amp;sc_channel=ps&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops&amp;ef_id=Cj0KCQjw--2aBhD5ARIsALiRlwDFPZ88H3uFiIkCnWi4D9UlevoHdZpeKzqzHO1-csUoGnxx2NfU7d8aAkgTEALw_wcB:G:s&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops#integration"><em>Continuous Integration</em></a></li><li><a href="https://aws.amazon.com/devops/what-is-devops/?trk=c5f58b77-8784-4fca-8a32-6c80ab18ac48&amp;sc_channel=ps&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops&amp;ef_id=Cj0KCQjw--2aBhD5ARIsALiRlwDFPZ88H3uFiIkCnWi4D9UlevoHdZpeKzqzHO1-csUoGnxx2NfU7d8aAkgTEALw_wcB:G:s&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops#cd"><em>Continuous Delivery</em></a></li><li><a href="https://aws.amazon.com/devops/what-is-devops/?trk=c5f58b77-8784-4fca-8a32-6c80ab18ac48&amp;sc_channel=ps&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops&amp;ef_id=Cj0KCQjw--2aBhD5ARIsALiRlwDFPZ88H3uFiIkCnWi4D9UlevoHdZpeKzqzHO1-csUoGnxx2NfU7d8aAkgTEALw_wcB:G:s&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops#microservices"><em>Microservices</em></a></li><li><a href="https://aws.amazon.com/devops/what-is-devops/?trk=c5f58b77-8784-4fca-8a32-6c80ab18ac48&amp;sc_channel=ps&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops&amp;ef_id=Cj0KCQjw--2aBhD5ARIsALiRlwDFPZ88H3uFiIkCnWi4D9UlevoHdZpeKzqzHO1-csUoGnxx2NfU7d8aAkgTEALw_wcB:G:s&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops#iac"><em>Infrastructure as Code</em></a></li><li><a href="https://aws.amazon.com/devops/what-is-devops/?trk=c5f58b77-8784-4fca-8a32-6c80ab18ac48&amp;sc_channel=ps&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops&amp;ef_id=Cj0KCQjw--2aBhD5ARIsALiRlwDFPZ88H3uFiIkCnWi4D9UlevoHdZpeKzqzHO1-csUoGnxx2NfU7d8aAkgTEALw_wcB:G:s&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops#monitoring"><em>Monitoring and Logging</em></a></li><li><a href="https://aws.amazon.com/devops/what-is-devops/?trk=c5f58b77-8784-4fca-8a32-6c80ab18ac48&amp;sc_channel=ps&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops&amp;ef_id=Cj0KCQjw--2aBhD5ARIsALiRlwDFPZ88H3uFiIkCnWi4D9UlevoHdZpeKzqzHO1-csUoGnxx2NfU7d8aAkgTEALw_wcB:G:s&amp;s_kwcid=AL!4422!3!536451522956!e!!g!!aws%20devops#communication"><em>Communication and Collaboration</em></a></li></ul><p><strong>What is the difference between Configuration Management and Infrastructure as Code?</strong></p><p><a href="https://geekflare.com/infrastructure-as-code-vs-configuration-management/">Infrastructure-as-Code Vs Configuration Management: Key Differences</a></p><p><strong>What is CI/CD?<br></strong><em>CI and CD are two acronyms frequently used in modern development practices and </em><a href="https://www.atlassian.com/devops"><em>DevOps</em></a><em>. CI stands for </em><a href="https://www.atlassian.com/continuous-delivery/continuous-integration"><em>continuous integration</em></a><em>, a fundamental </em><a href="https://www.atlassian.com/devops/what-is-devops/devops-best-practices"><em>DevOps best practice</em></a><em> where developers frequently merge code changes into a central repository where automated builds and tests run. But CD can either mean continuous delivery or continuous deployment.</em></p><p><a href="https://about.gitlab.com/topics/ci-cd/">What is CI/CD?</a></p><p><strong>What is the testing can we include in CI/CD pipelines?</strong></p><ul><li>Linting</li><li>Code Quality</li><li>SAST</li><li>Unit Tests</li><li>Component Tests</li><li>Integration Tests</li><li>Functional Tests</li><li>Regression Tests</li><li>E2E Tests</li><li>Performance Tests</li><li>UI Tests</li><li>Smoke Tests</li></ul><p><a href="https://about.gitlab.com/topics/devops/devops-test-automation/">DevOps Test Automation</a></p><p><strong>What are the Pros and Cons of GitFlow based development?</strong></p><ul><li><a href="https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow">Gitflow Workflow | Atlassian Git Tutorial</a></li><li><a href="https://www.gitkraken.com/learn/git/git-flow">What is Git Flow | How to use Git Flow | Learn Git</a></li></ul><p><strong>What are the Pros and Cons of Trunk based development?</strong></p><p><a href="https://trunkbaseddevelopment.com/">Trunk Based Development</a></p><p><strong>What is semantic versioning?</strong><br><em>Semantic Versioning is a 3-component number in the format of X.Y.Z, where :</em></p><ul><li><strong><em>X</em></strong><em> stands for a </em><strong><em>major version</em></strong><em>. The leftmost number denotes a major version. When you increase the major version number, you increase it by one but you reset both patch version and minor versions to zero. If the current version is 2.6.9 then the next upgrade for a major version will be 3.0.0. Increase the value of X when breaking the existing API.</em></li><li><strong><em>Y</em></strong><em> stands for a </em><strong><em>minor version</em></strong><em>. It is used for the release of new functionality in the system. When you increase the minor version, you increase it by one but you must reset the patch version to zero. If the current version is 2.6.9 then the next upgrade for a minor version will be 2.7.0. Increase the value of Y when implementing new features in a backward-compatible way.</em></li><li><strong><em>Z</em></strong><em> stands for a </em><strong><em>Patch Versions:</em></strong><em> Versions for patches are used for bug fixes. There are no functionality changes in the patch version upgrades. If the current version is 2.6.9 then the next version for a patch upgrade will be 2.6.10. There is no limit to these numbers. Increase the value of Z when fixing bugs</em></li></ul><p><a href="https://semver.org/">Semantic Versioning 2.0.0</a></p><p><strong>Explain Monitoring, Logging, Alerting and Tracing?</strong></p><ul><li><a href="https://www.dynatrace.com/news/blog/what-is-observability-2/">What is observability? Not just logs, metrics and traces</a></li><li><a href="https://aws.amazon.com/products/management-and-governance/use-cases/monitoring-and-observability">Monitoring and Observability | AWS Management &amp; Governance</a></li></ul><p><strong>What is artefact management?</strong><br><em>An artefact is any software asset that is connected to or part of a software project. Artefacts are normally binary packages and are used to characterise or describe the function, architecture, and design of the application. Common types of artefacts are images, executables, data models, libraries, use cases and of course the compiled application binary.</em></p><p><em>These artefacts need to be stored and shared with all the developers on that project. Some possible solutions include a shared drive, a source control management tool or an artefact management repository. A shared drive has limitations including limited version control and no artefact deployment capability. A source control management tool is really only designed for managing source code text files and not complex artefacts like large binaries or Docker images.</em></p><p><em>All of the artefacts need to be consistently managed, versioned, and deployed across development teams and sometimes across multiple sites, to ensure quality, reliability and auditability. This is where things get tough to do without the right tool. An artefact repository is specifically designed to house, manage, version, and deploy different types of artefacts for software builds from a central location, and offers the best solution to manage an infinitely expanding number of artefacts.</em></p><p><a href="https://jfrog.com/artifact-management/">Artifact Management Overview | JFrog Platform</a></p><p><strong>What is DNS and how does it work?<br></strong><em>All computers on the Internet, from your smart phone or laptop to the servers that serve content for massive retail websites, find and communicate with one another by using numbers. These numbers are known as IP addresses. When you open a web browser and go to a website, you don’t have to remember and enter a long number. Instead, you can enter a domain name like example.com and still end up in the right place.</em></p><p><em>A DNS service such as Amazon Route 53 is a globally distributed service that translates human readable names like </em><a href="http://www.example.com/"><em>www.example.com</em></a><em> into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other. The Internet’s DNS system works much like a phone book by managing the mapping between names and numbers. DNS servers translate requests for names into IP addresses, controlling which server an end user will reach when they type a domain name into their web browser. These requests are called queries.</em></p><p><em>Authoritative DNS: An authoritative DNS service provides an update mechanism that developers use to manage their public DNS names. It then answers DNS queries, translating domain names into IP address so computers can communicate with each other. Authoritative DNS has the final authority over a domain and is responsible for providing answers to recursive DNS servers with the IP address information. Amazon Route 53 is an authoritative DNS system.</em></p><p><em>Recursive DNS: Clients typically do not make queries directly to authoritative DNS services. Instead, they generally connect to another type of DNS service known a resolver, or a recursive DNS service. A recursive DNS service acts like a hotel concierge: while it doesn’t own any DNS records, it acts as an intermediary who can get the DNS information on your behalf. If a recursive DNS has the DNS reference cached, or stored for a period of time, then it answers the DNS query by providing the source or IP information. If not, it passes the query to one or more authoritative DNS servers to find the information.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrL4-vbsN35w%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrL4-vbsN35w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrL4-vbsN35w%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/1820e57fc26055f58676dfa7d72dae87/href">https://medium.com/media/1820e57fc26055f58676dfa7d72dae87/href</a></iframe><p><a href="https://aws.amazon.com/route53/what-is-dns/">What is DNS? - Introduction to DNS - AWS</a></p><p><strong>Explain the OSI model? <br></strong><em>The Open Systems Interconnection (OSI) model describes seven layers that computer systems use to communicate over a network. It was the first standard model for network communications, adopted by all major computer and telecommunication companies in the early 1980s</em></p><p><em>The modern Internet is not based on OSI, but on the simpler TCP/IP model. However, the OSI 7-layer model is still widely used, as it helps visualize and communicate how networks operate, and helps isolate and troubleshoot networking problems.</em></p><p><em>OSI was introduced in 1983 by representatives of the major computer and telecom companies, and was adopted by ISO as an international standard in 1984.</em></p><p><a href="https://www.geeksforgeeks.org/layers-of-osi-model/">Layers of OSI Model - GeeksforGeeks</a></p><p><strong>Explain the TCP/IP model?<br></strong><em>There are four layers of the TCP/IP model: network access, internet, transport, and application. Used together, these layers are a suite of protocols. The TCP/IP model passes data through these layers in a particular order when a user sends information, and then again in reverse order when the data is received.</em></p><p><a href="https://www.geeksforgeeks.org/tcp-ip-model/">TCP/IP Model - GeeksforGeeks</a></p><p><strong>Compare Fault tolerance and High availability?<br></strong><em>A</em><strong><em> </em></strong><em>fault tolerant system is a critical system that requires being operational with zero downtime, while a highly available system can tolerate short interruptions in service. Both high availability and fault tolerance require the ability to detect failure. A fault tolerant system typically has significantly higher costs than a highly available system. The higher costs are due to having physical redundancy added to the system. Redundancy is achieved by having mirrored components up and running, so failure of a component will not mean failure of the entire system</em></p><p><a href="https://cloudacademy.com/course/difference-between-ha-ft-1269/high-availability-vs-fault-tolerance/">The Difference Between High Availability &amp; Fault Tolerance Course | Cloud Academy</a></p><p><strong>What is an API?</strong><br><em>API is the acronym for Application Programming Interface, which is a software intermediary that allows two applications to talk to each other. Each time you use an app like Facebook, send an instant message, or check the weather on your phone, you’re using an API.</em></p><p><a href="https://aws.amazon.com/what-is/api/">What is an API? - Application Programming Interface Explained - AWS</a></p><p><strong>What are the differences between a Virtual machine and a Container? <br></strong><em>The Prime difference between Containers and Virtual Machine is the virtualisation of Operating System and Hardware respectively. While using Virtual machine each virtual machine has its own underlying operating system whereas, While using containers, Each container runs on same underlying operating system instance, While underlying OS is the same containers can still have different OS environment in their respective namespace.</em></p><p><a href="https://www.atlassian.com/microservices/cloud-computing/containers-vs-vms">Containers vs Virtual Machines | Atlassian</a></p><p><strong>Explain the difference between a stateless and stateful firewall?</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrL4-vbsN35w%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrL4-vbsN35w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrL4-vbsN35w%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/1820e57fc26055f58676dfa7d72dae87/href">https://medium.com/media/1820e57fc26055f58676dfa7d72dae87/href</a></iframe><p><strong>Explain a 3 tier Web Application?<br></strong><em>The three-tier architecture is the most popular implementation of a multi-tier architecture and consists of a single presentation tier, logic tier, and data tier.</em></p><ul><li><a href="https://docs.aws.amazon.com/whitepapers/latest/serverless-multi-tier-architectures-api-gateway-lambda/three-tier-architecture-overview.html">Three-tier architecture overview</a></li><li><a href="https://www.ibm.com/uk-en/cloud/learn/three-tier-architecture">What is Three-Tier Architecture</a></li></ul><p><strong>What are the differences between symmetric and asymmetric encryption?</strong></p><p><a href="https://www.geeksforgeeks.org/difference-between-symmetric-and-asymmetric-key-encryption/">Difference Between Symmetric and Asymmetric Key Encryption - GeeksforGeeks</a></p><p><strong>What is the difference between imperative and declarative?</strong></p><p><a href="https://www.freecodecamp.org/news/imperative-vs-declarative-programming-difference/">Imperative vs Declarative Programming - the Difference Explained in Plain English</a></p><p><strong>What does it mean to have an Idempotent solution?</strong><br><em>Idempotence, the ability of a given operation to always produce the same result, is an important IaC principle. A deployment command always sets the target environment into the same configuration, regardless of the environment’s starting state. Idempotence is achieved by either automatically configuring the existing target, or by discarding the existing target and recreating a fresh environment.</em></p><ul><li><a href="https://learn.microsoft.com/en-us/devops/deliver/what-is-infrastructure-as-code">What is infrastructure as code (IaC)? - Azure DevOps</a></li><li><a href="https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/">Making retries safe with idempotent APIs</a></li></ul><p><strong>What is the difference between mutable and immutable infrastructure? <br></strong><em>The word ‘mutable’ suggests the ability to change- to mutate into something new. In the DevOps world, the </em><a href="https://www.hashicorp.com/resources/what-is-mutable-vs-immutable-infrastructure"><em>advantage of mutability</em></a><em> is crucial when you wish to retain previous data without worrying about obtaining new infrastructure. You can apply patches, upgrade or downgrade, and scale up and down.</em></p><p><em>“Immutable” is the state of being unchangeable. It’s an antonym to mutable, which means that on this end, the infrastructure cannot be modified once deployed. When changes are necessary, you need to deploy afresh, add infrastructure, and decommission old infrastructure.</em></p><p><a href="https://www.hashicorp.com/resources/what-is-mutable-vs-immutable-infrastructure">Immutable Infrastructure: Benefits, Comparisons &amp; More</a></p><p><strong>What is Object Orientated Programming?<br></strong><em>Object-oriented programming (OOP) is a computer programming model that organizes software design around data, or objects, rather than functions and logic. An object can be defined as a data field that has unique attributes and behavior.</em></p><p><em>OOP focuses on the objects that developers want to manipulate rather than the logic required to manipulate them. This approach to programming is well-suited for programs that are large, complex and actively updated or maintained. This includes programs for manufacturing and design, as well as mobile applications; for example, OOP can be used for manufacturing system simulation software.</em></p><p><a href="https://www.freecodecamp.org/news/what-is-object-oriented-programming/">OOP Meaning - What is Object-Oriented Programming?</a></p><p><strong>What is the difference between a proxy and a reverse proxy?<br></strong><em>The key difference between a reverse proxy and a forward proxy is that a forward proxy enables computers isolated on a private network to connect to the public internet, while a reverse proxy enables computers on the internet to access a private subnet.</em></p><p><a href="https://www.theserverside.com/feature/Forward-proxy-vs-reverse-proxy-Whats-the-difference">Forward proxy vs. reverse proxy: What&#39;s the difference?</a></p><p><strong>What is the difference between SAST and DAST?</strong></p><p><a href="https://circleci.com/blog/sast-vs-dast-when-to-use-them/">SAST vs DAST: What they are and when to use them</a></p><p><strong>Explain the difference between connection orientated vs connectionless protocols?</strong></p><p><a href="https://www.geeksforgeeks.org/difference-between-connection-oriented-and-connection-less-services/">Difference between Connection-oriented and Connection-less Services - GeeksforGeeks</a></p><p><strong>Explain the uses of these well known ports: 22, 53, 80, 443, 3306 and 3389?<br></strong><em>Port 22: Remote login protocol secure shell (SSH)<br>Port 53: </em><a href="https://www.sciencedirect.com/topics/computer-science/domain-name-server"><em>DNS</em></a><em> protocol<br>Port 80: HTTP<br>Port 443: HTTPS<br>Port 3306: MySQL<br>Port 3389: RDP</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/1*29UPNsjMpqmrVP-0a4DgNQ.jpeg" /></figure><p><strong>What is the difference between a SQL and a NoSQL database?<br></strong><em>SQL databases are relational, NoSQL databases are non-relational.</em></p><p><em>SQL databases use structured query language and have a predefined schema. NoSQL databases have dynamic schemas for unstructured data.</em></p><p><em>SQL databases are vertically scalable, while NoSQL databases are horizontally scalable.</em></p><p><em>SQL databases are table-based, while NoSQL databases are document, key-value, graph, or wide-column stores.</em></p><p><em>SQL databases are better for multi-row transactions, while NoSQL is better for unstructured data like documents or JSON.</em></p><p><a href="https://www.mongodb.com/nosql-explained/nosql-vs-sql">NoSQL Vs SQL Databases</a></p><p><strong>What are the differences between monolithic vs micro-service architecture?</strong></p><ul><li><a href="https://www.atlassian.com/microservices/microservices-architecture/microservices-vs-monolith">Microservices vs. monolithic architecture | Atlassian</a></li><li><a href="https://www.dynatrace.com/news/blog/microservices-vs-monolithic-architecture/">Microservices vs. monolithic architecture: Understanding the difference</a></li></ul><p><strong>When would you design a system with asynchronous vs synchronous responses?</strong></p><p><a href="https://medium.com/transparent-data-eng/api-synchronous-vs-asynchronous-in-business-87ec9f442ab7">API synchronous vs asynchronous in business</a></p><p><strong>Explain how you handle secrets and parameters in your solutions?</strong></p><ul><li><a href="https://www.beyondtrust.com/resources/glossary/secrets-management">What is Secrets Management? | BeyondTrust</a></li><li><a href="https://www.vaultproject.io/">Vault by HashiCorp</a></li><li><a href="https://acloudguru.com/blog/engineering/an-inside-look-at-aws-secrets-manager-vs-parameter-store">An Inside Look At AWS Secrets Manager vs AWS Systems Manager Parameter Store</a></li></ul><p><strong>What is RTO and RPO?</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FKesoHnsZWoA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DKesoHnsZWoA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FKesoHnsZWoA%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/a8f3bc839daf06db8b1613d272a24099/href">https://medium.com/media/a8f3bc839daf06db8b1613d272a24099/href</a></iframe><p><strong>What is the difference between horizontal and vertical scaling?<br></strong><em>The difference between these two types of scaling comes from the way that computing resources are added to your infrastructure. With vertical scaling (“scaling up”), you’re adding more compute power to your existing instances/nodes. In horizontal scaling (“scaling out”), you get the additional capacity in a system by adding more instances to your environment, sharing the processing and memory workload across multiple devices.</em></p><ul><li><a href="https://www.section.io/blog/scaling-horizontally-vs-vertically/">Scaling Horizontally vs. Scaling Vertically | Section</a></li><li><a href="https://www.freecodecamp.org/news/horizontal-vs-vertical-scaling-in-database/">Horizontal vs. Vertical Scaling - How to Scale a Database</a></li></ul><p><strong>Explain what TLS is and how it works?</strong></p><p>Transport Layer Security is a cryptographic protocol designed to provide communications security over a computer network. The protocol is widely used in applications such as email, instant messaging, and voice over IP, but its use in securing HTTPS remains the most publicly visible.</p><ul><li><a href="https://www.internetsociety.org/deploy360/tls/basics/">What is TLS &amp; How Does it Work? | ISOC Internet Society</a></li><li><a href="https://www.onelogin.com/blog/real-difference-saml-oidc">What is the Real Difference Between SAML and OIDC</a></li></ul><p><strong>What are RFC 1918 CIDR ranges?</strong><br><em>RFC 1918 describes the use of IP address space deemed private by IANA, the Internet Assigned Numbers Authority (see, for example, </em><a href="http://www.faqs.org/rfcs/rfc1918.html"><em>RFC1918 — Address Allocation for Private Internets</em></a><em> for details). Private address space is available for use by any organisation and is guaranteed to be not routable in the public Internet. What this means in practice is that any host machine which is assigned a private address defined by RFC 1918 cannot be reached “directly” by any other machine not in the hosting organisation’s local network.</em></p><ul><li>10.0.0.0/8 (addresses 10.0.0.0 through 10.255.255.255 inclusive)</li><li>172.16.0.0/12 (addresses 172.16.0.0 through 172.31.255.255 inclusive)</li><li>192.168.0.0/16 (addresses 192.168.0.0 through 192.168.255.255 inclusive)</li></ul><p><a href="https://www.ibm.com/docs/en/networkmanager/4.2.0?topic=translation-private-address-ranges">Private Address Ranges</a></p><p><strong>What is Privileged access management?<br></strong><em>PAM consists of the cybersecurity strategies and technologies for exerting control over the elevated (“privileged”) access and permissions for users, accounts, processes, and systems across an IT environment. By dialling in the appropriate level of privileged access controls, PAM helps organizations condense their organization’s attack surface, and prevent, or at least mitigate, the damage arising from external attacks as well as from insider malfeasance or negligence.</em></p><ul><li><a href="https://www.beyondtrust.com/resources/glossary/privileged-access-management-pam">What is Privileged Access Management (PAM)? | BeyondTrust</a></li><li><a href="https://www.cyberark.com/what-is/privileged-access-management/">Privileged Access Management (PAM)</a></li></ul><p><strong>How does a browser display content of a website?</strong></p><p><a href="https://aws.amazon.com/blogs/mobile/what-happens-when-you-type-a-url-into-your-browser/">What happens when you type a URL into your browser? | Amazon Web Services</a></p><p><strong>What is a CDN?<br></strong><em>A content delivery network (CDN) refers to a geographically distributed group of servers which work together to provide fast delivery of Internet content.</em></p><p><em>A CDN allows for the quick transfer of assets needed for loading Internet content including HTML pages, javascript files, stylesheets, images, and videos. The popularity of CDN services continues to grow, and today the majority of web traffic is served through CDNs, including traffic from major sites like Facebook, Netflix, and Amazon.</em></p><p><em>A properly configured CDN may also help protect websites against some common malicious attacks, such as </em><a href="https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/"><em>Distributed Denial of Service (DDOS) attacks</em></a><em>.</em></p><p><a href="https://aws.amazon.com/what-is/cdn/">What is a CDN? - Content Delivery Network Explained - AWS</a></p><p><strong>What is the difference between a Data lake and a Data warehouse?<br></strong><em>A data lake contains all an organization’s data in a raw, unstructured form, and can store the data indefinitely — for immediate or future use. A data warehouse contains structured data that has been cleaned and processed, ready for strategic analysis based on predefined business needs.</em></p><p><a href="https://www.talend.com/uk/resources/data-lake-vs-data-warehouse/">Data Lake vs Data Warehouse: Key Differences</a></p><p><strong>What is meant by the term Serverless?<br></strong><em>Serverless is a cloud-native development model that allows developers to build and run applications without having to manage servers. There are still servers in serverless, but they are abstracted away from app development.</em></p><p><a href="https://aws.amazon.com/serverless/">Serverless Computing</a></p><p><strong>In cloud computing what is the shared responsibility model?<br></strong><em>Security and Compliance is a shared responsibility between AWS and the customer. This shared model can help relieve the customer’s operational burden as AWS operates, manages and controls the components from the host operating system and virtualization layer down to the physical security of the facilities in which the service operates. The customer assumes responsibility and management of the guest operating system (including updates and security patches), other associated application software as well as the configuration of the AWS provided security group firewall. Customers should carefully consider the services they choose as their responsibilities vary depending on the services used, the integration of those services into their IT environment, and applicable laws and regulations. The nature of this shared responsibility also provides the flexibility and customer control that permits the deployment. As shown in the chart below, this differentiation of responsibility is commonly referred to as Security “of” the Cloud versus Security “in” the Cloud.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LKUdqEnrNlW6beAY.jpg" /></figure><p><a href="https://aws.amazon.com/compliance/shared-responsibility-model/">Shared Responsibility Model - Amazon Web Services (AWS)</a></p><p><strong>What is the Cloud adoption framework?</strong></p><p><a href="https://docs.aws.amazon.com/whitepapers/latest/overview-aws-cloud-adoption-framework/welcome.html">An Overview of the AWS Cloud Adoption Framework</a></p><p><strong>In Identity Access Management what is ABAC and RBAC?</strong></p><p><a href="https://www.okta.com/uk/identity-101/role-based-access-control-vs-attribute-based-access-control/">RBAC vs. ABAC: Definitions &amp; When to Use</a></p><p><strong>What is the difference between a mono repository and a multi repository strategy?</strong></p><p><a href="https://www.hashicorp.com/blog/terraform-mono-repo-vs-multi-repo-the-great-debate">Terraform Mono Repo vs. Multi Repo: The Great Debate</a></p><p><strong>What are the different types of deployment strategies?</strong></p><p><a href="https://docs.aws.amazon.com/whitepapers/latest/practicing-continuous-integration-continuous-delivery/deployment-methods.html">Deployment methods</a></p><p><strong>What is CRUD?</strong></p><p><a href="https://www.codecademy.com/article/what-is-crud">What is CRUD? | Codecademy</a></p><p><strong>What is CQRS?<br></strong><em>CQRS stands for Command and Query Responsibility Segregation, a pattern that separates read and update operations for a data store. Implementing CQRS in your application can maximize its performance, scalability, and security. The flexibility created by migrating to CQRS allows a system to better evolve over time and prevents update commands from causing merge conflicts at the domain level.</em></p><p><a href="https://learn.microsoft.com/en-us/azure/architecture/patterns/cqrs">CQRS Pattern - Azure Architecture Center</a></p><p><strong>What is MVC?<br></strong><em>The MVC architecture pattern turns complex application development into a much more manageable process. It allows several developers to simultaneously work on the application.</em></p><ul><li><strong><em>Model</em></strong><em>: The backend that contains all the data logic</em></li><li><strong><em>View</em></strong><em>: The frontend or graphical user interface (GUI)</em></li><li><strong><em>Controller</em></strong><em>: The brains of the application that controls how data is displayed</em></li></ul><p><a href="https://learn.microsoft.com/en-us/aspnet/core/mvc/overview?view=aspnetcore-6.0">Overview of ASP.NET Core MVC</a></p><p><strong>What are common http responses?<br><em>1xxs — Informational responses: </em></strong><em>The server is thinking through the request.</em></p><p><strong><em>2xxs — Success!</em></strong><em> The request was successfully completed and the server gave the browser the expected response.</em></p><p><strong><em>3xxs </em></strong><em>— </em><strong><em>Redirection: </em></strong><em>You got redirected somewhere else. The request was received, but there’s a redirect of some kind.</em></p><p><strong><em>4xxs — Client errors:</em></strong><em> Page not found. The site or page couldn’t be reached. (The request was made, but the page isn’t valid — this is an error on the website’s side of the conversation and often appears when a page doesn’t exist on the site.)</em></p><p><strong><em>5xxs — Server errors: </em></strong><em>Failure. A valid request was made by the client but the server failed to complete the request.</em></p><p><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Status">HTTP response status codes - HTTP | MDN</a></p><p><strong>What is SDLC?<br></strong><em>The systems development life cycle, or software development life cycle in systems engineering, information systems and software engineering, is a process of creating or altering information systems, and the models and methodologies that people use to develop these systems. In software engineering the SDLC concept underpins many kinds of software development methodologies. These methodologies form the framework for planning and controlling the creation of an information system: the software development process.</em></p><p><a href="https://www.servicenow.com/uk/products/devops/what-is-sdlc.html">What is the Software Development Life Cycle (SDLC)? - ServiceNow</a></p><p><strong>What is ALM? <br></strong><em>Application Lifecycle Management is a continuous process of managing the life of an application through governance, development and maintenance. ALM is the marriage of business management to software engineering made possible by tools that facilitate and integrate requirements management, architecture, coding, testing, tracking, and release management.</em></p><p><a href="https://www.redhat.com/en/topics/devops/what-is-application-lifecycle-management-alm">What is application lifecycle management (ALM)?</a></p><h3>Concepts</h3><ul><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.apn-partner.en.html">APN Partner</a>: A software or professional services firm in the AWS APN program that offer a wide range of products and expertise to help customers take advantage of the AWS Cloud.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.cloudtrail.en.html">AWS CloudTrail</a>: A web service that records AWS API calls for your account and delivers log files to you. The recorded information includes the identity of the API caller, the time of the API call, the source IP address of the API caller, the request parameters, and the response elements returned by the AWS service.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.devtools.en.html">AWS Developer Tools</a>: A set of services designed to enable rapid and safe delivery of software</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.local-region.en.html">AWS Local Region</a>: A single datacenter designed to complement an existing AWS Region</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.apn.en.html">AWS Partner Network</a>: The AWS Partner Network (APN) is the global partner program for AWS.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.region.en.html">AWS Region</a>: A named set of AWS resources in the same geographical area. A Region comprises at least two Availability Zones.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.sts.en.html">AWS Security Token Service</a>: A web service for requesting temporary, limited-privilege credentials for AWS Identity and Access Management users or for users that you authenticate (federated users).</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.shared-resp-model.en.html">AWS Shared Responsibility Model</a>: Security and Compliance is a shared responsibility between AWS and the customer.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.amazoncw.en.html">Amazon CloudWatch</a>: A web service that enables you to monitor and manage various metrics, and configure alarm actions based on data from those metrics.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.amazon-ebs-optimized-instance.en.html">Amazon EBS-optimized instance</a>: An Amazon EBS–optimized instance uses an optimized configuration stack and provides additional, dedicated capacity for Amazon EBS I/O.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.VMimport.en.html">Amazon EC2 VM Import Connector</a>: VM Import/Export enables you to import and export virtual machines.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.ec2-instance-store.en.html">Amazon EC2 instance store</a>: Storage is located on disks that are physically attached to the host computer.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.amazon-s3-transfer-acceleration.en.html">Amazon S3 Transfer Acceleration</a>: Amazon S3 Transfer Acceleration enables fast, easy, and secure transfers of files over long distances between your client and an S3 bucket. Transfer Acceleration takes advantage of Amazon CloudFront’s globally distributed edge locations. As the data arrives at an edge location, data is routed to Amazon S3 over an optimized network path.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.architecture.en.html">Architecture</a>: How components interact and communicate.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.availability.en.html">Availability</a>: The percentage of time that a workload is available for use, where “available for use” means that it performs its agreed function when required. Availability (also known as service availability) is a commonly used metric to quantitatively measure reliability.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.az.en.html">Availability Zone</a>: A distinct location within a Region that is insulated from failures in other Availability Zones, and provides inexpensive, low-latency network connectivity to other Availability Zones in the same Region.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.best-practice.en.html">Best practice</a>: Proven ways of achieving successful outcomes.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.cache.en.html">Cache</a>: A place that data is stored, temporarily, to increase performance by decreasing access time to frequently used data.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.canary-deployment.en.html">Canary deployment</a>: The slow rollout of a new version of an existing application.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.component.en.html">Component</a>: The code, configuration and AWS Resources that deliver against a business requirement.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.consistency.en.html">Consistency</a>: A state where two systems, storing the same information, return the same results.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.continuous-deployment.en.html">Continuous deployment</a>: Automated deployment to production which is dependent on results from testing and building. Every time a build and all the tests occur with no errors or failed tests, code is deployed automatically.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.continuous-integration.en.html">Continuous integration</a>: Automation that is used to perform builds of software and automate tests against that software.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.coe.en.html">Correction of Error</a>: Process for improving quality by documenting and addressing issues</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.costalloctag.en.html">Cost Allocation Tag</a>: Organize your resource costs on your cost allocation report</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.data-warehouse.en.html">Data warehouse</a>: A central repository of information that can be analyzed to make better informed decisions.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.database-level-settings.en.html">Database-level settings</a>: Database systems, being software, almost uniformly have configuration settings that affect performance.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.durability.en.html">Durability</a>: The ability of a system to remain functional when faced with the challenges of normal operation over its lifetime.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.dynamic-content-delivery.en.html">Dynamic Content Delivery</a>: Delivery of application generated content that includes elements that are personalized to each viewer</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.ec2-instance.en.html">EC2 instance</a>: A compute instance in the Amazon EC2 service. Other AWS services use the term EC2 instance to distinguish these instances from other types of instances they support.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.edge-location.en.html">Edge location</a>: A site that CloudFront uses to cache copies of your content for faster delivery to users at any location.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.elasticity.en.html">Elasticity</a>: The ability to acquire resources as you need them and release resources when you no longer need them. In the cloud, you want to do this automatically.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.enhanced-networking.en.html">Enhanced Networking</a>: Enhanced networking uses single root I/O virtualization (SR-IOV) to provide high-performance networking capabilities on supported instance types.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.event.en.html">Event</a>: An instance of something happening that is significant to the workload.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.federated-identity.en.html">Federated Identity</a>: Federated identities are those which enable users to have a single identity stored in an organizations central identity provider.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.feedback-loop.en.html">Feedback loop</a>: A mechanism by which output from a process or system is fed back into the control of that process or system.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.fivewhys.en.html">Five whys</a>: Helps in identifying the root cause of a problem by determining the relationship between different root causes of a problem.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.gameday.en.html">Game day</a>: Simulates a failure or event to test systems, processes, and teams responses</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.horizontal-scaling.en.html">Horizontal scaling</a>: The ability for a system to grow by adding additional computers.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.iam-policy.en.html">IAM Policy</a>: Access in AWS is managed through policies, that can be attached to IAM identities or AWS resources.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.in-memory.en.html">In-memory</a>: The state of being stored in volatile system RAM rather than on stable storage, such as flash or disk.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.incident.en.html">Incident</a>: An event that requires an intervention or response.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.indexes.en.html">Indexes</a>: A technology that is designed to make looking up information more efficient.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.ishikawadiagram.en.html">Ishikawa diagram</a>: Helps in capturing the causal relationship between cause and effect, and groups causes into meaningful groupings.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.key-distribution.en.html">Key distribution</a>: The relative probability that a given key to access data is spread out across storage.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.latency.en.html">Latency</a>: A measurement of the amount of time between an action and the result, often between a request and a response.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.latency-based-routing.en.html">Latency-based Routing</a>: Improves performance by routing your customers to the AWS endpoint (e.g. EC2 instances, Elastic IPs or ELBs) that provides the fastest experience based on actual performance measurements of the different AWS regions where your application is running.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.mechanical-sympathy.en.html">Mechanical Sympathy</a>: Using a tool or system with an understanding of how it operates best.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.memory.en.html">Memory</a>: A component of a computer system that is designed for short-term, fast-access, data storage; often this is Random-Access Memory (RAM), but there are other forms as well.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.milestone.en.html">Milestone</a>: Mark key changes in your architecture as it evolves.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.mfa.en.html">Multi-factor Authentication</a>: Multi-factor Authentication adds an extra layer of protection on top of your user name and password.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.network-address-utilization.en.html">Network address utilization</a>: This is a measurement of the percentage of non-overlapping address space you consume out of all private address spaces available. VPCs are restricted to 65535 addresses, and data centers and offices have defined ranges. Networks are defined by Classless Inter-Domain Routing (CIDR) ranges that cannot overlap.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.nosql.en.html">NoSQL</a>: NoSQL databases are purpose built for specific data models and have flexible schemas for building modern applications.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.partition.en.html">Partition</a>: A division of elements, oftentimes data or resources, along certain boundaries.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.partition-tolerance.en.html">Partition tolerance</a>: A system’s ability to continue to operate correctly when it has been partial separated; often in reference to a distributed system.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.placement-group.en.html">Placement Group</a>: You can launch or start instances in a placement group, which determines how instances are placed on underlying hardware.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.playbook.en.html">Playbook</a>: A documented process to investigate the source of an issue.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.pec.en.html">Principal engineering community</a>: Amazon’s Principal Engineer Community sets the standard for engineering excellence at Amazon.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.problem.en.html">Problem</a>: An event that requires intervention and either recurs or cannot currently be resolved.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.piops.en.html">Provisioned IOPS</a>: For EBS volumes you can specify a consistent IOPS rate when you create the volume.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.query-capability.en.html">Query capability</a>: A way to ask for information from a system.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.relational.en.html">Relational database</a>: A relational database is a collection of data items with pre-defined relationships between them.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.c-reliability.en.html">Reliability</a>: The ability of a workload to perform its intended function correctly and consistently when it’s expected to. This includes the ability to operate and test the workload through its total lifecycle.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.resiliency.en.html">Resiliency</a>: The ability of a workload to recover from infrastructure or service disruptions, dynamically acquire computing resources to meet demand, and mitigate disruptions, such as misconfigurations or transient network issues.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.root-user.en.html">Root User</a>: When you first create an Amazon Web Services (AWS) account, you begin with a single sign-in identity that has complete access to all AWS services and resources in the account. This identity is called the AWS account root user and is accessed by signing in with the email address and password that you used to create the account.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.rca.en.html">Root cause analysis</a>: Helps in identifying what, how, and why an event or failure happened resulting in corrective and preventive measure.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.runbook.en.html">Runbook</a>: A procedure to achieve a specific outcome.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.scalability.en.html">Scalability</a>: A measurement of a system’s ability to grow to accommodate an increase in demand.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.service-limits.en.html">Service Limits</a>: Services have limitations to protect the consumer as well as the provider; physical locations have limitations built into their construction.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.service-accessibility.en.html">Service accessibility</a>: Ensures consumers of the workload are able to access your services, either through the internet, private networking, or VPN.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.ssd.en.html">Solid-state drive</a>: Solid-state drives are a storage device that uses memory to store data.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.storage-optimization.en.html">Storage optimization</a>: Choosing storage technology best matches the access patterns of the system using it.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.tag.en.html">Tagging</a>: Assign metadata to AWS resources to categorize and organize.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.technology-portfolio.en.html">Technology portfolio</a>: The collection of workloads that are required for the business to operate.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.vpc-endpoint.en.html">VPC Endpoint</a>: A VPC endpoint enables you to privately connect your VPC to supported AWS services and VPC endpoint services powered by PrivateLink without requiring an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC do not require public IP addresses to communicate with resources in the service. Traffic between your VPC and the other service does not leave the Amazon network.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.vpc-flow-logs.en.html">VPC Flow Logs</a>: enables you to capture information about the IP traffic going to and from network interfaces in your VPC.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.workload.en.html">Workload</a>: The set of components that together deliver business value.</li><li><a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.network-acl.en.html">network ACL</a>: An optional layer of security that acts as a firewall for controlling traffic in and out of a subnet. You can associate multiple subnets with a single network ACL, but a subnet can be associated with only one network ACL at a time.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1240ce9010b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Variables in Terraform]]></title>
            <link>https://medium.com/@Andy-scott/using-variables-in-terraform-fb2abb1ca130?source=rss-f66cef87d2dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb2abb1ca130</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[variables]]></category>
            <dc:creator><![CDATA[Andy Scott]]></dc:creator>
            <pubDate>Wed, 26 Oct 2022 12:23:05 GMT</pubDate>
            <atom:updated>2022-10-26T21:34:08.549Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*czolZgkXH58AlSMt" /><figcaption>Terraform variables</figcaption></figure><p>Input variables let you customise aspects of Terraform modules without altering the module’s own source code. This functionality allows you to share modules across different Terraform configurations, making your module composable and reusable.</p><p>In this article we will explore how to use variables in terraform, recap on basic usage and include real world examples. Every example includes a link to the example <a href="https://github.com/andyscott1547/terraform-aws-vpc-endpoints/tree/main/examples">GitHub</a> repository.</p><p>Variables are important in making Terraform modules reusable and also enabling solutions to be deployed into multiple environments, regions and accounts.</p><p><strong>Declaring variables</strong></p><p>To declare a variable we need a variable block, we need to give the variable a name. It is also recommended to give the variable a description and a type.</p><pre>variable &quot;example&quot; {<br>  type        = string<br>  description = &quot;example string to show how to declare a variable&quot;<br>}</pre><p>Below is a more complex example showing a default value, wether the variable is sensitive, condition and error message and wether the variable can be a null value.</p><pre>variable &quot;example&quot; {<br>  type          = string<br>  description   = &quot;example string to show how to declare a variable&quot;<br>  default       = &quot;example&quot;<br>  sensitive     = true<br>  condition     = var.example == &quot;example&quot;<br>  error_message = &quot;This is an example, var == example only&quot;<br>  nullable      = false<br>}</pre><p><strong>Assigning variables</strong></p><p>Variables can be assigned a number of different ways allowing flexibility in solutions.</p><p>Environment variables</p><pre>export TF_VAR_example=&quot;example&quot;</pre><p>Command line arguments</p><pre>terraform apply -var=&quot;example=example&quot;</pre><p>TF Vars Files</p><pre>terraform apply -var-file=&quot;example.tfvars&quot;</pre><p>In addition to these methods terraform will automatically take any values assigned from a file named terraform.tfvars or *.auto.tfvars. Finally if you haven’t assigned the variable correctly terraform will prompt you to manually enter the value when you run terraform commands that require these variables.</p><p>Hashicorp documentation is well written and easy to navigate, The link below gives further details of how to declare and assign variables in Terraform. Let’s go beyond the basic usage and explore some more complex scenarios.</p><p><a href="https://developer.hashicorp.com/terraform/language/values/variables">Input Variables - Configuration Language | Terraform | HashiCorp Developer</a></p><p>Now we’ll look at some examples of how to use variables in real world situations. Im going to use this <a href="https://registry.terraform.io/modules/andyscott1547/vpc-endpoints/aws/latest">terraform module</a> as our example, this module creates AWS VPC interface and gateway endpoints.</p><p><strong>Basic <br></strong>This example of module usage doesn&#39;t include any variables, the underlying module has lots of variables, some are required and some have defaults set. We have hardcoded all the values directly in main.tf, doing this would cause us issues if we intend to deploy the solution into multiple VPCs, multiple regions or multiple accounts.</p><pre># examples/basic/main.tf</pre><pre>module &quot;vpc_endpoints&quot; {<br>  source  = &quot;andyscott1547/vpc-endpoints/aws&quot;<br>  version = &quot;1.0.3&quot;<br>  vpc_id  = &quot;vpc-1234567890&quot;</pre><pre>  interface_endpoints = [<br>    &quot;ec2&quot;,<br>    &quot;rds&quot;,<br>    &quot;sqs&quot;,<br>    &quot;sns&quot;,<br>    &quot;ssm&quot;,<br>    &quot;logs&quot;,<br>    &quot;ssmmessages&quot;,<br>    &quot;ec2messages&quot;,<br>    &quot;autoscaling&quot;,<br>    &quot;ecs&quot;,<br>    &quot;athena&quot;<br>  ]</pre><pre>  gateway_endpoints = [<br>    &quot;s3&quot;,<br>    &quot;dynamodb&quot;<br>  ]</pre><pre>  subnet_ids = [<br>    &quot;subnet-1234567890&quot;,<br>    &quot;subnet-0987654321&quot;,<br>    &quot;subnet-1234567890&quot;<br>  ]</pre><pre>  route_table_ids = [<br>    &quot;rtb-1234567890&quot;,<br>    &quot;rtb-0987654321&quot;,<br>    &quot;rtb-1234567890&quot;<br>  ]<br>}</pre><p><a href="https://github.com/andyscott1547/terraform-aws-vpc-endpoints/tree/main/examples/basic">terraform-aws-vpc-endpoints/examples/basic at main · andyscott1547/terraform-aws-vpc-endpoints</a></p><p><strong>Multiple tfvars files<br></strong>This example of module usage we have created an &lt;environment&gt;.tfvars file per environment. This solves the problems we saw previously when deploying to multiple VPCs, Regions and Accounts. Wether using CICD or not the terraform apply command will include -<em>var-file </em>argument.</p><pre># examples/tfvars_environment_specific/main.tf</pre><pre>module &quot;vpc_endpoints&quot; {<br>  source                      = &quot;andyscott1547/vpc-endpoints/aws&quot;<br>  version                     = &quot;1.0.3&quot;<br>  managed_private_dns_enabled = var.managed_private_dns_enabled<br>  vpc_id                      = var.vpc_id<br>  interface_endpoints         = var.interface_endpoints<br>  gateway_endpoints           = var.gateway_endpoints<br>  subnet_ids                  = var.subnet_ids<br>  route_table_ids             = var.route_table_ids<br>}</pre><p><a href="https://github.com/andyscott1547/terraform-aws-vpc-endpoints/tree/main/examples/tfvars_environment_specific">terraform-aws-vpc-endpoints/examples/tfvars_environment_specific at main · andyscott1547/terraform-aws-vpc-endpoints</a></p><p><strong>Combining variables and data lookups</strong><br>This example of module usage we have decided that we don’t want to use a variable for the <em>vpc_id</em>, <em>subnet_ids</em> and <em>route_table_ids</em> but to deploy the same endpoints in each environment. Here we have used data lookups to retrieve the information we need to assign these variables within the module. To effectively use data lookups it is useful to have naming and tagging strategy, this allows us to filter results for the information we want. As the endpoints aren’t changing between environment i have used a *.auto.tfvars file so i don’t have to pass this as an argument to my terraform commands.</p><pre># examples/data_lookup/main.tf</pre><pre>module &quot;vpc_endpoints&quot; {<br>  source                      = &quot;andyscott1547/vpc-endpoints/aws&quot;<br>  version                     = &quot;1.0.3&quot;<br>  managed_private_dns_enabled = var.managed_private_dns_enabled<br>  vpc_id                      = data.aws_vpc.current.id<br>  interface_endpoints         = var.interface_endpoints<br>  gateway_endpoints           = var.gateway_endpoints<br>  subnet_ids                  = data.aws_subnets.current.ids<br>  route_table_ids             = data.aws_route_tables.current.ids<br>}</pre><p><a href="https://github.com/andyscott1547/terraform-aws-vpc-endpoints/tree/main/examples/data_lookup">terraform-aws-vpc-endpoints/examples/data_lookup at main · andyscott1547/terraform-aws-vpc-endpoints</a></p><p><strong>Auto tfvars with locals and data lookups<br></strong>This example of module usage we are combining data lookups with some additional logic to access relevant variables from a map in *.auto.tfvars. This time we want to deploy different VPC endpoints into different environments to help optimise costs. We have used data lookups to retrieve the information we need to assign the <em>vpc_id</em>, <em>subnet_ids</em> and <em>route_table_ids </em>variables.</p><p>In *.auto.tfvars we have two sections, one for global variables and one for environment specific variables. The env specific section contains a map of maps for each environment. This is indexed in locals from a separate variable, this variable can be passed by environment variable or command line argument. This is particularly useful in automation, there is a more preferred way using <em>Terraform workspaces</em> but we’ll cover that next as not all backends support workspaces.</p><pre>module &quot;vpc_endpoints&quot; {<br>  source                      = &quot;andyscott1547/vpc-endpoints/aws&quot;<br>  version                     = &quot;1.0.3&quot;<br>  managed_private_dns_enabled = var.managed_private_dns_enabled<br>  vpc_id                      = data.aws_vpc.current.id<br>  interface_endpoints         = local.environment.interface_endpoints<br>  gateway_endpoints           = local.environment.gateway_endpoints<br>  subnet_ids                  = data.aws_subnets.current.ids<br>  route_table_ids             = data.aws_route_tables.current.ids<br>}</pre><p><a href="https://github.com/andyscott1547/terraform-aws-vpc-endpoints/tree/main/examples/data_lookup_env_specific">terraform-aws-vpc-endpoints/examples/data_lookup_env_specific at main · andyscott1547/terraform-aws-vpc-endpoints</a></p><p><strong>Terraform Workspace with auto tfvars</strong></p><p><em>Terraform workspaces</em></p><p><em>Each Terraform configuration has an associated </em><a href="https://developer.hashicorp.com/terraform/language/settings/backends/configuration"><em>backend</em></a><em> that defines how Terraform executes operations and where Terraform stores persistent data, like </em><a href="https://developer.hashicorp.com/terraform/language/state/purpose"><em>state</em></a><em>.</em></p><p><em>The persistent data stored in the backend belongs to a workspace. The backend initially has only one workspace containing one Terraform state associated with that configuration. Some backends support multiple named workspaces, allowing multiple states to be associated with a single configuration. The configuration still has only one backend, but you can deploy multiple distinct instances of that configuration without configuring a new backend or changing authentication credentials.</em></p><p><a href="https://developer.hashicorp.com/terraform/language/state/workspaces">State: Workspaces | Terraform | HashiCorp Developer</a></p><p>Now we’ve recapped what a terraform workspace is…</p><p>This example of module usage we are using terraform workspaces and a *.auto.tfvars file that contains two sections, one for global variables and one for environment specific variables. The env specific section contains a map of maps for each environment. This is indexed in by the terraform workspace name, in this example we would have terraform workspace per environment so we can utilise the same code. When using terraform workspaces a new built in variable becomes available to us. <em>terraform.workspace</em></p><p>Create a new terraform workspace</p><pre>terraform workspace new &lt;environment&gt;</pre><pre># examples/workspace_specific/main.tf</pre><pre>module &quot;vpc_endpoints&quot; {<br>  source                      = &quot;andyscott1547/vpc-endpoints/aws&quot;<br>  version                     = &quot;1.0.3&quot;<br>  managed_private_dns_enabled = var.managed_private_dns_enabled<br>  vpc_id                      = local.environment.vpc_id<br>  interface_endpoints         = local.environment.interface_endpoints<br>  gateway_endpoints           = local.environment.gateway_endpoints<br>  subnet_ids                  = local.environment.subnet_ids<br>  route_table_ids             = local.environment.route_table_ids<br>}</pre><p><a href="https://github.com/andyscott1547/terraform-aws-vpc-endpoints/tree/main/examples/workspace_specific">terraform-aws-vpc-endpoints/examples/workspace_specific at main · andyscott1547/terraform-aws-vpc-endpoints</a></p><p>I hope you found this article useful, please clap 👏 and share.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb2abb1ca130" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Structuring Terraform Projects]]></title>
            <link>https://medium.com/@Andy-scott/structuring-terraform-projects-5e866468bb49?source=rss-f66cef87d2dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e866468bb49</guid>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[terraform-modules]]></category>
            <dc:creator><![CDATA[Andy Scott]]></dc:creator>
            <pubDate>Mon, 10 Oct 2022 15:20:42 GMT</pubDate>
            <atom:updated>2022-10-26T12:24:08.233Z</atom:updated>
            <content:encoded><![CDATA[<p>General guidance on how to structure a Git repository for a Terraform project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pCU2NVYpwdX4Jtk7" /></figure><p><strong>What is Terraform?</strong><br>HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle.</p><p><strong>How to structure a new project.<br></strong>I’ve had a lot of conversations and read a lot of blogs that push certain structures and state they are best practice. The truth is that Hashicorp provide some high level guidance and best practice is subjective in any domain.</p><p><a href="https://www.terraform.io/language/modules/develop/structure">Standard Module Structure | Terraform by HashiCorp</a></p><p>Hashicorp documentation is well written and easy to navigate, The link above gives a detailed view of a basic project and explains what the intent for each file is, so i wont cover these in this blog, Let’s go beyond the basic structure.</p><p>When writing a Terraform solution i follow a few principles that help give me consistent structure. This will help with readability of the code and how people can navigate the repository.</p><p><strong>Principles:<br>1. Pin Terraform and Provider versions.<br></strong>Conventions are that you pin the terraform and provider versions in either main.tf or providers.tf, if you migrated from an earlier version of terraform you may have a file created called versions.tf.</p><p>You can exactly or loosely pin provider versions. If you loosely pin you can commit the lock file to source control that will pin the providers.</p><p>You can exactly or loosely pin terraform versions. If you loosely pin you can use tfenv to manage multiple versions of terraform.</p><p><a href="https://www.terraform.io/language/expressions/version-constraints">Version Constraints - Configuration Language | Terraform by HashiCorp</a></p><p><strong>2. Use consistent naming.<br></strong>Use snake case for naming of files and resources. Resource names should identify the resource being created without duplicating the resource type.</p><p><strong>3. Declare variables.<br></strong>When declaring variables it is a good idea to define the type and description. Sometimes it is useful to set a sensible default value and also some validation on the contents of the variable.</p><p><a href="https://www.terraform.io/language/values/variables">Input Variables - Configuration Language | Terraform by HashiCorp</a></p><p><strong>4. Separate projects by lifecycle.<br></strong>Your Terraform project may vary in size, like the existing Mono vs Multi repository debate there is no strict definition of how you should break your projects up.</p><p>I like to think of the separate resources from what their life cycle will be. If you have a 3 tier web app using Amazon Elastic Container Service (ECS) and Amazon Relational Database Service (RDS), The Amazon Virtual Private Cloud (VPC) is less likely to change than the the database or the container orchestration layers. However the applications running in the ECS cluster will change more often, so in this scenario i would have 3 separate projects each in its own repository.<br> <strong><br>5. Use modules.<br></strong>The Terraform registry is rich with remote modules to use in your project. You may also decide to produce your own Terraform modules and host them in your SCM solution.</p><p>You can also use local modules within the solution, using local modules you can create reusable components and also use modules to break up larger solutions.</p><p>Modules should all be stored in the modules directory in the root of the solution.</p><p><strong>6. Include a comprehensive README.<br></strong>The README is a living document and lives closest to the code it documents, Including links to any external resources or examples you have used and details of how to use and deploy the solution, whether this is from a client machine or by a CICD pipeline.</p><p>Terraform-Docs is a useful tool for generating sections within the README.</p><p><a href="https://terraform-docs.io/">terraform-docs</a></p><p><strong>7. Use for_each over count.<br></strong>Count can be used for conditionally creating resources however for_each should be preferred for creating multiple resources. Using for_each will create a map where the created resources are accessed by a named index instead of a numbered index of a list that is unordered.</p><p><strong>8. Use remote state with locking.<br></strong>By default, Terraform stores state locally in a file named terraform.tfstate. When working with Terraform in a team, use of a local file makes Terraform usage complicated because each user must make sure they always have the latest state data before running Terraform and make sure that nobody else runs Terraform at the same time.</p><p>With <em>remote</em> state, Terraform writes the state data to a remote data store, which can then be shared between all members of a team. Terraform supports storing state in <a href="https://www.hashicorp.com/products/terraform/">Terraform Cloud</a>, <a href="https://www.consul.io/">HashiCorp Consul</a>, Amazon S3, Azure Blob Storage, Google Cloud Storage, Alibaba Cloud OSS, and more.</p><p>For fully-featured remote backends, Terraform can also use <a href="https://www.terraform.io/language/state/locking">state locking</a> to prevent concurrent runs of Terraform against the same state.</p><p><strong>9. Validate project with tools.<br></strong>To improve the speed and success of your deployments use tools early in the development cycle.</p><p>Terraform has built in tools to help:<br><em>terraform validate<br>terraform fmt — recursive<br>terraform plan</em></p><p>There are also useful external tools to help:<br><em>tflint — </em><a href="https://github.com/terraform-linters/tflint">https://github.com/terraform-linters/tflint</a><br><em>checkov — </em><a href="https://www.checkov.io/">https://www.checkov.io/</a><br><em>tfsec</em> — <a href="https://github.com/aquasecurity/tfsec">https://github.com/aquasecurity/tfsec</a><br><em>infracost — </em><a href="https://www.infracost.io/">https://www.infracost.io/</a><br><em>pre-commit</em> — <a href="https://pre-commit.com/">https://pre-commit.com/</a></p><p><strong>10. Plan for automation.<br></strong>Terraform is an IAC tool fundamental in the DevOps methodology, CICD is another key concept. When starting a new project have in mind that the solution will be deployed by automation and be deployed into multiple environments.</p><p>Give resources unique names, use variables, use terraform.workspace if using workspaces and also generate unique values.</p><p><strong>Example Template Repository.<br></strong>This is a Terraform template that can be used to start a new AWS project. This includes accelerators to all the principles listed above</p><p><a href="https://github.com/andyscott1547/terraform-template-project">GitHub - andyscott1547/terraform-template-project: This is a boilerplate template for a new terraform repository.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/276/1*SC9tcaZdt3-xPfTu8mV0JA.png" /></figure><p>I hope you found this article useful, please clap 👏 and share.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e866468bb49" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>