<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud on Teddy Ferdinand</title><link>https://tferdinand.net/en/tags/cloud/</link><description>Recent content in Cloud on Teddy Ferdinand</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 13 Oct 2020 20:18:22 +0000</lastBuildDate><atom:link href="https://tferdinand.net/en/tags/cloud/index.xml" rel="self" type="application/rss+xml"/><item><title>Accelerate the test of your lambda functions with Docker</title><link>https://tferdinand.net/en/accelerate-the-test-of-your-lambda-functions-with-docker/</link><pubDate>Mon, 27 Apr 2020 06:00:00 +0000</pubDate><guid>https://tferdinand.net/en/accelerate-the-test-of-your-lambda-functions-with-docker/</guid><description>&lt;p&gt;Lambda is a very powerful AWS tool. Executing scripts in serverless mode drastically reduces the cost and complexity of managing a scalable infrastructure, however, testing its functions directly on Lambda can sometimes be frustrating as it requires round trips between the development station and the AWS environment.&lt;/p&gt;
&lt;p&gt;There are testing features built into the AWS toolkit for the most popular editors (&lt;a href="https://aws.amazon.com/visualstudiocode/"&gt;for Microsoft Visual Studio Code&lt;/a&gt; / &lt;a href="https://aws.amazon.com/pycharm/"&gt;PyCharm&lt;/a&gt;, for example), however, this restricts the possible editors and creates an adherence that is not particularly desirable.&lt;/p&gt;</description></item><item><title>Is it really greener in the cloud?</title><link>https://tferdinand.net/en/is-it-really-greener-in-the-cloud/</link><pubDate>Mon, 10 Feb 2020 09:00:00 +0000</pubDate><guid>https://tferdinand.net/en/is-it-really-greener-in-the-cloud/</guid><description>&lt;p&gt;“It’s greener on AWS”, I can’t count the number of times I’ve heard this sentence at Amazon conferences.&lt;/p&gt;
&lt;p&gt;Is this mantra that companies repeat to look cool true?&lt;/p&gt;
&lt;h2 id="ecology-the-new-spearhead-of-companies"&gt;Ecology, the new spearhead of companies&lt;/h2&gt;
&lt;p&gt;Year after year, companies, and especially large groups, put forward their efforts always to be “greener”. Each company is, of course, more committed than its competitor. I wonder how we can still have problems related to pollution with so much commitment?&lt;/p&gt;</description></item><item><title>Understanding the success of the "Serverless" model</title><link>https://tferdinand.net/en/understanding-the-success-of-the-serverless-model/</link><pubDate>Thu, 19 Dec 2019 12:30:30 +0000</pubDate><guid>https://tferdinand.net/en/understanding-the-success-of-the-serverless-model/</guid><description>&lt;p&gt;Anyone who has ever done infrastructure on a cloud provider has already heard of the serverless model, behind this name is actually hiding many aspects. Let&amp;rsquo;s take a look&amp;hellip;&lt;/p&gt;
&lt;h2 id="the-serverless-model-logical-evolution-of-containers"&gt;The serverless model: logical evolution of containers?&lt;/h2&gt;
&lt;p&gt;For several years now, we have been talking about containers. A revolution over the last 5 years, containers (and orchestrators) have profoundly changed the approach to infrastructure, allowing applications composed of microservices to be deployed more and more simply and quickly. I won&amp;rsquo;t talk about this evolution here.&lt;/p&gt;</description></item><item><title>Terraform VS CloudFormation: Which tool to deploy on AWS?</title><link>https://tferdinand.net/en/terraform-vs-cloudformation-which-tool-to-deploy-on-aws/</link><pubDate>Fri, 13 Dec 2019 11:00:00 +0000</pubDate><guid>https://tferdinand.net/en/terraform-vs-cloudformation-which-tool-to-deploy-on-aws/</guid><description>&lt;p&gt;Terraform or CloudFormation, the two tools are often pitted against each other, asking DevOps to decide and choose one tool or the other. However, from my point of view, these two tools do not necessarily address the same needs.&lt;/p&gt;
&lt;h2 id="asking-the-question-of-ones-exact-need"&gt;Asking the question of one&amp;rsquo;s exact need&lt;/h2&gt;
&lt;p&gt;Before knowing which tool to go to, it is important to know the exact need to be addressed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Do I want to deploy only on AWS?&lt;/li&gt;
&lt;li&gt;Do I need to interface with existing tools (especially CI/CD)?&lt;/li&gt;
&lt;li&gt;Do I want to host the deployment solution myself or depend on a managed service?&lt;/li&gt;
&lt;li&gt;Do I already use other tools from the HashiCorp ecosystem (Nomad, Packer, Consul or Vault for example)?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Indeed, with these questions you can already target the tool you want to use more easily.&lt;/p&gt;</description></item><item><title>Migrate your infrastructure to AWS in an optimal way</title><link>https://tferdinand.net/en/migrate-your-infrastructure-to-aws-in-an-optimal-way/</link><pubDate>Fri, 12 Apr 2019 12:39:56 +0000</pubDate><guid>https://tferdinand.net/en/migrate-your-infrastructure-to-aws-in-an-optimal-way/</guid><description>&lt;p&gt;The Cloud appears to be an Eldorado for many companies: simpler application deployment, cost reduction, use of innovative technologies, so many advantages that Amazon promises to its potential customers, but is it that simple?&lt;/p&gt;
&lt;p&gt;AWS, and the cloud more generally, can be an excellent lever on the points mentioned above, however it is quite easy to lose feathers. In this article, I will list what, for me, seems to be the mistakes to avoid.&lt;/p&gt;</description></item><item><title>AWS Summit 2019 - Paris: Between success and disappointment</title><link>https://tferdinand.net/en/aws-summit-2019/</link><pubDate>Thu, 04 Apr 2019 18:27:27 +0000</pubDate><guid>https://tferdinand.net/en/aws-summit-2019/</guid><description>&lt;p&gt;I was at the AWS Summit in Paris a few days ago. For those of you who don&amp;rsquo;t know this event, it&amp;rsquo;s a full day of conferences around Amazon&amp;rsquo;s cloud, AWS. This meeting is quite interesting because it allows us to get feedback from a lot of companies coming from different backgrounds.&lt;/p&gt;
&lt;p&gt;I was going for the second time, the first time being in 2017. I was waiting for this day given the announced conference schedule.&lt;/p&gt;</description></item><item><title>What if we figured the cloud is just another data center like any other?</title><link>https://tferdinand.net/en/what-if-we-figured-the-cloud-is-just-another-data-center-like-any-other/</link><pubDate>Thu, 28 Feb 2019 19:54:58 +0000</pubDate><guid>https://tferdinand.net/en/what-if-we-figured-the-cloud-is-just-another-data-center-like-any-other/</guid><description>&lt;p&gt;I work daily on Amazon&amp;rsquo;s cloud infrastructure (AWS for short), and I&amp;rsquo;m thinking about the best way to implement new technical solutions on this platform.&lt;/p&gt;
&lt;p&gt;Amazon, and the cloud in general, has brought an impressive freedom:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Deploy on tailor-made infrastructures&lt;/li&gt;
&lt;li&gt;Bringing elasticity to infrastructures&lt;/li&gt;
&lt;li&gt;Benefits from machines on demand&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;However, these new approaches to infrastructure have also brought their share of negatives.&lt;/p&gt;
&lt;p&gt;Previously, to deploy an application in the data center, it was necessary to prepare and properly size its hosting before even starting any deployment, linked to the purchase of suitable hardware, or at least to a resource reservation that had to be amortized over several years.&lt;/p&gt;</description></item></channel></rss>