<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>joecot</author><text>My coworker is running a hosted affiliate tracking system on AWS as part of our company. He regularly has to deal with AWS wanting to pull our servers because of email spam -- not because we&amp;#x27;re sending spam emails, but because some affiliate link is in a spam email that resolves to our server, and Spamhaus complained to AWS.&lt;p&gt;Usually this can get handled after a few days of aggravating emails back and forth, we get our client to ban the affiliate in question, and move on with our days with no downtime. But a few weeks ago my coworker came in to find our server taken offline, because AWS emailed him about a spam complaint on a Friday night, and they hadn&amp;#x27;t gotten a response by Sunday. It&amp;#x27;d been down for hours before he realized.&lt;p&gt;They&amp;#x27;d just null terminated the IP of the server, so he updated IPs in DNS real quick, but he then spent half a day both resolving the complaint, and then getting someone at AWS to say it wouldn&amp;#x27;t happen again. They supposedly put a flag on his account requiring upper management approval to disable something again, but we&amp;#x27;ll see if that works when it comes up again.</text><parent_chain><item><author>warrentr</author><text>This is very concerning but can happen on AWS as well. July 4th last year at about 4PM PST amazon silently shutdown our primary load balancer (ALB) due to some copyright complaint. This took out our main api and several dependent apps. We were able to get a tech support agent on the phone but he wasn&amp;#x27;t able to determine why this happened for several hours. Eventually we figured out that another department within amazon was responsible for pulling down the alb in an undetectable way. Ironically we are now in the process of moving from aws -&amp;gt; gcp.</text></item></parent_chain></comment><story><title>Why you should not use Google Cloud</title><url>https://medium.com/@serverpunch/why-you-should-not-use-google-cloud-75ea2aec00de</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>duxup</author><text>They shutdown just the load balancer?&lt;p&gt;Forgive my ignorance but that seems like a weird choice rather than cutting access to the servers or in some more formal ways for copyright...&lt;p&gt;Also kinda concernit that multiple departments can take enforcement type action and others not know it.   That seems way disorganized &amp;#x2F; recipe for diasater.</text><parent_chain><item><author>warrentr</author><text>This is very concerning but can happen on AWS as well. July 4th last year at about 4PM PST amazon silently shutdown our primary load balancer (ALB) due to some copyright complaint. This took out our main api and several dependent apps. We were able to get a tech support agent on the phone but he wasn&amp;#x27;t able to determine why this happened for several hours. Eventually we figured out that another department within amazon was responsible for pulling down the alb in an undetectable way. Ironically we are now in the process of moving from aws -&amp;gt; gcp.</text></item></parent_chain></comment><story><title>Why you should not use Google Cloud</title><url>https://medium.com/@serverpunch/why-you-should-not-use-google-cloud-75ea2aec00de</url></story>