AWS OpsWorks - Flexible Application Management in the Cloud Using Chef. It’s been over six years since we launched Amazon EC2.
After that launch, we’ve delivered several solutions that make it easier for you to deploy and manage applications. Two years ago we launched AWS CloudFormation to provide an easy way to create a collection of related AWS resources and provision them in an orderly and predictable fashion and AWS Elastic Beanstalk that allows users to quickly deploy and manage their applications in the AWS cloud. As our customers run more applications on AWS they are asking for more sophisticated tools to manage their AWS resources and automate how they deploy applications.
AWS OpsWorks features an integrated management experience for the entire application lifecycle including resource provisioning, configuration management, application deployment, monitoring, and access control. It will work with applications of any level of complexity and is independent of any particular architectural pattern. Quickstart tutorial on how to deploy an API on Amazon EC2 for Amazon Web Services (AWS) rookies - 3scale API Management Platform & Infrastructure.
At 3scale we find Amazon to be a fantastic platform for running APIs due to the complete control you have on the application stack.
For people new to AWS the learning curve is quite steep. So we put together our best practices into this short tutorial. Besides Amazon EC2 we will use the Ruby Grape gem to create the API interface and an Nginx proxy to handle access control. Best of all everything in this tutorial is completely FREE :) Broken PMTUD on Amazon EC2. While at Amazon re:invent I had the opportunity to complain to some Amazonians again about an EC2 bug which has been annoying me for a long time: The default firewall rulset is broken.
I discovered this three years ago while debugging odd problems experienced by a Tarsnap user — sending a small amount of traffic worked fine, but as soon as large amounts of traffic started moving around, the TCP connection got stuck — and I've been complaining from time to time ever since; but somehow face-to-face communications tend to produce better results than mere emails. As most standards-aware network administrators know, blocking ICMP is evil.
Surviving AWS Failures with a Node.js and MongoDB Stack. Node+Mongo on EC2 is a very popular software stack among web services developers.
There are many user guides on how to design such a system with built-in redundancy so that even coordinated failures don’t bring down the service. The absolute minimum for a resilient service requires a MongoDB replica set behind a load-balanced node farm. However, you are not ready for an EC2 outage until you have deliberately shutdown components in your system and verified the expected behavior. As you periodically do this, you might discover that there are gaps you did not account for. In this blog I want to share our experiences beyond the initial configuration and add some fine details on creating a Node+Mongo application that is both secure and resilient to common EC2 failures. Connecting to Instances. Amazon Elastic Compute Cloud User Guide (API Version 2014-02-01) Connect to Your Instance This section describes how to connect to instances that you launched and how to transfer files between your local computer and your instance.
After you connect to your instance, you can try one of our tutorials, such as Tutorial: Installing a LAMP Web Server or Tutorial: Hosting a WordPress Blog with Amazon EC2.