<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Rds on Puppeteers Oy</title>
		<link>https://www.puppeteers.net/tags/rds/</link>
		<description>Recent content in Rds on Puppeteers Oy</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Thu, 10 Aug 2023 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.puppeteers.net/tags/rds/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>How to reduce RDS storage size in an automated way</title>
				<link>https://www.puppeteers.net/blog/how-to-reduce-rds-storage-size-in-an-automated-way/</link>
				<pubDate>Thu, 10 Aug 2023 00:00:00 +0000</pubDate>
				<guid>https://www.puppeteers.net/blog/how-to-reduce-rds-storage-size-in-an-automated-way/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://puppeteers-public.hel1.your-objectstorage.com/pexels-jakub-zerdzicki-16978372.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Amazon RDS is a relational database service available on Amazon Web Services. It is essentially a managed database server with a volume for the data. Both cost money. Having a large dataset is not the only reason have big volume: the volume size determines the number of I/O operations (IOPS) the volume can do. If you have high load on your RDS instance you may very well run out of IOPS which can result in a disaster. Scaling up the volume size is easy to avoid such disasters, but it is much more difficult to reduce RDS storage size. This is because downsizing RDS storage size &lt;a href=&#34;https://repost.aws/knowledge-center/rds-db-storage-size&#34;&gt;is not officially supported by AWS&lt;/a&gt;. If the load on your RDS instance goes down (e.g. due to refactoring), you may end up having a database with an oversized volume that costs lots of money for no reason.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
