The massive computing and storage resources that are needed to support big data deployments in general, and Hadoop in particular, make cloud environments, public and private, an ideal fit. Managing your big data app, however, is no walk in the park - especially when considering the fact that these systems and application stacks often include other services beyond Hadoop such as: relational databases, other NoSQL databases and more, where each framework comes with its own management, installation, configuration, and scaling solutions.
We use EBS volumes for persistent storage. To ensure we do not lose data and take backup regularly, AWS provides mechanism to take snapshot. Learn more on how to snapshot an EBS volume. In this guide, we will show, how to automate snapshots for an AWS EBS volume by schedule an automatic cron job. We will use Linux instance and see how to automate the snapshot using cronjobs.
It happened again… this was the second AWS outage in the same month. Did you fail to protect your service online? Don’t forget – you can’t pass your liability onto your IaaS vendor.
You can find a great amount of knowledge resources with regards to AWS cloud High Availability architectures in Newvem’s resources center, starting from Best Practice for High Availability Deployment all the way to knowing more about how to maintain availability for your specific environment, such as how to maintain a failover to MSSQL DB server, or a case study on how to replicate PostgreSQL DB Between AWS Regions.
Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides resizable compute capacity in the cloud. Amazon Cloud Computing is a good choice if you want to deploy a very large scale network on the cloud that requires high availability, auto scaling and load balancing features.
This article is a quick introduction on designing to achieve High Availability (HA) with your AWS infrastructure architecture. We’ll start with a simple (and vulnerable) architecture design and work our way up to a complex multi-region setup. How far you go up these steps is up to you, depending on your uptime requirements (or SLAs) and budget.
An EBS Snapshot is a copy of an EBS volume at a particular point in time. A snapshot can be taken of a volume, regardless of whether or not the volume is attached to a running instance. A snapshot comprises data blocks that are incrementally saved to Simple Storage Service (S3), meaning that only the blocks on the device that have changed since your last snapshot are saved. When saved to S3, the snapshot is assigned a timestamp and unique AWS ID.
AWS Elastic Load Balancing (ELB) automatically distributes incoming traffic to your application to multiple EC2 instances that are attached to your Elastic Load Balancer. At any time, Elastic Load Balancing detects the unhealthy instances in the pool, and distributes the incoming traffic only to the healthy instances until the unhealthy ones are restored.
In order to achieve greater fault tolerance and thus higher availability, it is recommended to distribute your instances in different geographical zones so that if all the instances in a single datacenter are not healthy, as may occur when there is an outage, your application will run in a data center in a different zone.
The Cloud Service Level Agreement (SLA) discussion puts penalties and compensations on the table. Can we say that the compensation method the customer expects is the same as the Software as a Service (SaaS) vendor’s SLA provides?