471–480 of 544 posts
Earlier quoted context omitted.
Atlassian is not on Google Cloud, they are an AWS shop. I suspect this is an unrelated personal project.
How much would you bet against that guy having fairly highly privileged AWS IAM access in Atlassian's account?
Works great. You can already find questions on Stack Overflow from people getting their database deleted https://stackoverflow.com/questions/63067062/elastic-search-... Edit: The person raising that question is working for Atlassian (Jira), looks like Atlassian got their database deleted lol
This edit is speculation. > I'm running an elastic search for a personal project on google-cloud and I use as a search index for my application. He very clearly says it’s a personal project. Trying to learn new topics outside of your direct responsibilities, while employed, is very common in the software industry. Not everyone that works at a company is involved in databases at that company.
Earlier quoted context omitted.
Sounds like a good public service. I’d much rather have my data deleted until it’s secured than have it stolen by someone else.
Vandalism is not a good public service. > I’d much rather have my data deleted until it’s secured than have it stolen by someone else There are multiple logical fallacies in this sentence. First is the use of the world 'until' which is ambiguous here; it suggests that your data can be 'undeleted' after the DB has been secured or you would rather not have any data stored anywhere that is not secured. Either option to…
Earlier quoted context omitted.
Vandalism is not a good public service. > I’d much rather have my data deleted until it’s secured than have it stolen by someone else There are multiple logical fallacies in this sentence. First is the use of the world 'until' which is ambiguous here; it suggests that your data can be 'undeleted' after the DB has been secured or you would rather not have any data stored anywhere that is not secured. Either option to…
I assume the comment was partially in jest. But this would actually work well if it was consistent and fast. If databases get wiped before you have time to put anything important in them then noone gets hurt.
Seem like this could be easily reconfigured to do the opposite. Leave the databases but overwrite all the existing data then write dummy data until disk is exhausted. Does that cross another ethical line?
You mean, to make data recovery impossible?
To whoever is doing that: you are doing god's work, please keep it up.
Earlier quoted context omitted.
Yeah, it's bad for the industry right now, but this is just a transition period! Once we get through the pain of losing a few databases, the new steady state where nobody's data is stored in world-writable databases will be better for everyone, and that will be worth the cost. Consider if this happened five years ago, it would have had a smaller cost than happening today. And it was probably going to happen at some p…
If you have Docker then make sure you have a firewall on top of it, otherwise it will expose pretty much what any docker user wants !
Earlier quoted context omitted.
I assume the comment was partially in jest. But this would actually work well if it was consistent and fast. If databases get wiped before you have time to put anything important in them then noone gets hurt.
No, think about it, stolen or deleted? Which option serves your clients better given the generally awful situation?
Earlier quoted context omitted.
I'm working on a personal project and not at all related to my work. I accidentally kept ports open :facepalm, sorting things out now :)
Recommend to setup two subnets in your project. One public and one private. This prevents this sort of issues, instances in the private subnet simply don't get a public IP, they can't be reached over the internet. For reference, the standard practice in a company is to have a (third) separate subnet for databases, with zero internet access (no NAT gateway). Connection must be explicitly opened from/to database client…