Running Elasticsearch cluster is not cheap, as it generally requires a couple of high spec servers to provides both performances and reliabilities. Below is a typical 3 nodes Elasticsearch cluster that is running on AWS: 3 nodes, one in each availability zone. each node is both master and data node, and it is formed by ec2 … Continue reading Run Elasticsearch Cluster on Spot Instances
Our nonprod environments have quite a lot Elastic Beanstalk environments. Most of them serves low traffics .Each ELB roughly costs $20 per month (no matter you use it or not) + data cost. From the cost perspective, I don't see there is a value that each of them needs a dedicated ELB (which was created by Elastic … Continue reading Consolidate Elastic Beanstalk ELB
We noticed that one of our Java applications that is deployed on Elastic Beanstalk has hourly service interruption. Each outage only lasts for about 40 - 60 seconds. By looking at the CloudWatch, the ELB has intermittent 5xx errors every one hour, like 09:01, 10:01, 11:01 ... After some investigations, I found it out that it … Continue reading Hourly Intermittent Elastic Beanstalk Service Interruption
Continue with yesterday's good news, another exciting new feature on EBS - Elastic Volumes. It allows you to dynamically increase capacity, tune performance, and change the type of any new or existing current generation volume with no downtime or performance impact. Check it out: https://aws.amazon.com/ebs/details/#elasticvolumes
It was painful that you are unable to change the instance profile for existing EC2 instance. A good news is that you CAN now via AWS CLI!! Here is a step by step example.
Can AWS default VPC be deleted? I checked AWS documentations and it seems the following two are against each other. So I opened a ticket with AWS, and here is their answer: Technically yes, you can delete default VPC's and create a non-default VPC. Some services such as CloudFormer to create CloudFormation templates do searches … Continue reading Can AWS default VPC be deleted?
Just found out that even with the same version number, the stack solution release date could be different in different region. Therefore, the stack name for the same version could be different across regions. For example, solution stack java 7 tomcat 7 v1.1.0. In ap-southeast-2 region, the stack name is 64bit Amazon Linux 2014.09 v1.1.0 running … Continue reading Elastic Beanstalk – No Solution Stack named … found