{"id":1551,"date":"2020-07-23T16:07:19","date_gmt":"2020-07-23T14:07:19","guid":{"rendered":"https:\/\/blog.besharp.it\/?p=1551"},"modified":"2021-03-24T12:01:53","modified_gmt":"2021-03-24T11:01:53","slug":"deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/","title":{"rendered":"Deploy of a Docker-compose application in an AWS environment using ECS CLI"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Nowadays, using Docker as an infrastructure container for local testing purposes is becoming more and more common. Many times developers exploit docker-compose functionality to create an infrastructure stack that contains their application, web server, and databases in different docker containers.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In this article, you will learn how to deploy an entire solution inside your AWS environment using AWS ECS Fargate service. Let&#8217;s start by explaining what AWS ECS Fargate is.<\/span><\/p>\n<h2><b>Amazon ECS and AWS Fargate in a nutshell<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Amazon ECS is a service that allows you to run and manage clusters of Docker containers. It\u2019s fully managed by Amazon and easily scalable based on your traffic load.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It comes in two possible flavors:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">EC2 instances hosting your containers: with this configuration, EC2 instances scaling policies are managed by the developer.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Fargate mode: automatically manages your containers, providing the correct computational resources to your application.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">AWS ECS three main actors are:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\"><b>Cluster<\/b><span style=\"font-weight: 400;\">: the logical grouping of ECS resources.<\/span><\/li>\n<li style=\"font-weight: 400;\"><b>Service<\/b><span style=\"font-weight: 400;\">: resource that allows you to run and maintain a specified number of instances of a task definition simultaneously, in an Amazon ECS cluster.<\/span><\/li>\n<li style=\"font-weight: 400;\"><b>Task-Definition<\/b><span style=\"font-weight: 400;\">: a text file, in JSON format, that contains all the definitions and configurations of your containers.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">Now that you\u2019ve learned what AWS ECS Fargate is, let&#8217;s try some hands-on.<\/span><\/p>\n<h2><b>Convert Docker containers to Fargate Task Definition<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Before starting to create resources inside the AWS environment, you have to split your docker defined inside the docker-compose file. To do this, some considerations must be made.\u00a0<\/span><\/p>\n<h3><b>Approaching Database deployment<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">If you have some databases inside your docker-compose, it is highly recommended to consider the adoption of the right AWS managed service, for example AWS RDS for relational databases, AWS DynamoDB for non-relational databases, or AWS ElastiCache for cache databases.\u00a0<\/span><\/p>\n<h3><b>Follow a Stateless approach instead of a Stateful one.<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">To reach scalability, a stateless approach should be used: this means that two requests of the same user session can be executed on different instances of your container application.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Let\u2019s start creating all the AWS services you need to build your application. For AWS Fargate we have already discussed all steps needed to create a cluster and services <\/span><a href=\"https:\/\/blog.besharp.it\/en\/aws-fargate-services-deployment-with-continuous-delivery-pipeline\/\"><span style=\"font-weight: 400;\">in this article<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">BUT<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you are searching for a <\/span><b>magical tool<\/b><span style=\"font-weight: 400;\"> that creates everything for you, you are in the right place!<\/span><\/p>\n<h2><b>Step 0: Install the ECS CLI<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Recently AWS has released a new command-line tool for interacting with the AWS ECS service. It simplifies creating, updating, and monitoring clusters and tasks from a local development environment. To install it simply run this command on your CLI:<\/span><\/p>\n<pre>sudo curl -Lo \/usr\/local\/bin\/ecs-cli https:\/\/amazon-ecs-cli.s3.amazonaws.com\/ecs-cli-darwin-amd64-latest<\/pre>\n<p>for downloading it inside your bin folder.<\/p>\n<pre>chmod +x \/usr\/local\/bin\/ecs-cli<\/pre>\n<p>to give executable permission.<br \/>\nAfter that, to verify that the CLI works properly, run<\/p>\n<pre>ecs-cli --version<\/pre>\n<h2>Step 1: Cluster Definition<\/h2>\n<p>Once you have installed the CLI, you can proceed with the ECS Cluster creation. First, configure your cluster using the ECS CLI and then deploy it on your AWS account.<\/p>\n<p>To configure the cluster simply run:<\/p>\n<pre>ecs-cli configure --cluster test --default-launch-type FARGATE --config-name test --region eu-west-1<\/pre>\n<p>This command defines a cluster named &#8220;test&#8221; with default lunch type &#8220;FARGATE&#8221; in the Ireland region.<\/p>\n<p>Now you just have to deploy it. In case your account contains a VPC that you want to use, you\u2019ll need to specify it in the deploy command:<\/p>\n<pre>ecs-cli up --cluster-config test --vpc YOUR_VPC_ID --subnets YOUR_SUBNET_ID_1, YOUR_SUBNET_ID_2<\/pre>\n<p>Keep in mind that if you specify a custom VPC ID you have to specify also the subnets ids where you want to deploy your service; to let ECS CLI create and configure the VPC for you, simply run:<\/p>\n<pre>ecs-cli up --cluster-config test<\/pre>\n<p>This command will create an empty ECS Cluster, and if you have not specified the VPC before, a CloudFormation stack with the VPC resources.<\/p>\n<p>Another thing that we need to create is the security group for your ECS service. You can create it using the AWS CLI running these commands:<\/p>\n<pre>aws ec2 create-security-group --description test --group-name testSecurityGroup --vpc-id YOUR_VPC_ID<\/pre>\n<pre>aws ec2 authorize-security-group-ingress --group-id SECURITY_GROUP_ID_CREATED --protocol tcp --port 80 --cidr 0.0.0.0\/0 --region eu-west-1<\/pre>\n<p>These commands create a security group associated with the passed VPC ID and authorize ingress rules from the Internet. Take note of the ID and the security group name specified here because you will use them in the next step.<\/p>\n<h2>Step 2: Role Creation<\/h2>\n<p>Now that you have your cluster up and running, go ahead by creating the AWS IAM Role used by your Task Definition. This role contains the access policy to AWS resources for your containers. To create this Role, you first have to create a file named &#8220;assume_role_policy.json&#8221; with this content:<\/p>\n<pre>{\r\n  \"Version\": \"2012-10-17\",\r\n  \"Statement\": [\r\n    {\r\n      \"Sid\": \"\",\r\n      \"Effect\": \"Allow\",\r\n      \"Principal\": {\r\n        \"Service\": \"ecs-tasks.amazonaws.com\"\r\n      },\r\n      \"Action\": \"sts:AssumeRole\"\r\n    }\r\n  ]\r\n}\r\n<\/pre>\n<p>Then run the following command:<\/p>\n<pre>aws iam --region eu-west-1 create-role --role-name ecsTaskExecutionRole --assume-role-policy-document file:\/\/assume-role_policy.json<\/pre>\n<p>After the role is created, run the following to attach the AWS managed policy for ECS Tasks that allow ECS containers to create AWS CloudWatch Log Group.<\/p>\n<pre>aws iam --region eu-west-1 attach-role-policy --role-name ecsTaskExecutionRole --policy-arn arn:aws:iam::aws:policy\/service-role\/AmazonECSTaskExecutionRolePolicy<\/pre>\n<h2>Step 3: Docker-Compose File and Ecs Configuration File<\/h2>\n<p>The next step is to modify your docker-compose file with some AWS references. Remember that, as per the current state of the art, the only supported versions of docker-compose are 1, 2, and 3.<\/p>\n<p>Let&#8217;s suppose that you have a docker-compose like this one:<\/p>\n<pre>version: '3'\r\nservices:\r\n  web:\r\n    image: nginx \r\n    ports:\r\n      - \"80:80\"\r\n<\/pre>\n<p>It simply defines a web service with the NGINX image and exposes the 80 port. What you have to do now is to add the logging property as per AWS logging\u2019s best practices to manage all container logs in AWS CloudWatch, and create the ECS CLI configuration file. To add the logging property simply modify the docker-compose file as described below:<\/p>\n<pre>version: '3'\r\nservices:\r\n  web:\r\n    image: nginx \r\n    ports:\r\n      - \"80:80\"\r\n    logging:\r\n      driver: awslogs\r\n      options: \r\n        awslogs-group: tutorial\r\n        awslogs-region: eu-west-1\r\n        awslogs-stream-prefix: web\r\n<\/pre>\n<p>The logging properties contain the driver property &#8220;awslogs&#8221;, that tells ECS to log on AWS CloudWatch service. The options section defines the name of the CloudWatch log group that is automatically created from AWS, the AWS region, and the stream prefix.<\/p>\n<p>Now that you have modified the docker-compose file, you have to create a new file called &#8220;ecs-params.yml&#8221; that contains the configurations of your ECS Cluster and ECS Service. In this file, you can specify:<br \/>\nThe networking configuration with your vpc and subnets.<br \/>\nThe Permission configuration with the role that you created in the second step.<br \/>\nTask configuration: properties like CPU and RAM limits for deploying the service.<\/p>\n<p>For our example, let\u2019s just define the basic configuration parameters:<\/p>\n<pre>version: 1\r\ntask_definition:\r\n  task_execution_role: YOUR_ECS_TASK_EXECUTION_ROLE_NAME\r\n  ecs_network_mode: awsvpc\r\n  task_size:\r\n    mem_limit: 0.5GB\r\n    cpu_limit: 256\r\nrun_params:\r\n  network_configuration:\r\n    awsvpc_configuration:\r\n      subnets:\r\n        - \"YOUR SUBNET ID 1\"\r\n        - \"YOUR SUBNET ID 2\"\r\n      security_groups:\r\n        - \"YOUR SECURITY GROUP ID\"\r\n      assign_public_ip: ENABLED\r\n<\/pre>\n<p>In the &#8220;task_execution_role&#8221; property, just enter the name of the role that you have defined in the second step.<\/p>\n<p>In the &#8220;subnets&#8221; and &#8220;security_groups&#8221; properties, enter the public subnet and the security group you\u2019ve defined in step one.<\/p>\n<h2>Step 4: Deploy the docker-compose<\/h2>\n<p>Now that everything is configured you can deploy the solution in your AWS account through the following command:<\/p>\n<pre>ecs-cli compose --project-name test service up --create-log-groups --cluster-config test<\/pre>\n<p>Your application is now deployed and ready to be used!<\/p>\n<p>As a bonus note: check the service status using this command:<\/p>\n<pre>ecs-cli compose --project-name test service ps --cluster-config test<\/pre>\n<p>That\u2019s all for today! In this article, we explained <strong>how to deploy a docker-compose application inside the AWS environment with a focus on the new ECS CLI provided by Amazon<\/strong>, see you soon in 14 days with the next article \ud83d\ude42<\/p>\n<p>#Proud2beCloud<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Nowadays, using Docker as an infrastructure container for local testing purposes is becoming more and more common. Many times developers [&hellip;]<\/p>\n","protected":false},"author":11,"featured_media":1554,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[242],"tags":[378,260,376,374],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v21.9.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Deploy of a Docker-compose application in an AWS environment using ECS CLI - Proud2beCloud Blog<\/title>\n<meta name=\"description\" content=\"In this article, you will learn how to deploy an entire solution inside your AWS environment using AWS ECS Fargate service.\" \/>\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\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Deploy of a Docker-compose application in an AWS environment using ECS CLI\" \/>\n<meta property=\"og:description\" content=\"How to deploy an entire solution inside your AWS environment using AWS ECS Fargate service.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/\" \/>\n<meta property=\"og:site_name\" content=\"Proud2beCloud Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-07-23T14:07:19+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-03-24T11:01:53+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/07\/deploy_Docker_Fargate-1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"834\" \/>\n\t<meta property=\"og:image:height\" content=\"626\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Mario Agati\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Deploy of a Docker-compose application in an AWS environment using ECS CLI\" \/>\n<meta name=\"twitter:description\" content=\"How to deploy an entire solution inside your AWS environment using AWS ECS Fargate service.\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/07\/deploy_Docker_Fargate.png\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Mario Agati\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/\",\"url\":\"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/\",\"name\":\"Deploy of a Docker-compose application in an AWS environment using ECS CLI - Proud2beCloud Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.besharp.it\/#website\"},\"datePublished\":\"2020-07-23T14:07:19+00:00\",\"dateModified\":\"2021-03-24T11:01:53+00:00\",\"author\":{\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/aa7c7be5d6521c0ddedc3ef11173540e\"},\"description\":\"In this article, you will learn how to deploy an entire solution inside your AWS environment using AWS ECS Fargate service.\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.besharp.it\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Deploy of a Docker-compose application in an AWS environment using ECS CLI\"}]},{\"@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\/aa7c7be5d6521c0ddedc3ef11173540e\",\"name\":\"Mario Agati\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/085d1a616fd504a1f7c22681f66e3af8?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/085d1a616fd504a1f7c22681f66e3af8?s=96&d=mm&r=g\",\"caption\":\"Mario Agati\"},\"description\":\"DevOps Engineer and Backend developer @ beSharp. Passionate about music, football, and motorsports. In my free time, I like to annoy my neighbors by playing drums.\",\"url\":\"https:\/\/blog.besharp.it\/author\/mario-agati\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Deploy of a Docker-compose application in an AWS environment using ECS CLI - Proud2beCloud Blog","description":"In this article, you will learn how to deploy an entire solution inside your AWS environment using AWS ECS Fargate service.","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\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/","og_locale":"en_US","og_type":"article","og_title":"Deploy of a Docker-compose application in an AWS environment using ECS CLI","og_description":"How to deploy an entire solution inside your AWS environment using AWS ECS Fargate service.","og_url":"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/","og_site_name":"Proud2beCloud Blog","article_published_time":"2020-07-23T14:07:19+00:00","article_modified_time":"2021-03-24T11:01:53+00:00","og_image":[{"width":834,"height":626,"url":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/07\/deploy_Docker_Fargate-1.png","type":"image\/png"}],"author":"Mario Agati","twitter_card":"summary_large_image","twitter_title":"Deploy of a Docker-compose application in an AWS environment using ECS CLI","twitter_description":"How to deploy an entire solution inside your AWS environment using AWS ECS Fargate service.","twitter_image":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/07\/deploy_Docker_Fargate.png","twitter_misc":{"Written by":"Mario Agati","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/","url":"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/","name":"Deploy of a Docker-compose application in an AWS environment using ECS CLI - Proud2beCloud Blog","isPartOf":{"@id":"https:\/\/blog.besharp.it\/#website"},"datePublished":"2020-07-23T14:07:19+00:00","dateModified":"2021-03-24T11:01:53+00:00","author":{"@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/aa7c7be5d6521c0ddedc3ef11173540e"},"description":"In this article, you will learn how to deploy an entire solution inside your AWS environment using AWS ECS Fargate service.","breadcrumb":{"@id":"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.besharp.it\/deploy-a-docker-compose-application-inside-an-aws-environment-new-with-ecs-cli\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.besharp.it\/"},{"@type":"ListItem","position":2,"name":"Deploy of a Docker-compose application in an AWS environment using ECS CLI"}]},{"@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\/aa7c7be5d6521c0ddedc3ef11173540e","name":"Mario Agati","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/085d1a616fd504a1f7c22681f66e3af8?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/085d1a616fd504a1f7c22681f66e3af8?s=96&d=mm&r=g","caption":"Mario Agati"},"description":"DevOps Engineer and Backend developer @ beSharp. Passionate about music, football, and motorsports. In my free time, I like to annoy my neighbors by playing drums.","url":"https:\/\/blog.besharp.it\/author\/mario-agati\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/1551"}],"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\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/comments?post=1551"}],"version-history":[{"count":0,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/1551\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media\/1554"}],"wp:attachment":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media?parent=1551"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/categories?post=1551"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/tags?post=1551"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}