<?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 Julian Dm on Medium]]></title>
        <description><![CDATA[Stories by Julian Dm on Medium]]></description>
        <link>https://medium.com/@juliandm?source=rss-60192032e883------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wIuCQUdphZza9k_zvlV7og.jpeg</url>
            <title>Stories by Julian Dm on Medium</title>
            <link>https://medium.com/@juliandm?source=rss-60192032e883------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:40:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juliandm/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[How to set up an affordable email service with a little help from Jeff]]></title>
            <link>https://juliandm.medium.com/how-to-set-up-an-affordable-email-service-with-a-little-help-from-jeff-ccac8d95f386?source=rss-60192032e883------2</link>
            <guid isPermaLink="false">https://medium.com/p/ccac8d95f386</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[workmail]]></category>
            <dc:creator><![CDATA[Julian Dm]]></dc:creator>
            <pubDate>Fri, 07 May 2021 11:38:23 GMT</pubDate>
            <atom:updated>2021-05-11T09:33:14.785Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*PvAOFz79_hyNlPR17URlyQ.jpeg" /></figure><p>If you wish to add a custom email domain (yourname@example.com) to your microsoft 365 account you are greeted with a great example of cross-selling: it’s only possible if you registered your domain at godaddy.com...</p><p>As a somewhat happy Microsoft 365 user myself i probably would have taken that offer, hadn’t i already parked my domain (juliandemourgues.com) at AWS.</p><p>But here we are and for the sake of curiosity let’s try out an often overlooked service by Amazon: <a href="https://aws.amazon.com/de/workmail/">AWS Workmail</a></p><h4>What you’ll need</h4><ul><li><strong>Any Email client </strong>(Outlook in this example)</li><li><strong>A registered Domain and a registrar other than godaddy.com </strong>(ideally at AWS Route53 in this example, if you already registered your domain at godaddy it’s probably more feasible to use <a href="https://support.microsoft.com/en-us/office/get-a-personalized-email-address-in-microsoft-365-75416a58-b225-4c02-8c07-8979403b427b">microsoft</a>)</li><li><strong>An AWS account</strong></li></ul><h4><strong>Upside of this solution</strong></h4><ul><li>independence from<strong> email-client </strong>and <strong>registrar</strong></li><li>50GB email storage per email</li><li>a browser-based email client for minimalists</li></ul><h4>Downside of this solution:</h4><ul><li><strong>4$</strong> per custom email address per month (i.e. test@example.com). Although that’s a steal if you use this address daily..</li><li>the browser-based email client is very spartanic to put it lightly. (I still use outlook as a client for this reason)</li></ul><h3>Let’s get started</h3><p>So our goal is to setup a managed email environment on AWS without too much hassle and for basic day-to-day email communication. For that we’ll use the Service AWS Workmail — an advanced and more consumer-friendly version of Amazon SES.</p><blockquote>Why not using SES which is part of the free tier?</blockquote><p>SES is not fully managed. Yes it’s an email server but it won’t transmit incoming email to your email client out-of-the box. Instead you need at least one S3 bucket to store the emails and a lambda function to forward them.</p><blockquote><em>This is a justified programming expense if you are planning to handle thousands of emails in bulks, for example email campaigns or other automatised tasks, or if you just want incoming emails forwarded to you from your professional to private email address without any other features. </em><a href="https://aws.amazon.com/de/getting-started/hands-on/setup-email-receiving-pipeline/"><em>This option is basically for free if you already have a domain and a bit of programming know-how!</em></a><em>.</em></blockquote><p>For our purposes however it’s just about having a fancy (and more professional) email address.</p><p>And on top of that we might need some of the features that WorkMail provides, like calender functionality, a browser based email client (if you want to cut ties with Office 365) or just a simple group feature (if you want to assign multiple users to one address, i.e. support@example.com)</p><h3>Setting up the AWS Side</h3><p>Let’s go to:</p><p><a href="https://eu-west-1.console.aws.amazon.com/workmail/v2/home?region=eu-west-1#/create-organization">https://eu-west-1.console.aws.amazon.com/workmail/v2/home?region=eu-west-1#/create-organization</a></p><p><em>This is assuming you live in the EU. Amazon only provides 3 email servers: on the east coast (us-east-1), west coast (us-west-2) and in Ireland (eu-west-1).</em></p><p>Then, In AWS Workmail you need to create an organization which acts as a very lean IAM wrapper:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/1*tbyQfPiXJkeK18SblfCkdw.png" /></figure><p>Since i had my website (juliandemourgues.com) already running on Route53 i could just choose the first selection on top and most of the necessary entries got automatically added to the hosted zone in Route 53.</p><p>However i still had to manually add some entries into Route 53 myself and wait for the “Verified” status. You’ll find this information by navigating to &lt;your_organisation&gt; — Domains — &lt;your_custom_domain&gt;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5rWNFtLJE-jnw0Z4gTa1UA.png" /><figcaption>I cut out the security relevant data. There might be some more entries you need to add to your DNS Service (Route 53 here)</figcaption></figure><p>Copy and paste all required entries into the DNS provider until the Status shows “Verified”. If you are using Route53 you’ll find your hosted zone (in my example juliandemourgues.com) here: <a href="https://console.aws.amazon.com/route53/v2/hostedzones#">https://console.aws.amazon.com/route53/v2/hostedzones</a></p><h3>Setting up your client</h3><p>This one is easy once you find the right information buried somewhere in the AWS Docs.</p><p>There’s custom docs for setting up an outlook client that didn’t work for me (probably wrong version). That’s why i can recommend to go for the IMAP alternative from the start. This should work with any client. <a href="https://docs.aws.amazon.com/workmail/latest/userguide/using_IMAP.html">https://docs.aws.amazon.com/workmail/latest/userguide/using_IMAP.html</a></p><p>For Example with outlook, This process will be almost identical in all email clients (gmail, thunderbird, etc…):</p><p>add a new account and select “manual setup“ and then IMAP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/1*omc5ggeT7YoWFt_G2DHT7w.png" /></figure><p>Then just enter in- and outgoing server endpoints:</p><ul><li><strong>In</strong>: imap.mail.eu-west-1.awsapps.com:993 with SSL</li><li><strong>Out</strong>: smtp.mail.eu-west-1.awsapps.com:465 with SSL</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*YrjPsjMwCBHli9lJ4F_Mbw.png" /></figure><p>And there you go. You have a custom email address now.</p><p>If you found this helpful then consider giving a clap for the algorithm, if not write me at <a href="/service/mailto:hello@juliandemourgues.com">hello@juliandemourgues.com</a> and let’s look at it together.</p><p>Happy to help!</p><h4><strong>Sources</strong></h4><p><a href="https://aws.amazon.com/de/getting-started/hands-on/setup-email-receiving-pipeline/">https://aws.amazon.com/de/getting-started/hands-on/setup-email-receiving-pipeline/</a></p><p><a href="https://aws.amazon.com/de/workmail/">https://aws.amazon.com/de/workmail/</a></p><p><a href="https://console.aws.amazon.com/route53/v2/hostedzones#">https://console.aws.amazon.com/route53/v2/hostedzones</a></p><p><a href="https://docs.aws.amazon.com/workmail/latest/userguide/using_IMAP.html">https://docs.aws.amazon.com/workmail/latest/userguide/using_IMAP.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccac8d95f386" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IaC Solutions for AWS Cloud 2020: which one is the right for you?]]></title>
            <link>https://juliandm.medium.com/iac-solutions-for-aws-cloud-2020-which-one-is-the-right-for-you-365f8411b28b?source=rss-60192032e883------2</link>
            <guid isPermaLink="false">https://medium.com/p/365f8411b28b</guid>
            <category><![CDATA[aws-amplify]]></category>
            <category><![CDATA[aws-sam]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-cdk]]></category>
            <category><![CDATA[aws-cloudformation]]></category>
            <dc:creator><![CDATA[Julian Dm]]></dc:creator>
            <pubDate>Thu, 29 Oct 2020 09:27:34 GMT</pubDate>
            <atom:updated>2023-08-18T11:32:27.601Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*46ViCVo2vfy2YzlxDYY2EA.png" /><figcaption>A high level graphic of how the tools interact with AWS</figcaption></figure><p>I recently had the benefit of testing several tools to deploy Amazon Web Service(AWS) cloud infrastructure as code(IaC) in hands-on projects. Let me share my findings with you.</p><blockquote>Just as a reminder: This guide focuses on the market leader AWS since it has the biggest variety in IaC frameworks. If your company is confident that AWS will be tamed by competitors and won’t disproportionately increase its prices in the next decade then you may stay with me and read this guide. If you are however using Azure or Google cloud or a mixture of all providers, you might as well skip this article and start learning <a href="https://www.terraform.io/">terraform</a>.</blockquote><p>You probably know AWS’s user interface to interact with cloud services called AWS “console”. It is quiet useful to gain a visual representation of the service’s state, other static information and monitoring data.</p><p>On the other side manually manipulating the state of services (starting, stopping, updating) is also possible but gets time-consuming and unmanageable quickly for deployments of bigger applications.</p><p>Infrastructure as Code(IaC) or:</p><blockquote>“…a <strong>single text-based description </strong>of a <strong>complete cloud infrastructure </strong>at a given <strong>point in time</strong>”</blockquote><p>eliminates these problems by being versionable through a VCS like GIT and automatically deployable without human effort through a CI service such as CodePipeline. The open-source community brought up several solutions on how to manage IaC for your cloud resources:</p><p>Since this shouldn’t be a sales pitch for one or the other solutions let’s first start off with a <strong>neutral comparison</strong> to get some basic facts about each service. Compare the release dates and Github Stars to get a sense about the popularity and maturity of each option.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fairtable.com%2Fembed%2FshrODKIOD84vk94bK&amp;display_name=Airtable&amp;url=https%3A%2F%2Fairtable.com%2FshrODKIOD84vk94bK&amp;image=https%3A%2F%2Fstatic.airtable.com%2Fimages%2Foembed%2Fairtable.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=airtable" width="800" height="533" frameborder="0" scrolling="no"><a href="https://medium.com/media/a16da176bcbbaec7c4ce4937aeca2826/href">https://medium.com/media/a16da176bcbbaec7c4ce4937aeca2826/href</a></iframe><h3>AWS CloudFormation</h3><p>The initial go-to solution for IaC in Amazon Web Services is called CloudFormation. A declarative specification that describes your whole cloud infrastructure in one or several .yaml files. You can use so-called “Stacks” to modularise your infrastructure deployment and will find various boilerplate templates of these stacks for almost any service provided by AWS on their website. Nowadays however it is very rare to see a devops engineer writing a “raw” CloudFormation script by hand due to some drawbacks explained below.</p><p>Since an example cloudFormation file for a basic deployment was too long to paste here, let me provide you with a link to a <a href="https://github.com/jthomerson/cloudformation-template-for-lambda-backed-api-gateway-with-dynamodb/blob/master/cloudformation/complete-api.template">github repository with a good example</a></p><h4>Pros</h4><ul><li>Widely known YAML and JSON syntax is supported</li><li>The last frontier to the AWS API: all other IaC Wrappers by AWS are based on CloudFormation. Debugging your failed deployment might necessitate that you have a peak into a CloudFormation file once in a while so it doesn’t hurt to know it.</li></ul><h4>Cons</h4><ul><li>Many older CloudFormation samples are broken indicating that the AWS services and their dependencies have frequent breaking changes.</li><li>CloudFormation is only for AWS and not useful for multi-cloud deployments</li><li>Downside of configuration languages like YAML/JSON: Your only two tools here are defining and nesting statements. On the other side you have the whole AWS landscape with rich semantics and interconnections that you now have to “syntactically downsample” into YAML.</li><li>Templates get long very quickly: For connecting related resources you have to nest statements various layers deep which increases the file length and is quiet verbose.</li></ul><p>Unlike in programming languages where you have a clear distinction between language specific syntax and your own custom logic, CloudFormation-specific statements (i.e. “Parameters”, “Ref”) use the same syntax as attributes that act as definition for the respective services (i.e. “InstanceType” for an ec2 instance). That makes it very hard to distinguish patterns and find structure as a human reader.</p><h4>Recommendation:</h4><p>The core idea of CloudFormation is still very neat, however there are now multiple other solutions established in the open-source community and recognised by AWS that wrap away the complexity of cloudformation templates. Most importantly, using CloudFormation directly might entail security risks, simply because the complexity and repetitiveness of CloudFormation encourages human error. Therefore, it is a bold (and slightly sadistic) move to directly use CloudFormation in 2020 for managing your cloud infrastructure in code, except maybe for debugging. Consider using one of the following solutions instead</p><h3>AWS Amplify</h3><p>A Cli based framework to develop cloud-native Apps. Therefore rolling out cloud resources is just one of its many capabilities next to its main purpose of supporting the complete back to front development of a (mobile) app. The current definition of your infrastructure and locally adapted version is saved in a backend/ folder as Code and CloudFormation Files within your app repository. Similar to git it compares the two states once you hit the cli command “amplify push” and only deploys the changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NVxcnTR3IEbve7IPsXhsHQ.png" /><figcaption>An example workflow with Amplify to add a lambda function to an existing project. The CLI is a foolproof way to set up and connect services in the cloud.</figcaption></figure><h4>Pros</h4><ul><li>Great CLI, you can create, delete, update your backend resources by just by answering simple (Yes/No-) Questions. This makes it very user-friendly, even if you don’t know anything about CloudFormation.</li><li>Integration with AWS Cognito: you can easily create a user-pool, add authentication (with OAuth etc, check Cognito for more), and if you choose even the accompanying frontend with Login/Register/Reset Screens from the command line.</li><li>Powerful integration with DynamoDB + GraphQl API: theoretically you can define the majority of the two tiers (Api &amp; Database) in one shema.graphql File: Define the data types with a few directives and Tables, Api Endpoints and resolvers are generated for you. Also basic GraphQl queries/mutations/events are generated from the CLI that you can use in your frontend.</li><li>All created services in amplify can be “connected”. So if you want to for example deploy a lambda function that accesses your user-pool, you define it in the Cli which automatically adds permissions and creates an ENV Variable that you can use in your function.</li><li>Hands-on documentation</li></ul><h4>Cons</h4><ul><li>Some early hickups: For example, at the moment there is no automatic User type created within Amplify. It is necessary to create custom resolvers in order to not duplicate every user in cognito and in your DynamoDb storage. Since user handling is such a basic feature of every app development platform it comes as a bad surprise that this was not automatically integrated. But there is <a href="https://github.com/aws-amplify/amplify-cli/issues/1313">hope</a></li><li>CLI overrides your custom changes: This comes by design since amplify relies heavily on its CLI. If you choose to edit the cloudFormation template of one resource for a custom modification, per my understanding you can’t use the CLI for this resource afterwards since it will override your changes.</li><li>A general rule for IaC but can’t be repeated enough: Refrain from remote drift also here (for example deleting a lambda function manually through the console that was deployed through amplify) since this will break your “amplify push” command.</li></ul><p>In general, at this point in time, you better hope that you can figure out the reason for any of the cli commands to fail since otherwise you might only be left with wiping the project and start afresh. Let’s be hopeful that the error handling of the CLI will improve here.</p><h4>Recommendation</h4><p>If you are a small or even one person team, rapidly developing a (mobile) App based on (AWS-) cloud resources and don’t know a whole lot about DevOps, Amplify is a very safe bet. I personally found it quiet useful and use it now preferredly for my personal projects. However, I am not sure if using AWS Amplify is a good idea in a corporate environment since you are encouraged to use the CLI-first which in turn is not versionable/traceable except for changes in the cloudformation templates.</p><p>While using Amplify, it served me well to get familiar with the contents of the backend/ folder to really understand what’s going on under the hood. I would advise you the same.</p><h3>AWS SAM</h3><p>SAM was the first IaC Framework for AWS i stumbled upon and introduced me to the magical wonders of IaC (Before i was still clicking around in the console). It is an extension to CloudFormation in which Identifiers for policies and the 3 fundamental services <strong>Lambda, DynamoDB and API Gateway</strong> were redefined in a much more lean and simple way, therefore reducing the lines of code in your template file substantially and improving your mental health while editing them.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2c2c0ef56cb88640f1d769a024633420/href">https://medium.com/media/2c2c0ef56cb88640f1d769a024633420/href</a></iframe><h4>Pros</h4><ul><li>The connection of resources is simple without handling around with lots of nested layers. Some popular policy scopes are even predefined (i.e. <em>DynamoDBCrudPolicy</em>) reducing the permission handling of a resource to one line.</li><li>As in Amplify, endpoints are automatically injected as ENV-Variables into your lambda handlers, no messing around with endpoints in the config</li><li>“Low-level” CloudFormation from the start, so custom extensions with CloudFormation are possible</li></ul><h4>Cons</h4><ul><li>Again only useful for very basic applications and a need for CloudFormation once app grows</li></ul><h4>Recommendation</h4><p>I personally see the benefit of SAM as a compromise between Amplify and CloudFormation. There is practically no overhead for your development environment compared to a full-fledged App Framework like Amplify and at the same time it is structured way simpler than vanilla CloudFormation. If you are working on a basic 3-Tier Application and would only use Lambda, the API Gateway and a NoSQL database anyway you can confidently base your app on SAM. I also found it very easy to migrate the project from the REST-based API in SAM to a GraphQL-based API in Amplify by just copy-pasting the lambda handlers into the respective resolver functions for the graphQL API (if you ever need to).</p><h3>AWS CDK</h3><p>The AWS Cloud Development Kit (AWS CDK) is an open source software development framework to define your cloud application resources using familiar programming languages.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9ff18787d269dfae06733bf2bd9697bd/href">https://medium.com/media/9ff18787d269dfae06733bf2bd9697bd/href</a></iframe><h4>Pros</h4><ul><li>Can handle any complexity and customisation of setup and supports any resource in the AWS ecosphere from the start. It’s handy for large deployments with an imperative, flexible approach.</li><li>Comparably easier to grasp what’s going on since you can benefit from your programming language of choice, especially if you are from a programming background.</li><li>Some more benefits of coding: You can access code completion so you don’t need to skim through the documentation that often, You can structure the roll-out in logical parts with object orientation and finally leverage the community by copying handy code-snippets (stackoverflow is your friend).</li></ul><h4>Cons</h4><ul><li>For simple rollouts writing an app with logical structuring just to in turn roll-out a basic cloud infrastructure (i.e. two-tier app) seems a bit overkill.</li><li>Still evolving and likely to have huge breaking changes between major versions.</li></ul><h4>Recommendation</h4><p>AWS CDK is especially well-suited for teams from a programming background, projects with a need for highly customizable infrastructure that’s extending basic app development and fluctuating teams that need a human-friendly description of infrastructure for quick onboarding. Just as an example for the variety, there’s already an open-source extension of CDK for kubernetes “cdk8s” that can generate any kubernetes configuration .yaml files through a few lines of code. However, in my humble opininion, for simple app deployments(a.k.a “give me a database and Api”) this might be too much and you are better off with one of the above solutions (SAM and Amplify) and investing your time into developing the app first.</p><h3>Terraform</h3><p>Terraform is a tool for building, changing, and versioning infrastructure across popular service providers as well as custom in-house solutions.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1e3544a2381faca19486859aaf8cba35/href">https://medium.com/media/1e3544a2381faca19486859aaf8cba35/href</a></iframe><h4>Pros</h4><ul><li>Independent of AWS, so can be used for or with other cloud providers in multi-cloud deployments.</li><li>You could already call it a standard for multicloud deployments by now</li></ul><h4>Cons</h4><ul><li>Rather flat learning curve for practical usage (Rule of thumb: If there’s a certificate for it, you cannot just learn it over a weekend)</li><li>Terraform has to be adapted constantly since the API of AWS, Azure etc. also change. This may create a small delay in which your roll-outs might fail until terraform releases a next version.</li><li>In comparison to dedicated AWS Solutions no implicit code generation. For example, while fitting access policies are generated on-the-fly in Amplify and partly in SAM, here you have to explicitly type it out.</li></ul><h4>Recommendation</h4><p>The go-to solution for multi-cloud roll-outs or cloud providers apart from AWS. If you are already planning a project that might extend app development and will be based on multiple cloud providers, there is practically no alternative to terraform. You might not be too excited about learning another Syntax (HCL).. but who knows maybe you already used or will use other HashiCorp products in the future.</p><h3>TL/DR</h3><p>Of the mentioned services all have their individual pros &amp; cons and deliver value in different scenarios. Let’s take in mind especially in the IT-World there is no such thing as a “perfect framework/paradigm”: just good enough solutions that hit the sweet spot between abstracting repetitive or complex stuff that you don’t want to deal with while giving you enough flexibility to change the stuff that you care about.</p><p><strong>To wrap it up:</strong></p><ul><li>Use <a href="https://aws.amazon.com/de/cloudformation/"><strong>CloudFormation</strong> </a>with care and patience since it is quiet verbose and not exactly intuitive. Unless you are very sure about choosing this option better go for the other IaC Tools.</li><li>If you are developing a production ready, user-based app with authentication, user-pool, custom backend, user-based blob storage, noSQL Storage (among others) and have a small agile team, go for <a href="https://docs.amplify.aws/"><strong>AWS Amplify</strong></a>.</li><li>If you are quickly developing a simple app, for example for a research project, that needs just the very basics: Database, custom backend/functions and an Api, go for <a href="https://aws.amazon.com/de/serverless/sam/"><strong>AWS SAM</strong></a>.</li><li>If you have a complex deployment on AWS in sight that isn’t covered by the solutions above and want to benefit from the advantages of your favourite coding language, go for <a href="https://aws.amazon.com/de/cdk/"><strong>AWS CDK</strong></a>.</li><li>If you are not sure about AWS and want to deploy your infrastructure on multiple cloud providers, go for <a href="https://www.terraform.io/"><strong>Terraform</strong></a>.</li></ul><h3><strong>Sources</strong></h3><p>h<a href="https://docs.microsoft.com/en-us/azure/devops/learn/what-is-infrastructure-as-code">ttps://docs.microsoft.com/en-us/azure/devops/learn/what-is-infrastructure-as-code</a></p><p><a href="https://zach-gollwitzer.medium.com/imperative-vs-declarative-programming-procedural-functional-and-oop-b03a53ba745c">https://zach-gollwitzer.medium.com/imperative-vs-declarative-programming-procedural-functional-and-oop-b03a53ba745c</a></p><p><a href="https://www.bayesian.ninja/2019/11/aws-cloudformation-pros-and-cons.html">https://www.bayesian.ninja/2019/11/aws-cloudformation-pros-and-cons.html</a></p><p><a href="https://www.trustradius.com/products/terraform/reviews?qs=pros-and-cons">https://www.trustradius.com/products/terraform/reviews?qs=pros-and-cons</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=365f8411b28b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>