AWS lambda functions vs. Virtual server for a DNS firewall

• Main Author: Hultgren Wärn, Buster
• Format: Others
• Language: English
• Published: Umeå universitet, Institutionen för datavetenskap 2020
• Subjects: Engineering and Technology; Teknik och teknologier
• Online Access: http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-175888

Malicious websites contain ways of tricking its victims into downloading malware or getting their sensitive information such as username and passwords. Traditional firewalls block these websites on the client side after already requesting their contents. One relatively new approach is to block suspicious IP addresses right after the DNS protocol on the server side. Here, every DNS request made through the clients side needs to travel through a server containing an IPaddress filter which blocks suspicious websites. The server with this approach implemented needs to handle huge amount of request per second during the whole day. This thesis looks into price efficiency for this approach and compares it operating on two types of servers, one on a virtual server and the other on Amazon Web Services lambda functions. How many requests can each type of server handle for the same price? The results show that for the same amount of money, the virtual server can handle far more results than AWS lambda functions. In three different tests, the virtual server could handle up to 5.98, 7.39 and 24.97 requests for every AWS lambda request.