> For the complete documentation index, see [llms.txt](https://notebook.iuriioapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notebook.iuriioapps.com/cloud/aws/networking/shield.md).

# Shield

* Standard
  * Free service that protects all AWS customers on ELB, CloudFront or Route53.
  * Protects against SYN/UDP floods, reflection attacks, and other Layer 3 / Layer 4 attacks.
* Advanced
  * Shield Advanced provides enhanced protection for your application running behind ELB, CloudFront or Route53 against larger and more sophisticated attacks. $3000 / month.
  * Always-on, flow-based monitoring of network traffic and active application monitoring to provide near real-time notifications of DDoS attacks.
  * DDoS Response Team (DRT) to manage and mitigate DDoS attacks.
  * Protects your AWS bill against higher fees due to ELB, CloudFront and Route53 usage spikes during DDoS.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://notebook.iuriioapps.com/cloud/aws/networking/shield.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
