I always thought that cloud shyt was a horrible fukking idea. All of your data and shyt in the hands of another company. Amazon can sell your customer database in the black market and fabricate some "dem Russian hackers" story. I bet most of the accounts hacked were of smaller businesses. Not the large ones and government clients.
I have my qualms with the Cloud but without going that far off-topic a lot of companies on-prem systems are even more susceptible to be hack because of bad practices. Cloud just gets a bad rap mainly because not enough individuals are trained on properly managing a Cloud environment. Best solution will always be to use MFA on everything you can and never reuse passwords.Summary:
Freeze your CRA files
Changes your password to pass phase
Don't keep your shyt in the cloud
Never trust those fat non-girlfriend having *****/8chan loving IT geeks
The video is so bad that it wasn't even clear. From my understanding it was just a server with a bunch of PII. I found a few similar articles mentioning it that have either been removed for inaccurate information or have not mention ot AWS being involved in anyway. Not sure who first reported on this initially but it appears like they jumped the gun and didn't have proper info.I think I read an article about this. From what I understood it was more so an AWS Account hack, rather than simply an aws hack. Did someone else understand it differently?
Agreed but the modern controllers of IT don't understand IT and just follow the fads.
Bandwagon effect.
AWS is just a mainframe by another name.
Old tech, old definitions rehashed. Some improvement.
Mainframes: The Cloud Before the Cloud - DevOps.com
It depends eh,
The CIO where I work wanted to move their billing system from the mainframe to the cloud. This makes more sense for a large institution since mainframes dead and expensive to operate, so it depends alot on your needs.
There's still going to a backup server kept on site but it costs too much damn money to run their own servers.
Ok.. How about the cloud is just another monolithic system.
We went from mainframes -> client server small servers -> to sun and other huge servers -> back to cloud (mainframe).
Other than cost why keep stuff in "the cloud".. AKA why host on other people's servers..
Ok.. How about the cloud is just another monolithic system.
We went from mainframes -> client server small servers -> to sun and other huge servers -> back to cloud (mainframe).
Other than cost why keep stuff in "the cloud".. AKA why host on other people's servers..
Breh, cloud is more than just dropbox. You can host complex applications in the cloud that would require mad technical overhead to manage or would be hella costly as you highlighted.
Other than cost, you have resilience(if your "mainframe" fails or a fire happens), high availability(if you have adequate performance if one virtual machine fails), improving performance (CDNs, increasing virtual machine/database specs on the fly etc).
I see your point that one has to surrender some autonomy, but there are pros and cons to both approaches, and seeing most businesses are in the business of making money, cost really trumps other concerns.
Improved resilience is a misnomer. I've been working in IT for a while now, in finance.
Every large bank has a DR site with everything there to keep the bank running.
![]()
Disaster Recovery Site
I wasn't comparing mainframes to cloud. I was comparing in-house to out-house.
Cost doesn't trump all other concerns.
I am still waiting for the pros....![]()