Google Cloud Platform

DoS Protection Service for Java

The App Engine Denial of Service (DoS) Protection Service enables you to protect your application from running out of quota when subjected to denial of service attacks or similar forms of abuse. You can blacklist IP addresses or subnets, and requests routed from those addresses or subnets will be dropped before your application code is called. No resource allocations, billed or otherwise, are consumed for these requests.

Do not use this service for security. It is designed for quantitative abuse prevention, such as preventing DoS attacks, only. Some requests from blacklisted users may still get through to your application.

  1. About dos.xml
  2. Limits
  3. Uploading DoS configuration

By default, App Engine serves a generic error page to blacklisted addresses. You can configure your app to serve a custom response instead. For details, see Custom Error Responses.

About dos.xml

A dos.xml file in the WEB-INF directory of your application (alongside appengine-web.xml) configures DoS Protection Service blacklists for your application. The following is an example dos.xml file:

<?xml version="1.0" encoding="UTF-8"?>
    <description>a single IP address</description>
    <description>an IPv4 subnet</description>
    <description>an IPv6 address</description>
    <description>an IPv6 subnet</description>

For an XSD describing the format, check the file docs/dos.xsd in the SDK.

A dos.xml file consists of a number of blacklist entries. A blacklist entry has a <subnet>, and can optionally specify a <description>. The description will be visible in the Developers Console. The <subnet> is any valid IPv4 or IPv6 subnet in CIDR notation.


You may define a maximum of 100 blacklist entries in your configuration file. Uploading a configuration file with more than 100 entries will fail.

Uploading DoS configuration

You can use AppCfg to upload DoS configs. When you upload your application to App Engine using AppCfg update, the DoS Protection Service is updated with the contents of dos.xml. The new config will be viewable using the Developers Console straight away, but may take a few minutes to take effect. You can update just the DoS configuration without uploading the rest of the application using AppCfg update_dos.

To delete all blacklist entries, change the dos.xml file to just contain:

<?xml version="1.0" encoding="UTF-8"?>