<?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 Tom Rosenfeld on Medium]]></title>
        <description><![CDATA[Stories by Tom Rosenfeld on Medium]]></description>
        <link>https://medium.com/@trosenfeld?source=rss-20328b403851------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Ea-C-jW_9cU8kqGL.</url>
            <title>Stories by Tom Rosenfeld on Medium</title>
            <link>https://medium.com/@trosenfeld?source=rss-20328b403851------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:31:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@trosenfeld/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[Transitioning from RDS Performance Insights to CloudWatch Database Insights]]></title>
            <link>https://medium.com/doit-international/migrate-aws-rds-performance-insights-cloudwatch-database-insights-f63e9c08a1cd?source=rss-20328b403851------2</link>
            <guid isPermaLink="false">https://medium.com/p/f63e9c08a1cd</guid>
            <category><![CDATA[aurora]]></category>
            <category><![CDATA[rds]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Tom Rosenfeld]]></dc:creator>
            <pubDate>Fri, 18 Jul 2025 09:01:29 GMT</pubDate>
            <atom:updated>2025-11-04T10:31:33.028Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Is the new pricing worth it?</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HHB4FdGlU36BL4ib.png" /></figure><p>AWS is changing its database observability solution. AWS announced the new <strong>CloudWatch Database Insights (DBI)</strong> in December 2024. This offering is similar to the older <strong>RDS Performance Insights</strong> <strong>(PI)</strong> that has been available for years. However, AWS has announced the end-of-life for Performance Insights, s̶c̶h̶e̶d̶u̶l̶e̶d̶ ̶f̶o̶r̶ ̶N̶o̶v̶e̶m̶b̶e̶r̶ ̶3̶0̶,̶ ̶2̶0̶2̶5, now extended to June 30, 2026. Here’s what you need to know about the transition, feature differences, new pricing, and actionable steps to ensure uninterrupted monitoring and data retention.</p><p>Both tools feature database performance tuning and monitoring with prebuilt dashboards. Database Insights is very similar to the older Performance Insights, and is in fact based on it. The new interface looks slightly different since it is in the CloudWatch console instead of RDS. If you are already familiar with PI, you will understand the basics of DBI.</p><h3>Free and paid versions</h3><p>There are 2 modes of operation:</p><ul><li>Database Insights Standard — free</li><li>Database Insights Advanced — paid</li></ul><p>All new RDS and Aurora DBs will have DBI standard mode enabled by default. That includes a rolling seven days of performance data history, just like the old PI. You can opt into the paid advanced mode to get 15 months of history and additional features, as discussed below.</p><h3>Feature Comparison: PI vs. DBI</h3><h4><strong>Where to Find It</strong></h4><ul><li>PI is accessible from the RDS console.</li><li>DBI is accessed via the CloudWatch console, though a link remains in the RDS console.</li></ul><h4><strong>Capabilities Overview</strong></h4><ul><li><strong>PI:</strong> Assessed the load on a single DB instance through a pre-built dashboard.</li><li><strong>DBI:</strong> Extends these insights with fleet-level metrics, integration with AWS Application Signals, richer metric/log/event correlation, and advanced root-cause analysis (e.g., lock diagnostics and execution plan analysis).</li></ul><h4><strong>Notable Improvements in DBI</strong></h4><ul><li>Visualize metrics across clusters and fleets (not just individual instances).</li><li>Deeper integration with logs, though, requires Advanced mode.</li><li>New features like Lock Analysis for PostgreSQL.</li></ul><h4><strong>Key Downgrades or Limitations</strong></h4><ul><li>Some features previously free (e.g., OS process analysis, execution plan capture) now require the paid tier.</li><li>Paid retention is reduced from 24 months (PI) to 15 months (DBI).</li><li>Advanced DBI must be enabled — and paid for — at the cluster (not instance) level.</li></ul><figure><img alt="Feature comparison" src="https://cdn-images-1.medium.com/max/694/1*Au3vSv5P1EzVsWkDcAs8_g.png" /><figcaption>Feature comparison</figcaption></figure><h3>Pricing: More Features — but Much More Expensive</h3><p>Confusingly, the AWS pricing page shows DBI priced by the vCPU-<strong>hour</strong>, while PI is priced at vCPU-<strong>month</strong>. So at first glance, the new pricing looks cheaper, until you realize that you need to multiply it by 730 to get hours per month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/437/1*n4x1Y8gVxRkvl0c0NWgH9Q.png" /><figcaption>Price comparison (assuming 1-month retention of PI)</figcaption></figure><p>In addition to the higher price per vCPU, DBI requires enabling it on the whole cluster, including all replicas. So, you cannot choose to enable it on just selected instances as you could with PI.</p><p>Another gotcha is that with DBI, you are billed for each hour, even if you temporarily stop your cluster.</p><p><strong>Bottom Line:</strong> DBI Advanced costs about 6x as much as PI (paid) for the same retention.</p><h3>Migration Steps and Recommendations</h3><h4><strong>Key Dates</strong></h4><ul><li><strong>Performance Insights EOL:</strong> November 30, 2025.</li><li><strong>Free trial period:</strong> If you upgrade an existing cluster before November 30, 2025, you may be eligible for credits covering incremental costs through the end of 2025. (You should have gotten an email from AWS if you qualify.)</li></ul><h4><strong>What You Should Do Now</strong></h4><ol><li><strong>Inventory:</strong> Identify all instances with PI enabled and decide if you require features only in DBI Advanced (i.e., long retention, execution plans, advanced analysis).</li><li><strong>Choose a mode:</strong> Determine if DBI Standard suffices for short-term (7 days) metrics, or enable Advanced for extended retention and features.</li><li><strong>Upgrade proactively:</strong> Enable DBI Advanced before EOL to avoid historical data loss. (However, even in Advanced, the retention cap is 15 months.)</li></ol><h4><strong>If You Take No Action</strong></h4><ul><li>Your DBs will default to DBI Standard after EOL, and you will lose access to metrics older than 7 days and to advanced features.</li></ul><h3>References</h3><ul><li><a href="https://aws.amazon.com/blogs/aws/new-amazon-cloudwatch-database-insights-comprehensive-database-observability-from-fleets-to-instances/">New Amazon CloudWatch Database Insights: Comprehensive database observability from fleets to instances | AWS News Blog</a></li><li><a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_DatabaseInsights.html">Monitoring Amazon RDS databases with CloudWatch Database Insights — Amazon Relational Database Service</a></li><li><a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Database-Insights.html">CloudWatch Database Insights — Amazon CloudWatch</a></li><li>List of DBI Advanced mode features: <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Database-Insights.html">https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Database-Insights.html</a></li></ul><h3>Call to Action</h3><p>Need more help with your database resources? Visit us at <a href="http://doit.com/expertise">doit.com/expertise</a> for more tips.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f63e9c08a1cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doit-international/migrate-aws-rds-performance-insights-cloudwatch-database-insights-f63e9c08a1cd">Transitioning from RDS Performance Insights to CloudWatch Database Insights</a> was originally published in <a href="https://medium.com/doit-international">DoiT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RDS Storage: GP3, GP2 and Provisioned IOPS Cost Comparison]]></title>
            <link>https://medium.com/doit-international/rds-storage-gp3-gp2-and-provisioned-iops-cost-comparison-dc70216b6dca?source=rss-20328b403851------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc70216b6dca</guid>
            <category><![CDATA[ebs-volume]]></category>
            <category><![CDATA[ssd]]></category>
            <category><![CDATA[rds]]></category>
            <category><![CDATA[amazon-web-services]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Tom Rosenfeld]]></dc:creator>
            <pubDate>Tue, 05 Mar 2024 12:59:58 GMT</pubDate>
            <atom:updated>2024-08-13T16:21:39.915Z</atom:updated>
            <content:encoded><![CDATA[<h4>So you want to create an RDS database in AWS, but which storage option to choose?</h4><p>This article highlights some of the issues and best practices for choosing the most cost effective SSD Volumes in RDS.</p><p>There are three choices for SSD storage in RDS. Amazon RDS offers two types of General Purpose SSD storage: <strong>gp2 </strong>or <strong>gp3</strong>. In addition, there is Provisioned IOPS SSD <strong>io1</strong>. (There is also the old magnetic storage, which is too slow for most applications. Note that io2, available in EBS, is not yet supported in RDS).</p><ul><li><strong>gp2 </strong>— Older generation, IOPS depends on the size of the volume, burstable</li><li><strong>gp3 </strong>— Current generation, consistent IOPS, comes with baseline IOPS but can purchase additional IOPS and throughput</li><li><strong>io1 </strong>— (Sometimes known as PIOPS). Consistent performance, Provisioned IOPS must be purchased. Most expensive.</li></ul><p>All three storage types provide single-digit millisecond latency.</p><p>The cost per GB is the same for gp2 or gp3 in RDS (unlike in EC2 where gp3 is cheaper). However, gp3 provides more baseline IOPS (for volumes up to 4,000 GB) without the limitation of bursting.</p><h3>Pricing matrix spreadsheet</h3><p>The following spreadsheet shows the details of pricing and IOPS for a given size volume in gp2 vs. gp3 vs. io1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*xjqUUPUWpaPdW672MwrmAQ.png" /><figcaption>SSD Volume cost comparison</figcaption></figure><p>Here are some examples from above:</p><p>If you have a 1,000GB volume, you will get 12,000 sustained IOPS on gp3. On gp2 you will get the same 12,000 IOPS, but only for limited bursts. Your sustained IOPS is only 3,000. Both will cost the same $115. Using io1 PIOPS configured with the same 12,000 IOPS, you will $425!</p><p>If you need a 5,000GB volume, gp2 will give you 15,000 IOPS for $525. For the same price, gp3 will only give you 12,000 IOPS (although you could pay more to get more). io1 PIOPS would cost much more at $2,125.</p><h3>RDS disk striping</h3><p>All the RDS engines (except for MS SQL Server) stripe on 4 volumes after a certain minimum size. This means both gp2 and gp3 give a higher IOPS and throughput than you would normally expect as shown above.</p><p>Striping details:</p><ul><li>MariaDB, MySQL, and PostgreSQL stripes for sizes above 400 GB</li><li>Oracle stripes above 200GB</li><li>Increasing an existing volume size that triggers a volume striping activity (e.g. &gt; 400GB) can cause a significant increase in IOPS and latency for several hours during the modification.</li></ul><p>See AWS for details on DB type and size [3].</p><h3>So which storage type should you use?</h3><p>In almost all cases, your default choice should be gp3. In the past, even for small IOPS needs, AWS recommended io1 for low consistent latency. However, now both io1 and gp3 offer single-digit millisecond latency. The only difference is that io1 provides it 99.9% of the time, while gp3 guarantees it “only” 99.0% of the time. Given that gp3 is up to 73% less expensive than io1 (assuming the io1 is configured with the same baseline as the gp3), this is an easy choice.</p><p>When you should use io1:</p><ul><li>need more than 64,000 IOPS</li><li>need consistent performance better than 99.0% of the time</li></ul><h3>Modifying volume type on a running DB:</h3><ul><li>In general, there is<strong> no downtime</strong> for changes between io1, gp2 or gp3 [2]</li><li>However, you cannot make more than one change every 6 hours</li></ul><h3>FAQ</h3><h4>Should I use io1 + PIOPs?</h4><ul><li>Only if you need 64,000–256,000 IOPS (or over 4,000 Mbps throughput)</li><li>If you need I/O consistency of 99.9% vs. 99% for gp2 or gp3</li><li>It will cost you 270% more than gp2/gp3</li><li>Even though the AWS console shows io1 as the default (for some configuration templates), you can change it to gp3 (or other).</li></ul><h4>Should I ever create a new RDS DB with gp2?</h4><ul><li>Yes. If your required volume size is over 4,000 GB. In that case, the gp2 IOPS will be greater than the baseline gp3 would give (see the sheet above). If you need more IOPS than the gp2 baseline, it will be cheaper to use gp3 and buy the extra IOPS.</li></ul><h4>Should I convert from io1 to gp3 (or gp2)?</h4><ul><li><strong>Yes!</strong> Assuming you need less than 64,000 IOPS you should convert to save up to 73% (see sheet).</li></ul><h4>Should I convert from gp2 to gp3?</h4><p>It depends:</p><ul><li>If it aint broke don’t fix it. No cost savings. Performance could get <strong>worse </strong>— see Gotchas below.</li><li>If the volume size is over 4,000 GB, gp3 will give fewer IOPS (unless you pay for more).</li><li>If your workload needs more IOPS than you are getting with gp2 then convert to gp3 and pay for any more needed IOPS.</li><li><strong>Caveat</strong>: Like any DB modification, the best practice is to first clone your DB and then test the conversion. Make sure that gp3 is giving you the expected IOPS and throughput.</li></ul><h3>Gotchas</h3><ul><li>Growing past 400 GB initiates striping and consumes a significant amount of IOPS during the process, which could seriously affect latency. Therefore, it is best to start at 400 GB if you expect to grow soon. Oracle stripes at 200 GB, while MS SQL Server never stripes.</li><li>RDS storage autoscaling can be the source of many surprises. Be sure to understand all the limitations [1]. For example, it could unexpectedly initiate striping.</li><li>AWS might be giving you more IOPS than you pay for on your current gp2 volume. (This is especially true for workloads that are years old). Thus, if you change to gp3, you may lose the free IOPS and get worse performance. (You can check this in Cloudwatch and see if you are getting higher than expected IOPS.)</li><li>Per instance type IOPS limitations: All RDS instances are limited in bandwidth and IOPS. Even if you pay for PIOPS, your instance will throttle you if it is not big enough. The limitations per instance type can be found in the AWS EC2 doc [4].<br>e.g.: <br><strong>c6g.4xlarge</strong> limited to<strong> </strong>20,000 IOPS<strong><br>c7g.4xlarge</strong> limited to 20,000 IOPS but can burst 40,000</li></ul><h3>Bottom line</h3><p>Be mindful when selecting the storage type for your RDS instances. You can usually save a bundle by selecting gp3 instead of io1 without sacrificing performance.</p><p>References:</p><p>[1] <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PIOPS.StorageTypes.html#USER_PIOPS.Autoscaling">Managing capacity automatically with Amazon RDS storage autoscaling</a> [2] <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.DBInstance.Modifying.html">Modifying an Amazon RDS DB instance</a><br>[3] <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Storage.html">Amazon RDS DB instance storage — Amazon R</a>DS<br>[4] <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html">Amazon EBS–optimized instances — Amazon Elastic Compute Cloud</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc70216b6dca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doit-international/rds-storage-gp3-gp2-and-provisioned-iops-cost-comparison-dc70216b6dca">RDS Storage: GP3, GP2 and Provisioned IOPS Cost Comparison</a> was originally published in <a href="https://medium.com/doit-international">DoiT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>