On Thursday, Amazon Web Services (AWS) customers encountered service disruptions as the company strived to hold back a distributed denial-of-service (DDoS) attack.
As part of such an attack, attackers try to deluge the target with traffic, which would ultimately lead to the inaccessibility of service.
While customers grumbled of their incapacity to access AWS S3 buckets, the company, on its status page, said that it was having problems with resolving AWS DNS names.
The company said that a very small number of particular DNS names encountered a higher error rate beginning 5:16 PM.
While reporting on Twitter that it was probing reports of sporadic DNS resolution mistakes with Route 53 and external DNS providers, the company also sent notices to customers to inform them of a continuing DDoS attack.
Related New Article DDoS: DDoS Attacks and How They Can be Mitigated
“We are investigating reports of occasional DNS resolution errors. The AWS DNS servers are currently under a DDoS attack. Our DDoS mitigations are absorbing the vast majority of this traffic, but these mitigations are also flagging some legitimate customer queries at this time,” AWS told customers.
Amazon also clarified that the DNS resolution problems were also sporadically affecting other AWS Service endpoints, including ELB, RDS, and EC2, given that they require public DNS resolution.
One of the impacted companies was Digital Ocean, which has had problems with accessing S3/RDS resources inside Droplets across numerous regions starting October 22.
“Our Engineering team is continuing to monitor the issue impacting accessibility to S3/RDS/ELB/EC2 resources across all regions,” the company wrote on the incident’s status page at 23:25 UTC on Oct 22.
The company announced yesterday that availability to the affected resources has been restored, but it was still checking for possible issues.