The cloud definitely marks a new era. Not only can we manage our resources in a flexible way and with no capital investment, but we can also enjoy the state-of-the-art infrastructure of large cloud providers, like AWS cloud. Specifically, when we use EC2 to compute endless resources, we know that in terms of the durability of our virtual servers, power supply, and storage, we can trust AWS to have the best of the best.
In case of a disaster we would like to make sure that our applications are still up and running, while taking advantage of our failover hosting/cloud provider. The Disaster Recovery (DR) architecture is driven by the criticality of applications and data. The decision regarding what to back up and deploy eventually translates into ongoing costs that can be extremely significant. Every IT organization has its own high level policy guidelines. These policies are eventually translated into the policy deployed for each of the different applications the enterprise runs. The CIO and its team need to make sure they define both the high level policies and the actual budget that can be spent for DR matters.
The policies for Disaster Recovery (DR) in an enterprise are driven by the criticality of applications and data. As the public cloud has gained in credibility, more and more IT teams are taking advantage of the failover public cloud provider as a way of addressing DR and ensuring business continuity.
On the following presentation Lahav Savir, architect and CEO of Emind Systems, gives an introduction to Disaster Recovery and presents his insights based on Emind’s best practices.
The following presentation was created by Lahav Savir - Architect and CEO at Emind Systems Ltd. Emind Systems is an AWS solutions & consulting vendor, serving ~100 AWS customers.
The following presentation was created by Adrian Cockcroft - Director, Cloud Architecture at Netflix Inc. It’s an architecture talk aimed at a well informed developer audience (i.e. QConSF Real Use Cases for NoSQL track), focused mainly on availability.
The security of the public cloud is a topic of on-going debate. As an end user you need to worry about your data privacy and security. In the past we have heard a few cases where security of mega online services compromised such as Sony PS3, Gmail and Linkedin. This raise questions about whether public online services can be trusted. Amazon cloud with its virtue of best of security implementation is still leading the race and there has never been a data breach of AWS cloud services. The AWS cloud environment is also compliant with certifications and audits such as FISMA, ISO 27001/2, SOC1T2 and more. You can learn more about AWS security features here.
In this article we will talk how you can enhance security of your AWS resource with extra precaution. We hope that using some of the tips offered in this article series will help you ensure proper safety of your AWS resources. In the first article, we presented some general as well EC2-specific AWS security tips. In this second part, we list ten more tips on the precautions you should take for the safety of EBS, snapshots, or AMI.
Keeping data private and secure has always been a business imperative for data privacy and regulatory compliance reasons, and as businesses seriously consider migrating to the cloud, data security is one of the most significant concerns. Once data is moved to the cloud, it becomes vulnerable to a number of new threats, and data security must be addressed jointly by the cloud provider and the customer itself. In our presentation we will discuss the shared responsibility module, review the pros and cons of current approaches to cloud data security, and discuss new and emerging technologies such as split-key encryption and partially homomorphic key encryption that enables organizations to maintain data privacy in a public cloud environment.
This presentation brought to you by Ariel Dan, Co-Founder VP sales & Marketing at Porticor cloud security.
[No time to attend to your AWS security breaches? Newvem automatically recognizes your database servers,analyzes their vulnerability, and provides you with drill downs covering insights on specific instances for a quick fix turnaround. Learn more]
Keywords: Amazon AWS Cloud services, security group, AMI, Amazon Machine Image, Cloud IP ports, database Ports, AWS Security vulnerabilities, AWS Firewall, Shared Resources, Data Encryption, S3, EBS
This presentation brought to you by Lahav Savir CEO at Emind. Emind services are focused on large scale system design, implementation, deployment and management specifically for the AWS cloud.
In his presentation he describes cloud enablement services that were provided to a global organization. According to Lahav this organization provides software solutions and technology for the travel industry – handles huge volumes of near real-time transactions and reservations. These slides are a result of a cloud migration of an inefficient and costly offsite backup infrastructure that was meant to manage an incrementally expanding database of more than 2.8 TB of storage.
Together with the great new capabilities cloud presented a new approach of multi-tenant environments and the sharing features. In this great capability also buried a great risk of resources exposure. AWS Cloud resource sharing options facilitates your ability to moce resources and application across multiple accounts and enjoy some public out-of-the-box service., yet it can also create risks for your digital property. Newvem informs you when an object is shared for you to determine if this is warranted or not. Check our Newvem security features to learn more.
The described deployment taking in mind regulatory compliance rule that the previous six months’ material must be readily available in a systematized fashion with cross-platform search functionality. This secured backup solution presented is based on AWS technologies such as S3 storage and EBS volumes explaining how to deal with great chunks of data in a secure manner while leveraging Porticor, cloud security solution.
