Our production servers were suspended by Google Cloud
Make sure your decision to migrate to AWS is not an emotional one.<p>I had my own feud with AWS over a $60,000 bill and an enormous amount of hours spent by my team fighting crypto hackers after they took over one of our accounts and use very advanced scripts to create hundreds of large instances.<p>AWS has become very complicated to manage and at the same time the attacks to their infrastructure have increased exponentially.<p>If your company doesn't have a dedicated team to stay on top of AWS you'll be vulnerable to attacks like the one I experienced.<p>You simply can't count on the baseline configuration of your account and instances provided by AMS, you need advanced knowledge on how to secure your resources beyond basic stuff like MFA and monitoring.<p>And if you think AWS will have your back when shit hits the fan, lol good luck with that.<p>They will try to collect the bills while providing absolutely no support, reminding you about their Shared Responsibility Agreement.<p>They also expect you to fight the attacks.<p>I ended up spending months of work securing my services and cleaning my debt with AWS billing, to the point we almost went to court.<p>So again, you may have good reasons to migrate, just beware that AWS won't come free of hassle.