People and organizations generally want to begin the new year with a clean house. That includes organizations seeking enterprise transformation involving cloud migration. The end of the year is as good a time as any to flip the switch.
With a little research, you can find all kinds of preparation lists for your cloud migration effort including this one, 21 Best Practices for Your Cloud Migration, from AWS. Do you know the one item AWS left off their own list? Attend ASW re:Invent. This year’s event takes place in Las Vegas (from November 29 to December 3) and you know what that means? They will not run out of hotel rooms.
Seeing as how somewhere between 30% – 40% of cloud customers use AWS, you might think that attending “the largest event of the year for both Amazon Web Services (AWS) and those on the AWS Event Technology Team” would make their all-important list. But nah.
Preparing for a Year-end Migration to AWS
Needless to say, but we’ll say it anyway because we’re on a minimum word count, if you’re planning a year-end migration to AWS, you should probably attend AWS re:Invent. And while time is running short, it’s not too late. The benefits of attending? Opportunities for certification, networking and expert sessions specifically targeted to enterprise migration.
Don’t Overlook Cloud Security
Since we’ve already agreed you’ll be attending AWS re:Invent, one of your objectives while there should be to do a deep dive on AWS cloud security, because of you know, the Shared Responsibility Model.
You don’t know what the Shared Responsibility Model is? It says, “Cloud service providers adhere to a shared security responsibility model, which means your security team maintains some responsibilities for security as you move applications, data, containers, and workloads to the cloud, while the provider takes some responsibility, but not all.”
In other words, your security headaches don’t go away when you migrate to the cloud. You are still responsible for the security of the guest operating systems and other associated application software, as well as the configuration of the AWS provided security group firewall. Come to think of it, understanding the Shared Responsibility Model also isn’t on the AWS list of 21 best practices.
While You’re at it
Now that we know you’ll be doing a security deep dive while attending AWS re:Invent, there’s one more thing you should probably do while you’re there. Stop by the Threat Modeler booth (#1626). Why? Three reasons.
First, Threat Modeler has a new joint offering with AWS which empowers DevSecOps to achieve security early in the cloud migration design phase. It reduces overall time-cost and effort to fix security issues, from weeks to just a few hours, thereby maximizing efficiency and ROI.
Second, Threat Modeler Cloud Edition comes as close as possible to one-click threat modeling. You can build threat models for your cloud environments in just a few steps using Threat Modeler’s patent pending Accelerator feature. You can also scan your cloud environment and ensure all the required security controls and requirements are implemented to secure your architecture.
Finally, maybe the best reason of all to stop by the Threat Modeler booth. The people who will be doing booth duty there are really friendly and helpful.
Can’t wait until then to get your questions answered? Reach out to Threat Modeler here.