{"id":642,"date":"2019-05-03T15:07:39","date_gmt":"2019-05-03T13:07:39","guid":{"rendered":"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/"},"modified":"2021-03-29T17:13:54","modified_gmt":"2021-03-29T15:13:54","slug":"aws-cloudformation-the-top-5-reasons-for-not-using-it","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/","title":{"rendered":"AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it"},"content":{"rendered":"<h2>How to survive the most common pitfalls and take advantage of this service, without too many headaches.<\/h2>\n<section class=\"section section--body section--first\">\n<div class=\"section-content\">\n<div class=\"section-inner sectionLayout--insetColumn\">\n<p id=\"7d87\" class=\"graf graf--p graf-after--figure\">Who hasn\u2019t had problems with\u00a0<strong class=\"markup--strong markup--p-strong\">AWS CloudFormation?<\/strong><\/p>\n<p id=\"8ef2\" class=\"graf graf--p graf-after--p\">Sadly, it is commonly known that AWS CloudFormation is as powerful of a tool as it is frustrating; this short article will highlight the most common pitfalls and the most annoying situations, as well as, obviously,\u00a0<strong class=\"markup--strong markup--p-strong\">ways to avoid them.<\/strong><\/p>\n<p id=\"8ed7\" class=\"graf graf--p graf-after--p\">We begin our journey by\u00a0<strong class=\"markup--strong markup--p-strong\">describing the service:<\/strong><\/p>\n<blockquote id=\"b45e\" class=\"graf graf--blockquote graf--startsWithDoubleQuote graf-after--p\"><p>\u201cAWS CloudFormation provides you with a common language for describing and provisioning all infrastructure resources in your cloud environment. With CloudFormation you can use a simple text file to model and implement provisioning, in an automated and secure manner, of all resources needed for your applications on all regions and all accounts. Such file will be the only source of your cloud environment.<\/p><\/blockquote>\n<blockquote id=\"a81c\" class=\"graf graf--blockquote graf-after--blockquote\"><p>CloudFormation is available at no additional cost; you are only charged the cost of AWS resources needed to run the applications.\u201d<\/p><\/blockquote>\n<p id=\"3f27\" class=\"graf graf--p graf-after--blockquote\">One of the main advantages of using AWS CloudFormation is precisely to have\u00a0<strong class=\"markup--strong markup--p-strong\">a template of your own infrastructure, which can be versioned, revised, and easily replicated<\/strong>\u00a0as often as necessary.<\/p>\n<p id=\"a430\" class=\"graf graf--p graf-after--p graf--trailing\">There are problems, however, right from the description of the service.<\/p>\n<\/div>\n<\/div>\n<\/section>\n<section class=\"section section--body\">\n<div class=\"section-divider\"><\/div>\n<div class=\"section-content\">\n<div class=\"section-inner sectionLayout--insetColumn\">\n<h3 id=\"8185\" class=\"graf graf--h3 graf--leading\">#1 An (in)complete modeling<\/h3>\n<p id=\"a28f\" class=\"graf graf--p graf-after--h3\">Although the AWS service presentation page explicitly states that AWS CloudFormation offers complete cloud infrastructure modeling, this, in fact, does not happen.<\/p>\n<p id=\"9f71\" class=\"graf graf--p graf-after--p\">At least, not always; in fact,\u00a0<strong class=\"markup--strong markup--p-strong\">there are many configurations and\/or resources that cannot be specified in an AWS CloudFormation template.<\/strong><\/p>\n<p id=\"eeb4\" class=\"graf graf--p graf-after--p\">To date, for example, it is not possible to:<\/p>\n<ul class=\"postList\">\n<li id=\"7d99\" class=\"graf graf--li graf-after--p\">Define the settings related to Cognito UserPool for federation with an external IDP<\/li>\n<li id=\"6743\" class=\"graf graf--li graf-after--li\">Add a route to a routing table that points to a Transit Gateway<\/li>\n<li id=\"4911\" class=\"graf graf--li graf-after--li\">Implement SSH key provisioning for EC2 (probably for security reasons)<\/li>\n<\/ul>\n<p id=\"5e67\" class=\"graf graf--p graf-after--li\"><strong class=\"markup--strong markup--p-strong\">Our advice is<\/strong>\u00a0to make sure that all the necessary services and configurations can be truly modeled with the current version.<\/p>\n<p id=\"3691\" class=\"graf graf--p graf-after--p\">Almost all services are supported, although for some it is necessary to wait a considerable amount of time between the release and official support of AWS CloudFormation.<\/p>\n<p id=\"8017\" class=\"graf graf--p graf-after--p\">There is also a way to\u00a0<strong class=\"markup--strong markup--p-strong\">extend the capabilities of AWS CloudFormation<\/strong>using custom resources. In fact, they allow the deployment of a Lambda function and execute it as a \u201cCustom Resource\u201d at a given time during the creation of the stack.<\/p>\n<p id=\"5f92\" class=\"graf graf--p graf-after--p graf--trailing\"><a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/docs.aws.amazon.com\/AWSCloudFormation\/latest\/UserGuide\/template-custom-resources.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/docs.aws.amazon.com\/AWSCloudFormation\/latest\/UserGuide\/template-custom-resources.html\">Here is the official documentation of this feature.<\/a><\/p>\n<\/div>\n<\/div>\n<\/section>\n<section class=\"section section--body\">\n<div class=\"section-divider\"><\/div>\n<div class=\"section-content\">\n<div class=\"section-inner sectionLayout--insetColumn\">\n<h3 id=\"a556\" class=\"graf graf--h3 graf--leading\">#2 Waiting time<\/h3>\n<p id=\"b745\" class=\"graf graf--p graf-after--h3\">If it is true that once the template is packaged, the execution is faster than the manual one, the template production process is a long process based on trial and error.<\/p>\n<p id=\"0396\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\">It is not possible to 100% check a template locally,<\/strong>\u00a0it is only possible to be certain of syntactic correctness without first executing it.<\/p>\n<p id=\"0a48\" class=\"graf graf--p graf-after--p\">Which means that prior to arriving at a working version, you have to go through numerous attempts, each having long execution times.<\/p>\n<p id=\"f71d\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\">To make life easier we can count on the following features:<\/strong><\/p>\n<p id=\"96ef\" class=\"graf graf--p graf-after--p\">The first is the\u00a0<a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/docs.aws.amazon.com\/AWSCloudFormation\/latest\/APIReference\/API_ValidateTemplate.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/docs.aws.amazon.com\/AWSCloudFormation\/latest\/APIReference\/API_ValidateTemplate.html\">ValidateTemplate<\/a>\u00a0API which does a much more thorough check than just a linter.<\/p>\n<p id=\"9158\" class=\"graf graf--p graf-after--p\">Another way is the extensive use of\u00a0<a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/docs.aws.amazon.com\/AWSCloudFormation\/latest\/APIReference\/API_CreateChangeSet.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/docs.aws.amazon.com\/AWSCloudFormation\/latest\/APIReference\/API_CreateChangeSet.html\">changesets<\/a>, which allow you to have a preview of the actions that will result in changes to a template.<\/p>\n<p id=\"e75b\" class=\"graf graf--p graf-after--p graf--trailing\">It is also advisable to\u00a0<strong class=\"markup--strong markup--p-strong\">proceed by making small and rapid changes: f<\/strong>irst, it is best to create all the resources that require a low provisioning time, then, only at the end, add the most time-consuming resources to the stack, such as EC2 instances, RDS and the like. This will allow all resources\u2019 waiting and validation times that are probably required by provisioning services to be shorter.<\/p>\n<\/div>\n<\/div>\n<\/section>\n<section class=\"section section--body\">\n<div class=\"section-divider\"><\/div>\n<div class=\"section-content\">\n<div class=\"section-inner sectionLayout--insetColumn\">\n<h3 id=\"8a58\" class=\"graf graf--h3 graf--leading\">#3 Unintelligible errors<\/h3>\n<p id=\"9597\" class=\"graf graf--p graf-after--h3\">Error messages are often meaningless, misleading, useless, or simply wrong.<\/p>\n<p id=\"15fc\" class=\"graf graf--p graf-after--p\">One can only be certain that the stack has failed.\u00a0<strong class=\"markup--strong markup--p-strong\">What has actually failed and why is as useful to know as it is difficult to find out.<\/strong><\/p>\n<p id=\"99e9\" class=\"graf graf--p graf-after--p graf--trailing\">The only way to quickly find the reason for failure is to\u00a0<strong class=\"markup--strong markup--p-strong\">analyze the execution log<\/strong>\u00a0to see exactly on which resource an error is found, and when the provisioning for that resource occurred.<\/p>\n<\/div>\n<\/div>\n<\/section>\n<section class=\"section section--body\">\n<div class=\"section-divider\"><\/div>\n<div class=\"section-content\">\n<div class=\"section-inner sectionLayout--insetColumn\">\n<h3 id=\"f9b0\" class=\"graf graf--h3 graf--leading\">#4 Cloudformation drift detection<\/h3>\n<p id=\"c672\" class=\"graf graf--p graf-after--h3\">AWS CloudFormation\u2019s drift detection was loudly requested by many users, and consists of the ability to\u00a0<strong class=\"markup--strong markup--p-strong\">automatically detect if changes were made to the configuration of the stack resources outside CloudFormation<\/strong>\u00a0via the AWS management console, the CLI and the SDK<\/p>\n<p id=\"ff56\" class=\"graf graf--p graf-after--p\">This is a very useful feature, unfortunately, in practice, it gives many false positives. In general, it indicates that it is likely that something has been modified externally and, therefore, that the stack can no longer be updated automatically.\u00a0<strong class=\"markup--strong markup--p-strong\">Unfortunately, it does not indicate that the stack is not actually editable.<\/strong><\/p>\n<p id=\"66af\" class=\"graf graf--p graf-after--p graf--trailing\">It is best not to consider it as a reliable indication, at least for now.<\/p>\n<\/div>\n<\/div>\n<\/section>\n<section class=\"section section--body\">\n<div class=\"section-divider\"><\/div>\n<div class=\"section-content\">\n<div class=\"section-inner sectionLayout--insetColumn\">\n<h3 id=\"4fd6\" class=\"graf graf--h3 graf--leading\">#5 Hard limit to 200 resources per stack<\/h3>\n<p id=\"16be\" class=\"graf graf--p graf-after--h3\">It is not possible to create more than 200 resources in a single stack.<\/p>\n<p id=\"a026\" class=\"graf graf--p graf-after--p\">Many argue that this is not a problem at all and that it is easily circumvented with common sense. After all, why should you create more than 200 things at a time?<\/p>\n<p id=\"9b38\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\">The problem lies in what is defined as a \u201cresource\u201d;<\/strong>\u00a0in fact, there are many objects that are normally invisible while creating resources from the web console. When creating a simple infrastructure with a dozen lambdas, an API Gateway with relative policies, and some additional resources,\u00a0<strong class=\"markup--strong markup--p-strong\">the hard limit can be easily reached.<\/strong><\/p>\n<p id=\"4a80\" class=\"graf graf--p graf-after--p graf--trailing\"><strong class=\"markup--strong markup--p-strong\">The microservices should be small, and a complex application should, therefore, consist of multiple CloudFormation stacks\u2026<\/strong>\u00a0however, even having many stacks becomes burdensome from an organizational and management point of view, thus\u00a0<strong class=\"markup--strong markup--p-strong\">it is better to measure the amount of resources to be included in a single template<\/strong>\u00a0well, and to develop a strategy to partition a complex architecture.<\/p>\n<\/div>\n<\/div>\n<\/section>\n<section class=\"section section--body section--last\">\n<div class=\"section-divider\"><\/div>\n<div class=\"section-content\">\n<div class=\"section-inner sectionLayout--insetColumn\">\n<p id=\"f080\" class=\"graf graf--p graf--leading\">These are <strong class=\"markup--strong markup--p-strong\">the \u2018top 5\u2019 reasons<\/strong>\u00a0for not using AWS Cloudformation. Well, at least these are five reasons not to use it regardless of the belief that it can solve everything without creating headaches.<\/p>\n<p id=\"e062\" class=\"graf graf--p graf-after--p\">In conclusion, AWS CloudFormation is powerful but insidious, better to plan ahead when starting a new project in order to avoid the most common mistakes.<\/p>\n<p id=\"fa34\" class=\"graf graf--p graf-after--p graf--trailing\"><a href=\"https:\/\/www.besharp.it\/en\/contact-us\/\"><strong class=\"markup--strong markup--p-strong\">Tell us your experience,<\/strong><\/a>\u00a0comment with the most insidious error you have detected. The best stories will be featured in a forthcoming article on AWS CloudFormation pitfalls.<\/p>\n<\/div>\n<\/div>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>How to survive the most common pitfalls and take advantage of this service, without too many headaches. Who hasn\u2019t had [&hellip;]<\/p>\n","protected":false},"author":8,"featured_media":644,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[242],"tags":[276],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v21.9.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it - Proud2beCloud Blog<\/title>\n<meta name=\"description\" content=\"AWS CloudFormation: How to survive the most common pitfalls and take advantage of this service, without too many headaches.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it\" \/>\n<meta property=\"og:description\" content=\"How to survive the most common pitfalls and take advantage of this service, without too many headaches.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/\" \/>\n<meta property=\"og:site_name\" content=\"Proud2beCloud Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-05-03T13:07:39+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-03-29T15:13:54+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2019\/05\/cloufront-blog_Tavola-disegno-1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1667\" \/>\n\t<meta property=\"og:image:height\" content=\"1250\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Alessio Gandini\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it\" \/>\n<meta name=\"twitter:description\" content=\"How to survive the most common pitfalls and take advantage of this service, without too many headaches.\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2019\/05\/cloufront-blog_Tavola-disegno-1.png\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Alessio Gandini\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/\",\"url\":\"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/\",\"name\":\"AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it - Proud2beCloud Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.besharp.it\/#website\"},\"datePublished\":\"2019-05-03T13:07:39+00:00\",\"dateModified\":\"2021-03-29T15:13:54+00:00\",\"author\":{\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/e7262d28e51528c2e420327f9b18cd43\"},\"description\":\"AWS CloudFormation: How to survive the most common pitfalls and take advantage of this service, without too many headaches.\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.besharp.it\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.besharp.it\/#website\",\"url\":\"https:\/\/blog.besharp.it\/\",\"name\":\"Proud2beCloud Blog\",\"description\":\"il blog di beSharp\",\"alternateName\":\"Proud2beCloud Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.besharp.it\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/e7262d28e51528c2e420327f9b18cd43\",\"name\":\"Alessio Gandini\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/eeb98518768d999bff24f8358b464fe2?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/eeb98518768d999bff24f8358b464fe2?s=96&d=mm&r=g\",\"caption\":\"Alessio Gandini\"},\"description\":\"Cloud-native Development Line Manager @ beSharp, DevOps Engineer e AWS expert. Computer geek da quando avevo 6 anni, appassionato di informatica ed elettronica a tutto tondo. Ultimamente sto esplorando l'esperienza utente vocale e il mondo dell'IoT. Appassionato di cinema e grande consumatore di serie TV, videogiocatore della domenica.\",\"url\":\"https:\/\/blog.besharp.it\/author\/alessio-gandini\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it - Proud2beCloud Blog","description":"AWS CloudFormation: How to survive the most common pitfalls and take advantage of this service, without too many headaches.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/","og_locale":"en_US","og_type":"article","og_title":"AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it","og_description":"How to survive the most common pitfalls and take advantage of this service, without too many headaches.","og_url":"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/","og_site_name":"Proud2beCloud Blog","article_published_time":"2019-05-03T13:07:39+00:00","article_modified_time":"2021-03-29T15:13:54+00:00","og_image":[{"width":1667,"height":1250,"url":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2019\/05\/cloufront-blog_Tavola-disegno-1.png","type":"image\/png"}],"author":"Alessio Gandini","twitter_card":"summary_large_image","twitter_title":"AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it","twitter_description":"How to survive the most common pitfalls and take advantage of this service, without too many headaches.","twitter_image":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2019\/05\/cloufront-blog_Tavola-disegno-1.png","twitter_misc":{"Written by":"Alessio Gandini","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/","url":"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/","name":"AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it - Proud2beCloud Blog","isPartOf":{"@id":"https:\/\/blog.besharp.it\/#website"},"datePublished":"2019-05-03T13:07:39+00:00","dateModified":"2021-03-29T15:13:54+00:00","author":{"@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/e7262d28e51528c2e420327f9b18cd43"},"description":"AWS CloudFormation: How to survive the most common pitfalls and take advantage of this service, without too many headaches.","breadcrumb":{"@id":"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.besharp.it\/aws-cloudformation-the-top-5-reasons-for-not-using-it\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.besharp.it\/"},{"@type":"ListItem","position":2,"name":"AWS CloudFormation: the \u201ctop 5\u201d reasons for not using it"}]},{"@type":"WebSite","@id":"https:\/\/blog.besharp.it\/#website","url":"https:\/\/blog.besharp.it\/","name":"Proud2beCloud Blog","description":"il blog di beSharp","alternateName":"Proud2beCloud Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.besharp.it\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/e7262d28e51528c2e420327f9b18cd43","name":"Alessio Gandini","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/eeb98518768d999bff24f8358b464fe2?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/eeb98518768d999bff24f8358b464fe2?s=96&d=mm&r=g","caption":"Alessio Gandini"},"description":"Cloud-native Development Line Manager @ beSharp, DevOps Engineer e AWS expert. Computer geek da quando avevo 6 anni, appassionato di informatica ed elettronica a tutto tondo. Ultimamente sto esplorando l'esperienza utente vocale e il mondo dell'IoT. Appassionato di cinema e grande consumatore di serie TV, videogiocatore della domenica.","url":"https:\/\/blog.besharp.it\/author\/alessio-gandini\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/642"}],"collection":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/comments?post=642"}],"version-history":[{"count":0,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/642\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media\/644"}],"wp:attachment":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media?parent=642"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/categories?post=642"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/tags?post=642"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}