title: Using S3 as a database vs. database (e.g. MongoDB)
body: <p>Due to simple setup and low costs I am considering using AWS S3 bucket instead of a NoSQL database to save simple user settings as a JSON (around 30 documents).</p>
  
  <p>I researched the following disadvantages of not using a database which are not relevant for my use case:</p>
  
  <ul>
  <li>Listing of buckets/files will cost you money.</li>
  <li>No updates - you cannot update a file, just replace it.</li>
  <li>No indexes.</li>
  <li>Versioning will cost you $$.</li>
  <li>No search</li>
  <li>No transactions</li>
  <li>No query API (SQL or NoSQL)</li>
  </ul>
  
  <p>Are there any other disavantages of using a S3 bucket instead of a database?</p>