With the showcase, AWS re:Invent 2017 just around the corner, excitement is definitely building in the world of cloud computing. AWS re:Invent is a learning conference hosted by Amazon Web Services for the global cloud computing community. The event, which annually takes over the Las Vegas strip, features keynote announcements, training and certification opportunities. At the conference, attendees have access to more than 1,000 technical sessions, a partner expo, after-hours events, and so much more. Over the coming days, we will take a look at all of the latest AWS announcements leading up to re:Invent and will also feature the top releases from this year’s keynote speakers Peter DeSantis, (VP, AWS Global Infrastructure), Andy Jassy, (CEO, Amazon Web Services) and Werner Vogels, (Chief Technology Officer, Amazon.com)
If you’re already using Amazon Web Services (AWS), you’re probably more than familiar with its Simple Storage Service (S3). And while S3’s scalable storage infrastructure is certainly a popular method for saving your data in the cloud, Amazon Glacier is an alternative method that’s worth exploring.
While both services offer cloud-based storage, S3 and Amazon Glacier each have their own unique benefits. So depending on what type of data you need to store, and your reasons for storing it, using both services in conjunction might make practical and financial sense. In the following post, we’ll explain what Amazon Glacier is (and what it isn’t), and look at instances where the service might be a better option than S3.
In theory, everyone seems to agree on the need for a comprehensive disaster recovery (DR) plan. But for IT professionals tasked with ensuring AWS business continuity, theory and reality are two very different things. After all, finding vocal managerial support for a DR plan is one thing. Finding the actual funds to implement it is another.
When pitching a DR plan, it can be difficult, if not impossible, to project ROI. It’s hard to accurately gauge the value of something that will hopefully never be used. As with fire extinguishers or airbags, DR plans are usually taken for granted until something goes horribly wrong. For that reason, it might be better to frame a DR plan in terms of an insurance policy that will mitigate possible losses rather than an investment that will produce tangible gains or cost savings. And as with other types of insurance, it might also make sense to bring in a third-party vendor to handle your disaster recovery needs. READ MORE
When it comes to setting up and utilizing development and test environments, cloud-based platforms such as Amazon Web Services (AWS) offer a number of major advantages over traditional on-site hardware. But at the end of the day, most organizations are primarily interested in the money-saving potential of an AWS development environment. So in the following article, we’ll take a look at various ways you can save money on AWS development environments can help your company reduce running costs. We’ll also look at how third-party applications like CloudRanger can further decrease the cost of running your development and test environments on AWS.
Regardless of what type of platform you are using, the need to make regular backups of your business’s data is self-evident. But a major benefit of working with Amazon Web Services (AWS) is the ability to easily and efficiently make incremental backups of your company’s data by utilizing Amazon EBS snapshots.
Despite their popularity, not everyone is familiar with how Amazon EBS snapshots work. So in the following article, we’ll take a more in-depth look at native EBS snapshots, and how they are able to save your company time and money with incremental backups. We’ll also take a look at how using a third-party service like CloudRanger can further simplify the process and lower costs.