The T family of instances are the best choice if you run a very small application, but occasionally it can handle sudden traffic spikes. If those spikes are becoming more and more common, your application is consuming the entire host bandwidth and sooner you’ll notice that you application is going to response slower than usual. In that case, the first instinct is to change the host type with a more powerful one, eventually with one that has fixed-performance (M type, C type, etc). But there is one more thing you can try: the T family offers a feature, named unlimited mode. While this is activatedRead More →

As things stand today, we can say AWS IAM is one of the most important services. Understanding its concepts and its features could make the difference between an average AWS engineer and a top one. In this post, we want to present 2 types of users and some use cases for each of them. One of the first best practices you should put in practice is to avoid using the root user. That means you have to create different IAM users for each engineer that access AWS, but also for applications that make calls to AWS. Basically, a IAM user is a user that isRead More →

Excluding costs, there are 2 main things that makes AWS great: large number of services offered and integration between those services. And for the last category, a good example is the integration between AWS S3 and Glacier. With only few clicks in the S3 console, you can create a lifecycle rule that automatically moves objects from S3 to Glacier. And this rule can be applied on the whole bucker or per key prefix or per tags. Sounds great, no? Yes, it is. But there is a very important aspect you should consider before setting such a rule. Do you remember that long time ago weRead More →