Elastic Security

Icon

Security for the Cloud

Reality Check: Data Center & Cloud Computing

Last week I visited the “Data Center & Cloud Computing” trade-show in Paris and talked to many exhibitors about their usage of public cloud infrastructures, their perception of services like Amazon EC or Rackspace, and the impact they might have on their business. The term “cloud computing” was omnipresent in almost all panels and discussions about IT organization, data center design, and software development. It was written on many banners, boot headers and brochures, but still people understand completely different things by it. It seems to cause as much rejection and fear as well as enthusiasm and hope. Here a collection of my impressions and discussion points that struck me…

Rejection & Fear

Rejection and fear often comes from existing hosters and managed service providers. There arguments against public cloud computing infrastructures:

  • The question of Service Level Agreements (SLAs) and service guarantees that include penalties for service outages
  • Performance guarantees
  • Security Concerns and data protection
  • Trust in local providers

They see a risk in the fact that IT transforms into a fully industrialized service with few big players that are – moreover – only coming from the US. Some have also built a differentiating core competence in managing IT more efficiently and negotiating better service contracts than their competitors – they fear to  loose this competitive advantage when cloud infrastructures becomes mainstream. In addition, there are fears of the system administrators that are confronted with the unknown and forced to learn a lot of new things and change well established processes.

Enthusiasm & Hope

Enthusiasm and Hope mainly comes from new players in the field, startups, and managed service providers. They see new business models and the possibility to start a software service with few capital expenses. Agile development finally found its friendly counterpart: agile deployment that no longer hurts at the bottlenecks of IT processes and static equipment.

But also established players including hosters see new opportunies, especially the opportunity to decomplexify IT processes and more cost effectiveness due to pay-per-use models. Some open-source partisans also expressed the hope that cloud computing infrastructures strengthen the open-source movement. I met also several companies – established hosters as well as new players – that offer pay-per-use models on top of their own data centers and started to offer resources the cloud way including APIs.

Conclusion

Cloud computing is omnipresent in all discussions on IT management, hosting and data centers. Amazon EC2 is the dominating name for cloud infrastructures. Young companies start using it, established ones anticipate the impact of cloud services and even consider it a strategic must to show presence in the domain.

Filed under: Discussions, IaaS

Impressions from AWS User Groups Paris

Last monday I participated in the AWS User Groups Event in Paris (perfectly organized by Ysance!). The goal of those series of events all around the world is to bring together users, potential users, and folks interested in what AWS (Amazon Web Services) is all about. It’s obvious that Europe clearly lags behind the US concerning the usage of cloud  infrastructure services. But things are moving! Let’s have a look at those that already use it and the experience they share. The event took around 5 hours and consisted of presentations with case-studies and technical insights. My interest focuses on the motivation to start an AWS based project, the tools used, the benefits, and the problems encountered.

Motivation

Two projects (sncf-voyage, Maporama) used EC2 because the delay to buy or allocate the necessary hardware from internal IT, external suppliers or even hosters took was not compatible with an ambitious project deadline. Scaling – to deal with growth and temporary peaks – was the motivation for Blogbang and cafe.com to migrate to EC2. The ease to adapt the infrastructure to a sophisticated and distributed architecture performing time-consuming background tasks made Silentale stick to EC2 after a prototyping and testing phase.

Tools

One thing that striked me was that almost every AWS user present used some own scripting facilities or built some own utilities to manage, monitor, and automate his platform. Even Excel is part of the game. Among cloud infrastructure management tools the AWS console, ElasticFox, and even the EC2 command line tools are being used. For server monitoring, Nagios and Zabbix were mentionned, for visualization Cacti, for automation Puppet and Capistrano. Interesting for me that consolidated billing and reserved instances were considered as ways to deal with the complexity induced by an important number of virtual machines (if I understood well, the largest EC2 infrastructure in France has around 100 machines).

Frederic Faure from Ysance gave an interesting presentation on the tools they recommend and how they work together. IT4Control recently migrated their existing workflow management platform to EC2. Guillaume Plessis showed a detailed performance comparison between Amazon RDS and MySQL running with EBS (slides). And Attila Narin from AWS talked about the patterns guiding the AWS platform.

Benefits

Here’s what I picked up from the presentations and discussions on the benefits and positive experiences with AWS:

  • agility: cloud infrastructures are the perfect complement to agile development
  • scaling and dealing with varying load
  • no more nead for IT to negociate and deal with different hardware and network suppliers
  • merging of staging and production environments: cloud infrastructures allow to incrementally improve and stabilize staging deployments until they are production ready and then to easily switch them into production by updating the DNS (and destroying the original production environment)
  • constant innovation, improvements, and new features on the AWS platform
  • the power of the API

Issues and Wishes

  • Security and legal concerns: features like integrated data encryption, API audit logs
  • Management and monitoring: Amazon UI’s lack to manage many instances, storages, or S3 buckets; integration with Cacti/Nagios like tools; changing security groups require restart of instance; API for billing
  • Performance: performance of large database support; varying network and disk performance; varying CPU performance based on the processor of the underlying physical machine
  • Other: IT is no longer a differentiator; the Microsoft world is not as well supported as the Linux world; lack of documentation and possibility to find consultant partners

Thanks again for this great event, sure to be back next time in October!

Other feedback:

Filed under: AWS, AWSUG

Twitter Updates

Follow

Get every new post delivered to your Inbox.