<?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 CloudCosts on Medium]]></title>
        <description><![CDATA[Stories by CloudCosts on Medium]]></description>
        <link>https://medium.com/@cloudcosts?source=rss-e28364014e8a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CoPq7TccWoCSzODJvkLOyg.png</url>
            <title>Stories by CloudCosts on Medium</title>
            <link>https://medium.com/@cloudcosts?source=rss-e28364014e8a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:35:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cloudcosts/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[Free, fast and scalable side projects on AWS]]></title>
            <link>https://medium.com/@cloudcosts/free-fast-and-scalable-side-projects-on-aws-aa8012b2ba72?source=rss-e28364014e8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa8012b2ba72</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[CloudCosts]]></dc:creator>
            <pubDate>Thu, 11 Apr 2019 04:14:21 GMT</pubDate>
            <atom:updated>2019-04-11T04:14:21.499Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IYnpCvvvMeLp-nFNbNCGLQ.jpeg" /></figure><p>When building out new side projects it’s often fun to work with hosting platforms like Heroku or Now. The downside is that when it comes to scale your application when all those new users show up, you may be stuck with big bills or solutions that don’t meet security standards.</p><p>We run the <a href="https://cloudcosts.io/">cloudcosts.io</a> infrastructure on the AWS free tier. This gives us the flexibility of having almost zero infrastructure costs monthly, the ability to adopt industry standard security practices and be able to scale up at a moments notice. We don’t have to worry about a successful side project outgrowing the hosting platform. In this post I want to share some of the cost effective solutions for running your project.</p><h3>1. Email using SES</h3><p>SES is one of the cheapest and most reliable email platforms that can handle inbound and outbound emails. You don’t need to pay for GSuite or Sendgrid. Send application emails, business emails and receive support requests through SES. This will minimize your costs and also significantly simplify your infrastructure.</p><p>SES can handle forwarding emails by wiring up a lambda function which forwards an email upon receiving a message. You can also send emails from your own personal Gmail account through SES. This will make sure that your support requests hide your personal email. The guides below cover everything that you need to set this up.</p><p>Guides:</p><ul><li>Email forwarding module: <a href="https://github.com/ColDog/ses-email-forwarder">https://github.com/ColDog/ses-email-forwarder</a></li><li>SES sending email: <a href="https://docs.aws.amazon.com/ses/latest/DeveloperGuide/sending-email.html">https://docs.aws.amazon.com/ses/latest/DeveloperGuide/sending-email.html</a></li><li>Using Gmail: <a href="http://www.daniloaz.com/en/use-gmail-with-your-own-domain-for-free-thanks-to-amazon-ses-lambda/">http://www.daniloaz.com/en/use-gmail-with-your-own-domain-for-free-thanks-to-amazon-ses-lambda/</a></li></ul><h3>2. Free tier sql databases</h3><p>One of the best offerings on AWS is the free tier RDS (Relational Database Service). With a new AWS account, you will receive a free (micro sized) database instance for up to a year. This is perfect for your side project and can keep costs low. And if the day comes where need to scale this database up, you are running on one of the most reliable platforms for managing SQL databases.</p><p>One tip here — if you want to run multiple side projects — use a single micro database instance and simply create a different schema inside the database. This can stretch costs out significantly.</p><h3>3. CloudFront CDN</h3><p>The CloudFront CDN has a very generous free tier that you are unlikely to hit for a small side project. The big advantage with CloudFront is that you can easily add a secure and fast serving layer in front of your application. If you add AWS Certificate Manager, you’ll have SSL in front of your application for free and the certificates will renew automatically!</p><p>Guides:</p><ul><li>CloudFront static site hosting: <a href="https://aws.amazon.com/premiumsupport/knowledge-center/cloudfront-serve-static-website/">https://aws.amazon.com/premiumsupport/knowledge-center/cloudfront-serve-static-website/</a></li></ul><h3>4. Elastic Container Service</h3><p>The ECS product is probably one of the more complex products on this list. It handles a lot of functions on AWS and is tricky to wrap your head around. The main selling point for your side project is that you can store docker containers and run a simple dockerized application for free. You just need to pick an underlying EC2 instance that is on the free tier.</p><p>This may feel like overhead compared to your simple Heroku stack, but it’s worth it in the long run. Building a dockerized version of your application will keep your application in a maintainable state in the long run and allow you to scale up with ECS.</p><p>The best way to get started with ECS is to run through the ‘first time’ guide. Check out some of the guides and documentation as well below which can help you out.</p><p>Guides:</p><ul><li>Getting started with ECS: <a href="https://medium.freecodecamp.org/amazon-ecs-terms-and-architecture-807d8c4960fd">https://medium.freecodecamp.org/amazon-ecs-terms-and-architecture-807d8c4960fd</a></li><li>A simple ECS deploy script: <a href="https://gist.github.com/ColDog/aa967716e8694fd34506edf258b107aa">https://gist.github.com/ColDog/aa967716e8694fd34506edf258b107aa</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa8012b2ba72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Launching CloudCosts — How to stop that surprise AWS bill]]></title>
            <link>https://medium.com/@cloudcosts/launching-cloudcosts-how-to-stop-that-surprise-aws-bill-42bd2694128?source=rss-e28364014e8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/42bd2694128</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[CloudCosts]]></dc:creator>
            <pubDate>Wed, 23 Jan 2019 15:34:23 GMT</pubDate>
            <atom:updated>2019-01-23T15:34:23.606Z</atom:updated>
            <content:encoded><![CDATA[<h3>Launching CloudCosts — How to stop that surprise AWS bill</h3><p><em>See the platform at </em><a href="https://cloudcosts.io/"><em>cloudcosts.io</em></a><em>.</em></p><p>Have you read posts like <a href="https://www.reddit.com/r/aws/comments/8nc8i9/massive_unexpected_aws_bill/">“My massive unexpected AWS bill”</a> or <a href="https://medium.com/@morgannegagne/a-very-expensive-aws-mistake-56a3334ed9ad">“A very expensive AWS mistake”</a>? Have you ever left infrastructure for your school project or other ideas running? CloudCosts is our new attempt at launching a platform for the hackers, creators and builders of the world that struggle with maintaining and managing infrastructure costs for their personal projects or even products that they manage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*UosBXrqM3APV1yXe" /></figure><p>I remember being on vacation and opening my email to an AWS bill of over $400 because I had forgotten to turn off a service before jumping on a plane. This is a simple problem that almost every developer I’ve met has.</p><p>The platform that we’ve built simply ingests cost metrics from your AWS (and eventually google cloud) accounts and provides simple graphs and alerts on when your spending has changed. Get notified daily of your forecasted spend and changes to your daily spend, and don’t worry, our forecasting methods factor out those one time costs so you can rely on the forecast that your are getting.</p><p>This platform is built by and for developers who want to build and create great things but have the billing get out of the way. Sign up over at <a href="https://cloudcosts.io/">cloudcosts.io</a> and join our <a href="https://gitter.im/CloudCosts-io/community">gitter</a> to start the conversation about how we can manage our costs better so we can all get back to building the things we love.</p><p>Want to read some more funny and sad stories about big infrastructure bills? We’ve curated a list in our <a href="https://gitter.im/CloudCosts-io/community">gitter</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42bd2694128" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>