{"id":4257,"date":"2025-10-07T06:15:34","date_gmt":"2025-10-07T06:15:34","guid":{"rendered":"https:\/\/code2deploy.com\/blog\/?p=4257"},"modified":"2025-10-07T06:15:35","modified_gmt":"2025-10-07T06:15:35","slug":"how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost","status":"publish","type":"post","link":"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/","title":{"rendered":"How to Automatically Stop and Start Your AWS EC2 Instance to Save Cost"},"content":{"rendered":"\n

 Introduction<\/strong><\/h3>\n\n\n\n

If you\u2019re running non-production environments such as staging, testing, or pre-production<\/strong> on AWS EC2, chances are your servers stay idle during off-hours<\/strong>.
Even when no one is using them, AWS continues charging for compute time \u2014 leading to unnecessary monthly costs.<\/p>\n\n\n\n

A smart and simple way to reduce your AWS bill is to automatically stop your EC2 instances during off-hours<\/strong> (e.g., at night) and start them again in the morning<\/strong>.
In this guide, we\u2019ll show how to do that using a cron job + AWS CLI<\/strong>, and we\u2019ll estimate how much you can save.<\/p>\n\n\n\n

\n\n\n\n

 Why Auto-Stop EC2 Makes Sense<\/strong><\/h2>\n\n\n\n

Many teams run development or pre-prod environments 24\/7 \u2014 even though they\u2019re used only 8\u201312 hours a day.
For example:<\/p>\n\n\n\n

    \n
  • QA servers used only in office hours
    <\/li>\n\n\n\n
  • Internal demo or staging environments
    <\/li>\n\n\n\n
  • Pre-prod servers used during testing cycles
    <\/li>\n<\/ul>\n\n\n\n

    These idle hours silently consume compute cost<\/strong>.<\/p>\n\n\n\n

    By automating start\/stop, you can:<\/p>\n\n\n\n

      \n
    • Reduce monthly EC2 compute cost by 30\u201350%<\/strong>
      <\/strong><\/li>\n\n\n\n
    • Keep environments ready for use every morning
      <\/li>\n\n\n\n
    • Maintain all EBS data and configuration (since stopping doesn\u2019t delete volumes)
      <\/li>\n\n\n\n
    • Apply the method without any extra AWS service cost
      <\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n

      Real Example: Cost Comparison<\/strong><\/h2>\n\n\n\n

      Let\u2019s take an example of a t2.medium EC2 instance<\/strong> in Singapore (ap-southeast-1) region.<\/p>\n\n\n\n

      Plan<\/strong><\/td>Runtime per Day<\/strong><\/td>Monthly Hours<\/strong><\/td>Approx. Monthly Cost<\/strong><\/td><\/tr>
      Always On (24\u00d77)<\/td>24 hrs<\/td>720 hrs<\/td>$33.41<\/strong><\/td><\/tr>
      Scheduled (08:00\u201322:00)<\/td>14 hrs<\/td>420 hrs<\/td>$19.49<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      That\u2019s a ~42% cost reduction<\/strong> just by stopping the instance overnight.
      If your previous month\u2019s bill was $51.81, you\u2019d bring it down to around $37.89<\/strong> \u2014 without changing instance type or performance.<\/p>\n\n\n\n

      \n\n\n\n

       Why Not Use Spot Instances Instead?<\/strong><\/h2>\n\n\n\n

      AWS Spot Instances are a great way to cut costs (up to 90%), but they come with limitations<\/strong>:<\/p>\n\n\n\n

        \n
      • Instances can be interrupted anytime<\/strong> when AWS needs capacity.
        <\/li>\n\n\n\n
      • Not ideal for long-running or stateful environments.
        <\/li>\n\n\n\n
      • You must design your system to handle instance termination<\/strong> gracefully.
        <\/li>\n<\/ul>\n\n\n\n

        For pre-prod or test servers<\/strong> that need consistent uptime during work hours, auto start\/stop<\/strong> is a safer and more predictable alternative.<\/p>\n\n\n\n

        \n\n\n\n

         Implementation Using AWS CLI + Cron Job<\/strong><\/h2>\n\n\n\n

        You don\u2019t need extra AWS services like Lambda or EventBridge (which add small costs).
        You can run commands directly from your local server<\/strong> or management VM<\/strong> that already has AWS CLI configured.<\/p>\n\n\n\n

        Step 1: Configure AWS CLI<\/strong><\/h3>\n\n\n\n

        Make sure you\u2019ve installed and configured AWS CLI with an IAM user that has permissions:<\/p>\n\n\n\n

        aws configure<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        IAM policy example (minimal):<\/p>\n\n\n\n

        {
          “Version”: “2012-10-17”,
          “Statement”: [
            {
              “Effect”: “Allow”,
              “Action”: [
                “ec2:StartInstances”,
                “ec2:StopInstances”
              ],
              “Resource”: “EC2-ARN”
            }
          ]
        }<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Step 2: Create Start\/Stop Scripts<\/strong><\/h3>\n\n\n\n

        start-ec2.sh<\/strong><\/p>\n\n\n\n

        #!\/bin\/bash
        aws ec2 start-instances –instance-ids i-0893e0c5ddd0ff2b5 –region ap-southeast-1<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        stop-ec2.sh<\/strong><\/p>\n\n\n\n

        #!\/bin\/bash
        aws ec2 stop-instances –instance-ids i-0893e0c5ddd0ff2b5 –region ap-southeast-1<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Make them executable:<\/p>\n\n\n\n

        chmod +x start-ec2.sh stop-ec2.sh<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Or<\/p>\n\n\n\n

        #!\/bin\/bash
        # =====================================================
        # Simple EC2 Start\/Stop Script (for Preprod)
        # Instance: i-0893e0c5ddd0ff2b5
        # Region: ap-southeast-1
        # Author: Tom
        # =====================================================

        INSTANCE_ID=”*****************”
        REGION=”***********”
        LOG_FILE=”\/var\/log\/ec2-scheduler.log”
        ACTION=$1   # start or stop

        timestamp() {
          date ‘+%Y-%m-%d %H:%M:%S’
        }

        case “$ACTION” in
          start)
            aws ec2 start-instances –instance-ids “$INSTANCE_ID” –region “$REGION”
            echo “$(timestamp) – Started EC2 $INSTANCE_ID” >> “$LOG_FILE”
            ;;
          stop)
            aws ec2 stop-instances –instance-ids “$INSTANCE_ID” –region “$REGION”
            echo “$(timestamp) – Stopped EC2 $INSTANCE_ID” >> “$LOG_FILE”
            ;;
          *)
            echo “Usage: $0 {start|stop}”
            ;;
        esac<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Step 3: Add Cron Jobs<\/strong><\/h3>\n\n\n\n

        Edit your crontab:<\/p>\n\n\n\n

        crontab -e<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Add these lines:<\/p>\n\n\n\n

        0 8 * * * \/path\/to\/start-ec2.sh >> \/var\/log\/ec2_start.log 2>&1
        0 22 * * * \/path\/to\/stop-ec2.sh >> \/var\/log\/ec2_stop.log 2>&1<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

         This will start the EC2 instance at 8 AM<\/strong> and stop it at 10 PM<\/strong> daily also you can add weekend scheduled<\/p>\n\n\n\n

        \n\n\n\n

         Security & Best Practices<\/strong><\/h2>\n\n\n\n
          \n
        • Use a dedicated IAM user or role<\/strong> with minimal privileges.
          <\/li>\n\n\n\n
        • Rotate access keys regularly.
          <\/li>\n\n\n\n
        • Store AWS credentials securely in ~\/.aws\/credentials or via environment variables.
          <\/li>\n\n\n\n
        • Optionally add a Slack or email notification<\/strong> after each successful\/failed job.
          <\/li>\n<\/ul>\n\n\n\n
          \n\n\n\n

           Summary<\/strong><\/h2>\n\n\n\n
          Feature<\/strong><\/td>Auto Stop\/Start<\/strong><\/td>Spot Instance<\/strong><\/td><\/tr>
          Cost Savings<\/td>30\u201350%<\/td>Up to 90%<\/td><\/tr>
          Reliability<\/td>High (Predictable uptime)<\/td>Low (Can be interrupted)<\/td><\/tr>
          Best For<\/td>Pre-prod, staging, test<\/td>Batch jobs, CI\/CD, temporary workloads<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
          \n\n\n\n

          Conclusion<\/strong><\/h2>\n\n\n\n

          Most companies keep their non-production servers running 24\u00d77, even when unused at night.
          With a simple cron job and AWS CLI, you can cut your EC2 cost by up to 40%<\/strong> \u2014 safely, automatically, and without losing any data.<\/p>\n","protected":false},"excerpt":{"rendered":"

           Introduction If you\u2019re running non-production environments such as staging, testing, or pre-production on AWS EC2, chances are your servers stay idle during off-hours.Even when no one is using them, AWS continues charging for compute time \u2014 leading to unnecessary monthly costs. A smart and simple way to reduce your AWS bill is to automatically stop […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[87,33],"tags":[861,864,859,866,863,869,867,860,868,865,862],"class_list":["post-4257","post","type-post","status-publish","format-standard","hentry","category-aws","category-cloud-native-technology","tag-auto-stop-ec2","tag-aws-cli-automation","tag-aws-ec2-cost-optimization","tag-dev","tag-ec2-cron-job","tag-ec2-scheduling-without-lambda","tag-preprod-cost-optimization","tag-reduce-aws-bill","tag-save-money-on-aws","tag-stage","tag-start-stop-ec2-schedule"],"yoast_head":"\nHow to Automatically Stop and Start Your AWS EC2 Instance to Save Cost - code2deploy.com<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Automatically Stop and Start Your AWS EC2 Instance to Save Cost - code2deploy.com\" \/>\n<meta property=\"og:description\" content=\" Introduction If you\u2019re running non-production environments such as staging, testing, or pre-production on AWS EC2, chances are your servers stay idle during off-hours.Even when no one is using them, AWS continues charging for compute time \u2014 leading to unnecessary monthly costs. A smart and simple way to reduce your AWS bill is to automatically stop […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/\" \/>\n<meta property=\"og:site_name\" content=\"code2deploy.com\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-07T06:15:34+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-10-07T06:15:35+00:00\" \/>\n<meta name=\"author\" content=\"enam\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"enam\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\\\/\"},\"author\":{\"name\":\"enam\",\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/#\\\/schema\\\/person\\\/e46930c19b999a87f12566fa8357481b\"},\"headline\":\"How to Automatically Stop and Start Your AWS EC2 Instance to Save Cost\",\"datePublished\":\"2025-10-07T06:15:34+00:00\",\"dateModified\":\"2025-10-07T06:15:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\\\/\"},\"wordCount\":771,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/#\\\/schema\\\/person\\\/e46930c19b999a87f12566fa8357481b\"},\"keywords\":[\"auto stop EC2\",\"AWS CLI automation\",\"AWS EC2 cost optimization\",\"dev\",\"EC2 cron job\",\"EC2 scheduling without Lambda\",\"preprod cost optimization\",\"reduce AWS bill\",\"save money on AWS\",\"stage\",\"start stop EC2 schedule\"],\"articleSection\":[\"AWS\",\"Cloud computing\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/code2deploy.com\\\/blog\\\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\\\/\",\"url\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\\\/\",\"name\":\"How to Automatically Stop and Start Your AWS EC2 Instance to Save Cost - code2deploy.com\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/#website\"},\"datePublished\":\"2025-10-07T06:15:34+00:00\",\"dateModified\":\"2025-10-07T06:15:35+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/code2deploy.com\\\/blog\\\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Automatically Stop and Start Your AWS EC2 Instance to Save Cost\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/\",\"name\":\"code2deploy.com\\\/blog\",\"description\":\"TechOps\",\"publisher\":{\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/#\\\/schema\\\/person\\\/e46930c19b999a87f12566fa8357481b\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/#\\\/schema\\\/person\\\/e46930c19b999a87f12566fa8357481b\",\"name\":\"enam\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d864e2f082f4499f8f1b33f004ec166eea77b9e94738553b120b6dca2410f203?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d864e2f082f4499f8f1b33f004ec166eea77b9e94738553b120b6dca2410f203?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d864e2f082f4499f8f1b33f004ec166eea77b9e94738553b120b6dca2410f203?s=96&d=mm&r=g\",\"caption\":\"enam\"},\"logo\":{\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d864e2f082f4499f8f1b33f004ec166eea77b9e94738553b120b6dca2410f203?s=96&d=mm&r=g\"},\"sameAs\":[\"https:\\\/\\\/code2deploy.com\\\/blog\"],\"url\":\"https:\\\/\\\/code2deploy.com\\\/blog\\\/author\\\/enam\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Automatically Stop and Start Your AWS EC2 Instance to Save Cost - code2deploy.com","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:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/","og_locale":"en_US","og_type":"article","og_title":"How to Automatically Stop and Start Your AWS EC2 Instance to Save Cost - code2deploy.com","og_description":" Introduction If you\u2019re running non-production environments such as staging, testing, or pre-production on AWS EC2, chances are your servers stay idle during off-hours.Even when no one is using them, AWS continues charging for compute time \u2014 leading to unnecessary monthly costs. A smart and simple way to reduce your AWS bill is to automatically stop […]","og_url":"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/","og_site_name":"code2deploy.com","article_published_time":"2025-10-07T06:15:34+00:00","article_modified_time":"2025-10-07T06:15:35+00:00","author":"enam","twitter_card":"summary_large_image","twitter_misc":{"Written by":"enam","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/#article","isPartOf":{"@id":"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/"},"author":{"name":"enam","@id":"https:\/\/code2deploy.com\/blog\/#\/schema\/person\/e46930c19b999a87f12566fa8357481b"},"headline":"How to Automatically Stop and Start Your AWS EC2 Instance to Save Cost","datePublished":"2025-10-07T06:15:34+00:00","dateModified":"2025-10-07T06:15:35+00:00","mainEntityOfPage":{"@id":"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/"},"wordCount":771,"commentCount":0,"publisher":{"@id":"https:\/\/code2deploy.com\/blog\/#\/schema\/person\/e46930c19b999a87f12566fa8357481b"},"keywords":["auto stop EC2","AWS CLI automation","AWS EC2 cost optimization","dev","EC2 cron job","EC2 scheduling without Lambda","preprod cost optimization","reduce AWS bill","save money on AWS","stage","start stop EC2 schedule"],"articleSection":["AWS","Cloud computing"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/","url":"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/","name":"How to Automatically Stop and Start Your AWS EC2 Instance to Save Cost - code2deploy.com","isPartOf":{"@id":"https:\/\/code2deploy.com\/blog\/#website"},"datePublished":"2025-10-07T06:15:34+00:00","dateModified":"2025-10-07T06:15:35+00:00","breadcrumb":{"@id":"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/code2deploy.com\/blog\/how-to-automatically-stop-and-start-your-aws-ec2-instance-to-save-cost\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/code2deploy.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to Automatically Stop and Start Your AWS EC2 Instance to Save Cost"}]},{"@type":"WebSite","@id":"https:\/\/code2deploy.com\/blog\/#website","url":"https:\/\/code2deploy.com\/blog\/","name":"code2deploy.com\/blog","description":"TechOps","publisher":{"@id":"https:\/\/code2deploy.com\/blog\/#\/schema\/person\/e46930c19b999a87f12566fa8357481b"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/code2deploy.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/code2deploy.com\/blog\/#\/schema\/person\/e46930c19b999a87f12566fa8357481b","name":"enam","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/d864e2f082f4499f8f1b33f004ec166eea77b9e94738553b120b6dca2410f203?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d864e2f082f4499f8f1b33f004ec166eea77b9e94738553b120b6dca2410f203?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d864e2f082f4499f8f1b33f004ec166eea77b9e94738553b120b6dca2410f203?s=96&d=mm&r=g","caption":"enam"},"logo":{"@id":"https:\/\/secure.gravatar.com\/avatar\/d864e2f082f4499f8f1b33f004ec166eea77b9e94738553b120b6dca2410f203?s=96&d=mm&r=g"},"sameAs":["https:\/\/code2deploy.com\/blog"],"url":"https:\/\/code2deploy.com\/blog\/author\/enam\/"}]}},"_links":{"self":[{"href":"https:\/\/code2deploy.com\/blog\/wp-json\/wp\/v2\/posts\/4257","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/code2deploy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/code2deploy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/code2deploy.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/code2deploy.com\/blog\/wp-json\/wp\/v2\/comments?post=4257"}],"version-history":[{"count":1,"href":"https:\/\/code2deploy.com\/blog\/wp-json\/wp\/v2\/posts\/4257\/revisions"}],"predecessor-version":[{"id":4258,"href":"https:\/\/code2deploy.com\/blog\/wp-json\/wp\/v2\/posts\/4257\/revisions\/4258"}],"wp:attachment":[{"href":"https:\/\/code2deploy.com\/blog\/wp-json\/wp\/v2\/media?parent=4257"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/code2deploy.com\/blog\/wp-json\/wp\/v2\/categories?post=4257"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/code2deploy.com\/blog\/wp-json\/wp\/v2\/tags?post=4257"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}