<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michael Warkentin on Medium]]></title>
        <description><![CDATA[Stories by Michael Warkentin on Medium]]></description>
        <link>https://medium.com/@mwarkentin?source=rss-9393b0b5cfaa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1OejRbYEIb1QYHksk40X7A@2x.jpeg</url>
            <title>Stories by Michael Warkentin on Medium</title>
            <link>https://medium.com/@mwarkentin?source=rss-9393b0b5cfaa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:07:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mwarkentin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AWS Re:invent Day 4 Highlights]]></title>
            <link>https://mwarkentin.medium.com/aws-re-invent-day-4-highlights-92f6952ffd0f?source=rss-9393b0b5cfaa------2</link>
            <guid isPermaLink="false">https://medium.com/p/92f6952ffd0f</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[reinvent]]></category>
            <category><![CDATA[amazon-web-services]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Michael Warkentin]]></dc:creator>
            <pubDate>Fri, 03 Dec 2021 15:59:07 GMT</pubDate>
            <atom:updated>2021-12-03T16:00:12.138Z</atom:updated>
            <content:encoded><![CDATA[<p>Other Re:invent 2021 content:</p><ul><li><a href="https://atom-wishbone-c6c.notion.site/88a6ad91cec24479be10f01fc0ee4a34?v=bac934a9474d48cb9a4bcfdaeaf30317">Full list of announcements with links to docs and blog posts</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-announcements-day-1-570d26e03c87">Day 1 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-announcements-day-2-169fbc425b7e">Day 2 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-day-3-highlights-4e5602edce4d">Day 3 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-day-4-highlights-92f6952ffd0f">Day 4 highlights</a></li></ul><p>Here are my most interesting announcements from the third day of AWS Re:invent.</p><h3><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/aws-amplify-studio/"><strong>Amplify Studio</strong></a><strong> (</strong><a href="https://aws.amazon.com/blogs/mobile/aws-amplify-studio-figma-to-fullstack-react-app-with-minimal-programming/"><strong>blog post</strong></a><strong>)</strong></h3><p>Amplify continues to expand its footprint for building and deploying apps from front-end and mobile to back-end and cloud integration. It now offers a UI builder which can integrate directly with <a href="https://www.figma.com/">Figma</a> and generate React UI Component code. If you’re starting to build an app from scratch, Amplify is definitely worth a look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*PsCdXvdTSbA6bvQwkKY6kg.gif" /></figure><h3><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/aws-repost-community-question-answer-service/">Re:post community Q+A</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VgQ3aPmTDL7OteORgu0qpw.png" /></figure><p>It looks like AWS is finally replacing the old <a href="https://forums.aws.amazon.com/">AWS Developer Forums</a> with something a little more modern — <a href="https://repost.aws/">AWS re:Post</a>. It looks pretty similar to Stack Overflow, but is apparently a public version of an internal Amazon tool.</p><p>It currently has 27 high level topics that you can follow — including things like Serverless, Security Identity &amp; Compliance, and Cloud Financial Management.</p><p>You can get points and rank up by answering questions, but it should be noted that your account is tied to an AWS account which means that if you login with your work account, you may lose access to your reputation if you switch employers somewhere down the line.</p><h3>CDK Updates</h3><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/aws-cloud-development-kit-cdk-generally-available/"><strong>CDKv2</strong></a><strong> (</strong><a href="https://aws.amazon.com/blogs/developer/how-customer-feedback-shaped-the-aws-cloud-development-kit-version-2/"><strong>blog post</strong></a><strong>)</strong></p><p>The AWS Cloud Development Kit (CDK) has just hit a new major release: 2.0! The major new features are:</p><ul><li>Consolidation of the <a href="https://docs.aws.amazon.com/cdk/api/v2/docs/aws-construct-library.html">AWS Construct Library</a> into a single package called aws-cdk-lib which means only a single dependency to work with AWS</li><li>Improved API reference with more examples</li><li><a href="https://docs.aws.amazon.com/cdk/v2/guide/cli.html#cli-deploy">CDK Watch</a> for faster iteration on application code like Lambda functions and ECS tasks</li><li>A new <a href="https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.assertions-readme.html">assertions library</a> to run automated unit tests in any CDK-supported language</li></ul><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/aws-construct-hub-availability/"><strong>Construct Hub for CDK</strong></a><strong> (</strong><a href="https://aws.amazon.com/blogs/aws/announcing-general-availability-of-construct-hub-and-aws-cloud-development-kit-version-2/"><strong>blog post</strong></a><strong>)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*27LPaExrNl_FPe7CDwgw5w.png" /></figure><p>Construct Hub is a centralized registry for CDK Constructs (think Terraform Modules) which makes it easy to discover and share reusable CDK building blocks.</p><h3>New SDKs in preview</h3><p>It’s always nice to have more languages with full support for interacting with AWS. Yesterday AWS launched preview SDKs for three new languages:</p><ul><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/aws-sdk-swift-developer-preview/">Swift</a> (<a href="https://github.com/awslabs/aws-sdk-swift">github</a>)</li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/aws-sdk-kotlin-developer-preview/">Kotlin</a> (<a href="https://github.com/awslabs/aws-sdk-kotlin">github</a>)</li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/aws-sdk-rust-developer-preview/">Rust</a> (<a href="https://github.com/awslabs/aws-sdk-rust">github</a>)</li></ul><p>One cool fact that most people might not be aware of — AWS SDKs are generated programatically using the <a href="https://awslabs.github.io/smithy/">smithy interface definition language</a>!</p><h3>GuardDuty for EKS</h3><p>Looks like this was pre-announced during a smaller session — excited to see GuardDuty expanding into more specialized areas!</p><h3>Mark Nunnikhoven on Twitter: &quot;. @awscloud GuardDuty support for #k8s audit logs coming in early 2022!#reinvent pic.twitter.com/dRHGxSPUEN / Twitter&quot;</h3><p>@awscloud GuardDuty support for #k8s audit logs coming in early 2022!#reinvent pic.twitter.com/dRHGxSPUEN</p><h3>Wrap up</h3><p>That’s most likely a wrap for all of the big announcements from Re:invent! It’s been fun keeping up with all of the announcements and launches. I was a bit surprised there wasn’t much news on Lambda, ECS / Fargate, or AppRunner. I’ll be back with one final post covering my Top 5 launches.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92f6952ffd0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Re:invent Day 3 Highlights]]></title>
            <link>https://mwarkentin.medium.com/aws-re-invent-day-3-highlights-4e5602edce4d?source=rss-9393b0b5cfaa------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e5602edce4d</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[sagemaker]]></category>
            <category><![CDATA[reinvent]]></category>
            <category><![CDATA[amazon-web-services]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Michael Warkentin]]></dc:creator>
            <pubDate>Thu, 02 Dec 2021 15:55:11 GMT</pubDate>
            <atom:updated>2021-12-03T16:00:43.180Z</atom:updated>
            <content:encoded><![CDATA[<p>Other Re:invent 2021 content:</p><ul><li><a href="https://atom-wishbone-c6c.notion.site/88a6ad91cec24479be10f01fc0ee4a34?v=bac934a9474d48cb9a4bcfdaeaf30317">Full list of announcements with links to docs and blog posts</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-announcements-day-1-570d26e03c87">Day 1 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-announcements-day-2-169fbc425b7e">Day 2 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-day-3-highlights-4e5602edce4d">Day 3 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-day-4-highlights-92f6952ffd0f">Day 4 highlights</a></li></ul><p>Here are my most interesting announcements from the third day of AWS Re:invent.</p><p><a href="https://www.notion.so/DevOps-Guru-for-RDS-7a2eea36e93240ff9f781afbef64f123"><strong>DevOps Guru for RDS</strong></a><strong> (</strong><a href="https://aws.amazon.com/blogs/aws/new-amazon-devops-guru-for-rds-to-detect-diagnose-and-resolve-amazon-aurora-related-issues-using-ml/"><strong>blog post</strong></a><strong>)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gMawg3-NVxJSKolG.png" /></figure><p>Managing relational databases can be a pain, especially once you’re running a large fleet of them. DevOps Guru has gained some new functionality to monitor and alert on performance and operational issues on those databases. These are based on the metrics out of <a href="https://aws.amazon.com/rds/performance-insights/">Performance Insights</a> which provides helpful metrics on database load, query details, locks, etc.</p><p>Unfortunately, this feature is only available for Aurora databases at this time — I’m hoping for plain old RDS support soon.</p><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/amazon-dynamodb-standard-infrequent-access-table-class/"><strong>DynamoDB Infrequent Access Tables</strong></a><strong> (</strong><a href="https://aws.amazon.com/blogs/aws/new-dynamodb-table-class-save-up-to-60-in-your-dynamodb-costs/"><strong>blog post</strong></a><strong>)</strong></p><p>DynamoDB added a new storage class for tables which reduces storage costs by 60% in exchange for 25% higher read and write costs:</p><ul><li>Storage: $0.25 per GB-month to $0.10 per GB-month</li><li>Reads: $0.25 per million read request units -&gt; $0.31 per million read request units</li><li>Writes: $1.25 per million write request units -&gt; $1.56 per million write request units</li></ul><p>It looks like this setting is all or nothing for a whole table — would’ve been nice if you could transition rows over after some amount of time. I’ve seen some ideas for patterns where it can still be helpful:</p><ul><li><a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-time-series.html">Time Series Tables</a> where you have a table per time period and can transition older tables</li><li>Using DynamoDB TTLs to clean up old data and use DynamoDB streams to replicate to an archive table using Infrequent Access</li></ul><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/amazon-vpc-network-access-analyzer/"><strong>VPC Network Access Analyzer</strong></a><strong> (</strong><a href="https://aws.amazon.com/blogs/aws/new-amazon-vpc-network-access-analyzer/"><strong>blog post</strong></a><strong>)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x7QXT7C3fImpwcsrFau9Ig.png" /></figure><p>I suspect this one will take a while to wrap our heads around, but it seems like it’s the flip side of the Network Reachability tool AWS released last year — instead of taking two resources and determining if network connections between them can happen, it can analyze your entire account / VPC against criteria you specify (or use a pre-populated scope out of the box) and tell you <strong>all</strong> of the paths and resources between them.</p><p>AWS has also added Automated Reasoning to its research areas along with an article introducing the technology powering this new tool as well as <a href="http://todo/">IAM Access Analyzer</a>, <a href="http://todo/">S3 Block Public Access</a>, and <a href="http://todo/">VPC Reachability Analyzer</a>.</p><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/amazon-sqs-dead-letter-queue-management-experience-queues/"><strong>SQS DLQ Redrive Tasks</strong></a><strong> (</strong><a href="https://aws.amazon.com/blogs/aws/enhanced-dlq-management-sqs/"><strong>blog post</strong></a><strong>)</strong></p><p>SQS has the concept of a Dead Letter Queue (DLQ) which is a separate queue where messages which fail to be processed successfully get redirected so that they don’t just hang around blocking up your queue all day long. You can use the DLQ to investigate what went wrong — like figuring out if there was a poison pill message with invalid data or structure.</p><p>Once you’ve figured out the issue and coded around it, you’d generally want to retry (or “redrive) those messages through your system. Until now this had to be done manually — but AWS has now built it into the console and manages the operations for you. Some #awswishlist items:</p><ul><li>Support for redrive to other services like EventBridge which <a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-rule-dlq.html">use SQS as a DLQ</a></li><li>API support for starting, stopping, and monitoring redrive tasks</li></ul><p><strong>Customer Carbon Footprint Tool</strong></p><h3>Matthew S. Wilson (msw) | #reInvent on Twitter: &quot;Coming soon: AWS Customer Carbon Footprint tool.The tool will show your carbon footprint, and also a projection of what this will be in the future with Amazon&#39;s investments toward renewable energy. pic.twitter.com/oleZITSmdQ / Twitter&quot;</h3><p>Coming soon: AWS Customer Carbon Footprint tool.The tool will show your carbon footprint, and also a projection of what this will be in the future with Amazon&#39;s investments toward renewable energy. pic.twitter.com/oleZITSmdQ</p><p>Not a lot of information yet on this, but it’s interesting to hear that AWS will be translating customer resource usage to carbon generation. I’m hopeful that can help to drive some change and help people do things more efficiently.</p><p><strong>VPC IP Address Manager (IPAM)</strong></p><p>This slipped by at first, sounding like some tool to manage large amounts of EIPs and BYOIPs (although apparently it can do that), but it can also help you manage your CIDRs and private IP pools for your VPCs across your entire org.</p><blockquote>For those of you with existing VPCs, after you create IPAM it will start monitoring, without any action on your part, to create an inventory of all your VPCs and EIPs. Once you create pools, IPAM will then backfill your VPCs into the pool. This means you can create VPCs today, using your existing workflow, and use IPAM for monitoring and audit only. Later on, you can switch your workflow to IPAM-based automated VPC assignment.</blockquote><p><strong>SageMaker Updates</strong></p><p>Yesterday was the ML keynote, so as expected there were a bunch of SageMaker updates announced (in order of interestingness):</p><ul><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/amazon-sagemaker-serverless-inference/">SageMaker Serverless Inference</a></li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/amazon-sagemaker-studio-data-notebook-integration-emr/">SageMaker Universal Notebook</a></li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/amazon-sagemaker-studio-lab-no-configuration-ml-service/">SageMaker Studio Lab</a></li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/12/amazon-sagemaker-studio-lab-no-configuration-ml-service/">SageMaker Inference Recommender</a></li></ul><p>I’ll check in again with my highlights tomorrow — hoping for some Lambda/DynamoDB news from Werner Vogel’s keynote today! Looks like something else leaked a little early!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_MkgWJkPCCiT-OnHV3kdOw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e5602edce4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Re:invent announcements day 2]]></title>
            <link>https://mwarkentin.medium.com/aws-re-invent-announcements-day-2-169fbc425b7e?source=rss-9393b0b5cfaa------2</link>
            <guid isPermaLink="false">https://medium.com/p/169fbc425b7e</guid>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[reinvent]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Michael Warkentin]]></dc:creator>
            <pubDate>Wed, 01 Dec 2021 14:35:23 GMT</pubDate>
            <atom:updated>2021-12-03T16:01:02.693Z</atom:updated>
            <content:encoded><![CDATA[<p>Other Re:invent 2021 content:</p><ul><li><a href="https://atom-wishbone-c6c.notion.site/88a6ad91cec24479be10f01fc0ee4a34?v=bac934a9474d48cb9a4bcfdaeaf30317">Full list of announcements with links to docs and blog posts</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-announcements-day-1-570d26e03c87">Day 1 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-announcements-day-2-169fbc425b7e">Day 2 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-day-3-highlights-4e5602edce4d">Day 3 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-day-4-highlights-92f6952ffd0f">Day 4 highlights</a></li></ul><p>I’m back at it again with the most interesting announcements from the second day of AWS Re:invent:</p><p><strong>Serverless Data Tools</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8pMCMA5cMm4JUviHsaMYaw.png" /></figure><p>These all got announced on one slide during Adam Selipsky’s keynote:</p><ul><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-redshift-serverless/">Redshift Serverless</a> (<a href="https://aws.amazon.com/blogs/aws/introducing-amazon-redshift-serverless-run-analytics-at-any-scale-without-having-to-manage-infrastructure/">blog post</a>)</li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-emr-serverless-preview/">EMR Serverless</a> (<a href="https://aws.amazon.com/blogs/big-data/announcing-amazon-emr-serverless-preview-run-big-data-applications-without-managing-servers/">blog post</a>)</li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-msk-serverless-public-preview/">MSK Serverless</a></li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-kinesis-data-streams-on-demand/">Kinesis “On-Demand”</a> (<a href="https://aws.amazon.com/blogs/aws/amazon-kinesis-data-streams-on-demand-stream-data-at-scale-without-managing-capacity/">blog post</a>)</li></ul><p>I’m curious how pricing for these services look compared to our current set up (particularly with Redshift 3 year RIs), but more services with simplified operations and scaling is always welcome.</p><p><strong>Graviton3 processors</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_t9Fyx3Ln2OypXSGZzhtJA.png" /></figure><p>A year after announcing Graviton2, AWS has launched their next generation ARM instance, the <a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-ec2-c7g-instances-aws-graviton3-processors/">Graviton3</a> — starting with the c7g instance class. According to AWS, these instances:</p><blockquote>provide up to 25% better compute performance, up to 2x higher floating-point performance, and up to 2x faster cryptographic workload performance compared to AWS Graviton2 processors. Graviton3 processors deliver up to 3x better performance compared to Graviton2 processors for CPU-based machine learning workloads, with support for bfloat16 and fp16 instructions. Graviton3 processors also support pointer authentication for enhanced security in addition to always-on 256-bit memory encryption available in AWS Graviton2.</blockquote><p><a href="https://twitter.com/lizthegrey/status/1465737094957965319">Liz Fong-Jones</a> has been running them at Honeycomb for a while now:</p><blockquote>+35% performance increase over #Graviton2. We were able to run 30% fewer instances of C7g than C6g serving same workload, and with 30% reduced latency.</blockquote><p>These are available in <a href="https://pages.awscloud.com/C7g-Preview.html">preview now</a>.</p><p><strong>S3 improvements</strong></p><p>A bunch of s3 announcements dropped during the evening yesterday. A couple of my favorites:</p><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/aws-backup-amazon-s3-backup/">AWS Backup for Amazon S3</a> (<a href="https://aws.amazon.com/blogs/aws/preview-aws-backup-adds-support-for-amazon-s3/">blog post</a>)</p><p>This seems like a huge deal — you can now centralize your backup management of S3 buckets, in addition to RDS, DynamoDB, EFS, etc.</p><p>Initial backups are a full snapshot of the bucket, and then it will track incremental changes. You are able to restore the entire bucket or specific objects into a new or existing S3 bucket.</p><p>To enroll in the Preview, send your account ID to <a href="/service/mailto:s3-backup-preview@amazon.com">s3-backup-preview@amazon.com</a>.</p><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-s3-object-ownership-simplify-access-management-data-s3/">S3 Object Ownership can now disable ACLs on a bucket</a> (<a href="https://aws.amazon.com/blogs/aws/preview-aws-backup-adds-support-for-amazon-s3/">blog post</a>)</p><p>S3 was the first AWS service launched, which means that it pre-dates AWS IAM. This has meant that it’s had a strange brew of its own access controls (known as S3 ACLs) and IAM access control. For the first time, we can now disable ACLs on a bucket level — hopefully account-level and org-level support are coming soon!</p><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-s3-glacier-instant-retrieval-storage-class/">New Amazon S3 Glacier Instant Retrieval storage class</a> (<a href="https://aws.amazon.com/blogs/aws/amazon-s3-glacier-is-the-best-place-to-archive-your-data-introducing-the-s3-glacier-instant-retrieval-storage-class/">blog post</a>)</p><p>You can now retrieve files from Glacier instantly by using this new storage class. Along with this, the old Glacier class becomes <a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-s3-glacier-storage-class-amazon-s3-glacier-flexible-retrieval/">Glacier Flexible Retrieval</a> with 10% cheaper storage and free bulk retrievals. S3 Intelligent Tiering supports the new <a href="https://aws.amazon.com/about-aws/whats-new/2021/11/s3-intelligent-tiering-archive-instant-access-tier/">Instant Retrieval storage class for up to 68% savings</a>.</p><p><strong>Late night lambda pre-announcement</strong></p><p>There was a definitely lack of Lambda news yesterday — I’m hoping for some bigger announcements later in the week (maybe during Werner’s keynote). However <a href="https://twitter.com/julian_wood/status/1465842874457763840">Julian Wood</a> posted a nice improvement for Lambda that should be coming soon — a 20x increase in available ephemeral storage (/tmp) of up to 10GB.</p><h3>Julian Wood on Twitter: &quot;Ephemeral storage coming to Lambda! Up to 10Gb! Pre-announced at #reInvent #serverless pic.twitter.com/MPZ2UyK3Al / Twitter&quot;</h3><p>Ephemeral storage coming to Lambda! Up to 10Gb! Pre-announced at #reInvent #serverless pic.twitter.com/MPZ2UyK3Al</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=169fbc425b7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Re:invent announcements day 1]]></title>
            <link>https://mwarkentin.medium.com/aws-re-invent-announcements-day-1-570d26e03c87?source=rss-9393b0b5cfaa------2</link>
            <guid isPermaLink="false">https://medium.com/p/570d26e03c87</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[reinvent]]></category>
            <dc:creator><![CDATA[Michael Warkentin]]></dc:creator>
            <pubDate>Tue, 30 Nov 2021 15:30:01 GMT</pubDate>
            <atom:updated>2021-12-03T16:01:17.386Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m3JbvDP8bec2oI-Gv-0B6w.png" /></figure><p>Other Re:invent 2021 content:</p><ul><li><a href="https://atom-wishbone-c6c.notion.site/88a6ad91cec24479be10f01fc0ee4a34?v=bac934a9474d48cb9a4bcfdaeaf30317">Full list of announcements with links to docs and blog posts</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-announcements-day-1-570d26e03c87">Day 1 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-announcements-day-2-169fbc425b7e">Day 2 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-day-3-highlights-4e5602edce4d">Day 3 highlights</a></li><li><a href="https://mwarkentin.medium.com/aws-re-invent-day-4-highlights-92f6952ffd0f">Day 4 highlights</a></li></ul><p>Here are the most interesting announcements from the first day of AWS Re:invent for me:</p><p><strong>S3 event improvements</strong></p><p>Announcements:</p><ul><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-s3-event-notifications-amazon-eventbridge-build-advanced-serverless-applications/">Amazon S3 Event Notifications with Amazon EventBridge help you build advanced serverless applications faster</a> (<a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/EventBridge.html">docs</a>)</li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-s3-event-notifications-s3-lifecycle-intelligent-tiering-object-tags-object-access-control-lists/">Amazon S3 adds new S3 Event Notifications for S3 Lifecycle, S3 Intelligent-Tiering, object tags, and object access control lists</a></li></ul><p>If you’ve ever tried setting up s3 event-driven applications before, there were a couple of options which worked, but weren’t great. You could either trigger a lambda directly from s3 or push the events into SNS / SQS. Alternatively you could use glue and duct tape and hook into EventBridge by setting up CloudTrail Data Events which required far too much configuration — particularly if you wanted to capture events from many buckets.</p><p>With this <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/EventBridge.html">new release</a>, it’s as simple as flipping a switch on the s3 bucket in order to route events to dozens of targets inside AWS (or outside with API destinations), archive events for replay, etc. This costs <a href="https://aws.amazon.com/eventbridge/pricing/">$1.00 / million events</a>.</p><p>They’ve added new event types as well if you need to handle objects in different storage tiers, or react to permission changes.</p><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-athena-acid-apache-iceberg/"><strong>Athena ACID Transactions powered by Apache Iceberg</strong></a></p><p>Athena gets more powerful with this release with new read, write, delete, and “time travel” via <a href="https://iceberg.apache.org/">Apache Iceberg</a>. Being able to reach into s3 to delete user data has been a particular pain point for us at Wave and caused us to do things like <a href="https://www.youtube.com/watch?v=i0v3lQENN68">full nightly dumps</a> instead of streaming our data into S3. Looking forward to digging into this more.</p><p><strong>EBS Snapshot Improvements</strong></p><p>Announcements:</p><ul><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/retention-ebs-snapshots-75-amazon-archive-tier/">Amazon EBS Snapshots introduces a new tier, Amazon EBS Snapshots Archive, to reduce the cost of long-term retention of EBS Snapshots by up to 75%</a></li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/recover-accidental-deletions-snapshots-recycle-bin/">Recover from accidental deletions of your snapshots using Recycle Bin</a></li></ul><p>We don’t use EBS snapshots that much, but I’m hopeful that these improvements will make their way to RDS snapshots during the upcoming year.</p><p>EBS Snapshots Archive seems like a straightforward way of saving money on those snapshots that you need to keep around in case of emergency.</p><p>Recycle Bin is interesting from a security perspective especially if you can enforce its application at the account level (sounds like you can) or org level (not sure if this is there) which would provide a layer of security and recovery time in case of accidental or malicious deletion of snapshots.</p><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/aws-control-tower-terraform/"><strong>AWS Control Tower Terraform account provisioning and customization</strong></a></p><p>Control Tower now integrates with Terraform for account provisioning. Interestingly this is the 2nd Terraform integration launched by AWS within the last week (<a href="https://aws.amazon.com/about-aws/whats-new/2021/11/aws-proton-terraform-infrastructure/">AWS Proton now supports Terraform Open Source for infrastructure provisioning</a>).</p><p>The setup <a href="https://docs.aws.amazon.com/controltower/latest/userguide/taf-account-provisioning.html">looks pretty complex</a>, but definitely still interesting for companies who use Terraform as their primary Infrastructure as Code tool.</p><p><strong>AWS CloudWatch Improvements</strong></p><p>Announcements:</p><ul><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-cloudwatch-metrics-insights-preview/">Introducing Amazon CloudWatch Metrics Insights (Preview)</a></li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-cloudwatch-rum-applications-client-side-performance/">Introducing Amazon CloudWatch RUM for monitoring applications’ client-side performance</a></li><li><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-cloudwatch-evidently-feature-experimentation-safer-launches/">Introducing Amazon CloudWatch Evidently for feature experimentation and safer launches</a></li></ul><p>Metrics Insights looks like a powerful new query tool for your metrics. It includes a visual query builder as well as SQL support for quickly sharing queries. During my testing, queries came back pretty much instantly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8VwH4e-QWNUt6bo-DYjpfg.png" /></figure><p>It comes with a bunch of <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch-metrics-insights-queryexamples.html">Sample Queries</a> which seem to also be available directly within the UI:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sJOE-t-7OqImio-7dkeo_Q.png" /></figure><p>CloudWatch Real User Monitoring (RUM) means another feature that you would’ve needed a separate tool like <a href="https://www.datadoghq.com/dg/real-user-monitoring/ts/overview-ts/?utm_source=Advertisement&amp;utm_medium=GoogleAdsRUM&amp;utm_campaign=GoogleAdsRUM-RealUserMonitoringTshirt&amp;utm_content=RUM&amp;utm_keyword=%2Breal%20%2Buser%20%2Bmonitoring&amp;utm_matchtype=b&amp;utm_campaignid=14748076492&amp;utm_adgroupid=128720687518&amp;gclid=Cj0KCQiAtJeNBhCVARIsANJUJ2HtVKKcPkRKeFy-iXfDN-x4J7fFy8o31WGKi3-5OXrO2IBOI-e8wsUaAox4EALw_wcB">Datadog</a> or <a href="https://newrelic.com/products/browser-monitoring">New Relic</a> can now be done within AWS.</p><p>CloudWatch Evidently is a feature flagging + AB testing tool (think <a href="https://www.optimizely.com/">Optimizely</a>). AWS continues to expand with services competing with entire billion dollar companies.</p><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-inspector-continual-vulnerability-management/"><strong>AWS announces the new Amazon Inspector for continual vulnerability management</strong></a></p><p>The release of InspectorV2 makes it a lot easier to configure — it can be enabled for your entire organization with a single click. It also no longer requires a standalone agent — instead it’s built into the Systems Manager agent which is already installed by default on most (all?) AWS provided AMIs.</p><p>Inspector now supports continuous scanning of Docker containers in ECR in addition to scanning EC2 instances. This appears to be powered by <a href="https://snyk.io/">Snyk</a>.</p><p>They claim improved risk score generation and SecurityHub integration, but I’ll need to test out those claims myself.</p><p>That’s a wrap for Re:invent Day 1! There were many more that weren’t as applicable to me — it looks like AWS is keeping a page up to date with <a href="https://aws.amazon.com/blogs/aws/top-announcements-of-aws-reinvent-2021/">all the news</a>. I’ll be back with a Day 2 summary tomorrow!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=570d26e03c87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secure remote access to Synology NAS using Tailscale —Getting Started]]></title>
            <link>https://mwarkentin.medium.com/secure-remote-access-to-synology-nas-using-tailscale-getting-started-6cba7a0dbb7c?source=rss-9393b0b5cfaa------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cba7a0dbb7c</guid>
            <category><![CDATA[nas]]></category>
            <category><![CDATA[synology]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[tailscale]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Michael Warkentin]]></dc:creator>
            <pubDate>Tue, 28 Sep 2021 01:06:23 GMT</pubDate>
            <atom:updated>2021-09-28T01:06:23.861Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qFQe496OzNrTjAOuRvGEzA.png" /></figure><p>I’ve had a <a href="https://www.synology.com/en-us/products/DS920+">Synology DS918+ NAS</a> for a couple of years now. It’s been a fantastic little machine that manages most of my media and computer backups.</p><p>It could be frustrating that I had no way to manage it when I was outside of my home — particularly when I was out of town on long trips. I kept thinking about ways that I could enable remote access for myself — however at best the options felt overly complex and at worst like I’d be opening up my home network to security issues by exposing my server publicly.</p><p>Earlier this summer, I came across a <a href="https://twitter.com/Tailscale/status/1427377725271052297">tidbit on Twitter</a> that caught my eye — there’s now an <a href="https://tailscale.com/kb/1131/synology/">official Tailscale package available through the Synology Package Manager</a>.</p><blockquote>Tailscale is a VPN service that makes the devices and applications you own accessible anywhere in the world, securely and effortlessly. It enables encrypted point-to-point connections using the open source <a href="https://www.wireguard.com/">WireGuard</a> protocol, which means only devices on your private network can communicate with each other.</blockquote><p>They’ve got a generous free “personal” tier with support for up to 20 devices:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wMMBaKp1KwDwVN7K2XM0ig@2x.jpeg" /></figure><p>Getting Tailscale set up on your NAS is easy. Start by installing the package through the Package Center:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AO0R5Diwmjw53XOBmDNrcw.png" /></figure><p>Once you’ve installed it, open the Tailscale app and authenticate with your account (I use Github for simplicity and Yubikey MFA support):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*GPHabuWYNa2kIrJKMRgtgw.png" /></figure><p>After authenticating, your Synology should show up in the list of available Tailscale devices where you can get the permanent private IP on your Tailscale mesh network for the host. You can now use that IP to manage your NAS both remotely and from your home network!</p><p>Up next I’ll cover setting up Tailscale’s Magic DNS so that you can access your devices by name instead of by IP!</p><p>References:</p><ul><li><a href="https://tailscale.com/kb/1131/synology/">https://tailscale.com/kb/1131/synology/</a></li><li><a href="https://twitter.com/Tailscale/status/1427377725271052297">https://twitter.com/Tailscale/status/1427377725271052297</a></li><li><a href="https://kb.synology.com/en-sg/DSM/tutorial/How_to_install_applications_with_Package_Center">https://kb.synology.com/en-sg/DSM/tutorial/How_to_install_applications_with_Package_Center</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cba7a0dbb7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fast AWS Amplify Console rollbacks with blue/green deploys]]></title>
            <link>https://mwarkentin.medium.com/fast-aws-amplify-console-rollbacks-with-blue-green-deploys-4352c78ffdf9?source=rss-9393b0b5cfaa------2</link>
            <guid isPermaLink="false">https://medium.com/p/4352c78ffdf9</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[amplify-console]]></category>
            <category><![CDATA[rollbacks]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Michael Warkentin]]></dc:creator>
            <pubDate>Sun, 18 Jul 2021 23:54:49 GMT</pubDate>
            <atom:updated>2021-07-18T23:59:39.512Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m a big fan of <a href="https://aws.amazon.com/amplify/hosting/">AWS Amplify Console</a> for hosting static applications on AWS without having to manage your own pipelines, S3 buckets, CloudFront distributions, and so on.</p><p>One feature that’s missing is the ability to quickly rollback to a previous build. If you deploy a broken application, the only way to restore a previous version is to go through your full deploy process which may take 5–10 minutes — and will feel a lot longer if production is down. We’ve had a lot of communication with AWS about this issue, and are hopeful that they’ll release native rollback support sometime soon (<a href="https://github.com/aws-amplify/amplify-console/issues/307">amplify-console#307</a>).</p><p>Through this process we worked with our AWS TAM Sumeet Mankoo and SA Arundeep Nagaraj to come up with a workaround to enable fast rollbacks in exchange for some extra build costs and complexity in our Git workflows. By connecting multiple branches to Amplify we can have multiple versions of our application always available — similar to a blue/green deployment approach. Switching applications between branches is a fast operation, so we can go between our current HEAD deploy, and swap to HEAD-1 for a rollback.</p><p>Our application requires linear history in Github for our production branch which makes this pretty simple. I haven’t figured out if there’s a good way to manage these rollback branches for branches which include merge commits or force pushes to mess with their history.</p><p>As part of our deploy job in Jenkins, I added the following to push the commit for rollback:</p><pre>echo &quot;Pushing previous commit to main-minus-one branch for instant rollback: \$(git rev-parse HEAD^1)&quot;</pre><pre>git push https://\${githubToken}:x-oauth-basic@github.com/org/repo \$(git rev-parse HEAD^1):main-minus-one --force</pre><p>Once you’ve connected multiple branches in Amplify Console, and automated the git operations to push the correct commits, all that remains is to update the branch/domain association to rollback. This can be done in a few ways, but here’s an example using the <a href="https://docs.aws.amazon.com/cli/latest/reference/amplify/update-domain-association.html">update-domain-association</a> AWS CLI command:</p><pre>aws amplify update-domain-association --app-id abcde12345 --domain-name example.com --sub-domain-settings prefix=www,branchName=main-minus-one</pre><p>Then when you’ve pushed a fix up to main you can swap back:</p><pre>aws amplify update-domain-association --app-id abcde12345 --domain-name example.com --sub-domain-settings prefix=www,branchName=main</pre><p>Swapping branches happens in under 10 seconds, which is a huge improvement on our previous 5–10 minute process. Here’s a GIF of the branch swap process (using the trusty border: 1px solid red test):</p><p>&lt;insert gif here, medium upload failing right now…&gt;</p><p>If you need to support rollbacks for multiple releases, you should be able to add any number of branches — just keep in mind that you’ll be paying $0.01 / build-minute for each of them on every deploy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4352c78ffdf9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello App Runner in Terraform]]></title>
            <link>https://mwarkentin.medium.com/hello-app-runner-in-terraform-fde413a2a047?source=rss-9393b0b5cfaa------2</link>
            <guid isPermaLink="false">https://medium.com/p/fde413a2a047</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[apprunner]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Michael Warkentin]]></dc:creator>
            <pubDate>Wed, 26 May 2021 02:21:42 GMT</pubDate>
            <atom:updated>2021-05-26T02:21:42.928Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week AWS launched a new service called App Runner. In their words:</p><blockquote><a href="https://aws.amazon.com/apprunner">AWS App Runner</a> makes it easier for you to deploy web apps and APIs to the cloud, regardless of the language they are written in, even for teams that lack prior experience deploying and managing containers or infrastructure. The service has AWS operational and security best practices built-it and automatically scale up or down at a moment’s notice, with no cold starts to worry about.</blockquote><p>Justin Garrison wrote a sample application called <a href="https://github.com/aws-containers/hello-app-runner">Hello App Runner</a> and published it to a <a href="https://gallery.ecr.aws/aws-containers/hello-app-runner">public ECR repository</a>.</p><p>Hashicorp added <a href="https://www.hashicorp.com/blog/announcing-launch-day-support-for-aws-app-runner-in-the-terraform-aws-provider">support for the new service on launch day</a> to Terraform to enable easy management of your App Runner services as code. I figured mashing these two together would give me an easy way to take the service for a test run!</p><h3>Set up an autoscaling configuration</h3><p>First you set up an <a href="https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/apprunner_auto_scaling_configuration_version">autoscaling configuration</a> which your service will use to scale up and down:</p><pre>resource &quot;aws_apprunner_auto_scaling_configuration_version&quot; &quot;hello&quot; {                            <br>  auto_scaling_configuration_name = &quot;hello&quot;</pre><pre>  # scale between 1-5 containers<br>  min_size = 1<br>  max_size = 5<br>}</pre><h3>Configure the service</h3><p>Now for the fun part — setting up the <a href="https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/apprunner_service">service</a>:</p><pre>resource &quot;aws_apprunner_service&quot; &quot;hello&quot; {                            <br>  auto_scaling_configuration_arn = aws_apprunner_auto_scaling_configuration_version.hello.arn                          <br>         <br>  service_name = &quot;hello-app-runner&quot;                          <br>                            <br>  source_configuration {                              <br>    image_repository {                                <br>      image_configuration {                                  <br>        port = &quot;8000&quot;                                <br>      }                                <br>      <br>      image_identifier       = &quot;public.ecr.aws/aws-containers/hello-app-runner:latest&quot;                                <br>      image_repository_type = &quot;ECR_PUBLIC&quot;                              <br>    }                          <br>                              <br>    auto_deployments_enabled = false                            <br>  }                          <br>}</pre><pre>output &quot;apprunner_service_hello&quot; {                            <br>  value = aws_apprunner_service.hello                          <br>}</pre><h3>Terraform Plan</h3><p>With those resources in place, you can run a terraform plan to see what will be created:</p><pre>An execution plan has been generated and is shown below.<br>Resource actions are indicated with the following symbols:<br>  + create<br>  ~ update in-place</pre><pre>Terraform will perform the following actions:</pre><pre># aws_apprunner_auto_scaling_configuration_version.example will be created<br>  + resource &quot;aws_apprunner_auto_scaling_configuration_version&quot; &quot;hello&quot; {<br>      + arn                                 = (known after apply)<br>      + auto_scaling_configuration_name     = &quot;hello&quot;<br>      + auto_scaling_configuration_revision = (known after apply)<br>      + id                                  = (known after apply)<br>      + latest                              = (known after apply)<br>      + max_concurrency                     = 100<br>      + max_size                            = 5<br>      + min_size                            = 1<br>      + status                              = (known after apply)<br>    }</pre><pre># aws_apprunner_service.hello will be created<br>  + resource &quot;aws_apprunner_service&quot; &quot;hello&quot; {<br>      + arn                            = (known after apply)<br>      + auto_scaling_configuration_arn = (known after apply)<br>      + id                             = (known after apply)<br>      + service_id                     = (known after apply)<br>      + service_name                   = &quot;hello-app-runner&quot;<br>      + service_url                    = (known after apply)<br>      + status                         = (known after apply)<br>      + tags                           = {<br>          + &quot;Name&quot; = &quot;hello-app-runner&quot;<br>        }<br>      + tags_all                       = {<br>          + &quot;Name&quot; = &quot;hello-app-runner&quot;<br>        }</pre><pre>+ health_check_configuration {<br>          + healthy_threshold   = (known after apply)<br>          + interval            = (known after apply)<br>          + path                = (known after apply)<br>          + protocol            = (known after apply)<br>          + timeout             = (known after apply)<br>          + unhealthy_threshold = (known after apply)<br>        }</pre><pre>+ instance_configuration {<br>          + cpu               = (known after apply)<br>          + instance_role_arn = (known after apply)<br>          + memory            = (known after apply)<br>        }</pre><pre>+ source_configuration {<br>          + auto_deployments_enabled = false</pre><pre>+ image_repository {<br>              + image_identifier      = &quot;public.ecr.aws/aws-containers/hello-app-runner:latest&quot;<br>              + image_repository_type = &quot;ECR_PUBLIC&quot;</pre><pre>+ image_configuration {<br>                  + port = &quot;8000&quot;<br>                }<br>            }<br>        }<br>    }</pre><h3>Terraform Apply</h3><p>If everything in the plan looks good, you can run terraform apply. A couple of minutes later your service should be up and running!</p><pre>aws_apprunner_auto_scaling_configuration_version.example: Creating...<br>aws_apprunner_auto_scaling_configuration_version.example: Creation complete after 1s [id=arn:aws:apprunner:us-east-1:123456789:autoscalingconfiguration/example/1/8a88cca0b41a4844821e92c33de84703]<br>aws_apprunner_service.hello: Creating...<br>aws_apprunner_service.hello: Still creating... [10s elapsed]<br>...<br>aws_apprunner_service.hello: Still creating... [5m40s elapsed]<br>aws_apprunner_service.hello: Creation complete after 5m42s [id=arn:aws:apprunner:us-east-1:123456789:service/hello-app-runner/1256948d8558405daceea9cbaabb6ec1]</pre><pre>Apply complete! Resources: 2 added, 1 changed, 0 destroyed.</pre><pre>Outputs:</pre><pre>apprunner_service_hello = {<br>  &quot;arn&quot; = &quot;arn:aws:apprunner:us-east-1:123456789:service/hello-app-runner/1256948d8558405daceea9cbaabb6ec1&quot;<br>  &quot;auto_scaling_configuration_arn&quot; = &quot;arn:aws:apprunner:us-east-1:123456789:autoscalingconfiguration/example/1/8a88cca0b41a4844821e92c33de84703&quot;<br>  &quot;encryption_configuration&quot; = []<br>  &quot;health_check_configuration&quot; = [<br>    {<br>      &quot;healthy_threshold&quot; = 1<br>      &quot;interval&quot; = 5<br>      &quot;path&quot; = &quot;/&quot;<br>      &quot;protocol&quot; = &quot;TCP&quot;<br>      &quot;timeout&quot; = 2<br>      &quot;unhealthy_threshold&quot; = 5<br>    },<br>  ]<br>  &quot;id&quot; = &quot;arn:aws:apprunner:us-east-1:123456789:service/hello-app-runner/1256948d8558405daceea9cbaabb6ec1&quot;<br>  &quot;instance_configuration&quot; = [<br>    {<br>      &quot;cpu&quot; = &quot;1024&quot;<br>      &quot;instance_role_arn&quot; = &quot;&quot;<br>      &quot;memory&quot; = &quot;2048&quot;<br>    },<br>  ]<br>  &quot;service_id&quot; = &quot;1256948d8558405daceea9cbaabb6ec1&quot;<br>  &quot;service_name&quot; = &quot;hello-app-runner&quot;<br>  &quot;service_url&quot; = &quot;bg2hcjuckx.us-east-1.awsapprunner.com&quot;<br>  &quot;source_configuration&quot; = [<br>    {<br>      &quot;authentication_configuration&quot; = []<br>      &quot;auto_deployments_enabled&quot; = false<br>      &quot;code_repository&quot; = []<br>      &quot;image_repository&quot; = [<br>        {<br>          &quot;image_configuration&quot; = [<br>            {<br>              &quot;port&quot; = &quot;8000&quot;<br>              &quot;start_command&quot; = &quot;&quot;<br>            },<br>          ]<br>          &quot;image_identifier&quot; = &quot;public.ecr.aws/aws-containers/hello-app-runner:latest&quot;<br>          &quot;image_repository_type&quot; = &quot;ECR_PUBLIC&quot;<br>        },<br>      ]<br>    },<br>  ]<br>  &quot;status&quot; = &quot;RUNNING&quot;<br>}</pre><h3>Wrap up</h3><p>Once the apply wraps up, you should have a public endpoint up and running. You can grab it from the output — in this case (no guarantees that my endpoint will stick around for long):</p><pre>“service_url” = “bg2hcjuckx.us-east-1.awsapprunner.com”</pre><p>If you visit the URL you will see the application page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hJ3g-bMIQfi2cwt7KoL3kA.png" /><figcaption>Hello App Runner!</figcaption></figure><p>I was impressed with how easy it was to get this basic application up and running using Terraform. I’m looking forward to seeing how the App Runner service evolves over time — here’s the <a href="https://github.com/aws/apprunner-roadmap/issues">public roadmap</a>. My wishlist items are:</p><ul><li><a href="https://github.com/aws/apprunner-roadmap/issues/1">Allow App Runner services to talk to AWS resources in a private Amazon VPC</a></li><li><a href="https://github.com/aws/apprunner-roadmap/issues/2">Allow private endpoints for App Runner services</a></li><li><a href="https://github.com/aws/apprunner-roadmap/issues/6">External Configuration/Secret Sources</a></li><li><a href="https://github.com/aws/apprunner-roadmap/issues/9">Scale to zero</a></li><li><a href="https://github.com/aws/apprunner-roadmap/issues/11">Buildpack support</a></li><li><a href="https://github.com/aws/apprunner-roadmap/issues/20">Branch preview environments</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fde413a2a047" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Convox Tips: Disabling racks on evenings and weekends]]></title>
            <link>https://mwarkentin.medium.com/convox-tips-disabling-racks-on-evenings-and-weekends-8847913e7c13?source=rss-9393b0b5cfaa------2</link>
            <guid isPermaLink="false">https://medium.com/p/8847913e7c13</guid>
            <category><![CDATA[convox]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[paas]]></category>
            <dc:creator><![CDATA[Michael Warkentin]]></dc:creator>
            <pubDate>Sat, 24 Dec 2016 14:30:29 GMT</pubDate>
            <atom:updated>2017-01-08T02:03:52.533Z</atom:updated>
            <content:encoded><![CDATA[<p>At <a href="https://www.waveapps.com/">Wave</a> we’re running several <a href="https://convox.com/">Convox</a> racks: production, staging, and multiple “dev” racks. Our production environment obviously needs to be running constantly, but the other environments are mainly used Monday to Friday, between 9am and 8pm.</p><p>One of the reasons we’re migrating to AWS is the improved automation that it provides, and we are leveraging that to turn off our dev and staging racks when they’re not in use — saving roughly 66% on our EC2 bills for those environments.</p><p>We played around with a few ways to achieve this, but the simplest ended up being <a href="http://docs.aws.amazon.com/autoscaling/latest/userguide/schedule_time.html">AWS Auto Scaling Groups Scheduled Actions</a>. You can set these up using the AWS console, CLI, or another tool like Terraform.</p><h3>Using the AWS Console</h3><p>Find your Auto Scaling Group (called <em>convox-&lt;rack&gt;-Instances-&lt;id&gt;</em>), and switch to the Scheduled Actions tab:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-eoQtSzpTpIbkli_y_gTg.png" /></figure><p>Create the Scale Down action by clicking on the <em>Create Scheduled Action</em> button, and fill in the form:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*pNh_WBr3rAoq-Ufzzl6I_A.png" /><figcaption>Make sure to adjust the cron schedule to fit your requirements — and make sure you convert the times to UTC</figcaption></figure><p>Create the Scale Up action by clicking on the Create Scheduled Action button, and fill in the form:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/1*GCLwAWk_Byl07Nt4RiVA0Q.png" /><figcaption>Note: the default Max for a convox rack is 100, and we only want to scale up Monday — Friday</figcaption></figure><p>When you’re done, you should be have something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4HZs66nLrTJFi7gyBJuncg.png" /></figure><h3>Using the AWS CLI</h3><p>If you want to automate things a bit more, you can configure the scheduled actions using the AWS CLI. Create the following files:</p><p><strong>down.json</strong></p><pre>{<br>    &quot;AutoScalingGroupName&quot;: &quot;convox-&lt;rackname&gt;-Instances-&lt;id&gt;&quot;,<br>    &quot;ScheduledActionName&quot;: &quot;ScaleDown&quot;,<br>    &quot;Recurrence&quot;: &quot;0 0 * * *&quot;,<br>    &quot;MinSize&quot;: 0,<br>    &quot;MaxSize&quot;: 0,<br>    &quot;DesiredCapacity&quot;: 0<br>}</pre><p><strong>up.json</strong></p><pre>{<br>    &quot;AutoScalingGroupName&quot;: &quot;convox-&lt;rackname&gt;-Instances-&lt;id&gt;&quot;,<br>    &quot;ScheduledActionName&quot;: &quot;ScaleUp&quot;,<br>    &quot;Recurrence&quot;: &quot;0 12 * * MON-FRI&quot;,<br>    &quot;MinSize&quot;: 0,<br>    &quot;MaxSize&quot;: 0,<br>    &quot;DesiredCapacity&quot;: 0<br>}</pre><p>And then run the following:</p><pre>$ aws autoscaling put-scheduled-update-group-action --cli-input-json file://down.json<br>$ aws autoscaling put-scheduled-update-group-action --cli-input-json file://up.json</pre><h3>Using Terraform</h3><p>We are using Terraform to manage things like this which are outside of Convox’ scope (another post coming soon!), so we created a simple module we can use for our dev environments to set up these scheduled actions for us:</p><p><strong>modules/dev_scaling_schedule/main.tf</strong></p><pre>variable &quot;asg_name&quot; {} </pre><pre>variable &quot;scale_up_capacity&quot; {  <br>  type    = &quot;string&quot;  <br>  default = &quot;4&quot;<br>}</pre><pre>variable &quot;scale_down_recurrence&quot; {  <br>  type    = &quot;string&quot;  <br>  default = &quot;45 0,6 * * *&quot; # UTC<br>} </pre><pre>variable &quot;scale_up_recurrence&quot; {  <br>  type    = &quot;string&quot;  <br>  default = &quot;15 12 * * MON-FRI&quot; # UTC<br>} </pre><pre>variable &quot;min_size&quot; {  <br>  type    = &quot;string&quot;  <br>  default = &quot;1&quot;<br>} </pre><pre>variable &quot;max_size&quot; {  <br>  type    = &quot;string&quot;  <br>  default = &quot;100&quot;<br>} </pre><pre>resource &quot;aws_autoscaling_schedule&quot; &quot;scale_down&quot; {  <br>  autoscaling_group_name = &quot;${var.asg_name}&quot;  <br>  scheduled_action_name  = &quot;ScaleDown&quot;  <br>  recurrence             = &quot;${var.scale_down_recurrence}&quot;       <br>  desired_capacity       = 0<br>} </pre><pre>resource &quot;aws_autoscaling_schedule&quot; &quot;scale_up&quot; {    <br>  autoscaling_group_name = &quot;${var.asg_name}&quot;  <br>  scheduled_action_name  = &quot;ScaleUp&quot;  <br>  recurrence             = &quot;${var.scale_up_recurrence}&quot;  <br>  desired_capacity       = &quot;${var.scale_up_capacity}&quot;  <br>  min_size               = &quot;${var.min_size}&quot;  <br>  max_size               = &quot;${var.max_size}&quot;<br>}</pre><h3>Final Notes</h3><ul><li>Sometimes, a dev needs to do some work late in the evening, or on a weekend. We’ve created Jenkins jobs to allow our devs to turn the environment on/off as needed. We also added a second scale down time late at night in case the developer forgot to turn the rack back off.</li><li>It usually takes between 5–10 minutes for a rack to spin up and start all of the app processes.</li><li>We’re saving over $200/m by scaling our dev racks down during off hours. This will only grow as we increase instance sizes, counts and number of developer racks.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8847913e7c13" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>