<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Aurora on FivexL. Cloud Engineering Specialists</title>
    <link>/tags/aurora/</link>
    <description>Recent content in Aurora on FivexL. Cloud Engineering Specialists</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <managingEditor>info@fivexl.io (FivexL)</managingEditor>
    <webMaster>info@fivexl.io (FivexL)</webMaster>
    <lastBuildDate>Tue, 16 Dec 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/aurora/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MVP: PostgreSQL on AWS in 10 Minutes</title>
      <link>/blog/mvp-on-aws-part-3/</link>
      <pubDate>Tue, 16 Dec 2025 00:00:00 +0000</pubDate><author>info@fivexl.io (FivexL)</author>
      <guid>/blog/mvp-on-aws-part-3/</guid>
      <description>&lt;p&gt;A lot of MVP teams pick PostgreSQL because it&amp;rsquo;s familiar, powerful, and boring in the best way. Then they open the AWS console, click through defaults, and accidentally create a database that&amp;rsquo;s hard to secure, annoying to operate, and painful to make audit-friendly later.&lt;/p&gt;&#xA;&lt;p&gt;In our work with startups, this is one of the most common patterns: the product ships fast, the first customers arrive… and suddenly you need tighter security, better logging, sane network boundaries, and fewer &amp;ldquo;who created this?&amp;rdquo; mysteries.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
