{"id":1467,"date":"2020-06-26T00:14:36","date_gmt":"2020-06-25T22:14:36","guid":{"rendered":"https:\/\/blog.besharp.it\/?p=1467"},"modified":"2021-03-24T12:08:50","modified_gmt":"2021-03-24T11:08:50","slug":"hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/","title":{"rendered":"Hosting a static site on AWS: is CloudFront always the right choice?"},"content":{"rendered":"<h2><span style=\"font-weight: 400;\">Introduction<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Binomial services <strong>CloudFront<\/strong> and <strong>S3<\/strong> are nowadays part of consolidated practices for many companies that have the necessity of hosting a static website (or part of it) while <strong>keeping its costs low without sacrificing security standards<\/strong> (eg: SSL termination on proprietary domain). But is this the only way pursuable? Are there any other means by which we can achieve the same result by also solving other necessities? This article tries to give an answer to that!<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Problem<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Imagine you have to handle the following need: your company&#8217;s frontend team requests testing a freshly developed feature on a production-like infrastructure to show and verify that the result is somewhat the one expected for the release. In particular, it would like to have a different domain name for every feature developed in order to avoid path related inconsistencies.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Even without some calculator at hand to predict costs of managed traffic, it is crystal clear that maintaining different CloudFront distributions for every feature and every frontend project can lead to useless complications from an AWS account\u2019s management perspective. It is worth mentioning that it\u2019s currently impossible to create two different origins from the main path and link them to two distinct domains within the same CloudFront distribution without incurring in a possible redirect that would lead to path problems mentioned above.\u00a0<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Solution<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">At first, we must notice that these deploys have an effimere nature. This means that a relatively short time of creation and removal for these infrastructural elements must be respected. To reach this goal it&#8217;s useful to share the same resources between more than one interlocutors to minimize overhead.\u00a0\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The proposed solution is made thanks to the following infrastructural elements:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">1 private S3 Bucket S3 (with Bucket policy)<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">1 LoadBalancer (with 2 Listener, 1 Target Group, 1 Security Group)<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">1 Lambda (in VPC with 1 Security Group)<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">1 S3 VPC Endpoint<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">n DNS record in Route 53 (where n represents the number of features to validate at determined time)<\/span><\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1465\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/06\/hosting_s3_infrastruttura.png\" alt=\"hosting sito su s3 infrastruttura\" width=\"1244\" height=\"988\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/06\/hosting_s3_infrastruttura.png 1244w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/06\/hosting_s3_infrastruttura-378x300.png 378w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/06\/hosting_s3_infrastruttura-1024x813.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/06\/hosting_s3_infrastruttura-768x610.png 768w\" sizes=\"(max-width: 1244px) 100vw, 1244px\" \/><\/p>\n<h2><span style=\"font-weight: 400;\">Creation and configuration of the S3 Bucket<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">To obtain the desired result it\u2019s imperative to create the S3 Bucket with the correct configuration. Following the definition of the CloudFormation template for this task:<\/span><\/p>\n<p>&nbsp;<\/p>\n<pre> \r\n  S3Bucket:\r\n   Type: AWS::S3::Bucket\r\n   Properties:\r\n     BucketName: 'subdomain.mydomain.com'\r\n     CorsConfiguration:\r\n       CorsRules:\r\n         - AllowedHeaders:\r\n             - '*'\r\n           AllowedMethods:\r\n             - GET\r\n             - HEAD\r\n             - POST\r\n             - PUT\r\n             - DELETE\r\n           AllowedOrigins:\r\n             - 'https:\/\/*.mydomain.com'\r\n     PublicAccessBlockConfiguration:\r\n       BlockPublicAcls: true\r\n       BlockPublicPolicy: true\r\n       IgnorePublicAcls: true\r\n       RestrictPublicBuckets: true\r\n     WebsiteConfiguration:\r\n       ErrorDocument: error.html\r\n       IndexDocument: index.html\r\n \r\n  S3BucketPolicy:\r\n   Type: AWS::S3::BucketPolicy\r\n   Properties:\r\n     Bucket: !Ref S3Bucket\r\n     PolicyDocument:\r\n       Version: '2012-10-17'\r\n       Statement:\r\n         - Sid: VPCEndpointReadGetObject\r\n           Effect: Allow\r\n           Principal: \"*\"\r\n           Action: s3:GetObject\r\n           Resource: !Sub '${S3Bucket.Arn}\/*'\r\n           Condition:\r\n             StringEquals:\r\n               aws:sourceVpce: !Ref S3VPCEndpointId\r\n<\/pre>\n<p><span style=\"font-weight: 400;\">It\u2019s worth noticing that \u201cwebsite configuration\u201d has been enabled to allow HTTP requests towards the bucket but at the same time a Bucket Policy denies retrieving any kind of object from it unless a request is coming from the S3\u2019s VPC endpoint, ensuring that only allowed actors passing from the account\u2019s VPC can access that very bucket.\u00a0<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Creation and configuration of the Load Balancer<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">To allow final users to see the static website hosted on S3, a Load Balancer must be created (depending on the final user\u2019s nature, you can choose to keep the Load Balancer private or not). In CloudFormation this is the set of resources that must be created:<\/span><\/p>\n<p>&nbsp;<\/p>\n<pre>  LoadBalancer:\r\n   Type: AWS::ElasticLoadBalancingV2::LoadBalancer\r\n   Properties:\r\n     Name: !Sub '${ProjectName}'\r\n     LoadBalancerAttributes:\r\n       - Key: 'idle_timeout.timeout_seconds'\r\n         Value: '60'\r\n       - Key: 'routing.http2.enabled'\r\n         Value: 'true'\r\n       - Key: 'access_logs.s3.enabled'\r\n         Value: 'true'\r\n       - Key: 'access_logs.s3.prefix'\r\n         Value: loadbalancers\r\n       - Key: 'access_logs.s3.bucket'\r\n         Value: !Ref S3LogsBucketName\r\n     Scheme: internet-facing\r\n     SecurityGroups:\r\n       - !Ref LoadBalancerSecurityGroup\r\n     Subnets:\r\n       - !Ref SubnetPublicAId\r\n       - !Ref SubnetPublicBId\r\n       - !Ref SubnetPublicCId\r\n     Type: application\r\n \r\n  LoadBalancerSecurityGroup:\r\n   Type: AWS::EC2::SecurityGroup\r\n   Properties:\r\n     GroupName: !Sub '${ProjectName}-alb'\r\n     GroupDescription: !Sub '${ProjectName} Load Balancer Security Group'\r\n     SecurityGroupIngress:\r\n       - CidrIp: 0.0.0.0\/0\r\n         Description: ALB Ingress rule from world\r\n         FromPort: 80\r\n         ToPort: 80\r\n         IpProtocol: tcp\r\n       - CidrIp: 0.0.0.0\/0\r\n         Description: ALB Ingress rule from world\r\n         FromPort: 443\r\n         ToPort: 443\r\n         IpProtocol: tcp\r\n     Tags:\r\n       - Key: Name\r\n         Value: !Sub '${ProjectName}-alb'\r\n       - Key: Environment\r\n         Value: !Ref Environment\r\n     VpcId: !Ref VPCId\r\n \r\n  HttpListener:\r\n   Type: AWS::ElasticLoadBalancingV2::Listener\r\n   Properties:\r\n     DefaultActions:\r\n       - RedirectConfig:\r\n           Port: '443'\r\n           Protocol: HTTPS\r\n           StatusCode: 'HTTP_301'\r\n         Type: redirect\r\n     LoadBalancerArn: !Ref LoadBalancer\r\n     Port: 80\r\n     Protocol: HTTP\r\n \r\n  HttpsListener:\r\n   Type: AWS::ElasticLoadBalancingV2::Listener\r\n   Properties:\r\n     Certificates:\r\n       - CertificateArn: !Ref LoadBalancerCertificateArn\r\n     DefaultActions:\r\n       - Type: forward\r\n         TargetGroupArn: !Ref TargetGroup\r\n     LoadBalancerArn: !Ref LoadBalancer\r\n     Port: 443\r\n     Protocol: HTTPS\r\n \r\n  TargetGroup:\r\n   Type: AWS::ElasticLoadBalancingV2::TargetGroup\r\n   Properties:\r\n     Name: !Sub '${ProjectName}'\r\n     HealthCheckEnabled: false\r\n     TargetType: lambda\r\n     Targets:\r\n       - Id: !GetAtt Lambda.Arn\r\n   DependsOn: LambdaPermission\r\n<\/pre>\n<p><span style=\"font-weight: 400;\">Thanks to this template, a public Load Balancer is deployed with a listener on port 80 (HTTP) redirecting on port 443 (HTTPS) with another listener which contacts a Target Group with a specific Lambda function registered on it.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Routing Lambda\u2019s code<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Proposed solution\u2019s logic is managed by a Lambda Function. Below an example code can be found (being an example it\u2019s better to review and adapt code in case of production-ready solutions):<\/span><\/p>\n<p>&nbsp;<\/p>\n<pre>import json\r\nfrom boto3 import client as boto3_client\r\nfrom os import environ as os_environ\r\nimport base64\r\nfrom urllib3 import PoolManager\r\n \r\nhttp = PoolManager()\r\ns3 = boto3_client('s3')\r\n \r\ndef handler(event, context):\r\n   try:\r\n       print(event)\r\n       print(context)\r\n \r\n       host = event['headers']['host']\r\n       print(\"Host:\", host)\r\n \r\n       feature = host.split('.')[0]\r\n       feature = \"-\".join(feature.split('-')[1:])\r\n       print(\"Feature:\", feature)\r\n \r\n       path = event['path'] if event['path'] != \"\/\" else \"\/index.html\"\r\n       print(\"Path:\", path)\r\n \r\n       query_string_parameters = event['queryStringParameters']\r\n       query_string_parameters = [f\"{key}={value}\" for key, value in event['queryStringParameters'].items()]\r\n       print(\"Query String Parameters:\", query_string_parameters)\r\n \r\n       http_method = event[\"httpMethod\"]\r\n       url = f\"http:\/\/{os_environ['S3_BUCKET']}.s3-website-eu-west-1.amazonaws.com\/{feature}{path}{'?' if [] != query_string_parameters else ''}{'&amp;'.join(query_string_parameters)}\"\r\n       print(url)\r\n \r\n       headers = event['headers']\r\n       headers.pop(\"host\")\r\n       print(\"Headers:\", headers)\r\n \r\n       body = event['body']\r\n       print(\"Body:\", body)\r\n \r\n       r = http.request(http_method, url, headers=headers, body=body)\r\n       print(\"Response:\", r)\r\n       print(\"Response Data:\", r.data)\r\n \r\n       try:\r\n           decoded_response = base64.b64encode(r.data).decode('utf-8')\r\n       except:\r\n           decoded_response =  base64.b64encode(r.data)\r\n \r\n       print(\"Decoded Response:\", decoded_response)\r\n       print(\"Headers Response:\", dict(r.headers))\r\n       return {\r\n           'statusCode': 200,\r\n           'body': decoded_response,\r\n           \"headers\": dict(r.headers),\r\n           \"isBase64Encoded\": True\r\n       }\r\n   except Exception as e:\r\n       print(e)\r\n       return {\r\n         'statusCode': 400\r\n       }\r\n<\/pre>\n<p><span style=\"font-weight: 400;\">Despite being a little tricky to read, operations done here are quite simple: starting from the DNS name which the user exploits to reach the Load Balancer, the Lambda Function processes the request to the S3 Bucket by building the feature\u2019s appropriate subfolder to contact. To ensure the entire process works as expected, a DNS name for each feature must be created.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Conclusions<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">We showed how it is possible, thanks to a wise choice of configuration of a set of specific resources, to maintain a S3 Bucket private, despite having public webhosting enabled, with the goal of managing more versions of a static website: one for each defined sub-folder, reachable with a specific yet different DNS name. This approach is undoubtedly more fast and agile when the needs are to verify visible aspects of a site instead of configure its infrastructure avoiding time and management efforts of a CloudFront distribution.\u00a0<\/span><\/p>\n<p>Nice, isn&#8217;t it? \ud83d\ude42 <a href=\"https:\/\/www.besharp.it\/en\/contact-us\/\" target=\"_blank\" rel=\"noopener noreferrer\">Write to us<\/a> to deepen the topic!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction Binomial services CloudFront and S3 are nowadays part of consolidated practices for many companies that have the necessity of [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":1471,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[470],"tags":[250,252,254],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v21.9.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Hosting a static site on AWS: is CloudFront always the right choice? - Proud2beCloud Blog<\/title>\n<meta name=\"description\" content=\"Hosting a static website on AWS: our alternatives to AWS CloudFront\" \/>\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\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Hosting a static site on AWS: is CloudFront always the right choice?\" \/>\n<meta property=\"og:description\" content=\"Hosting a static website on AWS: our alternatives to AWS CloudFront\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/\" \/>\n<meta property=\"og:site_name\" content=\"Proud2beCloud Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-06-25T22:14:36+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-03-24T11:08:50+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/06\/cloudfront-42.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1668\" \/>\n\t<meta property=\"og:image:height\" content=\"1251\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Alessandro Gaggia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Hosting a static site on AWS: is CloudFront always the right choice?\" \/>\n<meta name=\"twitter:description\" content=\"Hosting a static website on AWS: our alternatives to AWS CloudFront\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/06\/cloudfront-42.png\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Alessandro Gaggia\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/\",\"url\":\"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/\",\"name\":\"Hosting a static site on AWS: is CloudFront always the right choice? - Proud2beCloud Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.besharp.it\/#website\"},\"datePublished\":\"2020-06-25T22:14:36+00:00\",\"dateModified\":\"2021-03-24T11:08:50+00:00\",\"author\":{\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/f27fc12d10867c6ea6e0158ce4dd8924\"},\"description\":\"Hosting a static website on AWS: our alternatives to AWS CloudFront\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.besharp.it\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Hosting a static site on AWS: is CloudFront always the right choice?\"}]},{\"@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\/f27fc12d10867c6ea6e0158ce4dd8924\",\"name\":\"Alessandro Gaggia\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f58dc28050f26409e22ab60346d06220?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f58dc28050f26409e22ab60346d06220?s=96&d=mm&r=g\",\"caption\":\"Alessandro Gaggia\"},\"description\":\"Head of software development di beSharp, Full-Stack developer, mi occupo di garantire lo stato dell\u2019arte di tutta la nostra codebase. Scrivo codice in quasi ogni linguaggio, ma prediligo Typescript. Respiro Informatica, Game design, Cinema, Fumetti e buona cucina. Disegno per passione!\",\"url\":\"https:\/\/blog.besharp.it\/author\/alessandro-gaggia\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Hosting a static site on AWS: is CloudFront always the right choice? - Proud2beCloud Blog","description":"Hosting a static website on AWS: our alternatives to AWS CloudFront","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\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/","og_locale":"en_US","og_type":"article","og_title":"Hosting a static site on AWS: is CloudFront always the right choice?","og_description":"Hosting a static website on AWS: our alternatives to AWS CloudFront","og_url":"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/","og_site_name":"Proud2beCloud Blog","article_published_time":"2020-06-25T22:14:36+00:00","article_modified_time":"2021-03-24T11:08:50+00:00","og_image":[{"width":1668,"height":1251,"url":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/06\/cloudfront-42.png","type":"image\/png"}],"author":"Alessandro Gaggia","twitter_card":"summary_large_image","twitter_title":"Hosting a static site on AWS: is CloudFront always the right choice?","twitter_description":"Hosting a static website on AWS: our alternatives to AWS CloudFront","twitter_image":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/06\/cloudfront-42.png","twitter_misc":{"Written by":"Alessandro Gaggia","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/","url":"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/","name":"Hosting a static site on AWS: is CloudFront always the right choice? - Proud2beCloud Blog","isPartOf":{"@id":"https:\/\/blog.besharp.it\/#website"},"datePublished":"2020-06-25T22:14:36+00:00","dateModified":"2021-03-24T11:08:50+00:00","author":{"@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/f27fc12d10867c6ea6e0158ce4dd8924"},"description":"Hosting a static website on AWS: our alternatives to AWS CloudFront","breadcrumb":{"@id":"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.besharp.it\/hosting-a-static-site-on-aws-is-cloudfront-always-the-right-choice\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.besharp.it\/"},{"@type":"ListItem","position":2,"name":"Hosting a static site on AWS: is CloudFront always the right choice?"}]},{"@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\/f27fc12d10867c6ea6e0158ce4dd8924","name":"Alessandro Gaggia","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/f58dc28050f26409e22ab60346d06220?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f58dc28050f26409e22ab60346d06220?s=96&d=mm&r=g","caption":"Alessandro Gaggia"},"description":"Head of software development di beSharp, Full-Stack developer, mi occupo di garantire lo stato dell\u2019arte di tutta la nostra codebase. Scrivo codice in quasi ogni linguaggio, ma prediligo Typescript. Respiro Informatica, Game design, Cinema, Fumetti e buona cucina. Disegno per passione!","url":"https:\/\/blog.besharp.it\/author\/alessandro-gaggia\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/1467"}],"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\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/comments?post=1467"}],"version-history":[{"count":0,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/1467\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media\/1471"}],"wp:attachment":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media?parent=1467"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/categories?post=1467"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/tags?post=1467"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}