We are actively working on additional mitigations, as well as tracking down the source of the attack to shut it down. Our DDoS mitigations are absorbing the vast majority of this traffic, but these mitigations are also flagging some legitimate customer queries at this time. The AWS DNS servers are currently under a DDoS attack. We are investigating reports of occasional DNS resolution errors. These are services countless sites and applications rely on to handle visitors and process customer information. This affects more than just S3: it will hamper any connections to Amazon services that rely on external DNS queries, such as the Amazon Relational Database Service (RDS), Simple Queue Service (SQS), CloudFront, Elastic Compute Cloud (EC2), and Elastic Load Balancing (ELB). The partial downtime started about 10 hours ago, or around 0900 US East Coast time, and AWS's DNS servers are still, at time of writing, under siege. One workaround is to insert the region of the bucket into the address, eg: mycloudydata.s3., which should, we're told, resolve correctly. AWS DNS network hijack turns MyEtherWallet into ThievesEtherWallet READ MOREįor example, if your web application or software tries to talk to your storage bucket at mycloudydata.s3., the DNS query to convert that human-readable address into an IP address may not get through to Amazon, and could cause your code to fail.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |