In his 90 minute keynote address at the AWS re:Invent conference, Andy Jassy quite unabashedly gave these reasons for using AWS versus a private cloud, (at the 32 minute mark) :
So public cloud adoption should be a no-brainer, right? Oh wait, but Andy omitted security in the public cloud – how can I trust that my customers’ sensitive data is secure in the public cloud?
I agree, the message wears thin that enterprise businesses are apprehensive to store sensitive customer data in the public cloud, and thus hesitant to adopt the cloud at all. (By the way, it was also very refreshing in Jassy’s keynote to see NASA’s JPL use of the public cloud, as the Netflix story also gets old.)
Maybe it’s the network ?
Enterprises might not be able to migrate their applications to the public cloud, because of how their datacenter servers are connected and secured. A customer came over to our booth at AWS re:invent and while very excited about the AWS public and our announcement, wanted to know “What do I do about my VLANS? My physical and virtual servers are isolated at layer 2? And my servers have two networks: one network for data and applications, the second network only for administrators – how do I architect this in AWS?”
So we walk over the AWS booth, and discuss migrating VLANs to AWS, where the customer no longer controls the network. One idea proposed was to use VPC to isolate instances and elastic IP addressing for the management interface and IAM roles to lockdown who can access the instance.
“Lockdown” hmm, seems like security is a strong requirement for the public cloud after all!
What obstacles have you found in your path to cloud adoption?