{"id":4615,"date":"2022-06-24T10:25:55","date_gmt":"2022-06-24T08:25:55","guid":{"rendered":"https:\/\/blog.besharp.it\/?p=4615"},"modified":"2023-03-31T13:03:50","modified_gmt":"2023-03-31T11:03:50","slug":"thats-why-you-need-a-landing-zone-even-if-you-dont-know-it-yet","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/thats-why-you-need-a-landing-zone-even-if-you-dont-know-it-yet\/","title":{"rendered":"That\u2019s why you need a Landing Zone (even if you don\u2019t know it yet!)"},"content":{"rendered":"\n

Welcome to our 3-article-series<\/strong> dedicated to the Landing Zone principle on AWS. In these blog posts, you’ll understand why you should consider it before starting any project. <\/p>\n\n\n\n

Today, we’ll go through the definition, the basic concepts, and the guidelines and best practices to implement it the perfect way in your AWS Cloud environment. Let’s start!<\/p>\n\n\n\n

Interest in the Cloud is growing exponentially. On the one hand, the number of Cloud-native startups is growing exponentially. On the other hand, more and more traditional companies are also approaching this technology with modernization in mind. No matter the Cloud adoption maturity level, the company size, or the industry, it is essential for any organization to fully understand how to move in a world that is revolutionizing the typical on-premise infrastructure practices.<\/p>\n\n\n\n

When approaching a Cloud Adoption path, any company – from tech startups starting from scratch in the Cloud to big enterprises that want to move their existing workloads or extend their data centers through a hybrid solution – needs as a first thing to define well-structured governance rules over all the aspects of the AWS environments<\/strong>. Anyway, due to time-to-market needs, new workload necessities, or imminent depletion of on-premise resources, it is common between companies to jump into the Cloud in a rush while postponing the setup of these areas.<\/p>\n\n\n\n

But there is nothing more permanent than things born as \u201ctemporary\u201d: that\u2019s why it is good practice to adopt a consistent approach before starting any project on the Cloud<\/strong> in order to avoid the need to batten down the hatches.<\/p>\n\n\n\n

The on-demand and agile nature of the Cloud allows DevOps to experiment fast and fail at an extremely low cost, but in order to achieve this safely, it is necessary to ensure the perfect balance between governance aspects and flexibility typical of Cloud environments<\/strong> to allow developers to experiment freely according to the Fail-Fast principle<\/strong>. <\/p>\n\n\n\n

What is a Landing Zone<\/h2>\n\n\n\n

Before setting up any server or public APIs on the Cloud, you should consider foundational aspects, including governance<\/strong>, compliance<\/strong>, cost-sharing<\/strong>, access management<\/strong>, networking<\/strong> configurations, and disaster recovery<\/strong>. Basically, this is the idea on which the Landing Zone concept is based. <\/p>\n\n\n\n

A Landing Zone is a common set of rules, best practices, configurations, objects, and appliances that define the configuration of the AWS environment<\/strong> within which corporate workloads can run consistently and well-governed.<\/p>\n\n\n\n

The Landing Zone pillars<\/strong> are:<\/p>\n\n\n\n