I have just completed for a client a complete setup of a “SparkLab” on a cluster of AWS machines: the setup has been completely automated via a Bash script which I have published to this public github gist. The following is a copy of the README file there; the script can be used also on … More Building a Spark / SciPy / Cassandra “SparkLab” on AWS
Overview Deploying an application to AWS using Beanstalk and setting up autoscaling, monitoring and a number of other super useful features is very simple, and is extremely well-documented on AWS site. However, even when following the Beanstalk and Flask Getting Started guide, there are a few gotchas and areas that are less than clear. In the … More Deploying a Flask App to AWS Beanstalk
Or how to achieve bi-weekly releases at SaaS scale Background Almost exactly a year ago I joined RiverMeadow: a self-described “cloud mobility” SaaS platform, with the modest task of improving a product I was told was “ready for market” and a team that only needed “some improvement, and a better adoption of Engineering best practices” – in slightly … More From null to a hundred in six months
These are my notes from the talk at AWS re:Invent conference, more information about VPC can be found here.
AWS re:Invent post 3 of 3 A guiding principle for Amazon is its focus on “stuff that won’t change over time:” for example, it’s extremely unlikely that people will ever want stuff at higher prices or slower delivery. As an entrepreneur one should equally focus on the ‘basics’ of the respective problem domain: ask yourself, “what … More Fireside Chat with Jeff Bezos
Note – the first post (Notes about the AWS JDK) can be found here The following are the (minimally edited) notes I’ve taken while attending the session at AWS re:Invent conference in Las Vegas, NV on 27-30 November, 2012. Keynote speech by Andy Jassy (Sr. Vice President, Amazon Web Services) It is clear we are still at … More AWS re:Invent – my notes (post 2 of 3)
From Werner Vogels (Amazon.com CTO) keynote speech at re:Invent: ControllableArchitect with cost in mind ResilientDon’t treat failure as an exception AdaptiveMake no assumptions Data DrivenPut everything in logs