These are my links for 10 giu 2015 through 15 giu 2015:
- coderwall.com : establishing geek cred since 1305712800 – Setting up an EC2 instance on AWS used to be as straightforward as provisioning a machine and SSHing into it. However, this process has become a bit more complicated now that Amazon VPC has become the standard for managing machines in the cloud.
- Set up public and private subnets using AWS VPC — Mike Melnicki’s Blog – This is a step-by-step guide on how to set up public and private subnets for running a service on an internal network within AWS. This guide will also set up a bastion host (or jump host) and show you how you can easily ssh in to the hosts within your private subnet via the bastion host. All of this stuff can be done via the AWS web console, but I thought it would be helpful to show the specific commands and provide some commentary about what is happening on each step.
- WordPress Checklist (Infographic): 101 Easy Steps to Follow. – It’s a big struggle in remembering the steps involved in setting up a WordPress website. And we soon realized that, there were hardly any checklists that covered all the aspects of WordPress together! That’s when we decided to create “Killer WordPress Checklist” that would cover everything from the pre-launch directions and development process, to SEO, maintenance and security. Honestly, this checklist has worked wonders for us and hope it does for you too!
- Monitoring EC2 Memory and Disk Usage In CloudWatch Using Custom Metrics | Celingest Blog – Feel the Cloud – With CloudWatch we can track and monitor a lot of metrics across many AWS’s products and set alarms when certain conditions are met. When these alarms are triggered, they can notify us or automate actions such as shrinking or increasing an AutoScaling Group capacity. CloudWatch knows a lot about our EC2 instances’ at the hardware level but it lacks the software’s point of view. In this post we will explain how to use CloudWatch to monitor important resources it can’t monitor by default.
These are my links for 29 mag 2015 through 10 giu 2015:
- My Blog: AWS EC2 Auto Scaling: Basic Configuration – Our goal: Create an Auto Scaling EC2 Group in a single Availability Zone and use a HTTP status page as a Health Monitor for our Load Balancer and the Auto Scaling group instances. This exercise will show us some Auto Scaling basics and will be useful to understand the concepts beneath but the Auto Scaling Group will not automatically "scale" responding to external influence like Average CPU Usage or Total Apache Connections (This aspect is covered in this post: AWS EC2 Auto Scaling: External CloudWatch Metric). With the Auto Scaling configuration described here, we will obtain a web server cluster that can be increased and decreased in members with a simple Auto Scaling API call and we will transfer the monitoring role to the ELB to automatically replace failed EC2 instances or web servers.
- Autoscaling with custom metrics « That’s Geeky – One of the appeals of cloud computing is the idea of using what you need when you need. One of the ways that Amazon provides for this is through autoscaling. In essence, this allows you to vary the number of (related) running instances according to some metric that is being tracked. In this article, we look at how you can trigger a change in the number of running instances using a custom Cloudwatch metric – including the setup of said metric, and a brief look at the interactions between the various autoscaling commands used.
- Painless AWS Auto Scaling With EBS Snapshots And Capistrano – Boom – AWS (Amazon Web Services) auto scaling is a simple concept on the surface: You get an AMI, set up rules, and the load balancer takes care of the rest. However, actually getting it done is more complicated. Some choices are worse than others: you could bake an AMI (Amazon Machine Image) before you deploy, but that could add 10 minutes or more to each deployment. Some are dangerous: you could create an AMI after each deploy, but you run the risk that an auto scale even happens before your AMIs are done. Plus, you have a whole variety of AMIs deployed in at any given time. Some are similar to what we propose in this tutorial: you could push your code to S3 on each deploy and have user-data scripts that pull it down on each auto scaling event. However you slice it, to get auto scaling to fit into your development work flow in a transparent way takes careful thought and planning. We recently rolled out the following solution at CodePen. It keeps our AMIs static and our application ready for scaling on EBS (Elastic Block Store) snapshots. We can push code using Capistrano and let a few scripts distribute the ever-changing code base to our fleet of servers. I’d like to share the steps required to make it work. This series of posts will walk you through the steps required to build an auto-scaling infrastructure that stays out of your way.
- coderwall.com : establishing geek cred since 1305712800 – Did you accidentally set node.normal[:foo][:bar] = 'something bad' in your chef recipe? Then you found that the node's normal attributes persisted between chef runs, and you really wanted to use the default attribute precedence level in your cookbook's attributes/default.rb file?