Move Back to Datacenters
rakkhi.substack.com
Move Back to Datacenters
1–10 of 97 posts
Re: Move Back to Datacenters
#2The security points, which the main points hinges on, seem hyperfocused and in most cases misguided.
Redshift is not internet facing. If your Redshift is internet facing, you've messed up somewhere.
The CPU attack example given is for AMD ZEN, which the most common AWS workload CPUs aren't. Further, the benefit of using a cloud provider is that they put mitigations in place for most exploits, whereas running your own stack means it's now on you; running your own stack does not excuse you from having to put mitigations in place.
In the examples again, the speed to market's problems are a reflection of your organisation, not the cloud.
Stepping back a little, I'm thinking (as terrible as it is) that this is a case of blaming the tools, but never yourself; a lot of the problems the author is seeing seem very specific to their observations but are a poor use and poor understanding of AWS in general.
Overall not a great article, with a headline designed for people who already dislike AWS/GCP/Azure.
Re: Move Back to Datacenters
#3Re: Move Back to Datacenters
#4This prompts the question of "So, what are you selling this year?"
I'm sympathetic to on-prem and datacenters, but maybe all the reaction GIFs are distracting the CIO/CTO from the new fine print?
Re: Move Back to Datacenters
#5The conclusion completely handwaves the massive overheads that come with not only owning your own infrastructure, but also having to manage a complex platform stack and its security. The security points, which the main points hinges on, seem hyperfocused and in most cases misguided. Redshift is not internet facing. If your Redshift is internet facing, you've messed up somewhere. The CPU attack example given is for AM…
Re: Move Back to Datacenters
#6Naturally the first vulnerability they point out was never exploitable for cross-VM attacks on any major cloud provider at any point…
Re: Move Back to Datacenters
#7The conclusion completely handwaves the massive overheads that come with not only owning your own infrastructure, but also having to manage a complex platform stack and its security. The security points, which the main points hinges on, seem hyperfocused and in most cases misguided. Redshift is not internet facing. If your Redshift is internet facing, you've messed up somewhere. The CPU attack example given is for AM…
Re: Move Back to Datacenters
#8Re: Move Back to Datacenters
#9Naturally the first vulnerability they point out was never exploitable for cross-VM attacks on any major cloud provider at any point…
Thats a strong statement we only know about breaches that have a) being identified b) publicly disclosed