[{"data":1,"prerenderedAt":626},["ShallowReactive",2],{"nav-products":3,"articles-knowledge":10},[4],{"name":5,"tagline":6,"to":7,"isInternal":8,"icon":9},"Valdras Gate","no VPN licenses to manage","\u002Fproducts\u002Fgate\u002F",true,"\u002Fpublic\u002Fimg\u002Fproducts\u002Fgate\u002Fgate_logo.png",[11,179,266,377],{"id":12,"title":13,"author":14,"body":15,"category":166,"cover":167,"date":168,"description":169,"extension":170,"featured":171,"isFeatured":172,"meta":173,"navigation":8,"path":174,"preview":175,"seo":176,"stem":177,"__hash__":178},"articles\u002Farticles\u002Fknowledge\u002F2020-07-17-cloudformation-tips-and-tricks.md","CloudFormation Tips and Tricks","David Gatti",{"type":16,"value":17,"toc":155},"minimark",[18,26,31,34,45,53,56,60,63,66,69,72,76,79,83,86,89,92,103,106,109,113,116,119,122,125,129,132,135,138,145,148,152],[19,20,21,22],"p",{},"This article is meant for CEOs, CTOs, and Managers. The goal is to give a better understanding of what CloudFormation is and why it should be used for every AWS project, by answering a common question clients have: ",[23,24,25],"em",{},"What are the the most important things our team should be aware of when working on a CF file?",[27,28,30],"h2",{"id":29},"pick-a-framework","Pick a framework",[19,32,33],{},"Since a CloudFormation is nothing more then a JSON file, one might think that keeping everything in one big file is the right way to go. But it is not. After you have added multiple services, even as little as 3, then you will have to scroll across the file like crazy trying to edit it, and each new service exponentially extends the complexity of managing the file.",[19,35,36,37,44],{},"A good approach that I found helpful is to keep the JSON familiarity while braking down each service in a separated JSON file. Hence, I create a framework called ",[38,39,43],"a",{"href":40,"rel":41},"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@0x4447\u002Fgrapes",[42],"nofollow","Grapes",".",[19,46,47,48,52],{},"With the ",[38,49,51],{"href":40,"rel":50},[42],"Grapes framework",", you are free to structure the Resource folder however you want. You can nest folders and name your files in total freedom – whatever makes sense to your project.",[19,54,55],{},"The only imposed structure is the root folders. I have used Grapes since 2019 and I have been able to make and easily manage a massive stack, since everything remains neatly organized. Below you can find a handful of links to open source projects that I released using Grapes.",[27,57,59],{"id":58},"the-bare-minimum","The bare minimum",[19,61,62],{},"One of the few negatives about CloudFormation is the parameters part and how it is implemented in the AWS Console.",[19,64,65],{},"When you deploy a stack the first time with multiple parameters and there is an error, you'll loose everything you added. This is infuriating when you have a stack with 50 parameters, because if you have to redeploy a stack until it works, and let's say it takes 10 retries and you have 50 parameters, then that's equal to you having to do 500 copy and paste actions.",[19,67,68],{},"The only work around at this moment is to start small. Make the smallest stack that makes sense to you, deploy it successfully, and then the parameters will be saved. Afterwards you can incrementally add a service to the others.",[19,70,71],{},"This approach is also good to more quickly find issues within the CF file.",[27,73,75],{"id":74},"good-naming-and-description","Good naming and description",[19,77,78],{},"Since we are on the parameters topic, I highly recommend making sure all your parameters have simple, clear names that explain what to expect from them. You can add as many details of the description as you would like, even if the description is just a copy and paste of the input field. The purpose of this is to have a clear description with your default parameters in the description itself, which gives you a reference to the parameters. If you don't have a good description, then when you come back months after you made the stack and have to deploy it in another account, then you won't remember what parameters are needed for the stack.",[27,80,82],{"id":81},"do-not-rename-the-resources","Do not rename the resources",[19,84,85],{},"Each resource described in the CloudFormation file must have a unique name as the JSON object Key. I recommend that you name them carefully, ideally with a simple pattern, because once the stack is deploy it can cause a lot of drama to change the name of the resource. For example:",[19,87,88],{},"CloudFormation deploys changes by first making the new resource, and if all goes well, it deletes the old one. For example, if you have a S3 bucket that you want to rename (renaming the bucket not the service object Key), then AWS will make the new bucket first, and when all is successful, it will delete the old one if empty.",[19,90,91],{},"But if you were to rename the object Key, then AWS will see the changes as: \"I have to add a completely new service, while deleting the old one.\" But since AWS first makes resources and then deletes them, in this case you would get an error because AWS would try to make a S3 Bucket that already exists. Thus resulting in a update error.",[19,93,94,95,99,100,102],{},"Instead, the solution is to rename the resource while also renaming the S3 Bucket by adding at the end of the name, for example, ",[96,97,98],"code",{},"1",". Deploying that will be sufficient, since now the buckets have unique names. Then remove the ",[96,101,98],{}," from the name and update the stack again.",[19,104,105],{},"This trick won't work in some AWS resources and you might be stuck. Make sure your resource names are standardized, and always follow this standard, because once they are used it is going to be almost impossible to rename them.",[19,107,108],{},"CloudFormation is for people that like to be organized and keep everything neat. With this service, you can't just do something quick and later improve upon it; you have to have it right from the start - otherwise it is going to be difficult to work with later.",[27,110,112],{"id":111},"dont-refer-to-resource-outputs-in-another-aws-cloudformation-stack","Don't refer to Resource Outputs in Another AWS CloudFormation Stack",[19,114,115],{},"CloudFormation allows you to create a cross-stack reference that can be used in another stack. For example, one stack creates a S3 Bucket, and then you can reference the name of the Bucket in the 2nd stack.",[19,117,118],{},"At first this sounds like a cool and useful idea, but in practice it is the most dangerous feature out there for CF.",[19,120,121],{},"The problem is similar to the previous section. Because once a stack is referenced by other stack, the referenced one can't be modified because other stacks rely on it. Meaning if you have a daisy chain of 3 stacks and you wanted to edit the first one, you'd have to sequentially delete the whole stack before it, from right to left.",[19,123,124],{},"This feature is one that you should never use. The ideal approach when you want to reference a resource created in one stack with another, is to just output the resource name or ID in the original stack, copy it, and paste it in the params section of the second one. This way you still can split your stack and keep everything small and compact, while staying flexible and free to make any changes. Of course you have to remember that if you rename a S3 Bucket in the original stack, you then have to update all the CF files that uses the Bucket name.",[27,126,128],{"id":127},"dont-trust-a-working-cloudformation-file","Don't trust a working CloudFormation file.",[19,130,131],{},"If you have your work organized with 2 AWS accounts, one for production and one for development, then it doesn't necessarily mean that the CloudFormation file you created and tested in development will work in production.",[19,133,134],{},"When working on the CF file you add features as you go, slowly building it out. And by doing so, you build on top of pre-existing services that already exist from the previous deployment.",[19,136,137],{},"Deploying the stack from scratch in production will create all the services at once, and in some cases a service that relies on another one won't deploy because not everything is in place, which means that the stack will fail.",[19,139,140,141,144],{},"To mitigate this problem, I recommend that you delete the stack in development and then redeploy it from scratch. This approach will let you see what will fail, and then you will know how to set the ",[96,142,143],{},"DependsOn"," option to make sure the stack is deployed in the right order.",[19,146,147],{},"Only then can you be confident that deploying the stack in production will work.",[27,149,151],{"id":150},"to-sum-it-up","To sum it up",[19,153,154],{},"Move slowly, iterate piece by piece, and be organized - these are things to keep in mind when working with CloudFormation.",{"title":156,"searchDepth":157,"depth":157,"links":158},"",2,[159,160,161,162,163,164,165],{"id":29,"depth":157,"text":30},{"id":58,"depth":157,"text":59},{"id":74,"depth":157,"text":75},{"id":81,"depth":157,"text":82},{"id":111,"depth":157,"text":112},{"id":127,"depth":157,"text":128},{"id":150,"depth":157,"text":151},"knowledge","\u002Fpublic\u002Fimg\u002Farticles\u002Fcloudformation-tips-and-tricks\u002Fcover.jpg","2020-07-17","The goal is to give a better understanding of what CloudFormation is and why it should be used for every AWS project.","md","\u002Fpublic\u002Fimg\u002Farticles\u002Fcloudformation-tips-and-tricks\u002Ffeatured.jpg",false,{},"\u002Farticles\u002Fknowledge\u002F2020-07-17-cloudformation-tips-and-tricks","\u002Fpublic\u002Fimg\u002Farticles\u002Fcloudformation-tips-and-tricks\u002Fpreview.jpg",{"title":13,"description":169},"articles\u002Fknowledge\u002F2020-07-17-cloudformation-tips-and-tricks","lgev99u6Q5qfUW8ZJT9y8ExnfkveqYTn3Q383ld4yGM",{"id":180,"title":181,"author":14,"body":182,"category":166,"cover":257,"date":258,"description":169,"extension":170,"featured":259,"isFeatured":172,"meta":260,"navigation":8,"path":261,"preview":262,"seo":263,"stem":264,"__hash__":265},"articles\u002Farticles\u002Fknowledge\u002F2020-04-08-the-importance-of-cloudformation-files.md","The Importance of CloudFormation Files",{"type":16,"value":183,"toc":251},[184,189,193,196,199,202,206,209,212,230,234,237,240,243,246,248],[19,185,21,186],{},[23,187,188],{},"Why spend time making a CloudFormation file?",[27,190,192],{"id":191},"what-is-cloudformation","What is CloudFormation",[19,194,195],{},"A CloudFormation file is nothing more than a text file with the text formatted as JSON.",[19,197,198],{},"Within this JSON file, you are able to describe what type of resources you'd like AWS to create for you, as if you clicked them through the AWS Console.",[19,200,201],{},"Simple, right?",[27,203,205],{"id":204},"the-benefits-of-using-cloudformation","The Benefits of Using CloudFormation",[19,207,208],{},"Because everything is laid out as JSON format, when you upload this file, you get exactly what you've described.",[19,210,211],{},"This way...",[213,214,215,219,222],"ul",{},[216,217,218],"li",{},"it's much easier to update your configuration or service, because you just have to edit one value. You will also know the exact location, instead of losing yourself to an ever changing web UI and you end up wasting time looking for an option that's buried somewhere.",[216,220,221],{},"if the file is committed to GitHub, you can track and monitor the changes to the stack over time.",[216,223,224,225,229],{},"you can deploy the exact stack described in the JSON file to any AWS account. This is ideal when you have multiple environments, such as one AWS account for development and another for production (learn about ",[38,226,228],{"href":227},"\u002Farticles\u002Fknowledge\u002Fthe-benefits-of-aws-organizations.html","AWS Organizations"," here). What you test in one account, you can  then deploy in production within a few minutes and keep track of all your changes.",[27,231,233],{"id":232},"more-flexibility","More Flexibility",[19,235,236],{},"Another benefit that's hard to see in the beginning, is that as you become more comfortable with CloudFormation files you will start to like this way of working in the cloud.",[19,238,239],{},"After you've done one file (which takes some time at first), the next time you make a new project based on a similar cloud structure it will take just hours or a few days, instead of weeks or months.",[19,241,242],{},"You can just copy and past what you need from your completed file. The best thing is that once a file like this is created and tested, you know it works – now and in the future. And, even if AWS makes some changes, modifications to the file will be minor and easy to do.",[19,244,245],{},"It takes time and money to get the hang of it, but once you do you'll have a nice foundation to build upon and extend.",[27,247,151],{"id":150},[19,249,250],{},"I hope that you now understand the benefits of using CloudFormation files and that this AWS Service will help you streamline your DevOps work flow.",{"title":156,"searchDepth":157,"depth":157,"links":252},[253,254,255,256],{"id":191,"depth":157,"text":192},{"id":204,"depth":157,"text":205},{"id":232,"depth":157,"text":233},{"id":150,"depth":157,"text":151},"\u002Fpublic\u002Fimg\u002Farticles\u002Fthe-importance-of-cloudformation-files\u002Fcover.jpg","2020-04-08","\u002Fpublic\u002Fimg\u002Farticles\u002Fthe-importance-of-cloudformation-files\u002Ffeatured.jpg",{},"\u002Farticles\u002Fknowledge\u002F2020-04-08-the-importance-of-cloudformation-files","\u002Fpublic\u002Fimg\u002Farticles\u002Fthe-importance-of-cloudformation-files\u002Fpreview.jpg",{"title":181,"description":169},"articles\u002Fknowledge\u002F2020-04-08-the-importance-of-cloudformation-files","yIHmVUO1nALRiZfOvyJw2avVteQSICBiuBhZbj5NLcs",{"id":267,"title":268,"author":14,"body":269,"category":166,"cover":367,"date":368,"description":369,"extension":170,"featured":370,"isFeatured":172,"meta":371,"navigation":8,"path":372,"preview":373,"seo":374,"stem":375,"__hash__":376},"articles\u002Farticles\u002Fknowledge\u002F2020-03-28-should-i-go-all-in-with-serverless.md","Should I go all in with Serverless?",{"type":16,"value":270,"toc":358},[271,277,281,284,287,291,294,298,306,309,317,320,323,327,330,334,337,341,344,353,355],[19,272,273,274],{},"This article is meant for CEOs, CTOs, and managers who want to make a more educated decision about building products in the cloud. We will answer a common question clients have: ",[23,275,276],{},"Should I go serverless or build a project with regular servers?",[27,278,280],{"id":279},"first","First",[19,282,283],{},"There isn't a short answer to this question, because it all depends on the stage of your project. I always recommend that new clients start out serverless when in the initial phases of exploring an idea that may or may not work, meaning when you are not certain how much traffic the site is going to get. Then, once you begin to get some decent traffic, you are able to better predict how much load the solution will get, and thus transition some of the most expensive parts of the project to a regular server and lower the costs of running the solution. After your business is established, the final transition stage would likely be 90 percent use of servers with some serverless remaining for anything that isn't triggered often or when only used to manage DevOps daily tasks.",[19,285,286],{},"So the question becomes: Why this life cycle?",[27,288,290],{"id":289},"start-with-serverless","Start with serverless",[19,292,293],{},"One advantage of starting serverless is that is is not expensive at the outset of the project. It will cost you virtually nothing to run during development, regardless of how many resources you use. In the beginning phase as you are acquiring customers, all you pay for is traffic generated. If you have to pause the project for any reason, then you don't have to delete anything or worry about starting over, because you can preserve the entire set up and just pay for storage. Then, when all is back to normal, you can resume the project right where you left it.",[27,295,297],{"id":296},"move-to-managed-servers-to-lower-costs","Move to managed servers to lower costs",[19,299,300,301,305],{},"Serverless may be convenient in the beginning when you're testing the waters, but it's definitely not cheap in the long run. Once you see your idea is catching on and you're getting more and more traffic to your product, you should review your AWS bill on a monthly basis to identify the most expensive serverless resources. Use your list of the most expensive resources to begin converting to a custom server setup using EC2 Instances, but be sure that you understand the ",[38,302,304],{"href":303},"\u002Farticles\u002Fhow-to\u002Fhow-to-lower-ec2-costs.html","benefits of reserved instances"," in order to know that you are paying as little as possible for them.",[19,307,308],{},"A common misconception about using physical servers is that they requires dedicated people to monitor and react when something is not working as expected. Thankfully that way of thinking is old fashioned and doesn't take into account the current programmatic nature of AWS. Nowadays you can manage the whole infrastructure with code and automate many of the moving parts.",[19,310,311,312,316],{},"By using ",[38,313,315],{"href":314},"\u002Farticles\u002Fknowledge\u002Fthe-importance-of-cloudformation-files.html","CloudFormation"," and all the EC2 tools provided, you can create a server environment that acts like a serverless one. Operation is seamless and developers just have to push new code to a repository to make the stack automatically pull the changes and replace the old code, even without anyone having physical access to the servers.",[19,318,319],{},"Another important factor: a setup like this implies no need for physical access to the deployed servers, no SSH Keys, or Port 22 open, etc. Once set up correctly, everything should run smoothly. If AWS is able to operate your servers, then you should be able to as well, because serverless ends up being no more involved than a regular server set up in a organized and automated way. Serverless could be considered just a concept.",[19,321,322],{},"If you have migrated to EC2 Instances, then you can monitor the AWS bills and continue to transfer more and more resources until you find the price balance that's right for you.",[27,324,326],{"id":325},"volume-discount","Volume discount",[19,328,329],{},"With the right price balance in hand and your whole setup working correctly, you can take additional steps to lower your costs by contacting the AWS Pricing Team to see if they can give you a volume discount for some of the services you're using.",[27,331,333],{"id":332},"think-about-going-outside-aws","Think about going outside AWS",[19,335,336],{},"You can also look to see what's outside AWS. There are cloud providers out there that specialize in providing the cheapest price for specific AWS services. For example, Wasabi competes directly against S3. Their prices are truly much cheaper compared with what AWS has to offer, but you also have to consider that AWS has more regions available, more storage options for S3 to lower your prices, and more features - including triggers. This means that it all depends on your needs. But if what Wasabi offers is perfect for your solution, why not consider them?",[27,338,340],{"id":339},"go-custom-data-center","Go custom data center",[19,342,343],{},"And now, the last major step: a lot of online articles like to imply that AWS is too expensive and that having your our own data center is the cheapest way for you to serve a product to your clients. But this statement will only be true for a select few companies that have either outgrown the AWS volume discount, operate at a scale close to that of AWS, or only interact with a local market.",[19,345,346,347,352],{},"A good example would be ",[38,348,351],{"href":349,"rel":350},"https:\u002F\u002Fwww.businessinsider.com\u002Fbank-of-americas-350-million-internal-cloud-bet-striking-payoff-2019-10",[42],"Bank of America",", which transitioned to their own data center to lower costs. For a company of this size that deals only with the local market, this makes perfect sense and is the right move.",[27,354,151],{"id":150},[19,356,357],{},"I hope this explanation will help you organize your thoughts around the serverless approach and you'll know exactly how to discuss this with your team or contractors.",{"title":156,"searchDepth":157,"depth":157,"links":359},[360,361,362,363,364,365,366],{"id":279,"depth":157,"text":280},{"id":289,"depth":157,"text":290},{"id":296,"depth":157,"text":297},{"id":325,"depth":157,"text":326},{"id":332,"depth":157,"text":333},{"id":339,"depth":157,"text":340},{"id":150,"depth":157,"text":151},"\u002Fpublic\u002Fimg\u002Farticles\u002Fshould-i-go-all-in-with-serverless\u002Fcover.jpg","2020-03-28","The goal is to better understand Serverless technology and how it affects your costs as your project grows.","\u002Fpublic\u002Fimg\u002Farticles\u002Fshould-i-go-all-in-with-serverless\u002Ffeatured.jpg",{},"\u002Farticles\u002Fknowledge\u002F2020-03-28-should-i-go-all-in-with-serverless","\u002Fpublic\u002Fimg\u002Farticles\u002Fshould-i-go-all-in-with-serverless\u002Fpreview.jpg",{"title":268,"description":369},"articles\u002Fknowledge\u002F2020-03-28-should-i-go-all-in-with-serverless","Vo830ojtEdqHVcdTyvixIxi54cbitnOkxQb7R811bpE",{"id":378,"title":379,"author":14,"body":380,"category":166,"cover":616,"date":617,"description":618,"extension":170,"featured":619,"isFeatured":172,"meta":620,"navigation":8,"path":621,"preview":622,"seo":623,"stem":624,"__hash__":625},"articles\u002Farticles\u002Fknowledge\u002F2020-03-15-the-benefits-of-aws-organizations.md","The benefits of AWS organizations",{"type":16,"value":381,"toc":606},[382,388,392,395,412,415,419,436,440,443,460,464,467,491,499,502,506,509,512,515,519,533,537,540,601,603],[19,383,384,385],{},"This article is meant for CEOs, CTOs, and managers who want to understand the benefits of managing AWS infrastructure using Organizations. We will answer a common question clients have: ",[23,386,387],{},"Why spend the time setting up AWS Organizations?",[27,389,391],{"id":390},"why-i-wrote-this-article","Why I wrote this article",[19,393,394],{},"I have worked with countless clients on recurring issues that leave them feeling trapped and struggling how to:",[213,396,397,400,403,406,409],{},[216,398,399],{},"building new features",[216,401,402],{},"understanding where they are",[216,404,405],{},"figuring out whether their infrastructure is secure",[216,407,408],{},"running a stable product",[216,410,411],{},"Understand their costs",[19,413,414],{},"I am confident that this article will help you understand how important is to use AWS at the outset so that you start off organized and thus avoid the extra time and costs involved in having to later reorganize.",[27,416,418],{"id":417},"key-features-of-aws-organizations","Key features of AWS Organizations",[213,420,421,424,427,430,433],{},[216,422,423],{},"You have one bill to pay for all of your AWS accounts within Organizations.",[216,425,426],{},"You get a detailed breakdown of your bill per AWS account, which helps showcase where your money goes.",[216,428,429],{},"You can control access to AWS resources for each individual AWS account from the main Organizations account.",[216,431,432],{},"You can apply policies from the Organizations account down to all the sub-accounts.",[216,434,435],{},"You can organize the sub-accounts in Organization Unit (OU) to help you further organize the company in AWS and improve security.",[27,437,439],{"id":438},"the-benefits","The benefits",[19,441,442],{},"It's much easier to:",[213,444,445,448,451,454,457],{},[216,446,447],{},"Do audits",[216,449,450],{},"Set the right policies and access resources",[216,452,453],{},"Create test environments",[216,455,456],{},"Understand what each AWS account has for newcomers",[216,458,459],{},"Lower costs by exposing hidden costs",[27,461,463],{"id":462},"the-bare-minimum-setup","The bare-minimum setup",[19,465,466],{},"I always recommend this setup to my clients:",[213,468,469,477,484],{},[216,470,471,472,476],{},"In ",[473,474,475],"strong",{},"Development"," you test and work on the project. Here you have the most freedom to use different resources.",[216,478,479,480,483],{},"The ",[473,481,482],{},"Demo"," account is where you can showcase the latest features that are ready to go into production. This is your last chance to see if you like what's been done. It can also be used to perform demos for clients.",[216,485,486,487,490],{},"On the other hand, ",[473,488,489],{},"Production"," is for your customers with live data.",[19,492,479,493,495,496,498],{},[473,494,482],{}," and ",[473,497,489],{}," environments are locked down to the point that no one but the main admin has access to them.",[19,500,501],{},"All accounts have 100 percent automatic deployment and do not have access to the servers over SSH or other means – no exceptions.",[27,503,505],{"id":504},"a-word-of-caution","A word of caution",[19,507,508],{},"Having said all this, here's an example of what will happen if you start the wrong way, based on interacting with clients over the years.",[19,510,511],{},"Depending on project size, creating a CloudFormation from scratch takes an average of one month, and then it takes two more weeks to create all the AWS accounts to deploy the stack using the created CloudFormation files. This is the stage where all the final testing and final tuning happens.",[19,513,514],{},"Lastly, you'll start running your code in the new environment with a new work flow. A lot of the project's bugs will surface at this stage, because up to this point no one could log into the servers to perform ad hoc changes (also known as massaging the code). Now all the work a developer told himself he'd copy later in the repository shows up at this stage. How long will it take to fix everything? It depends on the project. From my experience, it takes a team of developers three months to normalize everything and adapt to the more organized environment.",[27,516,518],{"id":517},"what-else-should-i-know","What else should I know?",[213,520,521,524,527,530],{},[216,522,523],{},"You're limited to five nested OU, so design your infrastructure accordingly.",[216,525,526],{},"You can use CloudFormation to describe your organization.",[216,528,529],{},"You can programmatically request a limit increase.",[216,531,532],{},"Converting the main account to an Organization won't make any changes to what you already have in the account.",[27,534,536],{"id":535},"an-example-of-a-more-complex-organization","An example of a more complex Organization",[19,538,539],{},"This is an example for once you get your project off the ground. You could extend your Organization this way later on:",[213,541,542,556,567,581,598],{},[216,543,544,545],{},"Application (OU):\n",[213,546,547,550,553],{},[216,548,549],{},"Development - (AWS Account)",[216,551,552],{},"Demo - (AWS Account)",[216,554,555],{},"Production - (AWS Account)",[216,557,558,559],{},"Information security (OU):\n",[213,560,561,564],{},[216,562,563],{},"Log Collection - (AWS Account)",[216,565,566],{},"Auditing - (AWS Account)",[216,568,569,570],{},"Infrastructure (OU):\n",[213,571,572,575,578],{},[216,573,574],{},"DNS - (AWS Account)",[216,576,577],{},"Build Tools - (AWS Account)",[216,579,580],{},"Repos - (AWS Account)",[216,582,583,584],{},"Office (OU):\n",[213,585,586,589,592,595],{},[216,587,588],{},"Work Mail - (AWS Account)",[216,590,591],{},"VPN - (AWS Account)",[216,593,594],{},"NAS - (AWS Account)",[216,596,597],{},"AppStream - (AWS Account)",[216,599,600],{},"Etc.",[27,602,151],{"id":150},[19,604,605],{},"I hope this explanation helps you organize your thoughts around AWS Organizations so that you can know exactly what to ask for when talking to contractors or your team.",{"title":156,"searchDepth":157,"depth":157,"links":607},[608,609,610,611,612,613,614,615],{"id":390,"depth":157,"text":391},{"id":417,"depth":157,"text":418},{"id":438,"depth":157,"text":439},{"id":462,"depth":157,"text":463},{"id":504,"depth":157,"text":505},{"id":517,"depth":157,"text":518},{"id":535,"depth":157,"text":536},{"id":150,"depth":157,"text":151},"\u002Fpublic\u002Fimg\u002Farticles\u002Fthe-benefits-of-aws-organizations\u002Fcover.jpg","2020-03-15","The benefits of managing your AWS infrastructure using Organizations.","\u002Fpublic\u002Fimg\u002Farticles\u002Fthe-benefits-of-aws-organizations\u002Ffeatured.jpg",{},"\u002Farticles\u002Fknowledge\u002F2020-03-15-the-benefits-of-aws-organizations","\u002Fpublic\u002Fimg\u002Farticles\u002Fthe-benefits-of-aws-organizations\u002Fpreview.jpg",{"title":379,"description":618},"articles\u002Fknowledge\u002F2020-03-15-the-benefits-of-aws-organizations","Xyk0CwxQXhaifjerGV2IolmBjepS0fZ2XHHT78viI1I",1783756520364]