Split (1)

train · 107k rows

id stringlengths 8 78	source stringclasses 743 values	chunk_id int64 1 5.05k	text stringlengths 593 49.7k
waf-dg-294	waf-dg.pdf	294	and AWS Shield Advanced Developer Guide For the latest version of AWS WAF, see AWS WAF. Use the following information to help you diagnose and ﬁx common issues that you might encounter when working with AWS WAF Classic and IAM. Topics • I am not authorized to perform an action in AWS WAF Classic • I am not authorized to perform iam:PassRole • I want to allow people outside of my AWS account to access my AWS WAF Classic resources I am not authorized to perform an action in AWS WAF Classic If you receive an error that you're not authorized to perform an action, your policies must be updated to allow you to perform the action. The following example error occurs when the mateojackson IAM user tries to use the console to view details about a ﬁctional my-example-widget resource but doesn't have the ﬁctional waf:GetWidget permissions. User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: waf:GetWidget on resource: my-example-widget In this case, the policy for the mateojackson user must be updated to allow access to the my- example-widget resource by using the waf:GetWidget action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. I am not authorized to perform iam:PassRole If you receive an error that you're not authorized to perform the iam:PassRole action, your policies must be updated to allow you to pass a role to AWS WAF Classic. Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service. The following example error occurs when an IAM user named marymajor tries to use the console to perform an action in AWS WAF Classic. However, the action requires the service to have Identity and access management 833 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide permissions that are granted by a service role. Mary does not have permissions to pass the role to the service. User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole In this case, Mary's policies must be updated to allow her to perform the iam:PassRole action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. I want to allow people outside of my AWS account to access my AWS WAF Classic resources You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources. To learn more, consult the following: • To learn whether AWS WAF Classic supports these features, see How AWS WAF Classic works with IAM. • To learn how to provide access to your resources across AWS accounts that you own, see Providing access to an IAM user in another AWS account that you own in the IAM User Guide. • To learn how to provide access to your resources to third-party AWS accounts, see Providing access to AWS accounts owned by third parties in the IAM User Guide. • To learn how to provide access through identity federation, see Providing access to externally authenticated users (identity federation) in the IAM User Guide. • To learn the diﬀerence between using roles and resource-based policies for cross-account access, see How IAM roles diﬀer from resource-based policies in the IAM User Guide. Using service-linked roles for AWS WAF Classic Warning AWS WAF Classic support will end on September 30, 2025. Identity and access management 834 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note This is AWS WAF Classic documentation. You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your web ACLs, see Migrating your AWS WAF Classic resources to AWS WAF. For the latest version of AWS WAF, see AWS WAF. AWS WAF Classic uses AWS Identity and Access Management (IAM) service-linked roles. A service- linked role is a unique type of IAM role that is linked directly to AWS WAF Classic. Service-linked roles are predeﬁned by AWS WAF Classic and include all the permissions that the service requires to call other AWS services on your behalf. A service-linked role makes setting up AWS WAF Classic easier because you don’t have to manually add the necessary permissions. AWS WAF Classic deﬁnes the permissions of its service-linked roles, and unless deﬁned otherwise, only AWS WAF Classic can assume its roles.
waf-dg-295	waf-dg.pdf	295	AWS WAF. AWS WAF Classic uses AWS Identity and Access Management (IAM) service-linked roles. A service- linked role is a unique type of IAM role that is linked directly to AWS WAF Classic. Service-linked roles are predeﬁned by AWS WAF Classic and include all the permissions that the service requires to call other AWS services on your behalf. A service-linked role makes setting up AWS WAF Classic easier because you don’t have to manually add the necessary permissions. AWS WAF Classic deﬁnes the permissions of its service-linked roles, and unless deﬁned otherwise, only AWS WAF Classic can assume its roles. The deﬁned permissions include the trust policy and the permissions policy. That permissions policy can't be attached to any other IAM entity. You can delete a service-linked role only after ﬁrst deleting the role's related resources. This protects your AWS WAF Classic resources because you can't inadvertently remove permission to access the resources. For information about other services that support service-linked roles, see AWS Services That Work with IAM and look for the services that have Yes in the Service-Linked Role column. Choose a Yes with a link to view the service-linked role documentation for that service. Service-linked role permissions for AWS WAF Classic AWS WAF Classic uses the following service-linked roles: • AWSServiceRoleForWAFLogging • AWSServiceRoleForWAFRegionalLogging AWS WAF Classic uses these service-linked roles to write logs to Amazon Data Firehose. These roles are used only if you enable logging in AWS WAF. For more information, see Logging Web ACL traﬃc information. Identity and access management 835 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide The AWSServiceRoleForWAFLogging and AWSServiceRoleForWAFRegionalLogging service-linked roles trust the following services (respectively) to assume the role: • waf.amazonaws.com waf-regional.amazonaws.com The permissions policies of the roles allow AWS WAF Classic to complete the following actions on the speciﬁed resources: • Action: firehose:PutRecord and firehose:PutRecordBatch on Amazon Data Firehose data stream resources with a name that starts with "aws-waf-logs-." For example, aws-waf- logs-us-east-2-analytics. You must conﬁgure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see Service-Linked Role Permissions in the IAM User Guide. Creating a service-linked role for AWS WAF Classic You don't need to manually create a service-linked role. When you enable AWS WAF Classic logging on the AWS Management Console, or you make a PutLoggingConfiguration request in the AWS WAF Classic CLI or the AWS WAF Classic API, AWS WAF Classic creates the service-linked role for you. You must have the iam:CreateServiceLinkedRole permission to enable logging. If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you enable AWS WAF Classic logging, AWS WAF Classic creates the service-linked role for you again. Editing a service-linked role for AWS WAF Classic AWS WAF Classic doesn't allow you to edit the AWSServiceRoleForWAFLogging and AWSServiceRoleForWAFRegionalLogging service-linked roles. After you create a service- linked role, you can't change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see Editing a Service-Linked Role in the IAM User Guide. Identity and access management 836 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Deleting a service-linked role for AWS WAF Classic If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don’t have an unused entity that is not actively monitored or maintained. However, you must clean up the resources for your service-linked role before you can manually delete it. Note If the AWS WAF Classic service is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again. To delete AWS WAF Classic resources used by the AWSServiceRoleForWAFLogging and AWSServiceRoleForWAFRegionalLogging 1. On the AWS WAF Classic console, remove logging from every web ACL. For more information, see Logging Web ACL traﬃc information. 2. Using the API or CLI, submit a DeleteLoggingConfiguration request for each web ACL that has logging enabled. For more information, see AWS WAF Classic API Reference. To manually delete the service-linked role using IAM Use the IAM console, the IAM CLI, or the IAM API to delete the AWSServiceRoleForWAFLogging and AWSServiceRoleForWAFRegionalLogging service-linked roles. For more information, see Deleting a Service-Linked Role in the IAM User Guide. Supported Regions for AWS WAF Classic service-linked roles AWS WAF Classic supports using service-linked roles in the following AWS Regions. Region Name Region Identity US East (N. Virginia) US East (Ohio) US West (N. California) us-east-1 us-east-2 us-west-1 Support in AWS WAF Classic Yes Yes
waf-dg-296	waf-dg.pdf	296	web ACL that has logging enabled. For more information, see AWS WAF Classic API Reference. To manually delete the service-linked role using IAM Use the IAM console, the IAM CLI, or the IAM API to delete the AWSServiceRoleForWAFLogging and AWSServiceRoleForWAFRegionalLogging service-linked roles. For more information, see Deleting a Service-Linked Role in the IAM User Guide. Supported Regions for AWS WAF Classic service-linked roles AWS WAF Classic supports using service-linked roles in the following AWS Regions. Region Name Region Identity US East (N. Virginia) US East (Ohio) US West (N. California) us-east-1 us-east-2 us-west-1 Support in AWS WAF Classic Yes Yes Yes Identity and access management 837 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Region Name Region Identity Support in AWS WAF Classic US West (Oregon) Asia Paciﬁc (Mumbai) us-west-2 ap-south-1 Asia Paciﬁc (Osaka) ap-northeast-3 Asia Paciﬁc (Seoul) ap-northeast-2 Asia Paciﬁc (Singapore) ap-southeast-1 Asia Paciﬁc (Sydney) ap-southeast-2 Asia Paciﬁc (Tokyo) ap-northeast-1 Canada (Central) Europe (Frankfurt) Europe (Ireland) Europe (London) Europe (Paris) South America (São Paulo) ca-central-1 eu-central-1 eu-west-1 eu-west-2 eu-west-3 sa-east-1 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Identity and access management 838 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Logging and monitoring in AWS WAF Classic Warning AWS WAF Classic support will end on September 30, 2025. Note This is AWS WAF Classic documentation. You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your web ACLs, see Migrating your AWS WAF Classic resources to AWS WAF. For the latest version of AWS WAF, see AWS WAF. Monitoring is an important part of maintaining the reliability, availability, and performance of AWS WAF Classic and your AWS solutions. You should collect monitoring data from all parts of your AWS solution so that you can more easily debug a multi-point failure if one occurs. AWS provides several tools for monitoring your AWS WAF Classic resources and responding to potential events: Amazon CloudWatch Alarms Using CloudWatch alarms, you watch a single metric over a time period that you specify. If the metric exceeds a given threshold, CloudWatch sends a notiﬁcation to an Amazon SNS topic or AWS Auto Scaling policy. For more information, see Monitoring with Amazon CloudWatch. AWS CloudTrail Logs CloudTrail provides a record of actions taken by a user, role, or an AWS service in AWS WAF Classic. Using the information collected by CloudTrail, you can determine the request that was made to AWS WAF Classic, the IP address from which the request was made, who made the request, when it was made, and additional details. For more information, see Logging API calls with AWS CloudTrail. Logging and monitoring 839 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Compliance validation for AWS WAF Classic Warning AWS WAF Classic support will end on September 30, 2025. Note This is AWS WAF Classic documentation. You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your web ACLs, see Migrating your AWS WAF Classic resources to AWS WAF. For the latest version of AWS WAF, see AWS WAF. To learn whether an AWS service is within the scope of speciﬁc compliance programs, see AWS services in Scope by Compliance Program and choose the compliance program that you are interested in. For general information, see AWS Compliance Programs. You can download third-party audit reports using AWS Artifact. For more information, see Downloading Reports in AWS Artifact. Your compliance responsibility when using AWS services is determined by the sensitivity of your data, your company's compliance objectives, and applicable laws and regulations. AWS provides the following resources to help with compliance: • Security Compliance & Governance – These solution implementation guides discuss architectural considerations and provide steps for deploying security and compliance features. • HIPAA Eligible Services Reference – Lists HIPAA eligible services. Not all AWS services are HIPAA eligible. • AWS Compliance Resources – This collection of workbooks and guides might apply to your industry and location. • AWS Customer Compliance Guides – Understand the shared responsibility model through the lens of compliance. The guides summarize the best practices for securing AWS services and map the guidance to security controls across multiple frameworks (including National Institute of Standards and Technology (NIST), Payment Card Industry Security Standards Council (PCI), and International Organization for Standardization (ISO)). Compliance validation 840 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Evaluating Resources with Rules in the AWS Conﬁg Developer Guide – The AWS Conﬁg
waf-dg-297	waf-dg.pdf	297	– This collection of workbooks and guides might apply to your industry and location. • AWS Customer Compliance Guides – Understand the shared responsibility model through the lens of compliance. The guides summarize the best practices for securing AWS services and map the guidance to security controls across multiple frameworks (including National Institute of Standards and Technology (NIST), Payment Card Industry Security Standards Council (PCI), and International Organization for Standardization (ISO)). Compliance validation 840 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Evaluating Resources with Rules in the AWS Conﬁg Developer Guide – The AWS Conﬁg service assesses how well your resource conﬁgurations comply with internal practices, industry guidelines, and regulations. • AWS Security Hub – This AWS service provides a comprehensive view of your security state within AWS. Security Hub uses security controls to evaluate your AWS resources and to check your compliance against security industry standards and best practices. For a list of supported services and controls, see Security Hub controls reference. • Amazon GuardDuty – This AWS service detects potential threats to your AWS accounts, workloads, containers, and data by monitoring your environment for suspicious and malicious activities. GuardDuty can help you address various compliance requirements, like PCI DSS, by meeting intrusion detection requirements mandated by certain compliance frameworks. • AWS Audit Manager – This AWS service helps you continuously audit your AWS usage to simplify how you manage risk and compliance with regulations and industry standards. Compliance validation 841 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Resilience in AWS WAF Classic Warning AWS WAF Classic support will end on September 30, 2025. Note This is AWS WAF Classic documentation. You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your web ACLs, see Migrating your AWS WAF Classic resources to AWS WAF. For the latest version of AWS WAF, see AWS WAF. The AWS global infrastructure is built around AWS Regions and Availability Zones. AWS Regions provide multiple physically separated and isolated Availability Zones, which are connected with low-latency, high-throughput, and highly redundant networking. With Availability Zones, you can design and operate applications and databases that automatically fail over between Availability Zones without interruption. Availability Zones are more highly available, fault tolerant, and scalable than traditional single or multiple data center infrastructures. For more information about AWS Regions and Availability Zones, see AWS Global Infrastructure. Infrastructure security in AWS WAF Classic Warning AWS WAF Classic support will end on September 30, 2025. Note This is AWS WAF Classic documentation. You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your web ACLs, see Migrating your AWS WAF Classic resources to AWS WAF. Resilience 842 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide For the latest version of AWS WAF, see AWS WAF. As a managed service, AWS WAF Classic is protected by AWS global network security. For information about AWS security services and how AWS protects infrastructure, see AWS Cloud Security. To design your AWS environment using the best practices for infrastructure security, see Infrastructure Protection in Security Pillar AWS Well‐Architected Framework. You use AWS published API calls to access AWS WAF Classic through the network. Clients must support the following: • Transport Layer Security (TLS). We require TLS 1.2 and recommend TLS 1.3. • Cipher suites with perfect forward secrecy (PFS) such as DHE (Ephemeral Diﬃe-Hellman) or ECDHE (Elliptic Curve Ephemeral Diﬃe-Hellman). Most modern systems such as Java 7 and later support these modes. Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the AWS Security Token Service (AWS STS) to generate temporary security credentials to sign requests. AWS WAF Classic quotas Warning AWS WAF Classic support will end on September 30, 2025. Note This is AWS WAF Classic documentation. You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your web ACLs, see Migrating your AWS WAF Classic resources to AWS WAF. For the latest version of AWS WAF, see AWS WAF. AWS WAF Classic is subject to the following quotas (formerly referred to as limits). AWS WAF Classic quotas 843 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide AWS WAF Classic has default quotas on the number
waf-dg-298	waf-dg.pdf	298	You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your web ACLs, see Migrating your AWS WAF Classic resources to AWS WAF. For the latest version of AWS WAF, see AWS WAF. AWS WAF Classic is subject to the following quotas (formerly referred to as limits). AWS WAF Classic quotas 843 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide AWS WAF Classic has default quotas on the number of entities per account per Region. You can request an increase to these. Resource Web ACLs Rules Rate-based-rules Conditions per account per Region Requests per Second Default quota per account per Region 50 100 5 For all condition s except for regex match and geo match, 100 of each condition type. For example, 100 size constrain t condition s and 100 IP match condition s. For regex and geo match conditions, see the following table. 25,000 per web ACL* *This quota applies only to AWS WAF Classic on an Application Load Balancer. Requests per Second (RPS) quotas for AWS WAF Classic on CloudFront are the same as the RPS quotas support by CloudFront that is described in the CloudFront Developer Guide. AWS WAF Classic quotas 844 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide The following quotas on AWS WAF Classic entities can't be changed. Resource Rule groups per web ACL Rules per web ACL Conditions per rule Quota per account per Region 2: 1 customer- created rule group and 1 AWS Marketpla ce rule group 10 10 IP address ranges (in CIDR notation) per IP match condition 10,000 You can update up to 1,000 addresses at a time. The API call UpdateIPS et accepts a maximum of 1,000 addresses in a single request. 10,000 100 10 10 10 IP addresses blocked per rate-based rule Minimum rate-based rule rate limit per 5 minute period Filters per cross-site scripting match condition Filters per size constraint condition Filters per SQL injection match condition AWS WAF Classic quotas 845 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Resource Quota per account per Region Filters per string match condition In string match conditions, the number of characters in HTTP header names, when you've conﬁgured AWS WAF Classic to inspect the headers in web requests for a speciﬁed value In string match conditions, the number of characters in the value that you want AWS WAF Classic to search for Regex match conditions In regex match conditions, the number of characters in the pattern that you want AWS WAF Classic to search for In regex match conditions, the number of patterns per pattern set In regex match conditions, the number of pattern sets per regex condition Pattern sets Geo match conditions Locations per geo match condition 10 40 50 10 70 10 1 5 50 50 AWS WAF Classic has the following ﬁxed quotas on calls per account per Region. These quotas apply to the total calls to the service through any available means, including the console, CLI, AWS CloudFormation, the REST API, and the SDKs. These quotas can't be changed. Call type Maximum number of calls to AssociateWebACL Quota per account per Region 1 request every 2 seconds AWS WAF Classic quotas 846 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Call type Maximum number of calls to DisassociateWebACL Maximum number of calls to GetWebACLForResource Maximum number of calls to ListResourcesForWebACL Maximum number of calls to CreateWebACLMigrationStack Maximum number of calls to GetChangeToken Maximum number of calls to GetChangeTokenStatus Quota per account per Region 1 request every 2 seconds 1 request per second 1 request per second 1 request per second 10 requests per second 1 request per second Maximum number of calls to any individual List action, if no other quota is deﬁned for it 5 requests per second Maximum number of calls to any individual Create, Put, Get, or Update action, if no other quota is deﬁned for it 1 request per second AWS WAF Classic quotas 847 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide AWS Shield Protection against Distributed Denial of Service (DDoS) attacks is of primary importance for your internet-facing applications. When you build your application on AWS, you can make use of protections that AWS provides at no additional cost. Additionally, you can use the AWS Shield Advanced managed threat protection service to improve your security posture with additional DDoS detection, mitigation, and response capabilities. AWS is committed to providing you with the tools, best practices, and services to help ensure high availability, security, and resiliency in your defense against bad actors on the internet. This guide
waf-dg-299	waf-dg.pdf	299	AWS Shield Advanced Developer Guide AWS Shield Protection against Distributed Denial of Service (DDoS) attacks is of primary importance for your internet-facing applications. When you build your application on AWS, you can make use of protections that AWS provides at no additional cost. Additionally, you can use the AWS Shield Advanced managed threat protection service to improve your security posture with additional DDoS detection, mitigation, and response capabilities. AWS is committed to providing you with the tools, best practices, and services to help ensure high availability, security, and resiliency in your defense against bad actors on the internet. This guide is provided to help IT decision makers and security engineers understand how to use Shield and Shield Advanced to better protect their applications from DDoS attacks and other external threats. When you build your application on AWS, you receive automatic protection by AWS against common volumetric DDoS attack vectors, like UDP reﬂection attacks and TCP SYN ﬂoods. You can leverage these protections to ensure the availability of the applications that you run on AWS by designing and conﬁguring your architecture for DDoS resiliency. This guide provides recommendations that can help you design, create, and conﬁgure your application architectures for DDoS resiliency. Applications that adhere to the best practices provided in this guide can beneﬁt from an improved continuity of availability when they are targeted by larger DDoS attacks and by wider ranges of DDoS attack vectors. Additionally, this guide shows you how to use Shield Advanced to implement an optimized DDoS protection posture for your critical applications. These include applications for which you've guaranteed a certain level of availability to your customers and those that require operational support from AWS during DDoS events. Security is a shared responsibility between AWS and you. The shared responsibility model describes this as security of the cloud and security in the cloud: • Security of the cloud – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. AWS also provides you with services that you can use securely. The eﬀectiveness of our security is regularly tested and veriﬁed by third-party auditors as part of the AWS compliance programs. To learn about the compliance programs that apply to Shield Advanced, see AWS Services in Scope by Compliance Program. • Security in the cloud – Your responsibility is determined by the AWS service that you use. You are also responsible for other factors including the sensitivity of your data, your organization’s requirements, and applicable laws and regulations. 848 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide How AWS Shield and Shield Advanced work This page explains the diﬀerence between AWS Shield Standard and AWS Shield Advanced. It also describes the classes of attacks that Shield detects. AWS Shield Standard and AWS Shield Advanced provide protections against Distributed Denial of Service (DDoS) attacks for AWS resources at the network and transport layers (layer 3 and 4) and the application layer (layer 7). A DDoS attack is an attack in which multiple compromised systems try to ﬂood a target with traﬃc. A DDoS attack can prevent legitimate end users from accessing the target services and can cause the target to crash due to overwhelming traﬃc volume. AWS Shield provides protection against a wide range of known DDoS attack vectors and zero-day attack vectors. Shield detection and mitigation is designed to provide coverage against threats even if they are not explicitly known to the service at the time of detection. Shield Standard is provided automatically and at no extra charge when you use AWS. For higher levels of protection against attacks, you can subscribe to AWS Shield Advanced. Classes of attacks that Shield detects include the following: How Shield and Shield Advanced work 849 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Network volumetric attacks (layer 3) – This is a sub category of infrastructure layer attack vectors. These vectors attempt to saturate the capacity of the targeted network or resource, to deny service to legitimate users. • Network protocol attacks (layer 4) – This is a sub category of infrastructure layer attack vectors. These vectors abuse a protocol to deny service to the targeted resource. A common example of a network protocol attack is a TCP SYN ﬂood, which can exhaust connection state on resources like servers, load balancers, or ﬁrewalls. A network protocol attack can also be volumetric. For example, a larger TCP SYN ﬂood may intend to saturate the capacity of a network while also exhausting the state of the targeted resource or intermediate resources. • Application layer attacks (layer 7) – This category of attack vector attempts to deny service to legitimate users by ﬂooding an application with queries that are valid for the target, such as web request ﬂoods. Contents •
waf-dg-300	waf-dg.pdf	300	A common example of a network protocol attack is a TCP SYN ﬂood, which can exhaust connection state on resources like servers, load balancers, or ﬁrewalls. A network protocol attack can also be volumetric. For example, a larger TCP SYN ﬂood may intend to saturate the capacity of a network while also exhausting the state of the targeted resource or intermediate resources. • Application layer attacks (layer 7) – This category of attack vector attempts to deny service to legitimate users by ﬂooding an application with queries that are valid for the target, such as web request ﬂoods. Contents • AWS Shield Standard overview • AWS Shield Advanced overview • List of AWS resources that AWS Shield Advanced protects • AWS Shield Advanced capabilities and options • Deciding whether to subscribe to AWS Shield Advanced and apply additional protections • Examples of DDoS attacks • How AWS Shield detects events • AWS Shield detection logic for infrastructure layer threats (layer 3 and layer 4) • Shield Advanced detection logic for application layer threats (layer 7) • Shield Advanced detection logic for multiple resources in an application • How AWS Shield mitigates events • List of AWS Shield DDoS mitigation features • AWS Shield mitigation logic for CloudFront and Route 53 • AWS Shield mitigation logic for AWS Regions • AWS Shield mitigation logic for AWS Global Accelerator standard accelerators • AWS Shield Advanced mitigation logic for Elastic IPs • AWS Shield Advanced mitigation logic for web applications How Shield and Shield Advanced work 850 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide AWS Shield Standard overview AWS Shield is a managed threat protection service that protects the perimeter of your application. The perimeter is the ﬁrst point of entry for application traﬃc coming from outside the AWS network. To determine where your application perimeter lies, consider how users access your application from the internet. If the ﬁrst point of entry is in an AWS Region, then the application perimeter is your Amazon Virtual Private Cloud (VPC). If users are directed to your application by Amazon Route 53, and ﬁrst access the application using Amazon CloudFront or AWS Global Accelerator, then the application perimeter begins at the edge of the AWS network. Shield provides DDoS detection and mitigation beneﬁts for all applications running on AWS, but the decisions that you make when you design your application architecture will inﬂuence your level of DDoS resiliency. DDoS Resiliency is your application’s ability to continue operating within expected parameters during an attack. All AWS customers beneﬁt from the automatic protection of Shield Standard, at no additional charge. Shield Standard defends against the most common, frequently occurring network and transport layer DDoS attacks that target your website or applications. While Shield Standard helps protect all AWS customers, you get particular beneﬁt with Amazon Route 53 hosted zones, Amazon CloudFront distributions, and AWS Global Accelerator standard accelerators. These resources receive comprehensive availability protection against all known network and transport layer attacks. AWS Shield Advanced overview AWS Shield Advanced is a managed service that helps you protect your application against external threats, like DDoS attacks, volumetric bots, and vulnerability exploitation attempts. For higher levels of protection against attacks, you can subscribe to AWS Shield Advanced. When you subscribe to Shield Advanced and add protection to your resources, Shield Advanced provides expanded DDoS attack protection for those resources. The protections that you receive from Shield Advanced can vary depending on your architecture and conﬁguration choices. Use the information in this guide to build and protect resilient applications using Shield Advanced, and to escalate when you need expert help. Shield Advanced subscriptions and AWS WAF costs AWS Shield Standard overview 851 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Your Shield Advanced subscription covers the costs of using standard AWS WAF capabilities for resources that you protect with Shield Advanced. The standard AWS WAF fees that are covered by your Shield Advanced protections are the cost per web ACL, the cost per rule, and the base price per million requests for web request inspection, up to 1,500 WCUs and up to the default body size. Enabling Shield Advanced automatic application layer DDoS mitigation adds a rule group to your web ACL that uses 150 web ACL capacity units (WCUs). These WCUs count against the WCU usage in your web ACL. For more information, see Automating application layer DDoS mitigation with Shield Advanced , Protecting the application layer with the Shield Advanced rule group, and Web ACL capacity units (WCUs) in AWS WAF. Your subscription to Shield Advanced does not cover the use of AWS WAF for resources that you do not protect using Shield Advanced. It also does not cover any additional non-standard AWS WAF costs for protected resources. Examples of non-standard AWS
waf-dg-301	waf-dg.pdf	301	adds a rule group to your web ACL that uses 150 web ACL capacity units (WCUs). These WCUs count against the WCU usage in your web ACL. For more information, see Automating application layer DDoS mitigation with Shield Advanced , Protecting the application layer with the Shield Advanced rule group, and Web ACL capacity units (WCUs) in AWS WAF. Your subscription to Shield Advanced does not cover the use of AWS WAF for resources that you do not protect using Shield Advanced. It also does not cover any additional non-standard AWS WAF costs for protected resources. Examples of non-standard AWS WAF costs are those for Bot Control, for the CAPTCHA rule action, for web ACLs that use more than 1,500 WCUs, and for inspecting the request body beyond the default body size. The full list is provided on the AWS WAF pricing page. For full information and pricing examples, see Shield Pricing and AWS WAF Pricing. Shield Advanced subscription billing If you’re an AWS Channel Reseller, talk to your account team for information and guidance. This billing information is for customers that are not AWS Channel Resellers. For all others, the following subscription and billing guidelines apply: • For accounts that are members of an AWS Organizations organization, AWS bills the Shield Advanced subscriptions against the payer account for the organization, regardless of whether the payer account itself is subscribed. • When you subscribe multiple accounts that are in the same AWS Organizations consolidated billing account family, one subscription price covers all subscribed accounts in the family. The organization must own all of the AWS accounts and all of their resources. • When you subscribe multiple accounts for multiple organizations, you can still pay one subscription fee across all of the organizations, accounts, and resources providing you own all of them. Contact your account manager or AWS support and request a fee waiver on the AWS Shield Advanced subscription charges for all but one of the organizations. For detailed pricing information and examples, see AWS Shield Pricing. AWS Shield Advanced overview 852 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Topics • List of AWS resources that AWS Shield Advanced protects • AWS Shield Advanced capabilities and options • Deciding whether to subscribe to AWS Shield Advanced and apply additional protections List of AWS resources that AWS Shield Advanced protects Note Shield Advanced protections are only enabled for resources that you have explicitly speciﬁed in Shield Advanced or that you protect through an AWS Firewall Manager Shield Advanced policy. Shield Advanced doesn't automatically protect your resources. You can use Shield Advanced for advanced monitoring and protection with the following resource types: • Amazon CloudFront distributions. For CloudFront continuous deployment, Shield Advanced protects any staging distribution that's associated with a protected primary distribution. • Amazon Route 53 hosted zones. • AWS Global Accelerator standard accelerators. • Amazon EC2 Elastic IP addresses. Shield Advanced protects the resources that are associated with protected Elastic IP addresses. • Amazon EC2 instances, through association to Amazon EC2 Elastic IP addresses. • The following Elastic Load Balancing (ELB) load balancers: • Application Load Balancers. • Classic Load Balancers. • Network Load Balancers, through associations to Amazon EC2 Elastic IP addresses. For additional information about protections for these resource types, see List of resources that AWS Shield Advanced protects. AWS Shield Advanced overview 853 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide AWS Shield Advanced capabilities and options AWS Shield Advanced subscription includes the following capabilities and options. These supplement the DDoS detection and mitigation capabilities that you already receive with AWS. • AWS WAF integration – Shield Advanced uses AWS WAF web ACLs, rules, and rule groups as part of its application layer protections. For more information about AWS WAF, see How AWS WAF works. Note Your Shield Advanced subscription covers the costs of using standard AWS WAF capabilities for resources that you protect with Shield Advanced. The standard AWS WAF fees that are covered by your Shield Advanced protections are the cost per web ACL, the cost per rule, and the base price per million requests for web request inspection, up to 1,500 WCUs and up to the default body size. Enabling Shield Advanced automatic application layer DDoS mitigation adds a rule group to your web ACL that uses 150 web ACL capacity units (WCUs). These WCUs count against the WCU usage in your web ACL. For more information, see Automating application layer DDoS mitigation with Shield Advanced , Protecting the application layer with the Shield Advanced rule group, and Web ACL capacity units (WCUs) in AWS WAF. Your subscription to Shield Advanced does not cover the use of AWS WAF for resources that you do not protect using Shield Advanced. It also does not cover any additional non-
waf-dg-302	waf-dg.pdf	302	body size. Enabling Shield Advanced automatic application layer DDoS mitigation adds a rule group to your web ACL that uses 150 web ACL capacity units (WCUs). These WCUs count against the WCU usage in your web ACL. For more information, see Automating application layer DDoS mitigation with Shield Advanced , Protecting the application layer with the Shield Advanced rule group, and Web ACL capacity units (WCUs) in AWS WAF. Your subscription to Shield Advanced does not cover the use of AWS WAF for resources that you do not protect using Shield Advanced. It also does not cover any additional non- standard AWS WAF costs for protected resources. Examples of non-standard AWS WAF costs are those for Bot Control, for the CAPTCHA rule action, for web ACLs that use more than 1,500 WCUs, and for inspecting the request body beyond the default body size. The full list is provided on the AWS WAF pricing page. For full information and pricing examples, see Shield Pricing and AWS WAF Pricing. • Automatic application layer DDoS mitigation – You can conﬁgure Shield Advanced to respond automatically to mitigate application layer (layer 7) attacks against your protected resources. With automatic mitigation, Shield Advanced enforces AWS WAF rate limiting on requests from known DDoS sources, and it automatically adds and manages custom AWS WAF protections in response to detected DDoS attacks. You can conﬁgure automatic mitigation to count or block the web requests that are part of an attack. For more information, see Automating application layer DDoS mitigation with Shield Advanced . AWS Shield Advanced overview 854 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Health-based detection – You can use Amazon Route 53 health checks with Shield Advanced to inform event detection and mitigation. Health checks monitor your application according to your speciﬁcations, reporting healthy when your speciﬁcations are met and unhealthy when they aren't. Using health checks with Shield Advanced helps prevent false positives and provides faster detection and mitigation when a protected resource is unhealthy. You can use health- based detection for any resource type except Route 53 hosted zones. Shield Advanced proactive engagement is available only for resources that have health-based detection enabled. For more information, see Health-based detection using health checks with Shield Advanced and Route 53. • Protection groups – You can use protection groups to create logical groupings of your protected resources, for enhanced detection and mitigation of the group as a whole. You can deﬁne the criteria for membership in a protection group so that newly protected resources are automatically included. A protected resource can belong to multiple protection groups. For more information, see Grouping your AWS Shield Advanced protections. • Enhanced visibility into DDoS events and attacks – Shield Advanced gives you access to advanced, real-time metrics and reports for extensive visibility into events and attacks on your protected AWS resources. You can access this information through the Shield Advanced API and console, and through Amazon CloudWatch metrics. For more information, see Visibility into DDoS events with Shield Advanced. • Centralized management of Shield Advanced protections by AWS Firewall Manager – You can use Firewall Manager to automatically apply Shield Advanced protections to your new accounts and resources and to deploy AWS WAF rules to your web ACLs. Firewall Manager Shield Advanced protection policies are included at no additional charge for Shield Advanced customers. You can also centralize your Shield Advanced monitoring activities for your accounts by using Firewall Manager with an Amazon Simple Notiﬁcation Service (SNS) topic or AWS Security Hub. For more information about using Firewall Manager to manage Shield Advanced protections, see AWS Firewall Manager and Using AWS Shield Advanced policies in Firewall Manager. For information about Firewall Manager pricing, see AWS Firewall Manager Pricing. • AWS Shield Response Team (SRT) – The SRT has deep experience in protecting AWS, Amazon.com, and its subsidiaries. As an AWS Shield Advanced customer, you can contact the SRT at any time for assistance during a DDoS attack that aﬀects the availability of your application. You can also work with the SRT to create and manage custom mitigations for your resources. AWS Shield Advanced overview 855 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide To use the services of the SRT, you must also be subscribed to the Business Support plan or the Enterprise Support plan. For more information, see Managed DDoS event response with Shield Response Team (SRT) support. • Proactive engagement – With proactive engagement, the Shield Response Team (SRT) contacts you directly if the Amazon Route 53 health check that you have associated with your protected resource becomes unhealthy during an event that's detected by Shield Advanced. This gives you quicker engagement with experts when the availability of your application might be aﬀected by a suspected attack. For
waf-dg-303	waf-dg.pdf	303	Advanced Developer Guide To use the services of the SRT, you must also be subscribed to the Business Support plan or the Enterprise Support plan. For more information, see Managed DDoS event response with Shield Response Team (SRT) support. • Proactive engagement – With proactive engagement, the Shield Response Team (SRT) contacts you directly if the Amazon Route 53 health check that you have associated with your protected resource becomes unhealthy during an event that's detected by Shield Advanced. This gives you quicker engagement with experts when the availability of your application might be aﬀected by a suspected attack. For more information, see Setting up proactive engagement for the SRT to contact you directly. • Cost protection opportunities – Shield Advanced oﬀers some cost protection against spikes in your AWS bill that might result from a DDoS attack against your protected resources. This can include coverage for spikes in Shield Advanced data transfer out (DTO) usage fees. Shield Advanced provides any cost protection in the form of Shield Advanced service credits. For more information, see Requesting a credit in AWS Shield Advanced after an attack. Deciding whether to subscribe to AWS Shield Advanced and apply additional protections Review the scenarios in this section for help deciding which accounts to subscribe to AWS Shield Advanced and where to apply additional protections. With Shield Advanced, you pay one monthly subscription fee for all accounts created under a consolidated billing account, plus usage fees based on GB of data transferred out. For information about Shield Advanced pricing, see AWS Shield Advanced Pricing. To protect an application and its resources with Shield Advanced, you subscribe the accounts that manage the application to Shield Advanced and then you add protections to the application's resources. For information about subscribing accounts and protecting resources, see Setting up AWS Shield Advanced. Shield Advanced subscriptions and AWS WAF costs Your Shield Advanced subscription covers the costs of using standard AWS WAF capabilities for resources that you protect with Shield Advanced. The standard AWS WAF fees that are covered by AWS Shield Advanced overview 856 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide your Shield Advanced protections are the cost per web ACL, the cost per rule, and the base price per million requests for web request inspection, up to 1,500 WCUs and up to the default body size. Enabling Shield Advanced automatic application layer DDoS mitigation adds a rule group to your web ACL that uses 150 web ACL capacity units (WCUs). These WCUs count against the WCU usage in your web ACL. For more information, see Automating application layer DDoS mitigation with Shield Advanced , Protecting the application layer with the Shield Advanced rule group, and Web ACL capacity units (WCUs) in AWS WAF. Your subscription to Shield Advanced does not cover the use of AWS WAF for resources that you do not protect using Shield Advanced. It also does not cover any additional non-standard AWS WAF costs for protected resources. Examples of non-standard AWS WAF costs are those for Bot Control, for the CAPTCHA rule action, for web ACLs that use more than 1,500 WCUs, and for inspecting the request body beyond the default body size. The full list is provided on the AWS WAF pricing page. For full information and pricing examples, see Shield Pricing and AWS WAF Pricing. Shield Advanced subscription billing If you’re an AWS Channel Reseller, talk to your account team for information and guidance. This billing information is for customers that are not AWS Channel Resellers. For all others, the following subscription and billing guidelines apply: • For accounts that are members of an AWS Organizations organization, AWS bills the Shield Advanced subscriptions against the payer account for the organization, regardless of whether the payer account itself is subscribed. • When you subscribe multiple accounts that are in the same AWS Organizations consolidated billing account family, one subscription price covers all subscribed accounts in the family. The organization must own all of the AWS accounts and all of their resources. • When you subscribe multiple accounts for multiple organizations, you can still pay one subscription fee across all of the organizations, accounts, and resources providing you own all of them. Contact your account manager or AWS support and request a fee waiver on the AWS Shield Advanced subscription charges for all but one of the organizations. For detailed pricing information and examples, see AWS Shield Pricing. Identifying the applications to protect AWS Shield Advanced overview 857 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Consider implementing Shield Advanced protections for applications where you need any of the following: • Guaranteed availability for the users of the application. • Rapid access to DDoS mitigation experts if the application is aﬀected by a DDoS attack. • Awareness by
waf-dg-304	waf-dg.pdf	304	them. Contact your account manager or AWS support and request a fee waiver on the AWS Shield Advanced subscription charges for all but one of the organizations. For detailed pricing information and examples, see AWS Shield Pricing. Identifying the applications to protect AWS Shield Advanced overview 857 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Consider implementing Shield Advanced protections for applications where you need any of the following: • Guaranteed availability for the users of the application. • Rapid access to DDoS mitigation experts if the application is aﬀected by a DDoS attack. • Awareness by AWS that the application might be aﬀected by a DDoS attack and notiﬁcation of attacks from AWS and escalation to your security or operations teams. • Predictability in your cloud costs, including when a DDoS attack aﬀects your use of AWS services. If an application or its resources require any of the above, consider creating subscriptions for the related accounts. Identifying the resources to protect For each subscribed account, consider adding a Shield Advanced protection to each resource that has any of the following characteristics: • The resource serves external users on the internet. • The resource is exposed to the internet and is also part of a critical application. Consider every exposed resource, regardless of whether you intend it to be accessed by users on the internet. • The resource is protected by an AWS WAF web ACL. To learn more about creating and managing protections for your resources, see Resource protections in AWS Shield Advanced. Additionally, follow the recommendations in this guide to help ensure that you architect your application for DDoS resiliency and that you have properly conﬁgured the features of Shield Advanced for optimal protections. Examples of DDoS attacks AWS Shield Advanced provides expanded protection against many types of attacks. The following list describes some common attack types: Examples of DDoS attacks 858 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide User Datagram Protocol (UDP) reﬂection attacks In UDP reﬂection attacks, an attacker can spoof the source of a request and use UDP to elicit a large response from the server. The extra network traﬃc directed towards the spoofed, attacked IP address can slow the targeted server and prevent legitimate end users from accessing needed resources. TCP SYN ﬂood The intent of an TCP SYN ﬂood attack is to exhaust the available resources of a system by leaving connections in a half-open state. When a user connects to a TCP service like a web server, the client sends a TCP SYN packet. The server returns an acknowledgment, and the client returns its own acknowledgement, completing the three-way handshake. In a TCP SYN ﬂood, the third acknowledgment is never returned, and the server is left waiting for a response. This can prevent other users from connecting to the server. DNS query ﬂood In a DNS query ﬂood, an attacker uses multiple DNS queries to exhaust the resources of a DNS server. AWS Shield Advanced can help provide protection against DNS query ﬂood attacks on Route 53 DNS servers. HTTP ﬂood/cache-busting (layer 7) attacks With an HTTP ﬂood, including GET and POST ﬂoods, an attacker sends multiple HTTP requests that appear to be from a real user of the web application. Cache-busting attacks are a type of HTTP ﬂood that uses variations in the HTTP request's query string that prevent use of edge- located cached content and forces the content to be served from the origin web server, causing additional and potentially damaging strain on the origin web server. How AWS Shield detects events AWS operates service-level detection systems for the AWS network and individual AWS services, to ensure that they remain available during a DDoS attack. Additionally, resource-level detection systems monitor each individual AWS resource to ensure that traﬃc toward the resource remains within expected parameters. This combination protects both the targeted AWS resource and AWS services, by applying mitigations that drop known bad packets, highlight potentially malicious traﬃc, and prioritize traﬃc from end users. Detected events appear in your Shield Advanced event summaries, attack details, and Amazon CloudWatch metrics as either the name of the DDoS attack vector or as Volumetric if the How Shield detects events 859 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide evaluation was based on traﬃc volume instead of signature. For more information on the attack vector dimensions that are available within the DDoSDetected CloudWatch metric, see AWS Shield Advanced metrics. Topics • AWS Shield detection logic for infrastructure layer threats (layer 3 and layer 4) • Shield Advanced detection logic for application layer threats (layer 7) • Shield Advanced detection logic for multiple resources in an application AWS Shield detection logic for infrastructure layer threats (layer 3 and layer 4) This page explains how
waf-dg-305	waf-dg.pdf	305	How Shield detects events 859 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide evaluation was based on traﬃc volume instead of signature. For more information on the attack vector dimensions that are available within the DDoSDetected CloudWatch metric, see AWS Shield Advanced metrics. Topics • AWS Shield detection logic for infrastructure layer threats (layer 3 and layer 4) • Shield Advanced detection logic for application layer threats (layer 7) • Shield Advanced detection logic for multiple resources in an application AWS Shield detection logic for infrastructure layer threats (layer 3 and layer 4) This page explains how event detection works for the infrastructure (network and transport) layers. The detection logic used to protect targeted AWS resources against DDoS attacks in the infrastructure layers (layer 3 and layer 4) depends on the resource type and whether the resource is protected with AWS Shield Advanced. Detection for Amazon CloudFront and Amazon Route 53 When you serve your web application with CloudFront and Route 53, all packets to the application are inspected by a fully inline DDoS mitigation system, which does not introduce any observable latency. DDoS attacks against CloudFront distributions and Route 53 hosted zones are mitigated in real time. These protections apply regardless of whether you use AWS Shield Advanced. Follow the best practice of using CloudFront and Route 53 as the entry point of your web application wherever possible for the fastest detection and mitigation of DDoS events. Detection for AWS Global Accelerator and regional services Resource-level detection protects AWS Global Accelerator standard accelerators and resources that are launched in AWS Regions, like Classic Load Balancers, Application Load Balancers, and Elastic IP addresses (EIPs). These resource types are monitored for traﬃc elevations that may indicate the presence of a DDoS attack that requires a mitigation. Every minute, traﬃc to each AWS resource is evaluated. If traﬃc to a resource is elevated, additional checks are performed to measure the capacity of the resource. Shield performs the following standard checks: • Amazon Elastic Compute Cloud (Amazon EC2) instances, EIPs attached to Amazon EC2 instances – Shield retrieves capacity from the protected resource. The capacity depends on the How Shield detects events 860 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide target’s instance type, instance size, and other factors such as whether the instance is using enhanced networking. • Classic Load Balancers and Application Load Balancers – Shield retrieves capacity from the targeted load balancer node. • EIPs attached to Network Load Balancers – Shield retrieves capacity from the targeted load balancer. The capacity is independent of the target load balancer's group conﬁguration. • AWS Global Accelerator standard accelerators – Shield retrieves capacity, which is based on the endpoint conﬁguration. These evaluations occur across multiple dimensions of network traﬃc, such as port and protocol. If the capacity of the targeted resource is exceeded, Shield places a DDoS mitigation. The mitigations placed by Shield will reduce DDoS traﬃc, but might not eliminate it. Shield may also place a mitigation if a fraction of the resource’s capacity is exceeded on a traﬃc dimension that's consistent with known DDoS attack vectors. Shield places this mitigation with a limited time to live (TTL), which it extends as long as the attack is ongoing. Note Mitigations placed by Shield will reduce DDoS traﬃc, but may not eliminate it. You can augment Shield with solutions like AWS Network Firewall or an on-host ﬁrewall like iptables to prevent your application from processing traﬃc that is not valid for your application or was not generated by legitimate end users. Shield Advanced protections add the following to the existing Shield detection activities: • Lower detection thresholds – Shield Advanced places mitigations at one half of the calculated capacity. This can provide faster mitigations for attacks that ramp up slowly and mitigation of attacks that have a more ambiguous volumetric signature. • Intermittent attack protection – Shield Advanced places mitigations with an exponentially increasing time to live (TTL), based on the frequency and duration of attacks. This keeps mitigations in place longer when a resource is frequently targeted and when an attack occurs in short bursts. • Health-based detection – When you associate a Route 53 health check with a Shield Advanced protected resource, the status of the health check is used in the detection logic. During a detected event, if the health check is healthy, Shield Advanced requires greater conﬁdence that How Shield detects events 861 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide the event is an attack before placing a mitigation. If instead the health check is unhealthy, Shield Advanced might place a mitigation even before conﬁdence has been established. This feature helps avoid false positives and provides quicker reactions to attacks that aﬀect your application. For information about health checks
waf-dg-306	waf-dg.pdf	306	check with a Shield Advanced protected resource, the status of the health check is used in the detection logic. During a detected event, if the health check is healthy, Shield Advanced requires greater conﬁdence that How Shield detects events 861 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide the event is an attack before placing a mitigation. If instead the health check is unhealthy, Shield Advanced might place a mitigation even before conﬁdence has been established. This feature helps avoid false positives and provides quicker reactions to attacks that aﬀect your application. For information about health checks with Shield Advanced, see Health-based detection using health checks with Shield Advanced and Route 53. Shield Advanced detection logic for application layer threats (layer 7) This page explains how event detection works for the application layer. AWS Shield Advanced provides web application layer detection for protected Amazon CloudFront distributions and Application Load Balancers. When you protect these resource types with Shield Advanced, you can associate an AWS WAF web ACL with your protection to enable web application layer detection. Shield Advanced consumes request data for the associated web ACL and builds a traﬃc baseline for your application. Web application layer detection relies on the native integration between Shield Advanced and AWS WAF. To learn more about application layer protections, including associating an AWS WAF web ACL to a Shield Advanced protected resource, see Protecting the application layer (layer 7) with AWS Shield Advanced and AWS WAF. For web application layer detection, Shield Advanced monitors application traﬃc and compares it to historic baselines looking for anomalies. This monitoring covers total volume and the composition of traﬃc. During a DDoS attack, we expect both the volume and composition of traﬃc to change, and Shield Advanced requires a statistically signiﬁcant deviation in both to declare an event. Shield Advanced performs its measurements against historical time windows. This approach reduces false positive notiﬁcations from legitimate changes in traﬃc volume or from changes in traﬃc that match an expected pattern, such as a sale that's oﬀered at the same time each day. Note Avoid false positives in your Shield Advanced protections by giving Shield Advanced time to establish baselines that represent normal, legitimate traﬃc patterns. Shield Advanced begins to collect information for its baseline when you associate a web ACL with your protected resource. Associate a web ACL with your protected resource at least 24 hours before any planned event that might cause unusual patterns in your web traﬃc. Shield Advanced web application layer detection is most accurate when it has observed 30 days of normal traﬃc. How Shield detects events 862 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide The time that Shield Advanced takes to detect an event is aﬀected by how much change it observes in the volume of traﬃc. For lower volume changes, Shield Advanced observes traﬃc for a longer period, in order to build conﬁdence that an event is occurring. For higher volume changes, Shield Advanced detects and reports an event more quickly. A rate-based rule in your web ACL, whether added by you or by the Shield Advanced automatic application layer mitigation feature, can mitigate an attack before it reaches a detectable level. For more information about automatic application layer DDoS mitigation, see Automating application layer DDoS mitigation with Shield Advanced . Note You can architect your application to scale in response to elevated traﬃc or load to ensure that it is not aﬀected by smaller request ﬂoods. With Shield Advanced, your protected resources are covered by cost protection. This helps protect you against unexpected increases in your cloud bill that might occur as the result of a DDoS attack. To learn more about Shield Advanced cost protection, see Requesting a credit in AWS Shield Advanced after an attack. Shield Advanced detection logic for multiple resources in an application This page explains how event detection works for multiple resources in an application. You can use AWS Shield Advanced protection groups to create collections of protected resources that are part of the same application. You can choose which protected resources to place in a group or indicate that all resources of the same type should be treated as one group. For example, you might create a group of all Application Load Balancers. When you create a protection group, Shield Advanced detection aggregates all traﬃc for the protected resources within the group. This is useful if you have many resources that each have a small amount of traﬃc, but with a large aggregated volume. You can also use protection groups to preserve application baselines, for the case of blue-green deployments where traﬃc is transferred between protected resources. You can choose to aggregate the traﬃc in your protection group in one of the following ways: • Sum – This
waf-dg-307	waf-dg.pdf	307	as one group. For example, you might create a group of all Application Load Balancers. When you create a protection group, Shield Advanced detection aggregates all traﬃc for the protected resources within the group. This is useful if you have many resources that each have a small amount of traﬃc, but with a large aggregated volume. You can also use protection groups to preserve application baselines, for the case of blue-green deployments where traﬃc is transferred between protected resources. You can choose to aggregate the traﬃc in your protection group in one of the following ways: • Sum – This aggregation combines all traﬃc across resources in the protection group. You can use this aggregation to ensure that newly created resources have an existing baseline and to reduce detection sensitivity, which can help prevent false positives. How Shield detects events 863 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Mean – This aggregation uses the average of all traﬃc across the protection group. You can use this aggregation for applications where traﬃc across resources is uniform, like load balancers. • Max – This aggregation uses the highest traﬃc of any resource in the protection group. You can use this aggregation when there are multiple tiers of an application in a protection group. For example, you may have a protection group that includes a CloudFront distribution, its Application Load Balancer origin, and the Application Load Balancer’s Amazon EC2 instance targets. You can also use protection groups to improve the speed at which Shield Advanced places mitigations, for attacks that targets multiple internet-facing Elastic IPs or AWS Global Accelerator standard accelerators. When one resource in a protection group is targeted, Shield Advanced establishes conﬁdence for the other resources in the group. This places Shield Advanced detection on alert and can reduce the time required to create additional mitigations. To learn more about protection groups, see Grouping your AWS Shield Advanced protections. How AWS Shield mitigates events This page introduces how AWS Shield event mitigation works. The mitigation logic that protects your application can vary depending on your application architecture. When you protect a web application with Amazon CloudFront and Amazon Route 53, you beneﬁt from mitigations that are speciﬁc to web and DNS use cases and that protect all traﬃc for the services. When your application's entry point is a resource that runs in an AWS Region, the mitigation logic varies depending on the service, the resource type, and your use of AWS Shield Advanced. AWS DDoS mitigation systems are developed by Shield engineers and they're closely integrated with AWS services. The engineers take into account aspects of your architecture such as the capacity and health of targeted resources. Shield engineers continually monitor the eﬃcacy and performance of DDoS mitigation systems and are able to respond quickly when new threats are discovered or anticipated. You can architect your application to scale in response to elevated traﬃc or load, to help ensure that it's not aﬀected by smaller request ﬂoods. If you use Shield Advanced to protect your resources, you receive coverage against unexpected increases in your cloud bill that might occur as the result of a DDoS attack. Infrastructure mitigations How Shield mitigates events 864 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide For infrastructure layer attacks, AWS Shield DDoS mitigation systems are present at the AWS network border and at AWS edge locations. The placement of multiple levels of security controls throughout the AWS infrastructure provides defense-in-depth to your cloud applications. Shield maintains DDoS mitigation systems at all points of ingress from the internet. When Shield detects a DDoS attack, for each point of ingress, it reroutes the traﬃc through the DDoS mitigation systems in the same location. This doesn’t introduce any observable additional latency, and provides a mitigation capacity of more than 100 TeraBits Per Second (Tbps) across all AWS Regions and all edge locations. Shield protects your resource availability without rerouting traﬃc to external or remote scrubbing centers, which could increase latency. • At the AWS network border, for any AWS service or resource, DDoS mitigation systems mitigate infrastructure layer attacks coming from the internet. The systems perform their mitigations when signaled by Shield detection or by an engineer on the Shield Response Team (SRT). • At AWS edge locations, DDoS mitigation systems continuously inspect every packet that's forwarded to Amazon CloudFront distributions and Amazon Route 53 hosted zones, regardless of their origin. When needed, the systems apply mitigations that are speciﬁcally designed for web and DNS traﬃc. An added beneﬁt of using Amazon CloudFront and Amazon Route 53 to protect your web applications is that DDoS attacks are immediately mitigated, without requiring a signal from Shield detection. Application layer mitigations Shield Advanced provides web application layer mitigations for the Amazon CloudFront
waf-dg-308	waf-dg.pdf	308	by Shield detection or by an engineer on the Shield Response Team (SRT). • At AWS edge locations, DDoS mitigation systems continuously inspect every packet that's forwarded to Amazon CloudFront distributions and Amazon Route 53 hosted zones, regardless of their origin. When needed, the systems apply mitigations that are speciﬁcally designed for web and DNS traﬃc. An added beneﬁt of using Amazon CloudFront and Amazon Route 53 to protect your web applications is that DDoS attacks are immediately mitigated, without requiring a signal from Shield detection. Application layer mitigations Shield Advanced provides web application layer mitigations for the Amazon CloudFront distributions and Application Load Balancers where you've enabled Shield Advanced protections. When you enable protection, you associate an AWS WAF web ACL with the resource, to enable web application layer detection. Additionally, you have the option of enabling automatic application layer mitigation, which instructs Shield Advanced to manage protections for you during a DDoS attack. Shield only provides custom mitigations for application layer attacks on resources for which you've enabled Shield Advanced and automatic application layer mitigation. With automatic mitigation, Shield Advanced enforces AWS WAF rate limiting on requests from known DDoS sources, and it automatically adds and manages custom AWS WAF protections in response to detected DDoS attacks. For detailed information about mitigations of this type, see How Shield Advanced manages automatic mitigation. How Shield mitigates events 865 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide A rate-based rule in your web ACL, whether added by you or added by the Shield Advanced automatic application layer mitigation feature, can mitigate an attack before it reaches a detectable level. For more information about detection, see Shield Advanced detection logic for application layer threats (layer 7). Topics • List of AWS Shield DDoS mitigation features • AWS Shield mitigation logic for CloudFront and Route 53 • AWS Shield mitigation logic for AWS Regions • AWS Shield mitigation logic for AWS Global Accelerator standard accelerators • AWS Shield Advanced mitigation logic for Elastic IPs • AWS Shield Advanced mitigation logic for web applications List of AWS Shield DDoS mitigation features The main features of AWS Shield DDoS mitigation are the following: • Packet validation – This ensures that every inspected packet conforms to an expected structure and is valid for its protocol. Supported protocol validations include IP, TCP (including header and options), UDP, ICMP, DNS, and NTP. • Access Control Lists (ACLs) and shapers – An ACL evaluates traﬃc against speciﬁc attributes and either drops matching traﬃc or maps it to a shaper. The shaper limits the packet rate for the matching traﬃc, dropping excess packets in order to contain the volume that reaches the destination. AWS Shield detection and Shield Response Team (SRT) engineers can provide dedicated rate allocations to expected traﬃc and more restrictive rate allocations to traﬃc with attributes that match known DDoS attack vectors. The attributes that an ACL can match include the port, protocol, TCP ﬂags, destination address, source country, and arbitrary patterns in the packet payload. • Suspicion scoring – This uses the knowledge that Shield has of expected traﬃc to apply a score to every packet. Packets that more closely adhere to patterns of known good traﬃc are assigned a lower suspicion score. Observation of known bad traﬃc attributes can increase the suspicion score for a packet. When it's necessary to rate limit packets, Shield drops packets with higher suspicion scores ﬁrst. This helps Shield to mitigate both known and zero-day DDoS attacks while avoiding false positives. How Shield mitigates events 866 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • TCP SYN proxy – This provides protection against TCP SYN ﬂoods by sending TCP SYN cookies to challenge new connections before allowing them to pass to the protected service. The TCP SYN proxy provided by Shield DDoS mitigation is stateless, which allows it to mitigate the largest known TCP SYN ﬂood attacks without reaching state exhaustion. This is achieved by integrating with AWS services to hand oﬀ connection state instead of maintaining a continuous proxy between the client and the protected service. TCP SYN proxy is currently available on Amazon CloudFront and Amazon Route 53. • Rate distribution – This continuously adjusts per-location shaper values based on the ingress pattern of traﬃc toward a protected resource. This prevents rate limiting of customer traﬃc that might not enter the AWS network evenly. AWS Shield mitigation logic for CloudFront and Route 53 This page explains how Shield DDoS mitigation continually inspects traﬃc for CloudFront and Route 53. These services operate from a globally distributed network of AWS edge locations that provide you with broad access to Shield’s DDoS mitigation capacity and deliver your application from infrastructure that's closer to your end users. Important AWS Shield Advanced doesn’t support CloudFront tenants.
waf-dg-309	waf-dg.pdf	309	– This continuously adjusts per-location shaper values based on the ingress pattern of traﬃc toward a protected resource. This prevents rate limiting of customer traﬃc that might not enter the AWS network evenly. AWS Shield mitigation logic for CloudFront and Route 53 This page explains how Shield DDoS mitigation continually inspects traﬃc for CloudFront and Route 53. These services operate from a globally distributed network of AWS edge locations that provide you with broad access to Shield’s DDoS mitigation capacity and deliver your application from infrastructure that's closer to your end users. Important AWS Shield Advanced doesn’t support CloudFront tenants. • CloudFront – Shield DDoS mitigations only allow traﬃc that's valid for web applications to pass through to the service. This provides automatic protection against many common DDoS vectors, like UDP reﬂection attacks. CloudFront maintains persistent connections to your application origin, TCP SYN ﬂoods are automatically mitigated through integration with the Shield TCP SYN proxy feature, and Transport Layer Security (TLS) is terminated at the edge. These combined features ensure that your application origin only receives well-formed web requests and that it's protected against lower-layer DDoS attacks, connection ﬂoods, and TLS abuse. CloudFront uses a combination of DNS traﬃc direction and anycast routing. These techniques improve the resilience of your application by mitigating attacks close to the source, providing fault isolation, and ensuring access to capacity to mitigate the largest known attacks. How Shield mitigates events 867 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Route 53 – Shield mitigations only allow valid DNS requests to reach the service. Shield mitigates DNS query ﬂoods using suspicion scoring that prioritizes known good queries and deprioritizes queries that contain suspicious or known DDoS attack attributes. Route 53 uses shuﬄe sharding to provide a unique set of four resolver IP addresses to every hosted zone, for both IPv4 and IPv6. Each IP address corresponds to a diﬀerent subset of Route 53 locations. Each location subset consists of authoritative DNS servers that only partially overlap with infrastructure in any other subset. This ensures that if a user query fails for any reason, it will be successfully served on retry. Route 53 uses anycast routing to direct DNS queries to the nearest edge location, based on network proximity. Anycast also fans out DDoS traﬃc to many edge locations, which prevents attacks from focusing on a single location. In addition to the speed of mitigation, CloudFront and Route 53 provide broad access to the globally distributed capacity of Shield. To take advantage of these capabilities, use these services as the entry point of your dynamic or static web applications. To learn more about using CloudFront and Route 53 to protect web applications, see How to Help Protect Dynamic Web Applications Against DDoS Attacks by Using Amazon CloudFront and Amazon Route 53. To learn more about fault isolation on Route 53, see A Case Study in Global Fault Isolation. AWS Shield mitigation logic for AWS Regions This page explains how Shield event mitigation logic works in AWS Regions. Resources that are launched in AWS Regions are protected by AWS Shield DDoS mitigation systems placed by Shield resource-level detection. Regional resources include Elastic IPs (EIPs), Classic Load Balancers, and Application Load Balancers. Prior to placing a mitigation, Shield identiﬁes the targeted resource and its capacity. Shield uses the capacity to determine the maximum total traﬃc that its mitigations should allow to be forwarded to the resource. Access control lists (ACLs) and other shapers within the mitigation might decrease the allowed volumes for some traﬃc, for example traﬃc that matches known DDoS attack vectors or that isn't expected to come in large volume. This further limits the amount of traﬃc that the mitigations allow for UDP reﬂection attacks or for TCP traﬃc that has TCP SYN or FIN ﬂags. How Shield mitigates events 868 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Shield determines capacity and places mitigations diﬀerently for each resource type. • For an Amazon EC2 instance, or an EIP that's attached to an Amazon EC2 instance, Shield calculates the capacity based on the instance type and other instance attributes, such as whether the instance has enhanced networking enabled. • For an Application Load Balancer or Classic Load Balancer, Shield calculates capacity individually for each targeted node of the load balancer. DDoS attack mitigations for these resources are provided by a combination of Shield DDoS mitigations and automatic scaling by the load balancer. When the Shield Response Team (SRT) is engaged on an attack against an Application Load Balancer or Classic Load Balancer resource, they might accelerate scaling as an additional protection measure. • Shield calculates capacity for some AWS resources is based on the available capacity of the underlying AWS infrastructure. These resource types include Network Load Balancers (NLBs)
waf-dg-310	waf-dg.pdf	310	For an Application Load Balancer or Classic Load Balancer, Shield calculates capacity individually for each targeted node of the load balancer. DDoS attack mitigations for these resources are provided by a combination of Shield DDoS mitigations and automatic scaling by the load balancer. When the Shield Response Team (SRT) is engaged on an attack against an Application Load Balancer or Classic Load Balancer resource, they might accelerate scaling as an additional protection measure. • Shield calculates capacity for some AWS resources is based on the available capacity of the underlying AWS infrastructure. These resource types include Network Load Balancers (NLBs) and resources that route traﬃc through Gateway Load Balancers or AWS Network Firewall. Note Protect your Network Load Balancers by attaching EIPs that are protected by Shield Advanced. You can work with SRT to build custom mitigations that are based on the expected traﬃc and capacity of the underlying application. When Shield places a mitigation, the initial rate limits that Shield deﬁnes in the mitigation logic are applied equally to every Shield DDoS mitigation system. For example, if Shield places a mitigation with a 100,000 packets per second (pps) limit, it will initially allow 100,000 pps at every location. Then, Shield continuously aggregates mitigation metrics to determine the actual ratio of traﬃc, and uses the ratio to adapt the rate limit for each location. This prevents false positives and ensures that the mitigations are not overly permissive. AWS Shield mitigation logic for AWS Global Accelerator standard accelerators This page explains how Shield event mitigation logic works for AWS Global Accelerator standard accelerators. Shield mitigations only allow valid traﬃc to reach the listener endpoints of a Global Accelerator standard accelerator. Standard accelerators are deployed globally, and they provide you with IP addresses that you can use to route traﬃc to AWS resources in any AWS Region. The rate limits that Shield enforces for a How Shield mitigates events 869 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Global Accelerator mitigation are based on the capacities of the resources to which the standard accelerator routes traﬃc. Shield places mitigations when the total traﬃc exceeds the determined rate, and also when a fraction of that rate is exceeded for known DDoS vectors. When you conﬁgure a standard accelerator, you deﬁne endpoint groups for each AWS Region where you'll route traﬃc for your application. When Shield places a mitigation, it calculates the capacity of each endpoint group and updates rate limits at each Shield DDoS mitigation system accordingly. The rate varies for each location, based on assumptions made by Shield about how traﬃc will route from the internet to your AWS resources. The capacity for an endpoint group is calculated as the number of resources in the group multiplied by the lowest capacity for any resource in the group. At regular intervals, Shield recalculates the capacity for your application and updates the rate limits as needed. Note Using traﬃc dials to change the percentage of traﬃc that's directed to an endpoint group doesn't change how Shield calculates or distributes rate limits to its DDoS mitigation systems. If you use traﬃc dials, conﬁgure your endpoint groups to mirror one another in terms of resource type and quantity. This helps ensure that the capacity calculated by Shield is representative of the resources that are serving traﬃc for your application. For more information about endpoint groups and traﬃc dials in Global Accelerator, see Endpoint groups in AWS Global Accelerator standard accelerators. AWS Shield Advanced mitigation logic for Elastic IPs This page explains how Shield event mitigation logic works for Elastic IPs with AWS Shield Advanced. When you protect an Elastic IP (EIP) with AWS Shield Advanced, Shield Advanced enhances the mitigations that Shield places during a DDoS event. Shield Advanced DDoS mitigation systems replicate the Network ACL (NACL) conﬁguration for the public subnet to which the EIP is associated. For example, if your NACL is conﬁgured to block all UDP traﬃc, Shield Advanced merges that rule into the mitigations that Shield places. This additional functionality can help you to avoid availability risks due to traﬃc that's not valid for your application. You can also use NACLs to block individual source IP addresses or source IP address CIDR ranges. This can be a useful mitigation tool for DDoS attacks that aren't How Shield mitigates events 870 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide distributed. It also lets you easily manage your own allow lists or to block IP addresses that shouldn't communicate with your application, without relying on intervention by AWS engineers. AWS Shield Advanced mitigation logic for web applications AWS Shield Advanced uses AWS WAF to mitigate web application layer attacks. AWS WAF is included with Shield Advanced at no additional cost. Standard application layer protection When you protect an
waf-dg-311	waf-dg.pdf	311	IP address CIDR ranges. This can be a useful mitigation tool for DDoS attacks that aren't How Shield mitigates events 870 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide distributed. It also lets you easily manage your own allow lists or to block IP addresses that shouldn't communicate with your application, without relying on intervention by AWS engineers. AWS Shield Advanced mitigation logic for web applications AWS Shield Advanced uses AWS WAF to mitigate web application layer attacks. AWS WAF is included with Shield Advanced at no additional cost. Standard application layer protection When you protect an Amazon CloudFront distribution or Application Load Balancer with Shield Advanced, you can use Shield Advanced to associate an AWS WAF web ACL with your protected resource, if you don't already have one associated. If you haven't already conﬁgured a web ACL, you can use the Shield Advanced console wizard to create one and add a rate-based rule to it. A rate-based rule limits the number of requests per ﬁve minute time window for each IP address, providing basic protections against web application layer request ﬂoods. You can conﬁgure the rate, starting as low as 10. For more information, see Protecting the application layer with AWS WAF web ACLs and Shield Advanced. You can also use the AWS WAF service to manage the web ACL. Through AWS WAF, you can expand the web ACL conﬁguration to do things such as inspect speciﬁc web request components for string matches or patterns, add custom request and response handling, and match against the geolocation of the request origin. For more information about AWS WAF rules, see AWS WAF rules. Automatic application layer mitigation For enhanced protection, enable Shield Advanced automatic application layer mitigation. With this option, Shield Advanced maintains an AWS WAF rate limiting rule for requests from known DDoS sources and it provides custom mitigations for detected DDoS attacks. When Shield Advanced detects an attack on a protected resource, it attempts to identify an attack signature that isolates the attack traﬃc from the normal traﬃc to your application. Shield Advanced evaluates the identiﬁed attack signature against the historical traﬃc patterns for the resource that's under attack, as well as for any other resource that's associated with the same web ACL. If Shield Advanced determines that the attack signature isolates only the traﬃc that's involved in the DDoS attack, it implements the signature in AWS WAF rules inside the associated web ACL. You can instruct Shield Advanced to place mitigations that only count the traﬃc that they match against, or that block it, and you can change the setting at any time. When Shield Advanced determines that its mitigating rules are no longer needed, it removes them from the web ACL. For How Shield mitigates events 871 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide more information about application layer event mitigation, see Automating application layer DDoS mitigation with Shield Advanced . For more information about Shield Advanced application layer mitigations, see Protecting the application layer (layer 7) with AWS Shield Advanced and AWS WAF. Building basic DDoS resilient architectures with Shield Advanced This page explains Distributed Denial of Service (DDoS) resiliency and introduces two example architectures. DDoS resiliency is the ability of your application architecture to withstand DDoS attacks while continuing to serve legitimate end users. An application that is highly resilient can remain available during an attack with minimal impact on performance metrics such as errors or latency. This section shows some common example architectures and describes how to use the DDoS detection and mitigation capabilities that are provided by AWS and Shield Advanced to increase their DDoS resiliency. The example architectures in this section highlight the AWS services that provide the greatest DDoS resiliency beneﬁts for your deployed applications. The beneﬁts of the highlighted services include the following: • Access to globally distributed network capacity – The services Amazon CloudFront, AWS Global Accelerator, and Amazon Route 53 provide you with access to internet and DDoS mitigation capacity across the AWS global edge network. This is useful in mitigating larger volumetric attacks, which can reach terabits in scale. You can run your application in any AWS Region and use these services to protect availability and optimize performance for your legitimate users. • Protection against web application layer DDoS attack vectors – Web application layer DDoS attacks are best mitigated using a combination of application scale and a web application ﬁrewall (WAF). Shield Advanced uses web request inspection logs from AWS WAF to detect anomalies that can be mitigated either automatically or via engagement with the AWS Shield Response Team (SRT). Automatic mitigation is available through deployed AWS WAF rate-based rules and also through the Shield Advanced automatic application layer DDoS mitigation. In addition to reviewing these examples, review and
waf-dg-312	waf-dg.pdf	312	these services to protect availability and optimize performance for your legitimate users. • Protection against web application layer DDoS attack vectors – Web application layer DDoS attacks are best mitigated using a combination of application scale and a web application ﬁrewall (WAF). Shield Advanced uses web request inspection logs from AWS WAF to detect anomalies that can be mitigated either automatically or via engagement with the AWS Shield Response Team (SRT). Automatic mitigation is available through deployed AWS WAF rate-based rules and also through the Shield Advanced automatic application layer DDoS mitigation. In addition to reviewing these examples, review and follow the applicable best practices at AWS Best Practices for DDoS Resiliency. Building DDoS resilient architectures 872 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Topics • Example Shield Advanced DDoS resiliency architecture for common web applications • Example Shield Advanced DDoS resiliency architecture for TCP and UDP applications Example Shield Advanced DDoS resiliency architecture for common web applications This page provides an example architecture for maximizing resiliency against DDoS attacks with AWS web applications. You can build a web application in any AWS Region and receive automatic DDoS protection from the detection and mitigation capabilities that AWS provides in the Region. This example is for architectures that route users to a web application using resources like Classic Load Balancers, Application Load Balancers, Network Load Balancers, AWS Marketplace solutions, or your own proxy layer. You can improve DDoS resiliency by inserting Amazon Route 53 hosted zones, Amazon CloudFront distributions, and AWS WAF web ACLs between these web application resources and your users. These insertions can obfuscate the application origin, serve requests closer to your end users, and detect and mitigate application layer request ﬂoods. Applications that serve static or dynamic content to your users with CloudFront and Route 53 are protected by an integrated, fully inline DDoS mitigation system that mitigates infrastructure layer attacks in real time. With these architectural improvements in place, you can then protect your Route 53 hosted zones and your CloudFront distributions with Shield Advanced. When you protect CloudFront distributions, Shield Advanced prompts you to associate AWS WAF web ACLs and create rate- based rules for them, and gives you the option of enabling automatic application layer DDoS mitigation or proactive engagement. Proactive engagement and automatic application layer DDoS mitigation use Route 53 health checks that you associate with the resource. To learn more about these options, see Resource protections in AWS Shield Advanced. The following reference diagram depicts this DDoS resilient architecture for a web application. DDoS resiliency architecture for web applications 873 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide The beneﬁts that this approach provides to your web application include the following: • Protection against frequently used infrastructure layer (layer 3 and layer 4) DDoS attacks, without detection delay. In addition, if a resource is frequently targeted, Shield Advanced places mitigations for longer periods of time. Shield Advanced also uses application context inferred from Network ACLs (NACLs) to block unwanted traﬃc further upstream. This isolates failures closer to their source, minimizing the eﬀect on legitimate users. • Protection against TCP SYN ﬂoods. The DDoS mitigation systems that are integrated with CloudFront, Route 53, and AWS Global Accelerator provide a TCP SYN proxy capability that challenges new connection attempts and only serves legitimate users. • Protection against DNS application layer attacks, because Route 53 is responsible for serving authoritative DNS responses. • Protection against web application layer request ﬂoods. The rate-based rule that you conﬁgure in your AWS WAF web ACL blocks source IPs when they are sending more requests than the rule allows. DDoS resiliency architecture for web applications 874 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Automatic application layer DDoS mitigation for your CloudFront distributions, if you choose to enable this option. With automatic DDoS mitigation, Shield Advanced maintains a rate-based rule in the distribution's associated AWS WAF web ACL that limits the volume of requests from known DDoS sources. Additionally, when Shield Advanced detects an event that aﬀects the health of your application, it automatically creates, tests, and manages mitigating rules in web ACL. • Proactive engagement with the Shield Response Team (SRT), if you choose to enable this option. When Shield Advanced detects an event that aﬀects the health of your application, the SRT responds and proactively engages with your security or operations teams using the contact information that you provide. The SRT analyzes patterns in your traﬃc and can update your AWS WAF rules to block the attack. Example Shield Advanced DDoS resiliency architecture for TCP and UDP applications This example shows a DDoS resilient architecture for TCP and UDP applications in an AWS Region that uses Amazon Elastic Compute Cloud (Amazon EC2) instances or Elastic IP (EIP)
waf-dg-313	waf-dg.pdf	313	Response Team (SRT), if you choose to enable this option. When Shield Advanced detects an event that aﬀects the health of your application, the SRT responds and proactively engages with your security or operations teams using the contact information that you provide. The SRT analyzes patterns in your traﬃc and can update your AWS WAF rules to block the attack. Example Shield Advanced DDoS resiliency architecture for TCP and UDP applications This example shows a DDoS resilient architecture for TCP and UDP applications in an AWS Region that uses Amazon Elastic Compute Cloud (Amazon EC2) instances or Elastic IP (EIP) addresses. You can follow this general example to improve DDoS resiliency for the following application types: • TCP or UDP applications. For example, applications used for gaming, IoT, and voice over IP. • Web applications that require static IP addresses or that use protocols that Amazon CloudFront doesn't support. For example, your application might require IP addresses that your users can add to their ﬁrewall allow lists, and that aren't used by any other AWS customers. You can improve DDoS resiliency for these application types by introducing Amazon Route 53 and AWS Global Accelerator. These services can route users to your application and they can provide your application with static IP addresses that are anycast routed across the AWS global edge network. Global Accelerator standard accelerators can improve user latency by up to 60%. If you have a web application, you can detect and mitigate web application layer request ﬂoods by running the application on an Application Load Balancer, and then protecting the Application Load Balancer with an AWS WAF web ACL. After you've built your application, protect your Route 53 hosted zones, Global Accelerator standard accelerators, and any Application Load Balancers with Shield Advanced. When you protect your Application Load Balancers, you can associate AWS WAF web ACLs and create rate-based rules DDoS resiliency architecture for TCP and UDP applications 875 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide for them. You can conﬁgure proactive engagement with the SRT for both your Global Accelerator standard accelerators and your Application Load Balancers by associating new or existing Route 53 health checks. To learn more about the options, see Resource protections in AWS Shield Advanced. The following reference diagram depicts an example DDoS resilient architecture for TCP and UDP applications. The beneﬁts that this approach provides to your application include the following: • Protection against the largest known infrastructure layer (layer 3 and layer 4) DDoS attacks. If the volume of an attack causes congestion upstream from AWS, the failure will be isolated closer to its source and will have a minimized eﬀect on your legitimate users. • Protection against DNS application layer attacks, because Route 53 is responsible for serving authoritative DNS responses. • If you have a web application, this approach provides protection against web application layer request ﬂoods. The rate-based rule that you conﬁgure in your AWS WAF web ACL blocks source IPs while they are sending more requests than the rule allows. DDoS resiliency architecture for TCP and UDP applications 876 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Proactive engagement with the Shield Response Team (SRT), if you choose to enable this option for eligible resources. When Shield Advanced detects an event that aﬀects the health of your application, the SRT responds and proactively engages with your security or operations teams using the contact information that you provide. Combining Shield Advanced with other AWS services You can use Shield Advanced to protect your resources in many types of scenarios. However, in some cases you should use other services or combine other services with Shield Advanced to oﬀer the best protection. Following are examples of how to use Shield Advanced or other AWS services to help protect your resources. Goal Suggested services Related service documenta tion Protect a web application and RESTful APIs against a DDoS Shield Advanced protectin g an Amazon CloudFront Elastic Load Balancing documentation, Amazon attack distribution and an Applicati CloudFront Documentation on Load Balancer Protect a TCP-based applicati on against a DDoS attack Shield Advanced protectin g an AWS Global Accelerat AWS Global Accelerator Documentation, Elastic Load or standard accelerator; Balancing documentation Protect a UDP-based game server against a DDoS attack attached to an Elastic IP address Shield Advanced protectin g an Amazon EC2 instance attached to an Elastic IP address Amazon Elastic Compute Cloud Documentation For example, if you use Shield Advanced to protect an Elastic IP address, Shield Advanced protects whatever resource is associated with it. During an attack, Shield Advanced automatically deploys your network ACLs to the border of the AWS network. When your network ACLs are at the border of the network, Shield Advanced can provide protection against larger DDoS events. Typically,
waf-dg-314	waf-dg.pdf	314	Load or standard accelerator; Balancing documentation Protect a UDP-based game server against a DDoS attack attached to an Elastic IP address Shield Advanced protectin g an Amazon EC2 instance attached to an Elastic IP address Amazon Elastic Compute Cloud Documentation For example, if you use Shield Advanced to protect an Elastic IP address, Shield Advanced protects whatever resource is associated with it. During an attack, Shield Advanced automatically deploys your network ACLs to the border of the AWS network. When your network ACLs are at the border of the network, Shield Advanced can provide protection against larger DDoS events. Typically, network ACLs are applied near your Amazon EC2 instances within your Amazon VPC. The network Combining Shield Advanced with other AWS services 877 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide ACL can mitigate attacks only as large as your Amazon VPC and instance can handle. If the network interface attached to your Amazon EC2 instance can process up to 10 Gbps, volumes over 10 Gbps slow down and possibly block traﬃc to that instance. During an attack, Shield Advanced promotes your network ACL to the AWS border, which can process multiple terabytes of traﬃc. Your network ACL is able to provide protection for your resource well beyond your network's typical capacity. For more information about network ACLs, see Network ACLs. Setting up AWS Shield Advanced This tutorial walks you through getting started with AWS Shield Advanced using the Shield Advanced console. Note Shield Advanced requires a subscription, while AWS Shield Standard does not. The protections provided by Shield Standard are available free of charge to all AWS customers. Shield Advanced provides advanced DDoS detection and mitigation protection for network layer (layer 3), transport layer (layer 4), and application layer (layer 7) attacks. For more information about Shield Advanced, see AWS Shield Advanced overview. The AWS technical community has published an example of an automated process for conﬁguring Shield Advanced using the infrastructure as code (IaC) tools, AWS CloudFormation and Terraform. You can use AWS Firewall Manager with this solution if your accounts are part of an organization in AWS Organizations and if you're protecting any resource types except for Amazon Route 53 or AWS Global Accelerator. To explore this option, see the code repository at aws-samples / aws-shield- advanced-one-click-deployment and the tutorial at One-click deployment of Shield Advanced. Note It's important that you fully conﬁgure Shield Advanced prior to a Distributed Denial of Service (DDoS) event. Complete the conﬁguration to help ensure that your application is protected and that you are ready to respond if your application is aﬀected by a DDoS attack. Perform the following steps in sequence to get started using Shield Advanced. Setting up AWS Shield Advanced 878 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Contents • Subscribing to AWS Shield Advanced • Adding and conﬁguring resource protections with Shield Advanced • Conﬁguring application layer (layer 7) DDoS protections with AWS WAF • Conﬁguring health-based detection for your protections with Shield Advanced and Route 53 • Conﬁguring alarms and notiﬁcations with Shield Advanced and Amazon SNS • Reviewing and ﬁnishing your protection conﬁguration in Shield Advanced • Setting up AWS Shield Response Team (SRT) support for DDoS event response • Creating a DDoS dashboard in CloudWatch and setting CloudWatch alarms Subscribing to AWS Shield Advanced This page explains how to subscribe your accounts to Shield Advanced, to start using the service. You must subscribe to Shield Advanced for each AWS account that you want to protect. You do not need to subscribe to Shield Standard. Shield Advanced subscription billing If you’re an AWS Channel Reseller, talk to your account team for information and guidance. This billing information is for customers that are not AWS Channel Resellers. For all others, the following subscription and billing guidelines apply: • For accounts that are members of an AWS Organizations organization, AWS bills the Shield Advanced subscriptions against the payer account for the organization, regardless of whether the payer account itself is subscribed. • When you subscribe multiple accounts that are in the same AWS Organizations consolidated billing account family, one subscription price covers all subscribed accounts in the family. The organization must own all of the AWS accounts and all of their resources. • When you subscribe multiple accounts for multiple organizations, you can still pay one subscription fee across all of the organizations, accounts, and resources providing you own all of them. Contact your account manager or AWS support and request a fee waiver on the AWS Shield Advanced subscription charges for all but one of the organizations. For detailed pricing information and examples, see AWS Shield Pricing. Subscribing to Shield Advanced 879 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Consider simplifying subscriptions with AWS Firewall Manager
waf-dg-315	waf-dg.pdf	315	own all of the AWS accounts and all of their resources. • When you subscribe multiple accounts for multiple organizations, you can still pay one subscription fee across all of the organizations, accounts, and resources providing you own all of them. Contact your account manager or AWS support and request a fee waiver on the AWS Shield Advanced subscription charges for all but one of the organizations. For detailed pricing information and examples, see AWS Shield Pricing. Subscribing to Shield Advanced 879 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Consider simplifying subscriptions with AWS Firewall Manager If your accounts are part of an organization, we recommend that you use AWS Firewall Manager if you can, to automate your subscriptions and protections for the organization. Firewall Manager supports all protected resource types except for Amazon Route 53 and AWS Global Accelerator. To use Firewall Manager, see AWS Firewall Manager and Setting up AWS Firewall Manager AWS Shield Advanced policies. If you don't use Firewall Manager, for each account with resources to protect, subscribe and add protections using the following procedures. To subscribe an account to AWS Shield Advanced 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. 2. 3. In the AWS Shield navigation bar, choose Getting started. Choose Subscribe to Shield Advanced. In the Subscribe to Shield Advanced page, read each term of the agreement, and then select all of the check boxes to indicate that you accept the terms. For accounts in a consolidated billing family, you must agree to the terms for each account. Important When you are subscribed, to unsubscribe you must contact AWS Support. To disable autorenewal for your subscription, you must use the Shield API operation UpdateSubscription or the CLI command update-subscription. Choose Subscribe to Shield Advanced. This subscribes your account to Shield Advanced and activates the service. Your account is subscribed. Continue through the following steps to protect your account's resources with Shield Advanced. Subscribing to Shield Advanced 880 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note Shield Advanced doesn't automatically protect your resources after you subscribe. You must specify the resources you want Shield Advanced to protect. Adding and conﬁguring resource protections with Shield Advanced This page provides instructions for adding and conﬁguring protections for your resources. Shield Advanced only protects the resources that you specify, either through Shield Advanced or in a Firewall Manager Shield Advanced policy. It doesn't automatically protect the resources of a subscribed account. Note If you use an AWS Firewall Manager Shield Advanced policy for your protections, you don't need to do this step. You conﬁgure the policy with the types of resource to protect, and Firewall Manager automatically adds protections to resources that are within scope of the policy. If you don't use Firewall Manager, go through the following procedures for each account that has resources to protect. To choose the resources to protect using Shield Advanced 1. Choose Add resources to protect from the subscription conﬁrmation page of the prior procedure, or from the Protected resources or Overview page. 2. In the Choose resources to protect with Shield Advanced page, in Specify the Region and resource types, provide the Region and resource type speciﬁcations for the resources that you want to protect. You can protect resources in multiple Regions by selecting All Regions and you can narrow the selection to global resources by selecting Global. You can deselect any resource types that you do not want to protect. For information about protections for your resource types, see List of resources that AWS Shield Advanced protects. 3. Choose Load resources. Shield Advanced populates the Select Resources section with the AWS resources that match your criteria. Adding and conﬁguring resource protections 881 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 4. In the Select Resources section, you can ﬁlter the list of resources by entering a string to search for in the resource listings. Select the resources that you want to protect. 5. In the Tags section, if you want to add tags to the Shield Advanced protections that you are creating, specify those. For information about tagging AWS resources, see Working with Tag Editor. 6. Choose Protect with Shield Advanced. This adds Shield Advanced protections to the resources. Continue through the console wizard screens to complete the conﬁguration of your resource protections. Topics • Conﬁguring application layer (layer 7) DDoS protections with AWS WAF • Conﬁguring health-based detection for your protections with Shield Advanced and Route 53 • Conﬁguring alarms and notiﬁcations with Shield Advanced and Amazon SNS • Reviewing and ﬁnishing your protection conﬁguration in Shield Advanced Conﬁguring application layer (layer 7) DDoS protections with AWS WAF This page provides instructions for conﬁguring application layer
waf-dg-316	waf-dg.pdf	316	tagging AWS resources, see Working with Tag Editor. 6. Choose Protect with Shield Advanced. This adds Shield Advanced protections to the resources. Continue through the console wizard screens to complete the conﬁguration of your resource protections. Topics • Conﬁguring application layer (layer 7) DDoS protections with AWS WAF • Conﬁguring health-based detection for your protections with Shield Advanced and Route 53 • Conﬁguring alarms and notiﬁcations with Shield Advanced and Amazon SNS • Reviewing and ﬁnishing your protection conﬁguration in Shield Advanced Conﬁguring application layer (layer 7) DDoS protections with AWS WAF This page provides instructions for conﬁguring application layer protections with AWS WAF web ACLs. To protect an application layer resource, Shield Advanced uses an AWS WAF web ACL with a rate- based rule as a starting point. AWS WAF is a web application ﬁrewall that lets you monitor the HTTP and HTTPS requests that are forwarded to your application layer resources, and lets you control access to your content based on the characteristics of the requests. A rate-based rule limits the volume of traﬃc based on your request aggregation criteria, providing basic DDoS protection to your application. For more information, see How AWS WAF works and Using rate-based rule statements in AWS WAF. You can also optionally enable Shield Advanced automatic application layer DDoS mitigation, to have Shield Advanced rate limit requests from known DDoS sources and automatically provide incident-speciﬁc protections for you. Adding and conﬁguring resource protections 882 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Important If you manage your Shield Advanced protections through AWS Firewall Manager using a Shield Advanced policy, you can't manage application layer protections here. You must manage them in your Firewall Manager Shield Advanced policy. Shield Advanced subscriptions and AWS WAF costs Your Shield Advanced subscription covers the costs of using standard AWS WAF capabilities for resources that you protect with Shield Advanced. The standard AWS WAF fees that are covered by your Shield Advanced protections are the cost per web ACL, the cost per rule, and the base price per million requests for web request inspection, up to 1,500 WCUs and up to the default body size. Enabling Shield Advanced automatic application layer DDoS mitigation adds a rule group to your web ACL that uses 150 web ACL capacity units (WCUs). These WCUs count against the WCU usage in your web ACL. For more information, see Automating application layer DDoS mitigation with Shield Advanced , Protecting the application layer with the Shield Advanced rule group, and Web ACL capacity units (WCUs) in AWS WAF. Your subscription to Shield Advanced does not cover the use of AWS WAF for resources that you do not protect using Shield Advanced. It also does not cover any additional non-standard AWS WAF costs for protected resources. Examples of non-standard AWS WAF costs are those for Bot Control, for the CAPTCHA rule action, for web ACLs that use more than 1,500 WCUs, and for inspecting the request body beyond the default body size. The full list is provided on the AWS WAF pricing page. For full information and pricing examples, see Shield Pricing and AWS WAF Pricing. To conﬁgure layer 7 DDoS protections for a Region Shield Advanced gives you the option to conﬁgure layer 7 DDoS mitigation for each Region where your chosen resources are located. If you're adding protections in multiple regions, the wizard walks you through the following procedure for each Region. 1. The Conﬁgure layer 7 DDoS protections page lists each resource that isn't yet associated with a web ACL. For each of these, either choose an existing web ACL or create a new web ACL. For any resource that already has an associated web ACL, you can change web ACLs by ﬁrst disassociating the current one through AWS WAF. For more information, see Associating or disassociating a web ACL with an AWS resource. Adding and conﬁguring resource protections 883 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide For web ACLs that don't already have a rate-based rule, the conﬁguration wizard prompts you to add one. A rate-based rule limits traﬃc from IP addresses when they are sending a high volume of requests. Rate-based rules help protect your application against web request ﬂoods and can provide alerts about sudden spikes in traﬃc that might indicate a potential DDoS attack. Add a rate-based rule to a web ACL by choosing Add rate limit rule and then providing a rate limit and rule action. You can conﬁgure additional protections in the web ACL through AWS WAF. For information about using web ACLs and rate-based rules in your Shield Advanced protections, including additional conﬁguration options for rate-based rules, see Protecting the application layer with AWS WAF web ACLs and Shield Advanced. 2. For Automatic application layer DDoS mitigation, if
waf-dg-317	waf-dg.pdf	317	protect your application against web request ﬂoods and can provide alerts about sudden spikes in traﬃc that might indicate a potential DDoS attack. Add a rate-based rule to a web ACL by choosing Add rate limit rule and then providing a rate limit and rule action. You can conﬁgure additional protections in the web ACL through AWS WAF. For information about using web ACLs and rate-based rules in your Shield Advanced protections, including additional conﬁguration options for rate-based rules, see Protecting the application layer with AWS WAF web ACLs and Shield Advanced. 2. For Automatic application layer DDoS mitigation, if you want to have Shield Advanced automatically mitigate DDoS attacks against your application layer resources, choose Enable and then select the AWS WAF rule action that you want Shield Advanced to use in its custom rules. This setting applies to all of the web ACLs for the resources that you are managing in this wizard session. With automatic application layer DDoS mitigation, Shield Advanced maintains a rate-based rule in the resource's AWS WAF web ACL that limits the volume of requests from known DDoS sources. Additionally, Shield Advanced compares current traﬃc patterns against historic traﬃc baselines to detect deviations that might indicate a DDoS attack. When Shield Advanced detects a DDoS attack, it responds by creating, evaluating, and deploying custom AWS WAF rules to respond. You specify whether the custom rules count or block attacks on your behalf. Note Automatic application layer DDoS mitigation works only with web ACLs that were created using the latest version of AWS WAF (v2). For more information about Shield Advanced automatic application layer DDoS mitigation, including caveats and best practices for using this feature, see Automating application layer DDoS mitigation with Shield Advanced . 3. Choose Next. The console wizard advances to the health-based detection page. Adding and conﬁguring resource protections 884 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Conﬁguring health-based detection for your protections with Shield Advanced and Route 53 This page provides instructions for conﬁguring Shield Advanced to use health-based detection. This can help improve responsiveness and accuracy in attack detection and mitigation. Well-conﬁgured health checks are essential for accurate detection of events. You can conﬁgure health-based detection for any resource type except for Route 53 hosted zones. To use health-based detection, deﬁne a health check for your resource in Route 53, and then associate the health check with your Shield Advanced protection. It's important that the health check that you conﬁgure accurately reﬂect the health of the resource. For information and examples for conﬁguring health checks to use with Shield Advanced, see Health-based detection using health checks with Shield Advanced and Route 53. Health checks are required for Shield Response Team (SRT) proactive engagement support. For information about proactive engagement, see Setting up proactive engagement for the SRT to contact you directly. Note Health checks must be reporting healthy when you associate them with your Shield Advanced protections. To conﬁgure health-based detection 1. Under Associated Health Check, choose the ID of the health check that you want to associate with the protection. Note If you do not see the health check you need, go to the Route 53 console and verify the health check and its ID. For information, see Creating and Updating Health Checks. 2. Choose Next. The console wizard advances to the alarms and notiﬁcations page. Adding and conﬁguring resource protections 885 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Conﬁguring alarms and notiﬁcations with Shield Advanced and Amazon SNS This page provides instructions to optionally conﬁgure Amazon Simple Notiﬁcation Service notiﬁcations for detected Amazon CloudWatch alarms and rate-based rule activity. You can use these to receive notiﬁcation when Shield detects an event on a protected resource or when a rate- limit conﬁgured in a rate-based rule is exceeded. For information about Shield Advanced CloudWatch metrics, see AWS Shield Advanced metrics. For information about Amazon SNS, see the Amazon Simple Notiﬁcation Service Developer Guide. To conﬁgure alarms and notiﬁcations 1. Select the Amazon SNS topics that you want notiﬁcation for. You can use a single Amazon SNS topic for all protected resources and rate-based rules, or you can choose diﬀerent topics, customized to your organization. For example, you can create an SNS topic for each team that's responsible for incident response for a speciﬁc set of resources. 2. Choose Next. The console wizard advances to the resource protection review page. Reviewing and ﬁnishing your protection conﬁguration in Shield Advanced To review and ﬁnish your settings 1. In the Review and conﬁgure DDoS mitigation and visibility page, review your settings. To make modiﬁcations, choose Edit in the area that you want to modify. This takes you back to the associated page in the console wizard. Make your changes, then choose Next in the
waf-dg-318	waf-dg.pdf	318	to your organization. For example, you can create an SNS topic for each team that's responsible for incident response for a speciﬁc set of resources. 2. Choose Next. The console wizard advances to the resource protection review page. Reviewing and ﬁnishing your protection conﬁguration in Shield Advanced To review and ﬁnish your settings 1. In the Review and conﬁgure DDoS mitigation and visibility page, review your settings. To make modiﬁcations, choose Edit in the area that you want to modify. This takes you back to the associated page in the console wizard. Make your changes, then choose Next in the subsequent pages until you return to the Review and conﬁgure DDoS mitigation and visibility page. 2. Choose Finish conﬁguration. The Protected resources page lists your newly protected resources. Setting up AWS Shield Response Team (SRT) support for DDoS event response This page provides instructions for setting up Shield Response Team (SRT) support. The SRT includes security engineers who specialize in DDoS event response. You can optionally add permissions that allow the SRT to manage resources on your behalf during a DDoS event. In addition, you can conﬁgure the SRT to proactively engage with you if the Route 53 health checks Setting up SRT support 886 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide associated with your protected resources are unhealthy during a detected event. Both of these additions to your protections enable quicker responses to DDoS events. Note To use the services of the Shield Response Team (SRT), you must be subscribed to the Business Support plan or the Enterprise Support plan. The SRT can monitor AWS WAF request data and logs during application layer events to identify anomalous traﬃc. They can help craft custom AWS WAF rules to mitigate oﬀending traﬃc sources. As needed, the SRT might make architectural recommendations to help you better align your resources with AWS recommendations. For more information about the SRT, see Managed DDoS event response with Shield Response Team (SRT) support. To grant permissions to the SRT 1. In the AWS Shield console Overview page, under Conﬁgure AWS SRT support, choose Edit SRT access. The Edit AWS Shield Response Team (SRT) access page opens. 2. For SRT access setting select one of the options: • Do not grant the SRT access to my account – Shield removes any permissions you previously gave to the SRT to access your account and resources. • Create a new role for the SRT to access my account – Shield creates a role that trusts the service principal drt.shield.amazonaws.com, which represents the SRT, and attaches the managed policy AWSShieldDRTAccessPolicy to it. The managed policy allows the SRT to make AWS Shield Advanced and AWS WAF API calls on your behalf and to access your AWS WAF logs. For more information about the managed policy, see AWS managed policy: AWSShieldDRTAccessPolicy. • Choose an existing role for the SRT to access my accounts – For this option, you must modify the conﬁguration of the role in AWS Identity and Access Management (IAM) as follows: • Attach the managed policy AWSShieldDRTAccessPolicy to the role. This managed policy allows the SRT to make AWS Shield Advanced and AWS WAF API calls on your behalf and to access your AWS WAF logs. For more information about the managed policy, Setting up SRT support 887 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide see AWS managed policy: AWSShieldDRTAccessPolicy. For information about attaching the managed policy to your role, see Attaching and Detaching IAM Policies. • Modify the role to trust the service principal drt.shield.amazonaws.com. This is the service principal that represents the SRT. For more information, see IAM JSON Policy Elements: Principal. 3. Choose Save to save your changes. For more information about giving the SRT access to your protections and data, see Granting access for the SRT. To enable SRT proactive engagement 1. In the AWS Shield console Overview page, under Proactive engagement and contacts, in the contacts area, choose Edit. In the Edit contacts page, provide the contact information for the people that you want the SRT to contact for proactive engagement. If you provide more than one contact, in the Notes, indicate the circumstances under which each contact should be used. Include primary and secondary contact designations, and provide the hours of availability and time zones for each contact. Example contact notes: • This is a hotline that's staﬀed 24x7x365. Please work with the responding analyst and they will get the appropriate person on the call. • Please contact me if the hotline doesn't respond within 5 minutes. 2. Choose Save. The Overview page reﬂects the updated contact information. 3. Choose Edit proactive engagement feature, choose Enable, and then choose Save to enable proactive engagement. For more information about proactive engagement, see Setting up proactive
waf-dg-319	waf-dg.pdf	319	which each contact should be used. Include primary and secondary contact designations, and provide the hours of availability and time zones for each contact. Example contact notes: • This is a hotline that's staﬀed 24x7x365. Please work with the responding analyst and they will get the appropriate person on the call. • Please contact me if the hotline doesn't respond within 5 minutes. 2. Choose Save. The Overview page reﬂects the updated contact information. 3. Choose Edit proactive engagement feature, choose Enable, and then choose Save to enable proactive engagement. For more information about proactive engagement, see Setting up proactive engagement for the SRT to contact you directly. Setting up SRT support 888 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Creating a DDoS dashboard in CloudWatch and setting CloudWatch alarms This page provides instructions for creating a DDoS dashboard in CloudWatch and setting CloudWatch alarms. You can monitor potential DDoS activity using Amazon CloudWatch, which collects raw data from Shield Advanced and processes it into readable, near real-time metrics. You can use statistics in CloudWatch to gain a perspective on how your web application or service is performing. For more information about using CloudWatch, see What is CloudWatch in the Amazon CloudWatch User Guide. • For instructions for creating a CloudWatch dashboard, see Monitoring with Amazon CloudWatch. • For descriptions of the Shield Advanced metrics that you can add to your dashboard, see AWS Shield Advanced metrics. Shield Advanced reports resource metrics to CloudWatch more frequently during DDoS events than while no events are underway. Shield Advanced reports metrics once a minute during an event, and then once right after the event ends. While no events are underway, Shield Advanced reports metrics once a day, at a time assigned to the resource. This periodic report keeps the metrics active and available for use in your custom CloudWatch alarms. This completes the tutorial for getting started with Shield Advanced. To take full advantage of the protections you've chosen, continue exploring the features and options of Shield Advanced. To start, familiarize yourself with your options for viewing and responding to events at Visibility into DDoS events with Shield Advanced and Responding to DDoS events in AWS. Managed DDoS event response with Shield Response Team (SRT) support This page describes the function of the Shield Response Team (SRT). The SRT provides added support for Shield Advanced customers. The SRT are security engineers who specialize in DDoS event response. As an additional layer of support to your AWS Support plan, you can work directly with the SRT, leveraging their expertise as part of your event response workﬂow. For information about the options and for conﬁguration guidance, see the topics that follow. Creating a DDoS dashboard 889 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note To use the services of the Shield Response Team (SRT), you must be subscribed to the Business Support plan or the Enterprise Support plan. SRT support activities The primary goal in an engagement with the SRT is to protect the availability and performance of your application. Depending on the type of DDoS event and the architecture of your application, the SRT may take one or more of the following actions: • AWS WAF log analysis and rules – For resources that use an AWS WAF web ACL, the SRT can analyze your AWS WAF logs to identify attack characteristics in your application web requests. With your approval during engagement, the SRT can apply changes to your web ACL to block the attacks that they've identiﬁed. • Build custom network mitigations – The SRT can write custom mitigations for you for infrastructure layer attacks. The SRT can work with you to understand traﬃc that's expected for your application, to block unexpected traﬃc, and to optimize packet per second rate limits. For more information, see Setting up custom mitigations against DDoS attacks with the SRT. • Network traﬃc engineering – The SRT works closely with AWS networking teams to protect Shield Advanced customers. When required, AWS can change how internet traﬃc arrives on the AWS network in order to allocate more mitigation capacity to your application. • Architectural recommendations – The SRT may determine that the best mitigation for an attack requires architectural changes to better align with the AWS best practices, and they will help support your implementation of these practices. For information, see AWS Best Practices for DDoS Resiliency. The following sections provide instructions for engaging with the SRT Topics • Granting access for the SRT • Setting up proactive engagement for the SRT to contact you directly • Contacting the SRT for help with a suspected DDoS event • Setting up custom mitigations against DDoS attacks with the SRT SRT support 890 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced
waf-dg-320	waf-dg.pdf	320	that the best mitigation for an attack requires architectural changes to better align with the AWS best practices, and they will help support your implementation of these practices. For information, see AWS Best Practices for DDoS Resiliency. The following sections provide instructions for engaging with the SRT Topics • Granting access for the SRT • Setting up proactive engagement for the SRT to contact you directly • Contacting the SRT for help with a suspected DDoS event • Setting up custom mitigations against DDoS attacks with the SRT SRT support 890 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Granting access for the SRT This page provides instructions for granting permission to the SRT to act on your behalf, so that they can access your AWS WAF logs and make calls to the AWS Shield Advanced and AWS WAF APIs to manage protections. During application layer DDoS events, the SRT can monitor AWS WAF requests to identify anomalous traﬃc and help craft custom AWS WAF rules to mitigate oﬀending traﬃc sources. Additionally, you can grant the SRT access to other data that you have stored in Amazon S3 buckets, such as packet captures or logs from an Application Load Balancer, Amazon CloudFront, or from third party sources. Note To use the services of the Shield Response Team (SRT), you must be subscribed to the Business Support plan or the Enterprise Support plan. To manage permissions for the SRT 1. In the AWS Shield console Overview page, under Conﬁgure AWS SRT support, choose Edit SRT access. The Edit AWS Shield Response Team (SRT) access page opens. 2. For SRT access setting select one of the options: • Do not grant the SRT access to my account – Shield removes any permissions you previously gave to the SRT to access your account and resources. • Create a new role for the SRT to access my account – Shield creates a role that trusts the service principal drt.shield.amazonaws.com, which represents the SRT, and attaches the managed policy AWSShieldDRTAccessPolicy to it. The managed policy allows the SRT to make AWS Shield Advanced and AWS WAF API calls on your behalf and to access your AWS WAF logs. For more information about the managed policy, see AWS managed policy: AWSShieldDRTAccessPolicy. • Choose an existing role for the SRT to access my accounts – For this option, you must modify the conﬁguration of the role in AWS Identity and Access Management (IAM) as follows: • Attach the managed policy AWSShieldDRTAccessPolicy to the role. This managed policy allows the SRT to make AWS Shield Advanced and AWS WAF API calls on your Granting access for the SRT 891 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide behalf and to access your AWS WAF logs. For more information about the managed policy, see AWS managed policy: AWSShieldDRTAccessPolicy. For information about attaching the managed policy to your role, see Attaching and Detaching IAM Policies. • Modify the role to trust the service principal drt.shield.amazonaws.com. This is the service principal that represents the SRT. For more information, see IAM JSON Policy Elements: Principal. 3. For (Optional): Grant SRT access to an Amazon S3 bucket, if you need to share data that isn't in your AWS WAF web ACL logs, conﬁgure this. For example, Application Load Balancer access logs, Amazon CloudFront logs, or logs from third party sources. Note You don't need to do this for your AWS WAF web ACL logs. The SRT gains access to those when you grant access to your account. a. Conﬁgure the Amazon S3 buckets according to the following guidelines: • The bucket locations must be in the same AWS account as the one you gave the SRT general access to, in the prior step AWS Shield Response Team (SRT) access. • The buckets can be either plaintext or SSE-S3 encrypted. For more information about Amazon S3 SSE-S3 encryption, see Protecting Data Using Server-Side Encryption with Amazon S3-Managed Encryption Keys (SSE-S3) in the Amazon S3 User Guide. The SRT cannot view or process logs that are stored in buckets that are encrypted with keys stored in AWS Key Management Service (AWS KMS). b. In the Shield Advanced (Optional): Grant SRT access to an Amazon S3 bucket section, for each Amazon S3 bucket where your data or logs are stored, enter the name of the bucket and choose Add Bucket. You can add up to 10 buckets. This grants the SRT the following permissions on each bucket: s3:GetBucketLocation, s3:GetObject, and s3:ListBucket. If you want to give the SRT permission to access more than 10 buckets, you can do this by editing the additional bucket policies and manually granting the permissions listed here for the SRT. The following shows an example policy listing. Granting access for the SRT 892 AWS WAF,
waf-dg-321	waf-dg.pdf	321	SRT access to an Amazon S3 bucket section, for each Amazon S3 bucket where your data or logs are stored, enter the name of the bucket and choose Add Bucket. You can add up to 10 buckets. This grants the SRT the following permissions on each bucket: s3:GetBucketLocation, s3:GetObject, and s3:ListBucket. If you want to give the SRT permission to access more than 10 buckets, you can do this by editing the additional bucket policies and manually granting the permissions listed here for the SRT. The following shows an example policy listing. Granting access for the SRT 892 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide { "Sid": "AWSDDoSResponseTeamAccessS3Bucket", "Effect": "Allow", "Principal": { "Service": "drt.shield.amazonaws.com" }, "Action": [ "s3:GetBucketLocation", "s3:GetObject", "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::bucket-name", "arn:aws:s3:::bucket-name/*" ] } 4. Choose Save to save your changes. You can also authorize the SRT through the API by creating an IAM role, attaching the policy AWSShieldDRTAccessPolicy to it, and then passing the role to the operation AssociateDRTRole. Setting up proactive engagement for the SRT to contact you directly This page provides instructions for setting up proactive engagement with the SRT. With proactive engagement, the SRT contacts you directly when the availability or performance of your application is aﬀected because of a possible attack. We recommend this engagement model because it provides the quickest SRT response and it allows the SRT to begin troubleshooting even before they've established contact with you. Proactive engagement is available for network-layer and transport-layer events on Elastic IP addresses and AWS Global Accelerator standard accelerators, and for web request ﬂoods on Amazon CloudFront distributions and Application Load Balancers. Proactive engagement is available only for Shield Advanced resource protections that have an associated Amazon Route 53 health check. For information about managing and using health checks, see Health-based detection using health checks with Shield Advanced and Route 53. Setting up proactive engagement 893 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide During an event that's detected by Shield Advanced, the SRT uses the state of your health checks to determine whether the event qualiﬁes for proactive engagement. If so, the SRT will contact you according to the contact guidance that you provide in your proactive engagement conﬁguration. You can conﬁgure up to ten contacts for proactive engagement, and you can provide notes to guide the SRT in reaching out to you. Your proactive engagement contacts should be available to engage with the SRT during events. If you don't have a 24/7 operations center, you can provide a pager contact and indicate this contact preference in your contact notes. Proactive engagement requires you to do the following: • You must be subscribed to the Business Support plan or the Enterprise Support plan. • You must associate an Amazon Route 53 health check with any resource that you want to protect with proactive engagement. The SRT uses the status of your health checks to help determine whether an event requires proactive engagement, so it's important that your health checks accurately reﬂect the state of your protected resources. For more information and guidance, see Health-based detection using health checks with Shield Advanced and Route 53. • For a resource that has an AWS WAF web ACL associated, you must create the web ACL using AWS WAF (v2), which is the latest version of AWS WAF. • You must provide at least one contact for the SRT to use for proactive engagement during an event. Keep your contact information complete and up to date. To enable SRT proactive engagement 1. In the AWS Shield console Overview page, under Proactive engagement and contacts, in the contacts area, choose Edit. In the Edit contacts page, provide the contact information for the people that you want the SRT to contact for proactive engagement. If you provide more than one contact, in the Notes, indicate the circumstances under which each contact should be used. Include primary and secondary contact designations, and provide the hours of availability and time zones for each contact. Example contact notes: • This is a hotline that's staﬀed 24x7x365. Please work with the responding analyst and they will get the appropriate person on the call. Setting up proactive engagement 894 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Please contact me if the hotline doesn't respond within 5 minutes. 2. Choose Save. The Overview page reﬂects the updated contact information. 3. Choose Edit proactive engagement feature, choose Enable, and then choose Save to enable proactive engagement. Contacting the SRT for help with a suspected DDoS event You can contact the SRT in one of the following ways: Support case You can open a case under AWS Shield in the AWS Support Center console. For guidance on creating a support case, see AWS Support Center.
waf-dg-322	waf-dg.pdf	322	engagement 894 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Please contact me if the hotline doesn't respond within 5 minutes. 2. Choose Save. The Overview page reﬂects the updated contact information. 3. Choose Edit proactive engagement feature, choose Enable, and then choose Save to enable proactive engagement. Contacting the SRT for help with a suspected DDoS event You can contact the SRT in one of the following ways: Support case You can open a case under AWS Shield in the AWS Support Center console. For guidance on creating a support case, see AWS Support Center. Select the severity appropriate to your situation and provide your contact details. In the description, provide as much detail as possible. Provide information about any protected resources that you think might be aﬀected, and the current state of your end-user experience. For example, if your user experience is degraded or parts of your application are currently unavailable, provide that information. • For suspected DDoS attacks – If the availability or performance of your application is currently aﬀected by a possible DDoS attack, choose the following severity and contact options: • For severity, choose the highest severity available for your support plan: • For Business support this is Production system down: < 1 hour. • For Enterprise support this is Business-critical system down: < 15 minutes. • For contact option, select either Phone or Chat and provide your details. Using a live contact method provides the fastest response. Proactive engagement With AWS Shield Advanced proactive engagement, the SRT contacts you directly if the Amazon Route 53 health check associated with your protected resource becomes unhealthy during a detected event. For more information about this option, see Setting up proactive engagement for the SRT to contact you directly. Contacting the SRT 895 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Setting up custom mitigations against DDoS attacks with the SRT This page provides instructions for working with the SRT to build custom mitigations against DDoS attacks. For your Elastic IPs (EIPs) and your AWS Global Accelerator standard accelerators, you can work with the SRT to conﬁgure custom mitigations. This is useful in case you know of speciﬁc logic that should be enforced when a mitigation is placed. For example, you may wish to only allow traﬃc from certain countries, enforce speciﬁc rate limits, conﬁgure optional validations, disallow fragments, or only allow traﬃc that matches a speciﬁc pattern in the packet payload. Examples of common custom mitigations include the following: • Pattern matching – If you operate a service that interacts with client-side applications, you can choose to match on known patterns that are unique to those applications. For example, you may operate a gaming or communications service that requires the end-user to install speciﬁc software that you distribute. You can include a magic number in every packet sent by the application to your service. You can match on up to 128 bytes (separate or contiguous) of a non-fragmented TCP or UDP packet payload and headers. The match can be expressed in hexadecimal notation as a speciﬁc oﬀset from the beginning of the packet payload or a dynamic oﬀset following a known value. For example, the mitigation can look for the byte 0x01 and then expect 0x12345678 as the next four bytes. • DNS speciﬁc – If you operate your own authoritative DNS service using services like Global Accelerator or Amazon Elastic Compute Cloud (Amazon EC2), you can request a custom mitigation that validates packets to ensure that they are valid DNS queries and apply suspicion scoring that evaluates attributes that are speciﬁc to DNS traﬃc. To inquire about working with SRT to build custom mitigations, create a support case under AWS Shield. To learn more about creating AWS Support cases, see Getting started with AWS Support. Resource protections in AWS Shield Advanced You can add and conﬁgure AWS Shield Advanced protections for your resources. You can manage protections for a single resource and you can group your protected resources into logical collections for better event management. You can also track changes to your Shield Advanced protections using AWS Conﬁg. Setting up custom mitigations with the SRT 896 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note Shield Advanced protects only resources that you have speciﬁed either in Shield Advanced or through an AWS Firewall Manager Shield Advanced policy. It doesn't automatically protect your resources. If you're using an AWS Firewall Manager Shield Advanced policy, you don't need to manage protections for resources that are in scope of the policy. Firewall Manager automatically manages protections for accounts and resources that are in scope of a policy, according to the policy conﬁguration. For more information, see Using AWS Shield Advanced policies in Firewall Manager. Topics • List of
waf-dg-323	waf-dg.pdf	323	AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note Shield Advanced protects only resources that you have speciﬁed either in Shield Advanced or through an AWS Firewall Manager Shield Advanced policy. It doesn't automatically protect your resources. If you're using an AWS Firewall Manager Shield Advanced policy, you don't need to manage protections for resources that are in scope of the policy. Firewall Manager automatically manages protections for accounts and resources that are in scope of a policy, according to the policy conﬁguration. For more information, see Using AWS Shield Advanced policies in Firewall Manager. Topics • List of resources that AWS Shield Advanced protects • Protecting Amazon EC2 instances and Network Load Balancers with Shield Advanced • Protecting the application layer (layer 7) with AWS Shield Advanced and AWS WAF • Health-based detection using health checks with Shield Advanced and Route 53 • Adding AWS Shield Advanced protection to AWS resources • Editing AWS Shield Advanced protections • Creating alarms and notiﬁcations for resources protected by Shield Advanced • Removing AWS Shield Advanced protection from an AWS resource • Grouping your AWS Shield Advanced protections • Tracking Shield Advanced resource protection changes in AWS Conﬁg List of resources that AWS Shield Advanced protects This section provides information about Shield Advanced protections for each resource type. Shield Advanced protects AWS resources in the network and transport layers (layers 3 and 4) and in the application layer (layer 7). You can protect some resources directly and others through association with protected resources. Shield Advanced supports IPv4, and does not support IPv6. List of protected resources 897 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note Shield Advanced protects only resources that you have speciﬁed either in Shield Advanced or through an AWS Firewall Manager Shield Advanced policy. It doesn't automatically protect your resources. You can use Shield Advanced for advanced monitoring and protection with the following resource types: • Amazon CloudFront distributions. For CloudFront continuous deployment, Shield Advanced protects any staging distribution that's associated with a protected primary distribution. • Amazon Route 53 hosted zones. • AWS Global Accelerator standard accelerators. • Amazon EC2 Elastic IP addresses. Shield Advanced protects the resources that are associated with protected Elastic IP addresses. • Amazon EC2 instances, through association to Amazon EC2 Elastic IP addresses. • The following Elastic Load Balancing (ELB) load balancers: • Application Load Balancers. • Classic Load Balancers. • Network Load Balancers, through associations to Amazon EC2 Elastic IP addresses. Note You can't use Shield Advanced to protect any other resource type. For example, you can't protect AWS Global Accelerator custom routing accelerators or Gateway Load Balancers. You can monitor and protect up to 1,000 resources for each resource type per AWS account. For example, in a single account, you could protect 1,000 Amazon EC2 Elastic IP addresses, 1,000 CloudFront distributions, and 1,000 Application Load Balancers. You can request an increase to the number of resources that you can protect with Shield Advanced through the Service Quotas console at https://console.aws.amazon.com/servicequotas/. List of protected resources 898 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Protecting Amazon EC2 instances and Network Load Balancers with Shield Advanced This page explains how to use AWS Shield Advanced protections for Amazon EC2 instances and Network Load Balancers. You can protect Amazon EC2 instances and Network Load Balancers by ﬁrst attaching these resources to Elastic IP addresses, and then protecting the Elastic IP addresses in Shield Advanced. When you protect Elastic IP addresses, Shield Advanced identiﬁes and protects the resources that they're attached to. Shield Advanced automatically identiﬁes the type of resource that's attached to an Elastic IP address and applies the appropriate detections and mitigations for that resource. This includes conﬁguring network ACLs that are speciﬁc to the Elastic IP address. For more information about using Elastic IP addresses with your AWS resources, see the following guides: Amazon Elastic Compute Cloud documentation or Elastic Load Balancing documentation. During an attack, Shield Advanced automatically deploys your network ACLs to the border of the AWS network. When your network ACLs are at the border of the network, Shield Advanced can provide protection against larger DDoS events. Typically, network ACLs are applied near your Amazon EC2 instances within your Amazon VPC. The network ACL can mitigate attacks only as large as your Amazon VPC and instance can handle. For example, if the network interface attached to your Amazon EC2 instance can process up to 10 Gbps, then volumes over 10 Gbps will slow down and possibly block traﬃc to that instance. During an attack, Shield Advanced promotes your network ACL to the AWS border, which can process multiple terabytes of traﬃc. Your network ACL is able to provide protection for your resource well beyond your network's typical capacity. For more information
waf-dg-324	waf-dg.pdf	324	applied near your Amazon EC2 instances within your Amazon VPC. The network ACL can mitigate attacks only as large as your Amazon VPC and instance can handle. For example, if the network interface attached to your Amazon EC2 instance can process up to 10 Gbps, then volumes over 10 Gbps will slow down and possibly block traﬃc to that instance. During an attack, Shield Advanced promotes your network ACL to the AWS border, which can process multiple terabytes of traﬃc. Your network ACL is able to provide protection for your resource well beyond your network's typical capacity. For more information about network ACLs, see Network ACLs. Some scaling tools, like AWS Elastic Beanstalk, don't let you automatically attach an Elastic IP address to a Network Load Balancer. For those cases, you need to manually attach the Elastic IP address. Protecting the application layer (layer 7) with AWS Shield Advanced and AWS WAF This page explains how Shield Advanced and AWS WAF work together to protect resources at the application layer (layer 7). To protect your application layer resources with Shield Advanced, you start by associating an AWS WAF web ACL with the resource and adding one or more rate-based rules to it. You can Protecting Amazon EC2 instances and Network Load Balancers 899 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide additionally enable automatic application layer DDoS mitigation, which causes Shield Advanced to automatically create and manage web ACL rules on your behalf in response to DDoS attacks. When you protect an application layer resource with Shield Advanced, Shield Advanced analyzes traﬃc over time to establish and maintain baselines. Shield Advanced uses these baselines to detect anomalies in traﬃc patterns that might indicate a DDoS attack. The point at which Shield Advanced detects an attack depends on the traﬃc that Shield Advanced has been able to observe prior to the attack and on the architecture you use for your web applications. The architectural variations that can aﬀect Shield Advanced behavior include the type of instance you use, your instance size, and whether the instance type supports enhanced networking. You can also conﬁgure Shield Advanced to automatically place mitigations for application layer attacks. Shield Advanced subscriptions and AWS WAF costs Your Shield Advanced subscription covers the costs of using standard AWS WAF capabilities for resources that you protect with Shield Advanced. The standard AWS WAF fees that are covered by your Shield Advanced protections are the cost per web ACL, the cost per rule, and the base price per million requests for web request inspection, up to 1,500 WCUs and up to the default body size. Enabling Shield Advanced automatic application layer DDoS mitigation adds a rule group to your web ACL that uses 150 web ACL capacity units (WCUs). These WCUs count against the WCU usage in your web ACL. For more information, see Automating application layer DDoS mitigation with Shield Advanced , Protecting the application layer with the Shield Advanced rule group, and Web ACL capacity units (WCUs) in AWS WAF. Your subscription to Shield Advanced does not cover the use of AWS WAF for resources that you do not protect using Shield Advanced. It also does not cover any additional non-standard AWS WAF costs for protected resources. Examples of non-standard AWS WAF costs are those for Bot Control, for the CAPTCHA rule action, for web ACLs that use more than 1,500 WCUs, and for inspecting the request body beyond the default body size. The full list is provided on the AWS WAF pricing page. For full information and pricing examples, see Shield Pricing and AWS WAF Pricing. Topics • List of factors that aﬀect application layer event detection and mititgation with Shield Advanced • Protecting the application layer with AWS WAF web ACLs and Shield Advanced • Protecting the application layer with AWS WAF rate-based rules and Shield Advanced • Automating application layer DDoS mitigation with Shield Advanced Protecting the application layer (layer 7) 900 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide List of factors that aﬀect application layer event detection and mititgation with Shield Advanced This section describes the factors that aﬀect the detection and mitigation of application layer events by Shield Advanced. Health checks Health checks that accurately report the overall health of your application provide Shield Advanced with information about the traﬃc conditions that your application is experiencing. Shield Advanced requires less information pointing to a potential attack when your application is reporting unhealthy and it requires more evidence of an attack if your application is reporting healthy. It's important to conﬁgure your health checks so that they accurately report application health. For more information and guidance, see Health-based detection using health checks with Shield Advanced and Route 53. Traﬃc baselines Traﬃc baselines give Shield Advanced information about
waf-dg-325	waf-dg.pdf	325	by Shield Advanced. Health checks Health checks that accurately report the overall health of your application provide Shield Advanced with information about the traﬃc conditions that your application is experiencing. Shield Advanced requires less information pointing to a potential attack when your application is reporting unhealthy and it requires more evidence of an attack if your application is reporting healthy. It's important to conﬁgure your health checks so that they accurately report application health. For more information and guidance, see Health-based detection using health checks with Shield Advanced and Route 53. Traﬃc baselines Traﬃc baselines give Shield Advanced information about the characteristics of normal traﬃc for your application. Shield Advanced uses these baselines to recognize when your application isn't receiving normal traﬃc, so it can notify you and, as conﬁgured, start devising and testing mitigation options to counter a potential attack. For additional information about how Shield Advanced uses traﬃc baselines to detect potential events, see the overview section Shield Advanced detection logic for application layer threats (layer 7). Shield Advanced creates its baselines from information provided by the web ACL that's associated with the protected resource. The web ACL must be associated with the resource for at least 24 hours and up to 30 days before Shield Advanced can reliably determine the application's baselines. The time required begins when you associate the web ACL, either through Shield Advanced or through AWS WAF. For more information about using a web ACL with your Shield Advanced application layer protections, see Protecting the application layer with AWS WAF web ACLs and Shield Advanced. Rate-based rules Rate-based rules can help mitigate attacks. They can also obscure attacks, by mitigating them before they become a large enough problem to show up against normal traﬃc baselines or in health check status reporting. Protecting the application layer (layer 7) 901 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide We recommend using rate-based rules in your web ACL when you protect an application resource with Shield Advanced. Even though their mitigations can obscure a potential attack, they are a valuable ﬁrst line of defense, helping ensure that your application stays available to your legitimate customers. The traﬃc that your rate-based rules detect and rate limit is visible in your AWS WAF metrics. In addition to your own rate-based rules, if you enable automatic application layer DDoS mitigation, Shield Advanced adds a rule group to your web ACL that it uses to mitigate attacks. In this rule group, Shield Advanced always has a rate-based rule in place that limits the volume of requests from IP addresses that are known to be sources of DDoS attacks. Metrics for the traﬃc that the Shield Advanced rules mitigate aren't available for you to view. For more information about rate-based rules, see Using rate-based rule statements in AWS WAF. For information about the rate-based rule that Shield Advanced uses for automatic application layer DDoS mitigation, see Protecting the application layer with the Shield Advanced rule group. For more information about Shield Advanced and AWS WAF metrics, see Monitoring with Amazon CloudWatch. Protecting the application layer with AWS WAF web ACLs and Shield Advanced This page explains how AWS WAF web ACLs and Shield Advanced work together to create basic application layer protections. To protect an application layer resource with Shield Advanced, you start by associating an AWS WAF web ACL with the resource. AWS WAF is a web application ﬁrewall that lets you monitor the HTTP and HTTPS requests that are forwarded to your application layer resources, and lets you control access to your content based on the characteristics of the requests. You can conﬁgure a web ACL to monitor and manage requests based on factors such as where the request originated, the contents of query strings and cookies, and the rate of requests coming from a single IP address. At a minimum, your Shield Advanced protection requires you to associate a web ACL with a rate- based rule, which limits the rate of requests for each IP address. If the associated web ACL doesn't have a rate-based rule deﬁned, Shield Advanced prompts you to deﬁne at least one. Rate-based rules automatically block traﬃc from source IPs when they exceed the thresholds that you deﬁne. They help protect your application against web request ﬂoods and can provide alerts about sudden spikes in traﬃc that might indicate a potential DDoS attack. Protecting the application layer (layer 7) 902 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note A rate-based rule responds very quickly to spikes in the traﬃc that the rule is monitoring. Because of this, a rate-based rule can prevent not only an attack, but also the detection of a potential attack by Shield Advanced detection. This trade oﬀ favors prevention over complete visibility into attack
waf-dg-326	waf-dg.pdf	326	exceed the thresholds that you deﬁne. They help protect your application against web request ﬂoods and can provide alerts about sudden spikes in traﬃc that might indicate a potential DDoS attack. Protecting the application layer (layer 7) 902 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note A rate-based rule responds very quickly to spikes in the traﬃc that the rule is monitoring. Because of this, a rate-based rule can prevent not only an attack, but also the detection of a potential attack by Shield Advanced detection. This trade oﬀ favors prevention over complete visibility into attack patterns. We recommend using a rate-based rule as your ﬁrst line of defense against attacks. With your web ACL in place, if a DDoS attack occurs, you apply mitigations by adding and managing rules in the web ACL. You can do this directly, with the assistance of the Shield Response Team (SRT), or automatically through automatic application layer DDoS mitigation. Important If you also use automatic application layer DDoS mitigation, see the best practices for managing your web ACL at Best practices for using automatic application layer DDoS mitigation. For information about using AWS WAF to manage your web request monitoring and management rules, see Creating a web ACL in AWS WAF. Protecting the application layer with AWS WAF rate-based rules and Shield Advanced This page explains how AWS WAF rate-based rules and Shield Advanced work together to create basic application layer protections. When you use a rate-based rule with its default conﬁguration, AWS WAF periodically evaluates traﬃc for the prior 5-minute time window. AWS WAF blocks requests from any IP address that exceeds the rule's threshold until the request rate drops down to an acceptable level. When you conﬁgure a rate-based rule through Shield Advanced, conﬁgure its rate threshold to a value that's greater than the normal traﬃc rate that you expect from any one source IP in any ﬁve minute time window. You might want to use more than one rate-based rule in a web ACL. For example, you could have one rate-based rule for all traﬃc that has a high threshold plus one or more additional rules that Protecting the application layer (layer 7) 903 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide are conﬁgured to match select parts of your web application and that have lower thresholds. For example, you might match on the URI /login.html with a lower threshold, to mitigate abuse against a login page. You can conﬁgure a rate-based rule to use a diﬀerent evaluation time window and to aggregate requests by a number of request components, like header values, labels, and query arguments. For more information, see Using rate-based rule statements in AWS WAF. For additional information and guidance, see the security blog post The three most important AWS WAF rate-based rules. Expanded conﬁguration options through AWS WAF The Shield Advanced console enables you to add a rate-based rule and conﬁgure it with the basic, default settings. You can deﬁne additional conﬁguration options by managing your rate-based rules through AWS WAF. For example, you can conﬁgure the rule to aggregate requests based on keys such as a forwarded IP address, a query string, and a label. You can also add a scope-down statement to the rule to ﬁlter out some requests from evaluation and rate limiting. For more information, see Using rate-based rule statements in AWS WAF. Automating application layer DDoS mitigation with Shield Advanced This page introduces the topic of automatic application layer DDoS mitigation and lists associated caveats. You can conﬁgure Shield Advanced to respond automatically to mitigate application layer (layer 7) attacks against your protected application layer resources, by counting or blocking web requests that are part of the attack. This option is an addition to the application layer protection that you add through Shield Advanced with an AWS WAF web ACL and your own rate-based rule. When automatic mitigation is enabled for a resource, Shield Advanced maintains a rule group in the resource's associated web ACL where it manages mitigation rules on behalf of the resource. The rule group contains a rate-based rule that tracks the volume of requests from IP addresses that are known to be sources of DDoS attacks. Additionally, Shield Advanced compares current traﬃc patterns against historic traﬃc baselines to detect deviations that might indicate a DDoS attack. Shield Advanced responds to detected DDoS attacks by creating, evaluating, and deploying additional, custom AWS WAF rules in the rule group. Protecting the application layer (layer 7) 904 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Caveats for using automatic application layer DDoS mitigation The following list describes the caveats of Shield Advanced automatic application layer DDoS mitigation, and describes steps that you might want to take in response. • Automatic
waf-dg-327	waf-dg.pdf	327	to be sources of DDoS attacks. Additionally, Shield Advanced compares current traﬃc patterns against historic traﬃc baselines to detect deviations that might indicate a DDoS attack. Shield Advanced responds to detected DDoS attacks by creating, evaluating, and deploying additional, custom AWS WAF rules in the rule group. Protecting the application layer (layer 7) 904 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Caveats for using automatic application layer DDoS mitigation The following list describes the caveats of Shield Advanced automatic application layer DDoS mitigation, and describes steps that you might want to take in response. • Automatic application layer DDoS mitigation works only with web ACLs that were created using the latest version of AWS WAF (v2). • Shield Advanced requires time to establish a baseline of your application's normal, historic traﬃc, which it leverages to detect and isolate attack traﬃc from normal traﬃc, to mitigate attack traﬃc. The time to establish a baseline is between 24 hours and 30 days from the time you associate a web ACL with the protected application resource. For additional information about traﬃc baselines, see List of factors that aﬀect application layer event detection and mititgation with Shield Advanced. • Enabling automatic application layer DDoS mitigation adds a rule group to your web ACL that uses 150 web ACL capacity units (WCUs). These WCUs count against the WCU usage in your web ACL. For more information, see Protecting the application layer with the Shield Advanced rule group, and Web ACL capacity units (WCUs) in AWS WAF. • The Shield Advanced rule group generates AWS WAF metrics, but they are not available to view. This is the same as for any other rule groups that you use in your web ACL but do not own, such as AWS Managed Rules rule groups. For more information about AWS WAF metrics, see AWS WAF metrics and dimensions. For information about this Shield Advanced protection option, see Automating application layer DDoS mitigation with Shield Advanced . • For web ACLs that protect multiple resources, automatic mitigation only deploys custom mitigations that don't negatively impact any of the protected resources. • The time between the start of a DDoS attack and when Shield Advanced places custom automatic mitigation rules varies with each event. Some DDoS attacks might end before the custom rules are deployed. Other attacks might happen when a mitigation is already in place, and so might be mitigated by those rules from the start of the event. Additionally, rate-based rules in the web ACL and Shield Advanced rule group might mitigate attack traﬃc before it's detected as a possible event. • For Application Load Balancers that receive any traﬃc through a content delivery network (CDN), such as Amazon CloudFront, the application-layer automatic mitigation capabilities of Shield Advanced for those Application Load Balancer resources will be reduced. Shield Advanced uses client traﬃc attributes to identify and isolate attack traﬃc from normal traﬃc to your application, and CDNs may not preserve or forward the original client traﬃc attributes. If you use CloudFront, we recommend enabling automatic mitigation on the CloudFront distribution. Protecting the application layer (layer 7) 905 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Automatic application layer DDoS mitigation does not interact with protection groups. You can enable automatic mitigation for resources that are in protection groups, but Shield Advanced does not automatically apply attack mitigations based on protection group ﬁndings. Shield Advanced applies automatic attack mitigations for individual resources. Contents • Best practices for using automatic application layer DDoS mitigation • Enabling automatic application layer DDoS mitigation • What happens when you enable automatic mitigation • How Shield Advanced manages automatic mitigation • How Shield Advanced responds to DDoS attacks with automatic mitigation • How Shield Advanced manages the rule action setting • How Shield Advanced manages mitigations when an attack subsides • What happens when you disable automatic mitigation • Protecting the application layer with the Shield Advanced rule group • Viewing the automatic application layer DDoS mitigation conﬁguration for a resource • Enabling and disabling automatic application layer DDoS mitigation • Changing the action used for automatic application layer DDoS mitigation • Using AWS CloudFormation with automatic application layer DDoS mitigation Best practices for using automatic application layer DDoS mitigation Adhere to the guidance provided in this section when you use automatic mitigation. General protections management Follow these guidelines for planning and implementing your automatic mitigation protections. • Manage all of your automatic mitigation protections either through Shield Advanced or, if you're using AWS Firewall Manager to manage your Shield Advanced automatic mitigation settings, through Firewall Manager. Don't mix your use of Shield Advanced and Firewall Manager to manage these protections. • Manage similar resources using the same web ACLs and protection settings, and manage dissimilar resources
waf-dg-328	waf-dg.pdf	328	application layer DDoS mitigation Best practices for using automatic application layer DDoS mitigation Adhere to the guidance provided in this section when you use automatic mitigation. General protections management Follow these guidelines for planning and implementing your automatic mitigation protections. • Manage all of your automatic mitigation protections either through Shield Advanced or, if you're using AWS Firewall Manager to manage your Shield Advanced automatic mitigation settings, through Firewall Manager. Don't mix your use of Shield Advanced and Firewall Manager to manage these protections. • Manage similar resources using the same web ACLs and protection settings, and manage dissimilar resources using diﬀerent web ACLs. When Shield Advanced mitigates a DDoS attack on a protected resource, it deﬁnes rules for the web ACL that's associated with the resource Protecting the application layer (layer 7) 906 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide and then tests the rules against traﬃc of all resources that are associated with the web ACL. Shield Advanced will only apply the rules if they don't negatively impact any of the associated resources. For more information, see How Shield Advanced manages automatic mitigation. • For Application Load Balancers that have all their internet traﬃc proxied through a Amazon CloudFront distribution, only enable automatic mitigation on the CloudFront distribution. The CloudFront distribution will always have the greatest number of original traﬃc attributes, which Shield Advanced leverages to mitigate attacks. Detection and mitigation optimization Follow these guidelines to optimize the protections that automatic mitigation provides to protected resources. For an overview of application layer detection and mitigation, see List of factors that aﬀect application layer event detection and mititgation with Shield Advanced. • Conﬁgure health checks for your protected resources and use them to enable health-based detection in your Shield Advanced protections. For guidance, see Health-based detection using health checks with Shield Advanced and Route 53. • Enable automatic mitigation in Count mode until Shield Advanced has established a baseline for normal, historic traﬃc. Shield Advanced needs from 24 hours to 30 days to establish a baseline. Establishing a baseline of normal traﬃc patterns requires the following: • The association of a web ACL with the protected resource. You can use AWS WAF directly to associate your web ACL or you can have Shield Advanced associate it when you enable the Shield Advanced application layer protection and specify a web ACL to use. • Normal traﬃc ﬂow to your protected application. If your application isn't experiencing normal traﬃc, such as before the application is launched or if it lacks production traﬃc for extended periods of time, the historical data can't be gathered. Web ACL management Follow these guidelines for managing the web ACLs that you use with automatic mitigation. • If you need to replace the web ACL that's associated with the protected resource, make the following changes in order: 1. In Shield Advanced, disable automatic mitigation. 2. In AWS WAF, disassociate the old web ACL and associate the new web ACL. Protecting the application layer (layer 7) 907 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 3. In Shield Advanced, enable automatic mitigation. Shield Advanced doesn't automatically transfer automatic mitigation from the old web ACL to the new one. • Don't delete any rule group rule from your web ACLs whose name starts with ShieldMitigationRuleGroup. If you do delete this rule group, you disable the protections provided by Shield Advanced automatic mitigation for every resource that's associated with the web ACL. Additionally, it can take Shield Advanced some time to receive notice of the change and to update its settings. During this time, the Shield Advanced console pages will provide incorrect information. For more information about the rule group, see Protecting the application layer with the Shield Advanced rule group. • Don't modify the name of a rule group rule whose name starts with ShieldMitigationRuleGroup. Doing so can interfere with the protections provided by Shield Advanced automatic mitigation through the web ACL. • When you create rules and rule groups, don't use names that start with ShieldMitigationRuleGroup. This string is used by Shield Advanced to manage your automatic mitigations. • In your management of your web ACL rules, don't assign a priority setting of 10,000,000. Shield Advanced assigns this priority setting to its automatic mitigation rule group rule when it adds it. • Keep the ShieldMitigationRuleGroup rule prioritized so that it runs when you want it to in relation to the other rules in your web ACL. Shield Advanced adds the rule group rule to the web ACL with priority 10,000,000, to run after your other rules. If you use the AWS WAF console wizard to manage your web ACL, adjust the priority settings as needed after you add rules to the web ACL. • If you use AWS CloudFormation to manage
waf-dg-329	waf-dg.pdf	329	setting of 10,000,000. Shield Advanced assigns this priority setting to its automatic mitigation rule group rule when it adds it. • Keep the ShieldMitigationRuleGroup rule prioritized so that it runs when you want it to in relation to the other rules in your web ACL. Shield Advanced adds the rule group rule to the web ACL with priority 10,000,000, to run after your other rules. If you use the AWS WAF console wizard to manage your web ACL, adjust the priority settings as needed after you add rules to the web ACL. • If you use AWS CloudFormation to manage your web ACLs, you don't need to manage the ShieldMitigationRuleGroup rule group rule. Follow the guidance at Using AWS CloudFormation with automatic application layer DDoS mitigation. Enabling automatic application layer DDoS mitigation This page explains how to conﬁgure Shield Advanced to automatically respond to application layer attacks. Protecting the application layer (layer 7) 908 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide You enable Shield Advanced automatic mitigation as part of the application layer DDoS protections for your resource. For information about doing this through the console, see Conﬁgure application layer DDoS protections. The automatic mitigation functionality requires you to do the following: • Associate a web ACL with the resource – This is required for any Shield Advanced application layer protection. You can use the same web ACL for multiple resources. We recommend doing this only for resources that have similar traﬃc. For information about web ACLs, including the requirements for using them with multiple resources, see How AWS WAF works. • Enable and conﬁgure Shield Advanced automatic application layer DDoS mitigation – When you enable this, you specify whether you want Shield Advanced to automatically block or count web requests that it determines to be part of a DDoS attack. Shield Advanced adds a rule group to the associated web ACL and uses it to dynamically manage its response to DDoS attacks on the resource. For information about the rule action options, see Using rule actions in AWS WAF. • (Optional, but recommended) Add a rate-based rule to the web ACL – By default, the rate- based rule provides your resource with basic protection against DDoS attacks by preventing any individual IP address from sending too many requests in a short time. For information about rate-based rules, including custom request aggregation options and examples, see Using rate- based rule statements in AWS WAF. What happens when you enable automatic mitigation Shield Advanced does the following when you enable automatic mitigation: • As needed, adds a rule group for Shield Advanced use – If the AWS WAF web ACL that you have associated with the resource doesn't already have an AWS WAF rule group rule that's dedicated to automatic application layer DDoS mitigation, Shield Advanced adds one. The name of the rule group rule starts with ShieldMitigationRuleGroup. The rule group always contains a rate-based rule named ShieldKnownOffenderIPRateBasedRule, which limits the volume of requests from IP addresses that are known to be sources of DDoS attacks. For additional details about the Shield Advanced rule group and the web ACL rule that references it, see Protecting the application layer with the Shield Advanced rule group. • Starts responding to DDoS attacks against the resource – Shield Advanced automatically responds to DDoS attacks for the protected resource. In addition to the rate-based rule, which is always present, Shield Advanced uses its rule group to deploy custom AWS WAF rules for DDoS Protecting the application layer (layer 7) 909 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide attack mitigation. Shield Advanced tailors these rules to your application and to the attacks that your application experiences, and tests them against the resource's historical traﬃc before deploying them. Shield Advanced uses a single rule group rule in any web ACL that you use for automatic mitigation. If Shield Advanced has already added the rule group for another protected resource, it doesn't add another rule group to the web ACL. Automatic application layer DDoS mitigation depends on the presence of the rule group to mitigate attacks. If the rule group is removed from the AWS WAF web ACL for any reason, the removal disables automatic mitigation for all resources that are associated with the web ACL. How Shield Advanced manages automatic mitigation The topics in this section describe how Shield Advanced handles your conﬁguration changes for automatic application layer DDoS mitigation and how it handles DDoS attacks when automatic mitigation is enabled. Topics • How Shield Advanced responds to DDoS attacks with automatic mitigation • How Shield Advanced manages the rule action setting • How Shield Advanced manages mitigations when an attack subsides • What happens when you disable automatic mitigation How Shield Advanced responds to DDoS attacks with automatic
waf-dg-330	waf-dg.pdf	330	reason, the removal disables automatic mitigation for all resources that are associated with the web ACL. How Shield Advanced manages automatic mitigation The topics in this section describe how Shield Advanced handles your conﬁguration changes for automatic application layer DDoS mitigation and how it handles DDoS attacks when automatic mitigation is enabled. Topics • How Shield Advanced responds to DDoS attacks with automatic mitigation • How Shield Advanced manages the rule action setting • How Shield Advanced manages mitigations when an attack subsides • What happens when you disable automatic mitigation How Shield Advanced responds to DDoS attacks with automatic mitigation When you have automatic mitigation enabled on a protected resource, the rate-based rule ShieldKnownOffenderIPRateBasedRule in the Shield Advanced rule group responds automatically to elevated traﬃc volumes from known DDoS sources. This rate-limiting is applied quickly and acts as a front-line defense against attacks. When Shield Advanced detects an attack, it does the following: 1. Attempts to identify an attack signature that isolates the attack traﬃc from the normal traﬃc to your application. The goal is to produce high quality DDoS mitigation rules that, when placed, aﬀect only the attack traﬃc and don't impact normal traﬃc to your application. Protecting the application layer (layer 7) 910 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 2. Evaluates the identiﬁed attack signature against the historical traﬃc patterns for the resource that's under attack as well as for any other resource that's associated with the same web ACL. Shield Advanced does this before it deploys any rules in response to the event. Depending on the evaluation results, Shield Advanced does one of the following: • If Shield Advanced determines that the attack signature isolates only the traﬃc that is involved in the DDoS attack, it implements the signature in AWS WAF rules in the Shield Advanced mitigation rule group in the web ACL. Shield Advanced gives these rules the action setting that you've conﬁgured for the resource's automatic mitigation - either Count or Block. • Otherwise, Shield Advanced doesn't place a mitigation. Throughout an attack, Shield Advanced sends the same notiﬁcations and provides the same event information as for basic Shield Advanced application layer protections. You can see the information about events and DDoS attacks, and about any Shield Advanced mitigations for attacks, in the Shield Advanced event console. For information, see Visibility into DDoS events with Shield Advanced. If you've conﬁgured automatic mitigation to use the Block rule action and you experience false positives from the mitigation rules that Shield Advanced has deployed, you can change the rule action to Count. For information about how to this, see Changing the action used for automatic application layer DDoS mitigation. How Shield Advanced manages the rule action setting You can set the rule action for your automatic mitigations to Block or Count. When you change the automatic mitigation rule action setting for a protected resource, Shield Advanced updates all rule settings for the resource. It updates any rules that are currently in place for the resource in the Shield Advanced rule group and it uses the new action setting when it creates new rules. For resources that use the same web ACL, if you specify diﬀerent actions, Shield Advanced uses the Block action setting for the rule group's rate-based rule ShieldKnownOffenderIPRateBasedRule. Shield Advanced creates and manages other rules in the rule group on behalf of a speciﬁc protected resource, and uses the action setting that you've speciﬁed for the resource. All rules in the Shield Advanced rule group in a web ACL are applied to the web traﬃc of all of the associated resources. Protecting the application layer (layer 7) 911 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Changing the action setting can take a few seconds to propagate. During this time, you might see the old setting in some places where the rule group is in use, and the new setting in other places. You can change the rule action setting for your automatic mitigation conﬁguration in the events page of the console, and through the application layer conﬁguration page. For information about the events page, see Responding to DDoS events in AWS. For information about the conﬁguration page, see Conﬁgure application layer DDoS protections. How Shield Advanced manages mitigations when an attack subsides When Shield Advanced determines that mitigation rules that were deployed for a particular attack are no longer needed, it removes them from the Shield Advanced mitigation rule group. The removal of mitigating rules won't necessarily coincide with the end of an attack. Shield Advanced monitors patterns of attack that it detects on your protected resources. It might proactively defend against the recurrence of an attack with a speciﬁc signature by keeping the rules that it has deployed against the initial occurrence of
waf-dg-331	waf-dg.pdf	331	the conﬁguration page, see Conﬁgure application layer DDoS protections. How Shield Advanced manages mitigations when an attack subsides When Shield Advanced determines that mitigation rules that were deployed for a particular attack are no longer needed, it removes them from the Shield Advanced mitigation rule group. The removal of mitigating rules won't necessarily coincide with the end of an attack. Shield Advanced monitors patterns of attack that it detects on your protected resources. It might proactively defend against the recurrence of an attack with a speciﬁc signature by keeping the rules that it has deployed against the initial occurrence of that attack in place. As needed, Shield Advanced increases the window of time that it keeps rules in place. This way, Shield Advanced might mitigate repeated attacks with a speciﬁc signature before they impact your protected resources. Shield Advanced never removes the rate-based rule ShieldKnownOffenderIPRateBasedRule, which limits the volume of requests from IP addresses that are known to be sources of DDoS attacks. What happens when you disable automatic mitigation Shield Advanced does the following when you disable automatic mitigation for a resource: • Stops automatically responding to DDoS attacks – Shield Advanced discontinues its automatic response activities for the resource. • Removes unneeded rules from the Shield Advanced rule group – If Shield Advanced is maintaining any rules in its managed rule group on behalf of the protected resource, it removes them. • Removes the Shield Advanced rule group, if it's no longer in use – If the web ACL that you have associated with the resource isn't associated to any other resource that has automatic mitigation enabled, Shield Advanced removes its rule group rule from the web ACL. Protecting the application layer (layer 7) 912 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Protecting the application layer with the Shield Advanced rule group This page explains how the Shield Advanced rule group works in your web ACL. Shield Advanced manages automatic mitigation activities using rules in a rule group that it owns and manages for you. Shield Advanced references the rule group with a rule in the web ACL that you have associated with your protected resource. The rule group rule in your web ACL The Shield Advanced rule group rule in your web ACL has the following properties: • Name – ShieldMitigationRuleGroup_account-id_web-acl-id_unique-identifier • Web ACL capacity units (WCU) – 150. These WCUs count against the WCU usage in your web ACL. Shield Advanced creates this rule in your web ACL with a priority setting of 10,000,000, so that it runs after your other rules and rule groups in the web ACL. AWS WAF runs the rules in a web ACL from the lowest numeric priority setting on up. During your management of the web ACL, this priority setting might change. The automatic mitigation functionality doesn't consume any additional AWS WAF resources in your account, other than the WCUs used by the rule group in your web ACL. For example, the Shield Advanced rule group isn't counted as one of your account's rule groups. For information about account limits in AWS WAF, see AWS WAF quotas. Rules in the rule group Within the referenced Shield Advanced rule group, Shield Advanced maintains a rate-based rule ShieldKnownOffenderIPRateBasedRule, which limits the volume of requests from IP addresses that are known to be sources of DDoS attacks. This rule serves as the ﬁrst line of defense against any attack, because it's always present in the rule group and it doesn't rely on the analysis of traﬃc patterns to contain attacks. This rule's action is set to the action that you choose for your automatic mitigations, just like the other rules in the rule group. For information about rate-based rules, see Using rate-based rule statements in AWS WAF. Note The rate-based rule ShieldKnownOffenderIPRateBasedRule operates independent of Shield Advanced event detection. While automatic mitigation is enabled, this rule rate Protecting the application layer (layer 7) 913 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide limits IP addresses that are known to be sources of DDoS attacks. For these IP addresses, the rule's rate limiting can prevent attacks and also keep attacks from appearing in the Shield Advanced detection information. This trade oﬀ favors prevention over complete visibility into attack patterns. In addition to the permanent rate-based rule described above, the rule group contains any rules that Shield Advanced is currently using to mitigate DDoS attacks. Shield Advanced adds, modiﬁes, and removes these rules as needed. For information, see How Shield Advanced manages automatic mitigation. Metrics The rule group generates AWS WAF metrics, but because this rule group is owned by Shield Advanced, these metrics aren't available to view. For more information, see AWS WAF metrics and dimensions. Viewing the automatic application layer DDoS mitigation conﬁguration for a resource
waf-dg-332	waf-dg.pdf	332	information. This trade oﬀ favors prevention over complete visibility into attack patterns. In addition to the permanent rate-based rule described above, the rule group contains any rules that Shield Advanced is currently using to mitigate DDoS attacks. Shield Advanced adds, modiﬁes, and removes these rules as needed. For information, see How Shield Advanced manages automatic mitigation. Metrics The rule group generates AWS WAF metrics, but because this rule group is owned by Shield Advanced, these metrics aren't available to view. For more information, see AWS WAF metrics and dimensions. Viewing the automatic application layer DDoS mitigation conﬁguration for a resource You can view the automatic application layer DDoS mitigation conﬁguration for a resource in the Protected resources page and in the individual protections pages. To view the automatic application layer DDoS mitigation conﬁguration 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. 2. In the AWS Shield navigation pane, choose Protected resources. In the list of protected resources, the column Automatic application layer DDoS mitigation indicates whether automatic mitigation is enabled and, where enabled, the action that Shield Advanced is to use in its mitigations. You can also select any application layer resource to see the same information listed on the protections page for the resource. Enabling and disabling automatic application layer DDoS mitigation The following procedure shows how to enable or disable automatic response for a protected resource. Protecting the application layer (layer 7) 914 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide To enable or disable automatic application layer DDoS mitigation for a single resource 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// 2. 3. 4. 5. console.aws.amazon.com/wafv2/. In the AWS Shield navigation pane, choose Protected resources. In the Protections tab, select the application layer resource that you want to enable automatic mitigation for. The protections page opens for the resource. In the resource's protections page, choose Edit. In the page Conﬁgure layer 7 DDoS mitigation for global resources - optional, for Automatic application layer DDoS mitigation, choose the option that you want to use for automatic mitigations. The options in the console are the following: • Keep current settings – Make no changes to the automatic mitigation settings of the protected resource. • Enable – Enable automatic mitigation for the protected resource. When you choose this, also select the rule action that you want the automatic mitigations to use in the web ACL rules. For information about rule action settings, see Using rule actions in AWS WAF. If your protected resource doesn’t yet have a history of normal application traﬃc, enable automatic mitigation in Count mode until Shield Advanced can establish a baseline. Shield Advanced begins to collect information for its baseline when you associate a web ACL with your protected resource, and it can take 24 hour to 30 days to establish a good baseline of normal traﬃc. • Disable – Disable automatic mitigation for the protected resource. 6. Walk through the rest of the pages until you ﬁnish and save the conﬁguration. In the Protections page, the automatic mitigation settings are updated for the resource. Changing the action used for automatic application layer DDoS mitigation You can change the action that Shield Advanced uses for its application layer automatic response in multiple locations in the console: • Automatic mitigation conﬁguration – Change the action when you conﬁgure automatic mitigation for your resource. For the procedure, see the preceding section Enabling and disabling automatic application layer DDoS mitigation. Protecting the application layer (layer 7) 915 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Event details page – Change the action in the event details page, when you're viewing the event information in the console. For information, see Viewing AWS Shield Advanced event details. If you have two protected resources that share a web ACL, and you set the action to Count for one and Block for the other, Shield Advanced sets the action for the rule group's rate-based rule ShieldKnownOffenderIPRateBasedRule to Block. Using AWS CloudFormation with automatic application layer DDoS mitigation This page explains how to use AWS CloudFormation to manage your protections and AWS WAF web ACLs. Enabling or disabling automatic application layer DDoS mitigation You can enable and disable automatic application layer DDoS mitigation through AWS CloudFormation, using the AWS::Shield::Protection resource. The eﬀect is the same as when you enable or disable the feature through the console or any other interface. For information about the AWS CloudFormation resource, see AWS::Shield::Protection in the AWS CloudFormation user guide. Managing web ACLs used with automatic mitigation Shield Advanced manages automatic mitigation for your protected resource using a rule group rule in the protected resource's AWS WAF web ACL. Through the
waf-dg-333	waf-dg.pdf	333	to manage your protections and AWS WAF web ACLs. Enabling or disabling automatic application layer DDoS mitigation You can enable and disable automatic application layer DDoS mitigation through AWS CloudFormation, using the AWS::Shield::Protection resource. The eﬀect is the same as when you enable or disable the feature through the console or any other interface. For information about the AWS CloudFormation resource, see AWS::Shield::Protection in the AWS CloudFormation user guide. Managing web ACLs used with automatic mitigation Shield Advanced manages automatic mitigation for your protected resource using a rule group rule in the protected resource's AWS WAF web ACL. Through the AWS WAF console and APIs, you'll see the rule listed in your web ACL rules, with a name that starts with ShieldMitigationRuleGroup. This rule is dedicated to your automatic application layer DDoS mitigation and it's managed for you by Shield Advanced and AWS WAF. For more information, see Protecting the application layer with the Shield Advanced rule group and How Shield Advanced manages automatic mitigation. If you use AWS CloudFormation to manage your web ACLs, don't add the Shield Advanced rule group rule to your web ACL template. When you update a web ACL that's being used with your automatic mitigation protections, AWS WAF automatically manages the rule group rule in the web ACL. You'll see the following diﬀerences compared to other web ACLs that you manage through AWS CloudFormation: • AWS CloudFormation won't report any drift in the stack drift status between the actual conﬁguration of the web ACL, with the Shield Advanced rule group rule, and your web ACL Protecting the application layer (layer 7) 916 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide template, without the rule. The Shield Advanced rule won't appear in the actual listing for the resource in the drift details. You will be able to see the Shield Advanced rule group rule in web ACL listings that you retrieve from AWS WAF, such as through the AWS WAF console or AWS WAF APIs. • If you modify the web ACL template in a stack, AWS WAF and Shield Advanced automatically maintain the Shield Advanced automatic mitigation rule in the updated web ACL. The automatic mitigation protections provided by Shield Advanced are not interrupted by your update to the web ACL. Don't manage the Shield Advanced rule in your AWS CloudFormation web ACL template. The web ACL template shouldn't list the Shield Advanced rule. Follow the best practices for web ACL management at Best practices for using automatic application layer DDoS mitigation. Health-based detection using health checks with Shield Advanced and Route 53 You can conﬁgure Shield Advanced to use health-based detection for improved responsiveness and accuracy in attack detection and mitigation. You can use this option with any resource type except for Route 53 hosted zones. To conﬁgure health-based detection, you deﬁne a health check for your resource in Route 53, verify that it's reporting healthy, and then associate it with your Shield Advanced protection. For information about Route 53 health checks, see How Amazon Route 53 checks the health of your resources and Creating, updating, and deleting health checks in the Amazon Route 53 Developer Guide. Note Health checks are required for Shield Response Team (SRT) proactive engagement support. For information about proactive engagement, see Setting up proactive engagement for the SRT to contact you directly. Health checks measure the health of your resources based on the requirements that you deﬁne. The health check status provides vital input to the Shield Advanced detection mechanisms, giving them greater sensitivity to the current state of your speciﬁc applications. Health-based detection using health checks 917 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide You can enable health-based detection for any resource type except for Route 53 hosted zones. • Network and transport layer (layer 3/layer 4) resources – Health-based detection improves the accuracy of network-layer and transport-layer event detection and mitigation for Network Load Balancers, Elastic IP addresses, and Global Accelerator standard accelerators. When you protect these resource types with Shield Advanced, Shield Advanced can provide mitigations for smaller attacks and faster mitigation for attacks, even when traﬃc is within the application’s capacity. When you add health-based detection, during periods when the associated health check is unhealthy, Shield Advanced can place mitigations even more quickly and at even lower thresholds. • Application layer (layer 7) resources – Health-based detection improves the accuracy of web request ﬂood detection for CloudFront distributions and Application Load Balancers. When you protect these resource types with Shield Advanced, you receive web request ﬂood detection alerts when there's a statistically signiﬁcant deviation in traﬃc volume that's combined with signiﬁcant changes in traﬃc patterns, based on request characteristics. With health-based detection, when the associated Route 53 health check is unhealthy, Shield Advanced requires smaller deviations to
waf-dg-334	waf-dg.pdf	334	periods when the associated health check is unhealthy, Shield Advanced can place mitigations even more quickly and at even lower thresholds. • Application layer (layer 7) resources – Health-based detection improves the accuracy of web request ﬂood detection for CloudFront distributions and Application Load Balancers. When you protect these resource types with Shield Advanced, you receive web request ﬂood detection alerts when there's a statistically signiﬁcant deviation in traﬃc volume that's combined with signiﬁcant changes in traﬃc patterns, based on request characteristics. With health-based detection, when the associated Route 53 health check is unhealthy, Shield Advanced requires smaller deviations to alert and it reports events more quickly. Conversely, when the associated Route 53 health check is healthy, Shield Advanced requires larger deviations to alert. You'll beneﬁt the most from using a health check with Shield Advanced if the health check only reports healthy when your application is running within acceptable parameters and only reports unhealthy when it's not. Use the guidance in this section to manage your health check associations in Shield Advanced. Note Shield Advanced doesn't automatically manage your health checks. The following are required to use a health check with Shield Advanced: • The health check must report healthy when you associate it with your Shield Advanced protection. Health-based detection using health checks 918 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • The health check must be relevant to the health of your protected resource. You are responsible for deﬁning and maintaining health checks that accurately report the health of your application, based on your application's speciﬁc requirements. • The health check must remain available for use by the Shield Advanced protection. Don't delete a health check in Route 53 that you're using for a Shield Advanced protection. Contents • Best practices for using health checks with Shield Advanced • CloudWatch metrics commonly used for health checks with Shield Advanced • Metrics used to monitor application health • Amazon CloudWatch metrics for each resource type • Associating a health check with your resource protected by Shield Advanced • Disassociating a health check from your resource protected by Shield Advanced • Viewing health check association status in Shield Advanced • Health check examples for Shield Advanced • Amazon CloudFront distributions • Load balancers • Amazon EC2 elastic IP address (EIP) Best practices for using health checks with Shield Advanced Follow the best practices in this section when you create and use health checks with Shield Advanced. • Plan your health checks by identifying the components of your infrastructure that you want to monitor. Consider the following resource types for health checks: • Critical resources. • Any resources where you want higher sensitivity in Shield Advanced detection and mitigation. • Resources for which you want Shield Advanced to proactively reach out to you. Proactive engagement is informed by the status of your health checks. Examples of resources that you might want to monitor include Amazon CloudFront distributions, internet-facing load balancers, and Amazon EC2 instances. Health-based detection using health checks 919 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Deﬁne health checks that accurately reﬂect the health of your application origin with as few notiﬁcations as possible. • Write health checks so that they're only unhealthy when your application is unavailable or isn't performing within acceptable parameters. You are responsible for deﬁning and maintaining health checks based on your application's speciﬁc requirements. • Use as few health checks as possible while still accurately reporting on the health of your application. For example, multiple alarms from multiple areas of your application that all report the same problem might add overhead to your response activities without adding informational value. • Use calculated health checks to monitor application health using a combination of Amazon CloudWatch metrics. For example, you can calculate combined health based on the latency of your application servers and their 5xx error rates, which indicate that the origin server didn't fulﬁll the request. • Create and publish your own application health indicators to CloudWatch custom metrics as needed and use them in a calculated health check. • Implement and manage your health checks to improve detection and reduce unnecessary maintenance activities. • Before you associate a health check with a Shield Advanced protection, make sure that it's in a healthy state. Associating a health check that's reporting unhealthy can skew the Shield Advanced detection mechanisms for your protected resources. • Keep your health checks available for use by Shield Advanced. Don't delete a health check in Route 53 that you're using for a Shield Advanced protection. • Use staging and test environments only to test your health checks. Only maintain health check associations for environments that require production-level performance and availability. Don't maintain health check association in Shield Advanced for staging and test
waf-dg-335	waf-dg.pdf	335	you associate a health check with a Shield Advanced protection, make sure that it's in a healthy state. Associating a health check that's reporting unhealthy can skew the Shield Advanced detection mechanisms for your protected resources. • Keep your health checks available for use by Shield Advanced. Don't delete a health check in Route 53 that you're using for a Shield Advanced protection. • Use staging and test environments only to test your health checks. Only maintain health check associations for environments that require production-level performance and availability. Don't maintain health check association in Shield Advanced for staging and test environments. CloudWatch metrics commonly used for health checks with Shield Advanced This section lists the Amazon CloudWatch metrics that are commonly used in health checks to measure application health during distributed denial of service (DDoS) events. For full information about the CloudWatch metrics for each resource type, see the list that follows the table. Topics • Metrics used to monitor application health • Amazon CloudWatch metrics for each resource type Health-based detection using health checks 920 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Metrics used to monitor application health Resource Route 53 Metric Description HealthCheckStatus The status of the health check endpoint. CloudFront 5xxErrorRate Application Load Balancer HTTPCode_ELB_5XX_C ount Application Load Balancer RejectedConnection Count Application Load Balancer TargetConnectionEr rorCount Application Load Balancer TargetResponseTime Application Load Balancer UnHealthyHostCount The percentage of all requests for which the HTTP status code is 5xx. This indicates an attack that's impacting the application. The number of HTTP 5xx client error codes generated by the load balancer. The number of connections that were rejected because the load balancer reached its maximum number of connections. The number of connections that were not successfully established between the load balancer and the target. The time elapsed in seconds after the request leaves the load balancer and when it receives a response from the target. The number of targets that are considered unhealthy. Health-based detection using health checks 921 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Resource Metric Description Amazon EC2 CPUUtilization The percentage of allocated EC2 compute units that are currently in use. Amazon CloudWatch metrics for each resource type For additional information about the metrics that are available for your protected resources, see the following sections in the resource guides: • Amazon Route 53 – Monitoring your resources with Amazon Route 53 health checks and Amazon CloudWatch in the Amazon Route 53 Developer Guide. • Amazon CloudFront – Monitoring CloudFront with Amazon CloudWatch in the Amazon CloudFront Developer Guide. • Application Load Balancer – CloudWatch metrics for your Application Load Balancer in the User Guide for Application Load Balancers. • Network Load Balancer – CloudWatch metrics for your Network Load Balancer in the User Guide for Network Load Balancers. • AWS Global Accelerator – Using Amazon CloudWatch with AWS Global Accelerator in the AWS Global Accelerator Developer Guide. • Amazon Elastic Compute Cloud – List the available CloudWatch metrics for your instances in the https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/. • Amazon EC2 Auto Scaling – Monitoring CloudWatch metrics for your Auto Scaling groups and instances in the Amazon EC2 Auto Scaling User Guide. Associating a health check with your resource protected by Shield Advanced The following procedure shows how to associate an Amazon Route 53 health check with a protected resource. Health-based detection using health checks 922 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note Before you associate a health check with a Shield Advanced protection, make sure that it's in a healthy state. For information, see Monitoring health check status and getting notiﬁcations in the Amazon Route 53 Developer Guide. To associate a health check 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. 2. In the AWS Shield navigation pane, choose Protected resources. 3. On the Protections tab, select the resource that you want to associate with a health check. 4. Choose Conﬁgure protections. 5. Choose Next until you get to the page Conﬁgure health check based DDoS detection - optional. 6. Under Associated Health Check, choose the ID of the health check that you want to associate with the protection. Note If you do not see the health check you need, go to the Route 53 console and verify the health check and its ID. For information, see Creating and Updating Health Checks. 7. Walk through the rest of the pages until you ﬁnish the conﬁguration. On the Protections page, your updated health check association is listed for the resource. 8. On the Protections page, check that your newly associated health check is reporting healthy. You can't successfully begin using a health check in Shield Advanced while the health check is reporting unhealthy. Doing so causes Shield
waf-dg-336	waf-dg.pdf	336	with the protection. Note If you do not see the health check you need, go to the Route 53 console and verify the health check and its ID. For information, see Creating and Updating Health Checks. 7. Walk through the rest of the pages until you ﬁnish the conﬁguration. On the Protections page, your updated health check association is listed for the resource. 8. On the Protections page, check that your newly associated health check is reporting healthy. You can't successfully begin using a health check in Shield Advanced while the health check is reporting unhealthy. Doing so causes Shield Advanced to detect false positives at very low thresholds and can also negatively impact the ability of the Shield Response Team (SRT) to provide proactive engagement for the resource. If the newly associated health check is reporting unhealthy, do the following: a. Disassociate the health check from your protection in Shield Advanced. Health-based detection using health checks 923 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide b. Revisit your health check speciﬁcations in Amazon Route 53 and verify your overall application performance and availability. c. When your application is performing within your parameters for good health and your health check is reporting healthy, try again to associate the health check in Shield Advanced. The health check association procedure is complete when you've established your new health check association and it reports healthy in Shield Advanced. Disassociating a health check from your resource protected by Shield Advanced The following procedure shows how to disassociate an Amazon Route 53 health check from a protected resource. To disassociate a health check 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. 2. In the AWS Shield navigation pane, choose Protected resources. 3. On the Protections tab, select the resource that you want to disassociate from a health check. 4. Choose Conﬁgure protections. 5. Choose Next until you get to the page Conﬁgure health check based DDoS detection - optional. 6. Under Associated Health Check, choose the empty option, listed as -. 7. Walk through the rest of the pages until you ﬁnish the conﬁguration. On the Protections page, the health check ﬁeld for your resource is set to -, indicating no health check association. Viewing health check association status in Shield Advanced You can see the status of the health check that's associated with a protection on the AWS WAF & Shield console Protected resources page and on the details page of each resource. • Healthy – The health check is available and is reporting healthy. • Unhealthy – The health check is available and is reporting unhealthy. Health-based detection using health checks 924 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Unavailable – The health check is not available for use by Shield Advanced. To resolve an Unavailable health check Create and use a new health check. Don't try to associate a health check again after it has had a status of unavailable in Shield Advanced. For detailed guidance on following these steps, see the preceding topics. 1. 2. In Shield Advanced, disassociate the health check from the resource. In Route 53, create a new health check for the resource and note its ID. For information, see Creating and Updating Health Checks in the Amazon Route 53 Developer Guide. 3. In Shield Advanced, associate the new health check with the resource. Health check examples for Shield Advanced This section shows examples of health checks that you could use in a calculated health check. A calculated health check uses a number of individual health checks to determine a combined status. The status of each individual health check is based on the health of an endpoint or on the state of an Amazon CloudWatch metric. You combine health checks into a calculated health check and then conﬁgure your calculated health check to report health based on the combined health status of the individual health checks. Tune the sensitivity of your calculated health checks according to your requirements for application performance and availability. For information about calculated health checks, see Monitoring other health checks (calculated health checks) in the Amazon Route 53 Developer Guide. For additional information, see the blog post Route 53 Improvements – Calculated Health Checks and Latency Checks. Topics • Amazon CloudFront distributions • Load balancers • Amazon EC2 elastic IP address (EIP) Amazon CloudFront distributions The following examples describe health checks that could be combined into a calculated health check for a CloudFront distribution: Health-based detection using health checks 925 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Monitor an endpoint by specifying a domain name to a path on the distribution that's serving dynamic content. A healthy response would include
waf-dg-337	waf-dg.pdf	337	Amazon Route 53 Developer Guide. For additional information, see the blog post Route 53 Improvements – Calculated Health Checks and Latency Checks. Topics • Amazon CloudFront distributions • Load balancers • Amazon EC2 elastic IP address (EIP) Amazon CloudFront distributions The following examples describe health checks that could be combined into a calculated health check for a CloudFront distribution: Health-based detection using health checks 925 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Monitor an endpoint by specifying a domain name to a path on the distribution that's serving dynamic content. A healthy response would include HTTP response codes 2xx and 3xx. • Monitor the state of a CloudWatch alarm that's measuring the health of the CloudFront origin. For example, you can maintain a CloudWatch alarm on the Application Load Balancer metric TargetResponseTime, and create a health check that reﬂects the status of the alarm. The health check can be unhealthy when the response time, between request leaving the load balancer and when the load balancer receives a response from the target, exceeds the threshold conﬁgured in the alarm. • Monitor the state of a CloudWatch alarm that measures the percentage of requests for which the response’s HTTP status code is 5xx. If the CloudFront distribution's 5xx error rate is higher than the threshold deﬁned in the CloudWatch alarm, the status of this health check will switch to unhealthy. Load balancers The following examples describe health checks that could be used in calculated health checks for an Application Load Balancer, Network Load Balancer, or Global Accelerator standard accelerator. • Monitor the state of a CloudWatch alarm that measures the number of new connections established by clients to the load balancer. You can set the alarm threshold for the average number of new connections at some degree higher than your every day average. The metrics for each resource type are the following: • Application Load Balancer: NewConnectionCount • Network Load Balancer: ActiveFlowCount • Global Accelerator: NewFlowCount • For Application Load Balancer and Network Load Balancer, monitor the state of a CloudWatch alarm that measures the number of load balancers that are considered healthy. You can set the alarm threshold either on Availability Zone or on the minimum number of healthy hosts that your load balancer requires. The available metrics for the load balancer resources are as follows: • Application Load Balancer: HealthyHostCount • Network Load Balancer: HealthyHostCount • For Application Load Balancer, monitor the state of a CloudWatch alarm that measures the number of HTTP 5xx response codes generated by the load balancer targets. For an Application Load Balancer, you can use the metric HTTPCode_Target_5XX_Count and base the alarm threshold on the sum of all 5xx errors for the load balancer. Health-based detection using health checks 926 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Amazon EC2 elastic IP address (EIP) The following example health checks could be combined into a calculated health check for an Amazon EC2 elastic IP address: • Monitor an endpoint by specifying an IP address to the Elastic IP address. The health check will remain healthy as long as a TCP connection can be established with the resource behind the IP address. • Monitor the state of a CloudWatch alarm that measures the percentage of allocated Amazon EC2 compute units that are currently in use on the instance. You can use the Amazon EC2 metric CPUUtilization and base the alarm threshold on what you consider to be a high CPU utilization rate for your application, such as 90%. Adding AWS Shield Advanced protection to AWS resources Follow the guidance in this section to add Shield Advanced protection to one or more resources. To add protection for an AWS resource 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. 2. In the navigation pane, under AWS Shield choose Protected resources. 3. Choose Add resources to protect. 4. In the Choose resources to protect with Shield Advanced page, in Specify the Region and resource types, provide the Region and resource type speciﬁcations for the resources that you want to protect. You can protect resources in multiple Regions by selecting All Regions and you can narrow the selection to global resources by selecting Global. You can deselect any resource types that you do not want to protect. For information about protections for your resource types, see List of resources that AWS Shield Advanced protects. 5. Choose Load resources. Shield Advanced populates the Select Resources section with the AWS resources that match your criteria. 6. In the Select Resources section, you can ﬁlter the list of resources by entering a string to search for in the resource listings. Select the resources that you want to protect. Adding protection to a resource 927 AWS
waf-dg-338	waf-dg.pdf	338	and you can narrow the selection to global resources by selecting Global. You can deselect any resource types that you do not want to protect. For information about protections for your resource types, see List of resources that AWS Shield Advanced protects. 5. Choose Load resources. Shield Advanced populates the Select Resources section with the AWS resources that match your criteria. 6. In the Select Resources section, you can ﬁlter the list of resources by entering a string to search for in the resource listings. Select the resources that you want to protect. Adding protection to a resource 927 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 7. In the Tags section, if you want to add tags to the Shield Advanced protections that you are creating, specify those. For information about tagging AWS resources, see Working with Tag Editor. 8. Choose Protect with Shield Advanced. This adds Shield Advanced protections to the resources. Editing AWS Shield Advanced protections You can change the settings for your AWS Shield Advanced protections at any time. To do this, walk through the options for your selected protections and modify the settings that you need to change. To manage protected resources 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. 2. 3. In the AWS Shield navigation pane, choose Protected resources. In the Protections tab, select the resources that you want to protect. 4. Choose Conﬁgure protections and the resource speciﬁcation option that you want. 5. Walk through each of the resource protection options, making changes as needed. Conﬁgure application layer DDoS protections For protection against attacks on Amazon CloudFront and Application Load Balancer resources, you can add AWS WAF web ACLs and add rate-based rules. For information about this, see Protecting the application layer with AWS WAF web ACLs and Shield Advanced. You can also enable the Shield Advanced automatic application layer DDoS mitigation. For information about how AWS WAF works, see AWS WAF. For information about the automatic mitigation feature, see Automating application layer DDoS mitigation with Shield Advanced . Important If you manage your Shield Advanced protections through AWS Firewall Manager using a Shield Advanced policy, you can't manage the application layer protections here. For Editing protections 928 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide all other resources, we recommend that, at a minimum, you attach a web ACL to each resource, even if web ACL doesn't contain any rules. Note When you enable automatic application layer DDoS mitigation for a resource, if needed, the operation automatically adds a service-linked role to your account to give Shield Advanced the permissions it needs to manage your web ACL protections. For information, see Using service-linked roles for Shield Advanced. To conﬁgure application layer DDoS protections 1. In the Conﬁgure layer 7 DDoS protections page, if the resource isn't already associated with a web ACL, you can choose an existing web ACL or create your own. To create a web ACL, follow these steps: a. b. c. Choose Create web ACL. Enter a name. You can't change the name after you create the web ACL. Choose Create. Note If a resource is already associated with a web ACL, you can't change to a diﬀerent web ACL. If you want to change the web ACL, you must ﬁrst remove the associated web ACLs from the resource. For more information, see Associating or disassociating a web ACL with an AWS resource. 2. If the web ACL doesn't have a rate-based rule deﬁned, you can add one by choosing Add rate limit rule and then performing the following steps: a. b. Enter a name. Enter a rate limit. This is the maximum number of requests allowed in any ﬁve minute period from any single IP address before the rate-based rule action is applied to the Editing protections 929 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide IP address. When the requests from the IP address fall below the limit, the action is discontinued. c. Set the rule action to count or block requests from IP addresses while their request counts are over the limit. The application and removal of the rule action might take eﬀect a minute or two after the IP address request rate changes. d. Choose Add rule. 3. For Automatic application layer DDoS mitigation, choose whether you want Shield Advanced to automatically mitigate DDoS attacks on your behalf, as follows: • To enable automatic mitigation, choose Enable and then select the AWS WAF rule action that you want Shield Advanced to use in its custom rules. Your choices are Count and Block. For information about these AWS WAF rule actions, see Using rule actions in AWS WAF. For information about how Shield Advanced manages
waf-dg-339	waf-dg.pdf	339	removal of the rule action might take eﬀect a minute or two after the IP address request rate changes. d. Choose Add rule. 3. For Automatic application layer DDoS mitigation, choose whether you want Shield Advanced to automatically mitigate DDoS attacks on your behalf, as follows: • To enable automatic mitigation, choose Enable and then select the AWS WAF rule action that you want Shield Advanced to use in its custom rules. Your choices are Count and Block. For information about these AWS WAF rule actions, see Using rule actions in AWS WAF. For information about how Shield Advanced manages this action setting, see How Shield Advanced manages the rule action setting. • To disable automatic mitigation, choose Disable. • To leave the automatic mitigation settings unchanged for the resources that you're managing, leave the default choice Keep current settings. For information about Shield Advanced automatic application layer DDoS mitigation, see Automating application layer DDoS mitigation with Shield Advanced . 4. Choose Next. Creating alarms and notiﬁcations for resources protected by Shield Advanced The following procedure shows how to manage CloudWatch alarms for protected resources. Note CloudWatch incurs additional costs. For CloudWatch pricing, see Amazon CloudWatch Pricing. Creating alarms and notiﬁcations 930 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide To create alarms and notiﬁcations 1. In the protections page Create alarms and notiﬁcations - optional, conﬁgure the SNS topics for the alarms and notiﬁcations that you want to receive. For resources that you don't want notiﬁcations for, choose No topic. You can add an Amazon SNS topic or create a new topic. 2. To create an Amazon SNS topic, follow these steps: a. b. In the dropdown list, choose Create an SNS topic. Enter a topic name. c. Optionally enter an email address that the Amazon SNS messages will be sent to, and then choose Add email. You can enter more than one. d. Choose Create. 3. Choose Next. Removing AWS Shield Advanced protection from an AWS resource You can remove AWS Shield Advanced protection from any of your AWS resources at any time. Important Deleting an AWS resource doesn't remove the resource from AWS Shield Advanced. You must also remove the protection on the resource from AWS Shield Advanced, as described in this procedure. Remove AWS Shield Advanced protection from an AWS resource 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. In the AWS Shield navigation pane, choose Protected resources. In the Protections tab, select the resources whose protections you want to remove. 2. 3. 4. Choose Delete protections. • If you have an Amazon CloudWatch alarm conﬁgured for a protection, you are given the option to delete the alarm along with the protection. If you choose not to delete the alarm at this point, you can instead delete it later using the CloudWatch console. Removing protection from a resource 931 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note For protections that have an Amazon Route 53 health check conﬁgured, if you add the protection again later, the protection still includes the health check. The preceding steps remove AWS Shield Advanced protection from speciﬁc AWS resources. They don't cancel your AWS Shield Advanced subscription. You will continue to be charged for the service. For information about your AWS Shield Advanced subscription, contact the AWS Support Center. Removing a CloudWatch alarm from your Shield Advanced protections To remove a CloudWatch alarm from your Shield Advanced protections, do one of the following: • Delete the protection as described in Removing AWS Shield Advanced protection from an AWS resource. Be sure to select the check box next to Also delete related DDoSDetection alarm. • Delete the alarm using the CloudWatch console. The name of the alarm to delete starts with DDoSDetectedAlarmForProtection. Grouping your AWS Shield Advanced protections Use protection groups to create logical collections of your protected resources and manage their protections as a group. For information about managing resource protections, see Editing AWS Shield Advanced protections. Note Automatic application layer DDoS mitigation does not interact with protection groups. You can enable automatic mitigation for resources that are in protection groups, but Shield Advanced does not automatically apply attack mitigations based on protection group ﬁndings. Shield Advanced applies automatic attack mitigations for individual resources. Protection groups 932 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide AWS Shield Advanced protection groups give you a self-service way to customize the scope of detection and mitigation by treating multiple protected resources as a single unit. Resource grouping can provide a number of beneﬁts. • Improve accuracy of detection. • Reduce unactionable event notiﬁcations. • Increase coverage of mitigation actions to include protected resources that also might be aﬀected during an event. • Accelerate
waf-dg-340	waf-dg.pdf	340	Advanced does not automatically apply attack mitigations based on protection group ﬁndings. Shield Advanced applies automatic attack mitigations for individual resources. Protection groups 932 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide AWS Shield Advanced protection groups give you a self-service way to customize the scope of detection and mitigation by treating multiple protected resources as a single unit. Resource grouping can provide a number of beneﬁts. • Improve accuracy of detection. • Reduce unactionable event notiﬁcations. • Increase coverage of mitigation actions to include protected resources that also might be aﬀected during an event. • Accelerate time to mitigation of attacks with multiple similar targets. • Facilitate automatic protection of newly created protected resources. Protection groups can help reduce false positives in situations such as blue/green swap, where resources alternate between being near zero load and fully loaded. Another example is when you create and delete resources frequently while maintaining a load level that's shared among the members of the group. For situations such as these, monitoring individual resources can lead to false positives, while monitoring the health of the group of resources does not. You can conﬁgure protection groups to include all protected resources, all resources of speciﬁc resource types, or individually speciﬁed resources. Newly protected resources that satisfy your protection group criteria are automatically included in your protection group. A protected resource can belong to multiple protection groups. Creating a Shield Advanced protection group To create a protection group 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. 2. In the AWS Shield navigation pane, choose Protected resources. 3. Choose the Protection groups tab, then choose Create protection group. 4. 5. In the Create protection group page, provide a name for your group. You'll use this name to identify the group in your list of protected resources. You can't change the name of a protection group after you create it. For Protection grouping criteria, select the criteria that you want Shield Advanced to use to identify the protected resources to include in the group. Make your additional selections based on the criteria that you've chosen. Protection groups 933 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 6. For Aggregation, select how you want Shield Advanced to combine resource data for the group in order to detect, mitigate, and report events. • Sum – Use the total traﬃc across the group. This is a good choice for most cases. Examples include Elastic IP addresses for Amazon EC2 instances that scale manually or automatically. • Mean – Use the average of the traﬃc across the group. This is a good choice for resources that share traﬃc uniformly. Examples include accelerators and load balancers. • Max – Use the highest traﬃc from each resource. This is useful for resources that don't share traﬃc, and for resources that share traﬃc in a non-uniform way. Examples include Amazon CloudFront distributions and origin resources for CloudFront distributions. 7. Choose Save to save your protection group and return to the Protected resources page. In the Shield Events page, you can view events for your protection group and drill down to see additional information for the protected resources that are in the group. Updating a Shield Advanced protection group To update a protection group 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// 2. 3. 4. console.aws.amazon.com/wafv2/. In the AWS Shield navigation pane, choose Protected resources. In the Protection groups tab, select the check box next to the protection group that you want to modify. In the protection group's page, choose Edit. Make your changes to the protection group settings. 5. Choose Save to save your changes. Deleting a Shield Advanced protection group To delete a protection group 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. 2. In the AWS Shield navigation pane, choose Protected resources. Protection groups 934 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 3. In the Protection groups tab, select the check box next to the protection group that you want to remove. 4. In the protection group's page, choose Delete and conﬁrm the action. Tracking Shield Advanced resource protection changes in AWS Conﬁg This page explains how to record changes to the AWS Shield Advanced protection of your resources using AWS Conﬁg. You can then use this information to maintain a conﬁguration change history for audit and troubleshooting purposes. To record protection changes, enable AWS Conﬁg for each resource that you want to track. For more information, see Getting Started with AWS Conﬁg in the AWS Conﬁg Developer Guide. You must enable AWS Conﬁg for each AWS Region that contains the
waf-dg-341	waf-dg.pdf	341	remove. 4. In the protection group's page, choose Delete and conﬁrm the action. Tracking Shield Advanced resource protection changes in AWS Conﬁg This page explains how to record changes to the AWS Shield Advanced protection of your resources using AWS Conﬁg. You can then use this information to maintain a conﬁguration change history for audit and troubleshooting purposes. To record protection changes, enable AWS Conﬁg for each resource that you want to track. For more information, see Getting Started with AWS Conﬁg in the AWS Conﬁg Developer Guide. You must enable AWS Conﬁg for each AWS Region that contains the tracked resources. You can enable AWS Conﬁg manually, or you can use the AWS CloudFormation template "Enable AWS Conﬁg" at AWS CloudFormation StackSets Sample Templates in the AWS CloudFormation User Guide. If you enable AWS Conﬁg, you're charged as detailed on the AWS Conﬁg Pricing page. Note If you already have AWS Conﬁg enabled for the necessary Regions and resources, you don't need to do anything. AWS Conﬁg logs regarding protection changes to your resources start populating automatically. After enabling AWS Conﬁg, use the US East (N. Virginia) Region in the AWS Conﬁg console to view the conﬁguration change history for AWS Shield Advanced global resources. View the change history for AWS Shield Advanced regional resources via the AWS Conﬁg console in the US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), Europe (Ireland), Europe (Frankfurt), Asia Paciﬁc (Tokyo), and Asia Paciﬁc (Sydney) Regions. Visibility into DDoS events with Shield Advanced AWS Shield provides visibility into the following categories of events and event activities: Tracking protection changes 935 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Global – All customers can access an aggregated view of global threat activity over the last two weeks. You can see this information under the Getting Started and Global threat dashboard pages of the AWS Shield console. For more information, see Viewing AWS Shield global and account activity. • Account – All customers can access a summary of the events for their account over the prior year. You can see this information under the Getting Started page of the AWS Shield console. For more information, see Viewing AWS Shield global and account activity. When you subscribe to Shield Advanced and add protections to your resources, you gain access to additional information about the events and DDoS attacks on the protected resources: • Events on protected resources – Shield Advanced provides detailed information for each event through the Events page of the AWS Shield console. For more information, see Viewing AWS Shield Advanced events. • Event metrics for protected resources – Shield Advanced publishes detection, mitigation, and top contributor Amazon CloudWatch metrics for all resources that it protects. You can use these metrics to conﬁgure CloudWatch dashboards and alarms. For more information, see AWS Shield Advanced metrics. • Cross-account event visibility for protected resources – If you use AWS Firewall Manager to manage your Shield Advanced protections, you can enable visibility into protections across multiple accounts by using Firewall Manager combined with AWS Security Hub. For more information, see Viewing Shield Advanced events across multiple AWS accounts with AWS Firewall Manager and AWS Security Hub. If you enable automatic application layer DDoS mitigation for an application layer protection, Shield Advanced adds a rule group to your web ACL that it uses to manage automated protections. This rule group generates AWS WAF metrics, but they are not available to view. This is the same as for any other rule groups that you use in your web ACL but do not own, such as AWS Managed Rules rule groups. For more information about AWS WAF metrics, see AWS WAF metrics and dimensions. For information about this Shield Advanced protection option, see Automating application layer DDoS mitigation with Shield Advanced . Topics • Viewing AWS Shield global and account activity • Viewing AWS Shield Advanced events Visibility into DDoS events 936 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Viewing Shield Advanced events across multiple AWS accounts with AWS Firewall Manager and AWS Security Hub Viewing AWS Shield global and account activity This page provides instructions for accessing an aggregated view of global threat activity and a per-account event summary in the AWS Shield console Getting Started and Global threat dashboard pages. The following screenshot shows an example Getting Started page. Global and account activity 937 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide To access the AWS Shield console • Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. You don't need a subscription to Shield Advanced to access global activity and account event summary information. Global and account activity 938 AWS
waf-dg-342	waf-dg.pdf	342	instructions for accessing an aggregated view of global threat activity and a per-account event summary in the AWS Shield console Getting Started and Global threat dashboard pages. The following screenshot shows an example Getting Started page. Global and account activity 937 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide To access the AWS Shield console • Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. You don't need a subscription to Shield Advanced to access global activity and account event summary information. Global and account activity 938 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Global activity This information is available through the AWS Shield console Global threat dashboard and Getting Started pages. The following screenshot shows an example of the global activity pane. Global activity describes DDoS events observed across all AWS customers. Once per hour, AWS updates the information for the prior two weeks. In the console pane, you can see the results, partitioned by AWS Region and displayed on a world heat map. Next to the map, Shield displays summary information such as the largest packet attack, largest bit rate, most common vector, total number of attacks, and threat level. The threat level is an assessment of the current global activity compared to what AWS typically observes. The default threat level value is Normal. AWS automatically updates the value to High for elevated DDoS activity. The Global threat dashboard also provides time-series metrics and gives you the ability to change between time durations. To view the history of signiﬁcant DDoS attacks, you can customize the dashboard for views from the last day to the last two weeks. Time-series metrics provide a view of the largest bit rate, packet rate, or request rate for all events detected by AWS Shield for applications running on AWS during the time window that you select. Account activity Global and account activity 939 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide This information is available in the AWS Shield console Getting Started page. The following screenshot shows an example account activity pane. Account activity describes DDoS events that Shield detected for your resources that are eligible for protection by Shield Advanced. Each day, Shield creates summary metrics for the year ending at 00:00 UTC the prior day, and then displays total events, largest bit rate, largest packet rate, and largest request rate. • The total events metric reﬂects every time that Shield observed suspicious attributes in traﬃc that was destined to your application. Suspicious attributes can include traﬃc that is at a higher than normal volume, traﬃc that does not match your application’s historical proﬁle, or traﬃc that does not match heuristics that are deﬁned by Shield for valid application traﬃc. • Largest bit rate and largest packet rate statistics are available for every resource. • The largest request rate statistic is available only for Amazon CloudFront distributions and Application Load Balancers that have an associated AWS WAF web ACL. Note You can also access the account level event summary through the AWS Shield API operation DescribeAttackStatistics. Viewing AWS Shield Advanced events This page provides instructions for accessing information about events in Shield Advanced. Events 940 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide When you subscribe to Shield Advanced, and protect your resources, you gain access to additional visibility features for the resources. These include near real-time notiﬁcation of events that are detected by Shield Advanced and additional information about detected events and mitigations. Note Your event information in the Shield Advanced console is based on Shield Advanced metrics. For information about Shield Advanced metrics, see AWS Shield Advanced metrics AWS Shield evaluates traﬃc to your protected resource along multiple dimensions. When an anomaly is detected, Shield Advanced creates a separate event for each resource that's aﬀected. You can access event summaries and details through the Events page of the Shield console. The top level Events page provides an overview of current and past events. The following screenshot shows an example Events page with a single ongoing event. This active event is also ﬂagged in the left navigation pane. Shield Advanced might also automatically place mitigations against attacks, depending on the traﬃc type and on your conﬁgured protections. These mitigations can protect your resource from receiving excess traﬃc or traﬃc that matches a known DDoS attack signature. The following screenshot shows an example Events listing where all events have been mitigated by Shield Advanced or have subsided on their own. Events 941 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Protect your resources before an event Improve the accuracy of event detection by protecting resources with Shield Advanced while they are receiving the normal expected traﬃc, before
waf-dg-343	waf-dg.pdf	343	Advanced might also automatically place mitigations against attacks, depending on the traﬃc type and on your conﬁgured protections. These mitigations can protect your resource from receiving excess traﬃc or traﬃc that matches a known DDoS attack signature. The following screenshot shows an example Events listing where all events have been mitigated by Shield Advanced or have subsided on their own. Events 941 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Protect your resources before an event Improve the accuracy of event detection by protecting resources with Shield Advanced while they are receiving the normal expected traﬃc, before they are subject to a DDoS attack. In order to accurately report events for a protected resource, Shield Advanced must ﬁrst establish a baseline of expected traﬃc patterns for it. • Shield Advanced reports infrastructure layer events for resources after they've been protected for at least 15 minutes. • Shield Advanced reports web application layer events for resources after they've been protected for at least 24 hours. The accuracy of detection for application layer events is best after Shield Advanced has observed expected traﬃc for 30 days. To access events information in the AWS Shield console 1. Sign in to the AWS Management Console and open the AWS WAF & Shield console at https:// console.aws.amazon.com/wafv2/. 2. 3. In the AWS Shield navigation pane, choose Events. The console shows the Events page. From the Events page, you can select any event in the list to see additional summary information and details for the event. Topics • List of ﬁelds in AWS Shield Advanced event summaries Events 942 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Viewing AWS Shield Advanced event details List of ﬁelds in AWS Shield Advanced event summaries This page lists and deﬁnes the ﬁelds in Shield Advanced event summaries. You can view summary and detail information for an event in the event's console page. To open the page for an event, select its AWS resource name from the Events page list. The following screenshot shows an example event summary for a network layer event. The event page summary information includes the following. • Current status – Values that indicate the state of the event and the actions that Shield Advanced has taken on the event. Status values apply to infrastructure layer (layer 3 or 4) and application layer (layer 7) events. • Identiﬁed (ongoing) and Identiﬁed (subsided) – These indicate that Shield Advanced detected an event, but has taken no action on it so far. Identiﬁed (subsided) indicates that the suspicious traﬃc that Shield detected has stopped without intervention. • Mitigation in progress and Mitigated – These indicate that Shield Advanced detected an event and has taken action on it. Mitigated is also used when the targeted resource is an Amazon Events 943 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide CloudFront distribution or Amazon Route 53 hosted zone, which have their own automatic inline mitigations. • Attack vectors – DDoS attack vectors like TCP SYN ﬂoods and Shield Advanced detection heuristics like request ﬂood. These can be indicators of a DDoS attack. • Start time – The date and time that the ﬁrst anomalous traﬃc data point was detected. • Duration or end time – Indicates the time elapsed between the event start time and the last observed anomalous data point that Shield Advanced observed. While an event is ongoing, these values will continue to increase. • Protection – Names the Shield Advanced protection that's in associated with the resource, and provides a link to its protection page. This is available in the individual event's page. • Automatic application layer DDoS mitigation – Used for application layer protections, to indicate whether the Shield Advanced automatic application layer DDoS mitigation is enabled for the resource. If it is enabled, this provides a link to access and manage the conﬁguration. This is available in the individual event's page. • Network layer automatic mitigation – Indicates whether the resource has automatic mitigation at the network layer. If a resource has a network layer component, it will have this enabled. This information is available in the individual event's page. For resources that are frequently targeted, Shield may leave mitigations in place after excess traﬃc has subsided, to prevent further recurring events. Note You can also access event summaries for protected resources through the AWS Shield API operation ListAttacks. Viewing AWS Shield Advanced event details You can see details about an event's detection, mitigation, and top contributors in the bottom section of the console page for the event. This section can include a mix of legitimate and potentially unwanted traﬃc, and may represent both traﬃc that was passed to your protected resource and traﬃc that was blocked by Shield mitigations. Events 944 AWS WAF, AWS
waf-dg-344	waf-dg.pdf	344	targeted, Shield may leave mitigations in place after excess traﬃc has subsided, to prevent further recurring events. Note You can also access event summaries for protected resources through the AWS Shield API operation ListAttacks. Viewing AWS Shield Advanced event details You can see details about an event's detection, mitigation, and top contributors in the bottom section of the console page for the event. This section can include a mix of legitimate and potentially unwanted traﬃc, and may represent both traﬃc that was passed to your protected resource and traﬃc that was blocked by Shield mitigations. Events 944 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Detection and mitigation – Provides information about the observed event and any applied mitigations against it. For information about event mitigation, see Responding to DDoS events in AWS. • Top contributors – Categorizes the traﬃc that's involved in the event, and lists the primary sources of traﬃc that Shield has identiﬁed for each category. For application layer events, use the top contributors information to get a general idea of the nature of an event, but use the AWS WAF logs for your security decisions. For more information, see the sections that follow. Your event information in the Shield Advanced console is based on Shield Advanced metrics. For information about Shield Advanced metrics, see AWS Shield Advanced metrics Mitigation metrics aren't included for Amazon CloudFront or Amazon Route 53 resources, because these services are protected by a mitigation system that's always enabled and doesn't require mitigations for individual resources. The details sections vary according to whether the information is for an infrastructure layer or application layer event. Topics • Viewing application layer (layer 7) event details in Shield Advanced • Viewing infrastructure layer (layer 3 or 4) event details in Shield Advanced Viewing application layer (layer 7) event details in Shield Advanced You can see details about an application layer event's detection, mitigation, and top contributors in the bottom section of the console page for the event. This section can include a mix of legitimate and potentially unwanted traﬃc, and may represent both traﬃc that was passed to your protected resource and traﬃc that was blocked by Shield Advanced mitigations. The mitigation details are for any rules in the web ACL that's associated with the resource, including rules that are deployed speciﬁcally in response to an attack and rate-based rules that are deﬁned in the web ACL. If you enable automatic application layer DDoS mitigation for an application, the mitigation metrics include metrics for those additional rules. For information about these application layer protections, see Protecting the application layer (layer 7) with AWS Shield Advanced and AWS WAF. Events 945 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Detection and mitigation For an application layer (layer 7) event, the Detection and mitigation tab shows detection metrics that are based on information obtained from the AWS WAF logs. Mitigation metrics are based on AWS WAF rules in the associated web ACL that are conﬁgured to block the unwanted traﬃc. For Amazon CloudFront distributions, you can conﬁgure Shield Advanced to apply automatic mitigations for you. With any application layer resources, you can choose to deﬁne your own mitigating rules in your web ACL and you can request help from the Shield Response Team (SRT). For information about these options, see Responding to DDoS events in AWS. The following screenshot shows an example of the detection metrics for an application layer event that subsided after a number of hours. Event traﬃc that subsides before a mitigating rule takes eﬀect isn't represented in mitigation metrics. This can result in a diﬀerence between the web request traﬃc shown in the detection graphs and the allow and block metrics shown in the mitigation graphs. Top contributors The Top contributors tab for application layer events displays the top 5 contributors that Shield has identiﬁed for the event, based on the AWS WAF logs that it has retrieved. Shield categorizes the top contributors information by dimensions such as source IP, source country, and destination URL. Events 946 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note For the most accurate information about the traﬃc that's contributing to an application layer event, use the AWS WAF logs. Use the Shield application layer top contributors information only to get a general idea of the nature of an attack, and do not base your security decisions on it. For application layer events, the AWS WAF logs are the best source of information for understanding the contributors to an attack and for devising your mitigation strategies. The Shield top contributors information doesn't always completely reﬂect the data in the AWS WAF logs. When it ingests the logs, Shield prioritizes reducing the impact to system performance over retrieving the
waf-dg-345	waf-dg.pdf	345	that's contributing to an application layer event, use the AWS WAF logs. Use the Shield application layer top contributors information only to get a general idea of the nature of an attack, and do not base your security decisions on it. For application layer events, the AWS WAF logs are the best source of information for understanding the contributors to an attack and for devising your mitigation strategies. The Shield top contributors information doesn't always completely reﬂect the data in the AWS WAF logs. When it ingests the logs, Shield prioritizes reducing the impact to system performance over retrieving the complete set of data from the logs. This can result in a loss of granularity in the data that's available to Shield for analysis. In most cases, the majority of the information is available, but it's possible for the top contributor data to be skewed to some degree for any attack. The following screenshot shows an example Top contributors tab for an application layer event. Contributor information is based on requests for both legitimate and potentially unwanted traﬃc. Larger volume events and events where the request sources aren't highly distributed are more likely to have identiﬁable top contributors. A signiﬁcantly distributed attack could have any number of sources, making it hard to identify top contributors to the attack. If Shield Advanced doesn't identify signiﬁcant contributors for a speciﬁc category, it displays the data as unavailable. Events 947 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Viewing infrastructure layer (layer 3 or 4) event details in Shield Advanced You can see details about an infrastructure layer event's detection, mitigation, and top contributors in the bottom section of the console page for the event. This section can include a mix of legitimate and potentially unwanted traﬃc, and may represent both traﬃc that was passed to your protected resource and traﬃc that was blocked by Shield mitigations. Detection and mitigation For an infrastructure layer (layer 3 or 4) event, the Detection and mitigation tab shows detection metrics that are based on sampled network ﬂows and mitigation metrics that are based on traﬃc observed by the mitigation systems. Mitigation metrics are a more precise measurement of the traﬃc into your resource. Shield automatically creates a mitigation for the protected resource types Elastic IP (EIP), Classic Load Balancer (CLB), Application Load Balancer (ALB), and AWS Global Accelerator standard accelerator. Mitigation metrics for EIP addresses and AWS Global Accelerator standard accelerators indicate the number of passed and dropped packets. The following screenshot shows an example Detection and mitigation tab for an infrastructure layer event. Event traﬃc that subsides before Shield places a mitigation isn't represented in the mitigation metrics. This can result in a diﬀerence between the traﬃc shown in the detection graphs and the pass and drop metrics shown in the mitigation graphs. Events 948 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Top contributors The Top contributors tab for infrastructure layer events lists metrics for up to 100 top contributors on several traﬃc dimensions. The details include network layer properties for any dimension where at least ﬁve signiﬁcant sources of traﬃc could be identiﬁed. Examples of sources of traﬃc are source IP and source ASN. The following screenshot shows an example Top contributors tab for an infrastructure layer event. Events 949 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Contributor metrics are based on sampled network ﬂows for both legitimate and potentially unwanted traﬃc. Larger volume events and events where the traﬃc sources aren't highly distributed are more likely to have identiﬁable top contributors. A signiﬁcantly distributed attack could have any number of sources, making it hard to identify top contributors to the attack. If Shield doesn't identify any signiﬁcant contributors for a speciﬁc metric or category, it displays the data as unavailable. In an infrastructure layer DDoS attack, traﬃc sources might be spoofed or reﬂected. A spoofed source is intentionally forged by the attacker. A reﬂected source is the real source of detected traﬃc, but it's not a willing participant in the attack. For example, an attacker might generate a large, ampliﬁed ﬂood of traﬃc to a target by reﬂecting the attack oﬀ of services on the internet that are usually legitimate. In this case, the source information might be valid while it's not the actual source of the attack. These factors can limit the viability of mitigation techniques that block sources based on packet headers. Viewing Shield Advanced events across multiple AWS accounts with AWS Firewall Manager and AWS Security Hub You can use AWS Firewall Manager and AWS Security Hub to manage and monitor AWS Shield Advanced protected resources across multiple accounts. With Firewall Manager, you can create a Shield Advanced security policy that reports and enforces DDoS protection compliance across all
waf-dg-346	waf-dg.pdf	346	services on the internet that are usually legitimate. In this case, the source information might be valid while it's not the actual source of the attack. These factors can limit the viability of mitigation techniques that block sources based on packet headers. Viewing Shield Advanced events across multiple AWS accounts with AWS Firewall Manager and AWS Security Hub You can use AWS Firewall Manager and AWS Security Hub to manage and monitor AWS Shield Advanced protected resources across multiple accounts. With Firewall Manager, you can create a Shield Advanced security policy that reports and enforces DDoS protection compliance across all of your accounts. Firewall Manager monitors your protected resources, including adding protections to new resources that come into scope of the Shield Advanced policy. You can integrate Firewall Manager with AWS Security Hub to get a single dashboard that reports DDoS events that are detected by Shield Advanced and Firewall Manager compliance ﬁndings, when Firewall Manager identiﬁes a resource that's out of compliance with your Shield Advanced security policy. The following ﬁgure depicts a typical architecture for monitoring Shield Advanced protected resources with Firewall Manager and Security Hub. Event visibility across accounts 950 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide When you integrate Firewall Manager with Security Hub, you can view security ﬁndings in a single place, alongside other alerts and compliance status information for the applications that you run on AWS. The following screenshot highlights the information that you can see for a Shield Advanced event inside the Security Hub console when you have an integration of this type. Event visibility across accounts 951 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide To learn how to integrate Firewall Manager and Security Hub with Shield Advanced to centralize event and compliance monitoring across your protected accounts, see the AWS security blog Set up centralized monitoring for DDoS events and auto-remediate noncompliant resources. Responding to DDoS events in AWS This page explains how AWS responds to DDoS attacks, and provides options for how you can further respond. AWS automatically mitigates network and transport layer (layer 3 and layer 4) DDoS attacks. If you use Shield Advanced to protect your Amazon EC2 instances, during an attack Shield Advanced automatically deploys your Amazon VPC network ACLs to the border of the AWS network. This allows Shield Advanced to provide protection against larger DDoS events. For more information about network ACLs, see Network ACLs. For application layer (layer 7) DDoS attacks, AWS attempts to detect and notify AWS Shield Advanced customers through CloudWatch alarms. By default, it doesn't automatically apply mitigations, to avoid inadvertently blocking valid user traﬃc. For application layer (layer 7) resources, you have the following options available for responding to an attack. Responding to DDoS events 952 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Provide your own mitigations – You can investigate and mitigate the attack on your own. For information, see Manually mitigating an application layer DDoS attack. • Contact support – If you're a Shield Advanced customer, you can contact the AWS Support Center to get help with mitigations. Critical and urgent cases are routed directly to DDoS experts. For information, see Contacting the support center during an application layer DDoS attack. Additionally, before an attack occurs, you can proactively enable the following mitigation options: • Automatic mitigations on Amazon CloudFront distributions – With this option, Shield Advanced deﬁnes and manages mitigating rules for you in your web ACL. For information about automatic application layer mitigation, see Automating application layer DDoS mitigation with Shield Advanced . • Proactive engagement – When AWS Shield Advanced detects a large application layer attack against one of your applications, the SRT can proactively contact you. The SRT triages the DDoS event and creates AWS WAF mitigations. The SRT contacts you and, with your consent, can apply the AWS WAF rules. For more information about this option, see Setting up proactive engagement for the SRT to contact you directly. Contacting the support center during an application layer DDoS attack This page provides instructions for contacting the support center during an application layer DDoS attack. If you're an AWS Shield Advanced customer, you can contact the AWS Support Center to get help with mitigations. Critical and urgent cases are routed directly to DDoS experts. With AWS Shield Advanced, complex cases can be escalated to the AWS Shield Response Team (SRT), which has deep experience in protecting AWS, Amazon.com, and its subsidiaries. For more information about the SRT, see Managed DDoS event response with Shield Response Team (SRT) support. To get Shield Response Team (SRT) support, contact the AWS Support Center. The response time for your case depends on the severity that you select and the response times, which are documented on the AWS
waf-dg-347	waf-dg.pdf	347	can contact the AWS Support Center to get help with mitigations. Critical and urgent cases are routed directly to DDoS experts. With AWS Shield Advanced, complex cases can be escalated to the AWS Shield Response Team (SRT), which has deep experience in protecting AWS, Amazon.com, and its subsidiaries. For more information about the SRT, see Managed DDoS event response with Shield Response Team (SRT) support. To get Shield Response Team (SRT) support, contact the AWS Support Center. The response time for your case depends on the severity that you select and the response times, which are documented on the AWS Support Plans page. Select the following options: • Case type: Technical Support • Service: Distributed Denial of Service (DDoS) Contacting support for an application layer attack 953 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Category: Inbound to AWS • Severity: Choose an appropriate option When discussing with our representative, explain that you're an AWS Shield Advanced customer experiencing a possible DDoS attack. Our representative will direct your call to the appropriate DDoS experts. If you open a case with the AWS Support Center using the Distributed Denial of Service (DDoS) service type, you can speak directly with a DDoS expert by chat or telephone. DDoS support engineers can help you identify attacks, recommend improvements to your AWS architecture, and provide guidance in the use of AWS services for DDoS attack mitigation. For application layer attacks, the SRT can help you analyze the suspicious activity. If you have automatic mitigation enabled for your resource, the SRT can review the mitigations that Shield Advanced is automatically placing against the attack. In any case, the SRT can assist you to review and mitigate the issue. Mitigations that the SRT recommends often require the SRT to create or update AWS WAF web access control lists (web ACLs) in your account. The SRT will need your permission to do this work. Important We recommend that as part of enabling AWS Shield Advanced, you follow the steps in Granting access for the SRT to proactively provide the SRT with the permissions that they need to assist you during an attack. Providing permission ahead of time helps to prevent any delays in the event of an actual attack. The SRT helps you triage the DDoS attack to identify attack signatures and patterns. With your consent, the SRT creates and deploys AWS WAF rules to mitigate the attack. You can also contact the SRT before or during a possible attack to review mitigations and to develop and deploy custom mitigations. For example, if you're running a web application and need only ports 80 and 443 open, you can work with the SRT to preconﬁgure a web ACL to "allow" only ports 80 and 443. You authorize and contact the SRT at the account level. That is, if you use Shield Advanced within a Firewall Manager Shield Advanced policy, the account owner, not the Firewall Manager administrator, must contact the SRT for support. The Firewall Manager administrator can contact the SRT only for accounts that they own. Contacting support for an application layer attack 954 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Manually mitigating an application layer DDoS attack This page provides instructions for manually mitigating an application layer DDoS attack. If you determine that the activity in the events page for your resource represents a DDoS attack, you can create your own AWS WAF rules in your web ACL to mitigate the attack. This is the only option available if you aren't a Shield Advanced customer. AWS WAF is included with AWS Shield Advanced at no additional cost. For information about creating rules in your web ACL, see Using web ACLs in AWS WAF. If you use AWS Firewall Manager, you can add your AWS WAF rules to a Firewall Manager AWS WAF policy. To manually mitigate a potential application layer DDoS attack 1. Create rule statements in your web ACL with criteria that matches the unusual behavior. To start with, conﬁgure them to count matching requests. For information about conﬁguring your web ACL and rule statements, see Using web ACLs with rules and rule groups in AWS WAF and Testing and tuning your AWS WAF protections. Note Always test your rules ﬁrst by initially using the rule action Count instead of Block. After you're comfortable that your new rules are identifying the correct requests, you can modify them to block the requests. 2. Monitor the request counts to determine whether you want to block the matching requests. If the volume of requests continues to be unusually high and you're conﬁdent that your rules are capturing the requests that are causing the high volume, change the rules in your web ACL to block the requests. 3. Continue monitoring the
waf-dg-348	waf-dg.pdf	348	and Testing and tuning your AWS WAF protections. Note Always test your rules ﬁrst by initially using the rule action Count instead of Block. After you're comfortable that your new rules are identifying the correct requests, you can modify them to block the requests. 2. Monitor the request counts to determine whether you want to block the matching requests. If the volume of requests continues to be unusually high and you're conﬁdent that your rules are capturing the requests that are causing the high volume, change the rules in your web ACL to block the requests. 3. Continue monitoring the events page to ensure that your traﬃc is being handled as you want it to be. AWS provides preconﬁgured templates to get you started quickly. The templates include a set of AWS WAF rules that you can customize and use to block common web-based attacks. For more information, see AWS WAF Security Automations. Manually mitigating an application layer attack 955 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Requesting a credit in AWS Shield Advanced after an attack If you're subscribed to AWS Shield Advanced and you experience a DDoS attack that increases utilization of a Shield Advanced protected resource, you can request a Shield Advanced service credit for charges related to the increased utilization, to the extent that it is not mitigated by Shield Advanced. Note You can apply any credits received through this process only to Shield Advanced usage. Shield Advanced credits are not available for use with other services. Credits are available only for the following types of charges: • Shield Advanced data transfer out • Amazon CloudFront HTTP/HTTPS requests • CloudFront data transfer out • Amazon Route 53 queries • AWS Global Accelerator standard accelerator data transfer • Load balancer capacity units for Application Load Balancer • Instance costs for protected Amazon Elastic Compute Cloud (Amazon EC2) instances that were created by an auto-scaling policy in response to the attack Prerequisites for requesting a credit To be eligible to receive a credit, before the attack began, you must have done the following: • You must have added Shield Advanced protection to the resources for which you want to request a credit. Protected resources added during an attack are not eligible for cost protection. Note Enabling Shield Advanced on your AWS account does not automatically enable Shield Advanced protection for individual resources. Requesting a credit after an attack 956 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide For more information about how to protect AWS resources using Shield Advanced, see Adding AWS Shield Advanced protection to AWS resources. • For applicable CloudFront and Application Load Balancer protected resources, you must have associated an AWS WAF web ACL and implemented a rate-based rule in the web ACL in Block mode. For information about AWS WAF rate-based rules, see Using rate-based rule statements in AWS WAF. For information about how to associate web ACLs with AWS resources, see Using web ACLs in AWS WAF. • You must have implemented the appropriate best practices in AWS Best Practices for DDoS Resiliency to conﬁgure your application in a way that minimizes cost during a DDoS attack. How to apply for a credit To be eligible for a credit, you must submit your credit request within the 15 day period immediately following the billing month in which the attack occurred. To apply for a credit, submit a billing case through the AWS Support Center. Include the following in your request: • The words "DDoS Concession" in the subject line • The dates and times of each event or availability interruption for which you're requesting a credit • The AWS services and speciﬁc resources that were aﬀected After you submit a request, the AWS Shield Response Team (SRT) will validate whether a DDoS attack occurred and, if so, whether any protected resources scaled to absorb the DDoS attack. If AWS determines that protected resources scaled to absorb the DDoS attack, AWS will issue a credit for that portion of traﬃc that AWS determines was caused by the DDoS attack. Credits are valid for 12 months. Security in your use of the AWS Shield service This section explains how the shared responsibility model applies to AWS Shield. Cloud security at AWS is the highest priority. As an AWS customer, you beneﬁt from a data center and network architecture that is built to meet the requirements of the most security-sensitive organizations. Security in your use of the Shield service 957 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note This section provides standard AWS security guidance for your use of the AWS Shield service and its AWS resources, such as Shield Advanced protections. For information about protecting your AWS resources using Shield and Shield Advanced, see
waf-dg-349	waf-dg.pdf	349	how the shared responsibility model applies to AWS Shield. Cloud security at AWS is the highest priority. As an AWS customer, you beneﬁt from a data center and network architecture that is built to meet the requirements of the most security-sensitive organizations. Security in your use of the Shield service 957 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note This section provides standard AWS security guidance for your use of the AWS Shield service and its AWS resources, such as Shield Advanced protections. For information about protecting your AWS resources using Shield and Shield Advanced, see the rest of the AWS Shield guide. Security is a shared responsibility between AWS and you. The shared responsibility model describes this as security of the cloud and security in the cloud: • Security of the cloud – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. AWS also provides you with services that you can use securely. The eﬀectiveness of our security is regularly tested and veriﬁed by third-party auditors as part of the AWS compliance programs. To learn about the compliance programs that apply to Shield, see AWS Services in Scope by Compliance Program. • Security in the cloud – Your responsibility is determined by the AWS service that you use. You are also responsible for other factors including the sensitivity of your data, your organization’s requirements, and applicable laws and regulations. This documentation helps you understand how to apply the shared responsibility model when using Shield. The following topics show you how to conﬁgure Shield to meet your security and compliance objectives. You also learn how to use other AWS services that help you to monitor and secure your Shield resources. Topics • Protecting your data in Shield • Using IAM with AWS Shield • Logging and monitoring in Shield • Validating compliance in Shield • Building for resilience in Shield • Infrastructure security in AWS Shield Security in your use of the Shield service 958 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Protecting your data in Shield This section explains how the AWS shared responsibility model applies to data protection in Shield. The AWS shared responsibility model applies to data protection in AWS Shield. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security conﬁguration and management tasks for the AWS services that you use. For more information about data privacy, see the Data Privacy FAQ. For information about data protection in Europe, see the AWS Shared Responsibility Model and GDPR blog post on the AWS Security Blog. For data protection purposes, we recommend that you protect AWS account credentials and set up individual users with AWS IAM Identity Center or AWS Identity and Access Management (IAM). That way, each user is given only the permissions necessary to fulﬁll their job duties. We also recommend that you secure your data in the following ways: • Use multi-factor authentication (MFA) with each account. • Use SSL/TLS to communicate with AWS resources. We require TLS 1.2 and recommend TLS 1.3. • Set up API and user activity logging with AWS CloudTrail. For information about using CloudTrail trails to capture AWS activities, see Working with CloudTrail trails in the AWS CloudTrail User Guide. • Use AWS encryption solutions, along with all default security controls within AWS services. • Use advanced managed security services such as Amazon Macie, which assists in discovering and securing sensitive data that is stored in Amazon S3. • If you require FIPS 140-3 validated cryptographic modules when accessing AWS through a command line interface or an API, use a FIPS endpoint. For more information about the available FIPS endpoints, see Federal Information Processing Standard (FIPS) 140-3. We strongly recommend that you never put conﬁdential or sensitive information, such as your customers' email addresses, into tags or free-form text ﬁelds such as a Name ﬁeld. This includes when you work with Shield or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form text ﬁelds used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server. Protecting your data 959 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Shield entities—such as protections—are encrypted at rest, except in certain Regions where encryption is not available, including China (Beijing) and China (Ningxia). Unique encryption keys are used for each Region. Using IAM with
waf-dg-350	waf-dg.pdf	350	SDKs. Any data that you enter into tags or free-form text ﬁelds used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server. Protecting your data 959 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Shield entities—such as protections—are encrypted at rest, except in certain Regions where encryption is not available, including China (Beijing) and China (Ningxia). Unique encryption keys are used for each Region. Using IAM with AWS Shield This section explains how to use IAM with AWS Shield. AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be authenticated (signed in) and authorized (have permissions) to use Shield resources. IAM is an AWS service that you can use with no additional charge. Topics • Audience • Authenticating with identities • Managing access using policies • How AWS Shield works with IAM • Identity-based policy examples for AWS Shield • AWS managed policies for AWS Shield • Troubleshooting AWS Shield identity and access • Using service-linked roles for Shield Advanced Audience How you use AWS Identity and Access Management (IAM) diﬀers, depending on the work that you do in Shield. Service user – If you use the Shield service to do your job, then your administrator provides you with the credentials and permissions that you need. As you use more Shield features to do your work, you might need additional permissions. Understanding how access is managed can help you request the right permissions from your administrator. If you cannot access a feature in Shield, see Troubleshooting AWS Shield identity and access. Service administrator – If you're in charge of Shield resources at your company, you probably have full access to Shield. It's your job to determine which Shield features and resources your service users should access. You must then submit requests to your IAM administrator to change Using IAM with Shield 960 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide the permissions of your service users. Review the information on this page to understand the basic concepts of IAM. To learn more about how your company can use IAM with Shield, see How AWS Shield works with IAM. IAM administrator – If you're an IAM administrator, you might want to learn details about how you can write policies to manage access to Shield. To view example Shield identity-based policies that you can use in IAM, see Identity-based policy examples for AWS Shield. Authenticating with identities Authentication is how you sign in to AWS using your identity credentials. You must be authenticated (signed in to AWS) as the AWS account root user, as an IAM user, or by assuming an IAM role. You can sign in to AWS as a federated identity by using credentials provided through an identity source. AWS IAM Identity Center (IAM Identity Center) users, your company's single sign-on authentication, and your Google or Facebook credentials are examples of federated identities. When you sign in as a federated identity, your administrator previously set up identity federation using IAM roles. When you access AWS by using federation, you are indirectly assuming a role. Depending on the type of user you are, you can sign in to the AWS Management Console or the AWS access portal. For more information about signing in to AWS, see How to sign in to your AWS account in the AWS Sign-In User Guide. If you access AWS programmatically, AWS provides a software development kit (SDK) and a command line interface (CLI) to cryptographically sign your requests by using your credentials. If you don't use AWS tools, you must sign requests yourself. For more information about using the recommended method to sign requests yourself, see AWS Signature Version 4 for API requests in the IAM User Guide. Regardless of the authentication method that you use, you might be required to provide additional security information. For example, AWS recommends that you use multi-factor authentication (MFA) to increase the security of your account. To learn more, see Multi-factor authentication in the AWS IAM Identity Center User Guide and AWS Multi-factor authentication in IAM in the IAM User Guide. AWS account root user When you create an AWS account, you begin with one sign-in identity that has complete access to all AWS services and resources in the account. This identity is called the AWS account root user and Using IAM with Shield 961 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide is accessed by signing in with the email address and password that you used to create the account. We strongly recommend that
waf-dg-351	waf-dg.pdf	351	more, see Multi-factor authentication in the AWS IAM Identity Center User Guide and AWS Multi-factor authentication in IAM in the IAM User Guide. AWS account root user When you create an AWS account, you begin with one sign-in identity that has complete access to all AWS services and resources in the account. This identity is called the AWS account root user and Using IAM with Shield 961 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide is accessed by signing in with the email address and password that you used to create the account. We strongly recommend that you don't use the root user for your everyday tasks. Safeguard your root user credentials and use them to perform the tasks that only the root user can perform. For the complete list of tasks that require you to sign in as the root user, see Tasks that require root user credentials in the IAM User Guide. Federated identity As a best practice, require human users, including users that require administrator access, to use federation with an identity provider to access AWS services by using temporary credentials. A federated identity is a user from your enterprise user directory, a web identity provider, the AWS Directory Service, the Identity Center directory, or any user that accesses AWS services by using credentials provided through an identity source. When federated identities access AWS accounts, they assume roles, and the roles provide temporary credentials. For centralized access management, we recommend that you use AWS IAM Identity Center. You can create users and groups in IAM Identity Center, or you can connect and synchronize to a set of users and groups in your own identity source for use across all your AWS accounts and applications. For information about IAM Identity Center, see What is IAM Identity Center? in the AWS IAM Identity Center User Guide. IAM users and groups An IAM user is an identity within your AWS account that has speciﬁc permissions for a single person or application. Where possible, we recommend relying on temporary credentials instead of creating IAM users who have long-term credentials such as passwords and access keys. However, if you have speciﬁc use cases that require long-term credentials with IAM users, we recommend that you rotate access keys. For more information, see Rotate access keys regularly for use cases that require long- term credentials in the IAM User Guide. An IAM group is an identity that speciﬁes a collection of IAM users. You can't sign in as a group. You can use groups to specify permissions for multiple users at a time. Groups make permissions easier to manage for large sets of users. For example, you could have a group named IAMAdmins and give that group permissions to administer IAM resources. Users are diﬀerent from roles. A user is uniquely associated with one person or application, but a role is intended to be assumable by anyone who needs it. Users have permanent long-term credentials, but roles provide temporary credentials. To learn more, see Use cases for IAM users in the IAM User Guide. Using IAM with Shield 962 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide IAM roles An IAM role is an identity within your AWS account that has speciﬁc permissions. It is similar to an IAM user, but is not associated with a speciﬁc person. To temporarily assume an IAM role in the AWS Management Console, you can switch from a user to an IAM role (console). You can assume a role by calling an AWS CLI or AWS API operation or by using a custom URL. For more information about methods for using roles, see Methods to assume a role in the IAM User Guide. IAM roles with temporary credentials are useful in the following situations: • Federated user access – To assign permissions to a federated identity, you create a role and deﬁne permissions for the role. When a federated identity authenticates, the identity is associated with the role and is granted the permissions that are deﬁned by the role. For information about roles for federation, see Create a role for a third-party identity provider (federation) in the IAM User Guide. If you use IAM Identity Center, you conﬁgure a permission set. To control what your identities can access after they authenticate, IAM Identity Center correlates the permission set to a role in IAM. For information about permissions sets, see Permission sets in the AWS IAM Identity Center User Guide. • Temporary IAM user permissions – An IAM user or role can assume an IAM role to temporarily take on diﬀerent permissions for a speciﬁc task. • Cross-account access – You can use an IAM role to allow someone (a trusted principal) in a diﬀerent account to access resources in your account. Roles
waf-dg-352	waf-dg.pdf	352	use IAM Identity Center, you conﬁgure a permission set. To control what your identities can access after they authenticate, IAM Identity Center correlates the permission set to a role in IAM. For information about permissions sets, see Permission sets in the AWS IAM Identity Center User Guide. • Temporary IAM user permissions – An IAM user or role can assume an IAM role to temporarily take on diﬀerent permissions for a speciﬁc task. • Cross-account access – You can use an IAM role to allow someone (a trusted principal) in a diﬀerent account to access resources in your account. Roles are the primary way to grant cross- account access. However, with some AWS services, you can attach a policy directly to a resource (instead of using a role as a proxy). To learn the diﬀerence between roles and resource-based policies for cross-account access, see Cross account resource access in IAM in the IAM User Guide. • Cross-service access – Some AWS services use features in other AWS services. For example, when you make a call in a service, it's common for that service to run applications in Amazon EC2 or store objects in Amazon S3. A service might do this using the calling principal's permissions, using a service role, or using a service-linked role. • Forward access sessions (FAS) – When you use an IAM user or role to perform actions in AWS, you are considered a principal. When you use some services, you might perform an action that then initiates another action in a diﬀerent service. FAS uses the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. FAS requests are only made when a service receives a request that requires interactions with other AWS services or resources to complete. In this case, you must have permissions to perform both actions. For policy details when making FAS requests, see Forward access sessions. Using IAM with Shield 963 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Service role – A service role is an IAM role that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see Create a role to delegate permissions to an AWS service in the IAM User Guide. • Service-linked role – A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles. • Applications running on Amazon EC2 – You can use an IAM role to manage temporary credentials for applications that are running on an EC2 instance and making AWS CLI or AWS API requests. This is preferable to storing access keys within the EC2 instance. To assign an AWS role to an EC2 instance and make it available to all of its applications, you create an instance proﬁle that is attached to the instance. An instance proﬁle contains the role and enables programs that are running on the EC2 instance to get temporary credentials. For more information, see Use an IAM role to grant permissions to applications running on Amazon EC2 instances in the IAM User Guide. Managing access using policies You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy is an object in AWS that, when associated with an identity or resource, deﬁnes their permissions. AWS evaluates these policies when a principal (user, root user, or role session) makes a request. Permissions in the policies determine whether the request is allowed or denied. Most policies are stored in AWS as JSON documents. For more information about the structure and contents of JSON policy documents, see Overview of JSON policies in the IAM User Guide. Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions. By default, users and roles have no permissions. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. IAM policies deﬁne permissions for an action regardless of the method that you use to perform the operation. For example, suppose that you have a policy that allows the iam:GetRole action. A user with that policy can get role information from the AWS Management Console, the AWS CLI, or the AWS API. Using IAM with Shield 964 AWS WAF, AWS Firewall Manager,
waf-dg-353	waf-dg.pdf	353	no permissions. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. IAM policies deﬁne permissions for an action regardless of the method that you use to perform the operation. For example, suppose that you have a policy that allows the iam:GetRole action. A user with that policy can get role information from the AWS Management Console, the AWS CLI, or the AWS API. Using IAM with Shield 964 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Identity-based policies Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see Deﬁne custom IAM permissions with customer managed policies in the IAM User Guide. Identity-based policies can be further categorized as inline policies or managed policies. Inline policies are embedded directly into a single user, group, or role. Managed policies are standalone policies that you can attach to multiple users, groups, and roles in your AWS account. Managed policies include AWS managed policies and customer managed policies. To learn how to choose between a managed policy or an inline policy, see Choose between managed policies and inline policies in the IAM User Guide. Resource-based policies Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM role trust policies and Amazon S3 bucket policies. In services that support resource-based policies, service administrators can use them to control access to a speciﬁc resource. For the resource where the policy is attached, the policy deﬁnes what actions a speciﬁed principal can perform on that resource and under what conditions. You must specify a principal in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services. Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy. Access control lists (ACLs) Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format. Amazon S3, AWS WAF, and Amazon VPC are examples of services that support ACLs. To learn more about ACLs, see Access control list (ACL) overview in the Amazon Simple Storage Service Developer Guide. Other policy types AWS supports additional, less-common policy types. These policy types can set the maximum permissions granted to you by the more common policy types. Using IAM with Shield 965 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Permissions boundaries – A permissions boundary is an advanced feature in which you set the maximum permissions that an identity-based policy can grant to an IAM entity (IAM user or role). You can set a permissions boundary for an entity. The resulting permissions are the intersection of an entity's identity-based policies and its permissions boundaries. Resource-based policies that specify the user or role in the Principal ﬁeld are not limited by the permissions boundary. An explicit deny in any of these policies overrides the allow. For more information about permissions boundaries, see Permissions boundaries for IAM entities in the IAM User Guide. • Service control policies (SCPs) – SCPs are JSON policies that specify the maximum permissions for an organization or organizational unit (OU) in AWS Organizations. AWS Organizations is a service for grouping and centrally managing multiple AWS accounts that your business owns. If you enable all features in an organization, then you can apply service control policies (SCPs) to any or all of your accounts. The SCP limits permissions for entities in member accounts, including each AWS account root user. For more information about Organizations and SCPs, see Service control policies in the AWS Organizations User Guide. • Resource control policies (RCPs) – RCPs are JSON policies that you can use to set the maximum available permissions for resources in your accounts without updating the IAM policies attached to each resource that you own. The RCP limits permissions for resources in member accounts and can impact the eﬀective permissions for identities, including the AWS account root user, regardless of whether they belong to your organization. For more information about Organizations and RCPs, including a list of AWS services that support RCPs, see Resource control policies (RCPs) in the AWS Organizations User Guide. • Session policies – Session policies are advanced policies that you pass as a parameter when you programmatically create a temporary session for a role or federated user.
waf-dg-354	waf-dg.pdf	354	your accounts without updating the IAM policies attached to each resource that you own. The RCP limits permissions for resources in member accounts and can impact the eﬀective permissions for identities, including the AWS account root user, regardless of whether they belong to your organization. For more information about Organizations and RCPs, including a list of AWS services that support RCPs, see Resource control policies (RCPs) in the AWS Organizations User Guide. • Session policies – Session policies are advanced policies that you pass as a parameter when you programmatically create a temporary session for a role or federated user. The resulting session's permissions are the intersection of the user or role's identity-based policies and the session policies. Permissions can also come from a resource-based policy. An explicit deny in any of these policies overrides the allow. For more information, see Session policies in the IAM User Guide. Multiple policy types When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see Policy evaluation logic in the IAM User Guide. How AWS Shield works with IAM This section explains how to use the features of IAM with AWS Shield. Using IAM with Shield 966 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Before you use IAM to manage access to Shield, learn what IAM features are available to use with Shield. IAM features you can use with AWS Shield IAM feature Shield support Identity-based policies Resource-based policies Policy actions Policy resources Policy condition keys (service-speciﬁc) ACLs Yes No Yes Yes Yes No ABAC (tags in policies) Partial Temporary credentials Forward access sessions (FAS) Service roles Service-linked roles Yes Yes Yes Yes To get a high-level view of how Shield and other AWS services work with most IAM features, see AWS services that work with IAM in the IAM User Guide. Identity-based policies for Shield This section provides identity-based policy examples for AWS Shield. Supports identity-based policies: Yes Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can Using IAM with Shield 967 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see Deﬁne custom IAM permissions with customer managed policies in the IAM User Guide. With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. You can't specify the principal in an identity-based policy because it applies to the user or role to which it is attached. To learn about all of the elements that you can use in a JSON policy, see IAM JSON policy elements reference in the IAM User Guide. To view examples of Shield identity-based policies, see Identity-based policy examples for AWS Shield. Resource-based policies within Shield Supports resource-based policies: No Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM role trust policies and Amazon S3 bucket policies. In services that support resource-based policies, service administrators can use them to control access to a speciﬁc resource. For the resource where the policy is attached, the policy deﬁnes what actions a speciﬁed principal can perform on that resource and under what conditions. You must specify a principal in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services. To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. Adding a cross-account principal to a resource- based policy is only half of establishing the trust relationship. When the principal and the resource are in diﬀerent AWS accounts, an IAM administrator in the trusted account must also grant the principal entity (user or role) permission to access the resource. They grant permission by attaching an identity-based policy to the entity. However, if a resource-based policy grants access to a principal in the same account, no additional identity-based policy is required. For more information, see Cross account resource access in IAM in the IAM User Guide. Policy actions for Shield Supports policy actions: Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions. Using IAM with Shield 968 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide The Action element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Policy actions usually
waf-dg-355	waf-dg.pdf	355	the same account, no additional identity-based policy is required. For more information, see Cross account resource access in IAM in the IAM User Guide. Policy actions for Shield Supports policy actions: Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions. Using IAM with Shield 968 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide The Action element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Policy actions usually have the same name as the associated AWS API operation. There are some exceptions, such as permission-only actions that don't have a matching API operation. There are also some operations that require multiple actions in a policy. These additional actions are called dependent actions. Include actions in a policy to grant permissions to perform the associated operation. To see a list of Shield actions, see Actions deﬁned by AWS Shield in the Service Authorization Reference. Policy actions in Shield use the following preﬁx before the action: shield To specify multiple actions in a single statement, separate them with commas. "Action": [ "shield:action1", "shield:action2" ] You can specify multiple actions using wildcards (). For example, to specify all actions in Shield that begin with List, include the following action: "Action": "shield:List" To view examples of Shield identity-based policies, see Identity-based policy examples for AWS Shield. Policy resources for Shield Supports policy resources: Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions. The Resource JSON policy element speciﬁes the object or objects to which the action applies. Statements must include either a Resource or a NotResource element. As a best practice, Using IAM with Shield 969 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide specify a resource using its Amazon Resource Name (ARN). You can do this for actions that support a speciﬁc resource type, known as resource-level permissions. For actions that don't support resource-level permissions, such as listing operations, use a wildcard () to indicate that the statement applies to all resources. "Resource": "" To see the list of Shield resource types and their ARNs, see Resources deﬁned by AWS Shield in the Service Authorization Reference. To learn with which actions you can specify the ARN of each resource, see Actions deﬁned by AWS Shield. To allow or deny access to a subset of Shield resources, include the ARN of the resource in the resource element of your policy. In AWS Shield, the resources are protections and attacks. These resources have unique Amazon Resource Names (ARNs) associated with them, as shown in the following table. Name in AWS Shield Name in AWS Shield SDK/ ARN Format Console CLI Event or attack AttackDet arn:aws:s ail hield:: account:attack/ID Protection Protection arn:aws:s hield:: account:protection/ ID To allow or deny access to a subset of Shield resources, include the ARN of the resource in the resource element of your policy. The ARNs for Shield have the following format: arn:partition:shield::account:resource/ID Replace the account, resource, and ID variables with valid values. Valid values can be the following: • account: The ID of your AWS account. You must specify a value. • resource: The type of Shield resource, either attack or protection. • ID: The ID of the Shield resource, or a wildcard () to indicate all resources of the speciﬁed type that are associated with the speciﬁed AWS account. Using IAM with Shield 970 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide For example, the following ARN speciﬁes all protections for the account 111122223333: arn:aws:shield::111122223333:protection/ The ARNs of Shield resources have the following format: arn:partition:shield:region:account-id:scope/resource-type/resource-name/resource-id For general information about ARN speciﬁcations, see Amazon Resource Names (ARNs) in the Amazon Web Services General Reference. The following lists requirements that are speciﬁc to the ARNs of wafv2 resources: • region: For Shield resources that you use to protect Amazon CloudFront distributions, set this to us-east-1. Otherwise, set this to the Region you're using with your protected regional resources. • scope: Set the scope to global for use with an Amazon CloudFront distribution or regional for use with any of the regional resources that AWS WAF supports. The regional resources are an Amazon API Gateway REST API, an Application Load Balancer, an AWS AppSync GraphQL API, an Amazon Cognito user pool, an AWS App Runner service, and an AWS Veriﬁed Access instance. • resource-type: Specify one of the following values: attack for events or attacks, protection for protections. • resource-name: Specify the name that you gave the Shield resource, or specify a wildcard (*) to indicate all resources that satisfy the other speciﬁcations in the
waf-dg-356	waf-dg.pdf	356	global for use with an Amazon CloudFront distribution or regional for use with any of the regional resources that AWS WAF supports. The regional resources are an Amazon API Gateway REST API, an Application Load Balancer, an AWS AppSync GraphQL API, an Amazon Cognito user pool, an AWS App Runner service, and an AWS Veriﬁed Access instance. • resource-type: Specify one of the following values: attack for events or attacks, protection for protections. • resource-name: Specify the name that you gave the Shield resource, or specify a wildcard () to indicate all resources that satisfy the other speciﬁcations in the ARN. You must either specify the resource name and resource ID or specify a wildcard for both. • resource-id: Specify the ID of the Shield resource, or specify a wildcard () to indicate all resources that satisfy the other speciﬁcations in the ARN. You must either specify the resource name and resource ID or specify a wildcard for both. For example, the following ARN speciﬁes all web ACLs with regional scope for the account 111122223333 in Region us-west-1: arn:aws:wafv2:us-west-1:111122223333:regional/webacl// The following ARN speciﬁes the rule group named MyIPManagementRuleGroup with global scope for the account 111122223333 in Region us-east-1: Using IAM with Shield 971 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide arn:aws:wafv2:us-east-1:111122223333:global/rulegroup/MyIPManagementRuleGroup/1111aaaa- bbbb-cccc-dddd-example-id To view examples of Shield identity-based policies, see Identity-based policy examples for AWS Shield. Policy condition keys for Shield Supports service-speciﬁc policy condition keys: Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions. The Condition element (or Condition block) lets you specify conditions in which a statement is in eﬀect. The Condition element is optional. You can create conditional expressions that use condition operators, such as equals or less than, to match the condition in the policy with values in the request. If you specify multiple Condition elements in a statement, or multiple keys in a single Condition element, AWS evaluates them using a logical AND operation. If you specify multiple values for a single condition key, AWS evaluates the condition using a logical OR operation. All of the conditions must be met before the statement's permissions are granted. You can also use placeholder variables when you specify conditions. For example, you can grant an IAM user permission to access a resource only if it is tagged with their IAM user name. For more information, see IAM policy elements: variables and tags in the IAM User Guide. AWS supports global condition keys and service-speciﬁc condition keys. To see all AWS global condition keys, see AWS global condition context keys in the IAM User Guide. To see a list of Shield condition keys, see Condition keys for AWS Shield in the Service Authorization Reference. To learn with which actions and resources you can use a condition key, see Actions deﬁned by AWS Shield. To view examples of Shield identity-based policies, see Identity-based policy examples for AWS Shield. ACLs in Shield Supports ACLs: No Using IAM with Shield 972 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format. ABAC with Shield Supports ABAC (tags in policies): Partial Attribute-based access control (ABAC) is an authorization strategy that deﬁnes permissions based on attributes. In AWS, these attributes are called tags. You can attach tags to IAM entities (users or roles) and to many AWS resources. Tagging entities and resources is the ﬁrst step of ABAC. Then you design ABAC policies to allow operations when the principal's tag matches the tag on the resource that they are trying to access. ABAC is helpful in environments that are growing rapidly and helps with situations where policy management becomes cumbersome. To control access based on tags, you provide tag information in the condition element of a policy using the aws:ResourceTag/key-name, aws:RequestTag/key-name, or aws:TagKeys condition keys. If a service supports all three condition keys for every resource type, then the value is Yes for the service. If a service supports all three condition keys for only some resource types, then the value is Partial. For more information about ABAC, see Deﬁne permissions with ABAC authorization in the IAM User Guide. To view a tutorial with steps for setting up ABAC, see Use attribute-based access control (ABAC) in the IAM User Guide. Using temporary credentials with Shield Supports temporary credentials: Yes Some AWS services don't work when you sign in using temporary credentials. For additional information, including which AWS services work with temporary credentials, see AWS services that work with IAM in the IAM User Guide. You are
waf-dg-357	waf-dg.pdf	357	a service supports all three condition keys for only some resource types, then the value is Partial. For more information about ABAC, see Deﬁne permissions with ABAC authorization in the IAM User Guide. To view a tutorial with steps for setting up ABAC, see Use attribute-based access control (ABAC) in the IAM User Guide. Using temporary credentials with Shield Supports temporary credentials: Yes Some AWS services don't work when you sign in using temporary credentials. For additional information, including which AWS services work with temporary credentials, see AWS services that work with IAM in the IAM User Guide. You are using temporary credentials if you sign in to the AWS Management Console using any method except a user name and password. For example, when you access AWS using your company's single sign-on (SSO) link, that process automatically creates temporary credentials. You also automatically create temporary credentials when you sign in to the console as a user and then Using IAM with Shield 973 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide switch roles. For more information about switching roles, see Switch from a user to an IAM role (console) in the IAM User Guide. You can manually create temporary credentials using the AWS CLI or AWS API. You can then use those temporary credentials to access AWS. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see Temporary security credentials in IAM. Forward access sessions for Shield Supports forward access sessions (FAS): Yes When you use an IAM user or role to perform actions in AWS, you are considered a principal. When you use some services, you might perform an action that then initiates another action in a diﬀerent service. FAS uses the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. FAS requests are only made when a service receives a request that requires interactions with other AWS services or resources to complete. In this case, you must have permissions to perform both actions. For policy details when making FAS requests, see Forward access sessions. Service roles for Shield Supports service roles: Yes A service role is an IAM role that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see Create a role to delegate permissions to an AWS service in the IAM User Guide. Warning Changing the permissions for a service role might break Shield functionality. Edit service roles only when Shield provides guidance to do so. Service-linked roles for Shield Supports service-linked roles: Yes A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS Using IAM with Shield 974 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles. For details about creating or managing Shield service-linked roles, see Using service-linked roles for Shield Advanced. Identity-based policy examples for AWS Shield By default, users and roles don't have permission to create or modify Shield resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. To learn how to create an IAM identity-based policy by using these example JSON policy documents, see Create IAM policies (console) in the IAM User Guide. For details about actions and resource types deﬁned by Shield, including the format of the ARNs for each of the resource types, see Actions, resources, and condition keys for AWS Shield in the Service Authorization Reference. Topics • Policy best practices • Using the Shield console • Allow users to view their own permissions • Grant read access to your Shield Advanced protections • Grant read-only access to Shield, CloudFront, and CloudWatch • Grant full access to Shield, CloudFront, and CloudWatch Policy best practices Identity-based policies determine whether someone can create, access, or delete Shield resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: • Get started with AWS managed policies and move toward least-privilege permissions – To get started granting permissions to your users and workloads, use the AWS managed policies that grant permissions for many common use cases. They are available in your AWS account. We
waf-dg-358	waf-dg.pdf	358	Grant read-only access to Shield, CloudFront, and CloudWatch • Grant full access to Shield, CloudFront, and CloudWatch Policy best practices Identity-based policies determine whether someone can create, access, or delete Shield resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: • Get started with AWS managed policies and move toward least-privilege permissions – To get started granting permissions to your users and workloads, use the AWS managed policies that grant permissions for many common use cases. They are available in your AWS account. We Using IAM with Shield 975 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide recommend that you reduce permissions further by deﬁning AWS customer managed policies that are speciﬁc to your use cases. For more information, see AWS managed policies or AWS managed policies for job functions in the IAM User Guide. • Apply least-privilege permissions – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by deﬁning the actions that can be taken on speciﬁc resources under speciﬁc conditions, also known as least-privilege permissions. For more information about using IAM to apply permissions, see Policies and permissions in IAM in the IAM User Guide. • Use conditions in IAM policies to further restrict access – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a speciﬁc AWS service, such as AWS CloudFormation. For more information, see IAM JSON policy elements: Condition in the IAM User Guide. • Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see Validate policies with IAM Access Analyzer in the IAM User Guide. • Require multi-factor authentication (MFA) – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see Secure API access with MFA in the IAM User Guide. For more information about best practices in IAM, see Security best practices in IAM in the IAM User Guide. Using the Shield console To access the AWS Shield console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the Shield resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy. You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they're trying to perform. Using IAM with Shield 976 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Users who can access and use the AWS console can also access the AWS Shield console. No additional permissions are required. Allow users to view their own permissions This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API. { "Version": "2012-10-17", "Statement": [ { "Sid": "ViewOwnUserInfo", "Effect": "Allow", "Action": [ "iam:GetUserPolicy", "iam:ListGroupsForUser", "iam:ListAttachedUserPolicies", "iam:ListUserPolicies", "iam:GetUser" ], "Resource": ["arn:aws:iam:::user/${aws:username}"] }, { "Sid": "NavigateInConsole", "Effect": "Allow", "Action": [ "iam:GetGroupPolicy", "iam:GetPolicyVersion", "iam:GetPolicy", "iam:ListAttachedGroupPolicies", "iam:ListGroupPolicies", "iam:ListPolicyVersions", "iam:ListPolicies", "iam:ListUsers" ], "Resource": "" } ] } Using IAM with Shield 977 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Grant read access to your Shield Advanced protections AWS Shield allows cross-account resource access, but it doesn't allow you to create cross-account resource protections. You can only create protections for resources from within the account that owns those resources. The following is an example policy that grants permissions for the shield:ListProtections action on all resources. Shield doesn't support identifying speciﬁc resources using the resource ARNs (also referred to as resource-level permissions) for some of the API actions, so you specify a wildcard character (*). This only permits access to the resources that you can retrieve through
waf-dg-359	waf-dg.pdf	359	Shield Advanced Developer Guide Grant read access to your Shield Advanced protections AWS Shield allows cross-account resource access, but it doesn't allow you to create cross-account resource protections. You can only create protections for resources from within the account that owns those resources. The following is an example policy that grants permissions for the shield:ListProtections action on all resources. Shield doesn't support identifying speciﬁc resources using the resource ARNs (also referred to as resource-level permissions) for some of the API actions, so you specify a wildcard character (). This only permits access to the resources that you can retrieve through the action ListProtections. { "Version": "2016-06-02", "Statement": [ { "Sid": "ListProtections", "Effect": "Allow", "Action": [ "shield:ListProtections" ], "Resource": "" } ] } Grant read-only access to Shield, CloudFront, and CloudWatch The following policy grants users read-only access to Shield and associated resources, including Amazon CloudFront resources, and Amazon CloudWatch metrics. It's useful for users who need permission to view the settings in Shield protections and attacks and to monitor metrics in CloudWatch. These users can't create, update, or delete Shield resources. { "Version": "2012-10-17", "Statement": [ { "Sid": "ProtectedResourcesReadAccess", "Effect": "Allow", "Action": [ "cloudfront:List", "elasticloadbalancing:List", Using IAM with Shield 978 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide "route53:List", "cloudfront:Describe", "elasticloadbalancing:Describe", "route53:Describe", "cloudwatch:Describe", "cloudwatch:Get", "cloudwatch:List", "cloudfront:GetDistribution", "globalaccelerator:ListAccelerators", "globalaccelerator:DescribeAccelerator" ], "Resource": [ "arn:aws:elasticloadbalancing:::", "arn:aws:cloudfront:::", "arn:aws:route53:::hostedzone/", "arn:aws:cloudwatch::::", "arn:aws:globalaccelerator:::" ] }, { "Sid": "ShieldReadOnly", "Effect": "Allow", "Action": [ "shield:List", "shield:Describe", "shield:Get" ], "Resource": "" } ] } Grant full access to Shield, CloudFront, and CloudWatch The following policy lets users perform any Shield operation, perform any operation on CloudFront web distributions, and monitor metrics and a sample of requests in CloudWatch. It's useful for users who are Shield administrators. { "Version": "2012-10-17", "Statement": [ { "Sid": "ProtectedResourcesReadAccess", Using IAM with Shield 979 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide "Effect": "Allow", "Action": [ "cloudfront:List", "elasticloadbalancing:List", "route53:List", "cloudfront:Describe", "elasticloadbalancing:Describe", "route53:Describe", "cloudwatch:Describe", "cloudwatch:Get", "cloudwatch:List", "cloudfront:GetDistribution", "globalaccelerator:ListAccelerators", "globalaccelerator:DescribeAccelerator" ], "Resource": [ "arn:aws:elasticloadbalancing:::", "arn:aws:cloudfront:::", "arn:aws:route53:::hostedzone/", "arn:aws:cloudwatch::::", "arn:aws:globalaccelerator:::" ] }, { "Sid": "ShieldFullAccess", "Effect": "Allow", "Action": [ "shield:" ], "Resource": "" } ] } We strongly recommend that you conﬁgure multi-factor authentication (MFA) for users who have administrative permissions. For more information, see Using Multi-Factor Authentication (MFA) Devices with AWS in the IAM User Guide. Using IAM with Shield 980 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide AWS managed policies for AWS Shield An AWS managed policy is a standalone policy that is created and administered by AWS. AWS managed policies are designed to provide permissions for many common use cases so that you can start assigning permissions to users, groups, and roles. Keep in mind that AWS managed policies might not grant least-privilege permissions for your speciﬁc use cases because they're available for all AWS customers to use. We recommend that you reduce permissions further by deﬁning customer managed policies that are speciﬁc to your use cases. You cannot change the permissions deﬁned in AWS managed policies. If AWS updates the permissions deﬁned in an AWS managed policy, the update aﬀects all principal identities (users, groups, and roles) that the policy is attached to. AWS is most likely to update an AWS managed policy when a new AWS service is launched or new API operations become available for existing services. For more information, see AWS managed policies in the IAM User Guide. AWS managed policy: AWSShieldDRTAccessPolicy This section explains how to use AWS managed policies for Shield. AWS Shield uses this managed policy when you grant permission to the Shield Response Team (SRT) to act on your behalf. This policy gives the SRT limited access to your AWS account, to assist with DDoS attack mitigation during high-severity events. This policy allows the SRT to manage your AWS WAF rules and Shield Advanced protections and to access your AWS WAF logs. For information about granting permission to the SRT to operate on your behalf, see Granting access for the SRT. For details about this policy, see AWSShieldDRTAccessPolicy in the IAM console. AWS managed policy: AWSShieldServiceRolePolicy Shield Advanced uses this managed policy when you enable automatic application layer DDoS mitigation, to set the permissions it needs to manage resources for your account. This policy allows Shield Advanced to create and apply AWS WAF rules and rule groups in the web ACLs that you've associated with your protected resources, to automatically respond to DDoS attacks. Using IAM with Shield 981 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide You can't attach AWSShieldServiceRolePolicy to your IAM entities. Shield attaches this policy to the service-linked role AWSServiceRoleForAWSShield to allow Shield to perform actions on your behalf. Shield Advanced enables the use of this policy when you enable automatic application layer DDoS mitigation. For more information about the use
waf-dg-360	waf-dg.pdf	360	resources for your account. This policy allows Shield Advanced to create and apply AWS WAF rules and rule groups in the web ACLs that you've associated with your protected resources, to automatically respond to DDoS attacks. Using IAM with Shield 981 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide You can't attach AWSShieldServiceRolePolicy to your IAM entities. Shield attaches this policy to the service-linked role AWSServiceRoleForAWSShield to allow Shield to perform actions on your behalf. Shield Advanced enables the use of this policy when you enable automatic application layer DDoS mitigation. For more information about the use for this policy, see Automating application layer DDoS mitigation with Shield Advanced . For information about the service-linked role AWSServiceRoleForAWSShield that uses this policy, see Using service-linked roles for Shield Advanced For details about this policy, see AWSShieldServiceRolePolicy in the IAM console. Shield updates to AWS managed policies View details about updates to AWS managed policies for Shield since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the Shield document history page at Document history. Policy Description of change Date December 1, 2021 Added this policy to provide Shield Advanced with the permissions required for the automatic applicati on layer DDoS mitigation functionality. For informati on about this feature, see Automating application layer DDoS mitigation with Shield Advanced . AWSShieldServiceRo lePolicy This policy allows Shield to access and manage AWS resources in order to automatically respond to application layer DDoS attacks on your behalf. Details in IAM console: AWSShieldServiceRolePolicy The service-linked role AWSServiceRoleForA WSShield uses this policy. For information, see Using Using IAM with Shield 982 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Policy Description of change Date service-linked roles for Shield Advanced. Shield started tracking changes Shield started tracking changes for its AWS managed March 3, 2021 policies. Troubleshooting AWS Shield identity and access Use the following information to help you diagnose and ﬁx common issues that you might encounter when working with Shield and IAM. Topics • I am not authorized to perform an action in Shield • I am not authorized to perform iam:PassRole • I want to allow people outside of my AWS account to access my Shield resources I am not authorized to perform an action in Shield If you receive an error that you're not authorized to perform an action, your policies must be updated to allow you to perform the action. The following example error occurs when the mateojackson IAM user tries to use the console to view details about a ﬁctional my-example-widget resource but doesn't have the ﬁctional shield:GetWidget permissions. User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: shield:GetWidget on resource: my-example-widget In this case, the policy for the mateojackson user must be updated to allow access to the my- example-widget resource by using the shield:GetWidget action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. Using IAM with Shield 983 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide I am not authorized to perform iam:PassRole If you receive an error that you're not authorized to perform the iam:PassRole action, your policies must be updated to allow you to pass a role to Shield. Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service. The following example error occurs when an IAM user named marymajor tries to use the console to perform an action in Shield. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service. User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole In this case, Mary's policies must be updated to allow her to perform the iam:PassRole action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. I want to allow people outside of my AWS account to access my Shield resources You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources. To learn more, consult the following: • To learn whether Shield supports these features, see How AWS Shield works with IAM. • To learn how to provide access to your resources across AWS accounts that you own, see Providing access to an IAM user in another AWS account
waf-dg-361	waf-dg.pdf	361	a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources. To learn more, consult the following: • To learn whether Shield supports these features, see How AWS Shield works with IAM. • To learn how to provide access to your resources across AWS accounts that you own, see Providing access to an IAM user in another AWS account that you own in the IAM User Guide. • To learn how to provide access to your resources to third-party AWS accounts, see Providing access to AWS accounts owned by third parties in the IAM User Guide. • To learn how to provide access through identity federation, see Providing access to externally authenticated users (identity federation) in the IAM User Guide. • To learn the diﬀerence between using roles and resource-based policies for cross-account access, see How IAM roles diﬀer from resource-based policies in the IAM User Guide. Using IAM with Shield 984 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Using service-linked roles for Shield Advanced This section explains how to use service-linked roles to give Shield Advanced access to resources in your AWS account. AWS Shield Advanced uses AWS Identity and Access Management (IAM) service-linked roles. A service-linked role is a unique type of IAM role that is linked directly to Shield Advanced. Service- linked roles are predeﬁned by Shield Advanced and include all the permissions that the service requires to call other AWS services on your behalf. A service-linked role makes setting up Shield Advanced easier because you don’t have to manually add the necessary permissions. Shield Advanced deﬁnes the permissions of its service-linked roles, and unless deﬁned otherwise, only Shield Advanced can assume its roles. The deﬁned permissions include the trust policy and the permissions policy, and that permissions policy cannot be attached to any other IAM entity. You can delete a service-linked role only after ﬁrst deleting their related resources. This protects your Shield Advanced resources because you can't inadvertently remove permission to access the resources. For information about other services that support service-linked roles, see AWS Services That Work with IAM and look for the services that have Yes in the Service-Linked Role column. Choose a Yes with a link to view the service-linked role documentation for that service. Service-Linked Role Permissions for Shield Advanced Shield Advanced uses the service-linked role named AWSServiceRoleForAWSShield. This role allows Shield Advanced to access and manage AWS resources in order to automatically respond to application layer DDoS attacks on your behalf. For more information about this functionality, see Automating application layer DDoS mitigation with Shield Advanced . The AWSServiceRoleForAWSShield service-linked role trusts the following services to assume the role: • shield.amazonaws.com The role permissions policy named AWSShieldServiceRolePolicy allows Shield Advanced to complete the following actions on all AWS resources: • wafv2:GetWebACL Using IAM with Shield 985 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • wafv2:UpdateWebACL • wafv2:GetWebACLForResource • wafv2:ListResourcesForWebACL • cloudfront:ListDistributions • cloudfront:GetDistribution When actions are permitted on all AWS resources, this is indicated in the policy as "Resource": "*". This only means that the service-linked role can take each indicated action on all AWS resources that the action supports. For example, the action wafv2:GetWebACL is supported only for wafv2 web ACL resources. Shield Advanced only makes resource-level API calls for protected resources for which you've enabled the application layer protections feature and for web ACLs that are associated with those protected resources. You must conﬁgure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see Service-Linked Role Permissions in the IAM User Guide. Creating a Service-Linked Role for Shield Advanced You don't need to manually create a service-linked role. When you enable automatic application layer DDoS mitigation for a resource in the AWS Management Console, the AWS CLI, or the AWS API, Shield Advanced creates the service-linked role for you. If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you enable automatic application layer DDoS mitigation for a resource, Shield Advanced creates the service-linked role for you again. Editing a Service-Linked Role for Shield Advanced Shield Advanced does not allow you to edit the AWSServiceRoleForAWSShield service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see Editing a Service-Linked Role
waf-dg-362	waf-dg.pdf	362	role, and then need to create it again, you can use the same process to recreate the role in your account. When you enable automatic application layer DDoS mitigation for a resource, Shield Advanced creates the service-linked role for you again. Editing a Service-Linked Role for Shield Advanced Shield Advanced does not allow you to edit the AWSServiceRoleForAWSShield service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see Editing a Service-Linked Role in the IAM User Guide. Using IAM with Shield 986 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Deleting a Service-Linked Role for Shield Advanced If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don’t have an unused entity that is not actively monitored or maintained. However, you must clean up the resources for your service-linked role before you can manually delete it. Note If Shield Advanced is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again. To delete the Shield Advanced resources that are used by the AWSServiceRoleForAWSShield For all of your resources that have application layer DDoS protections conﬁgured, disable automatic application layer DDoS mitigation. For console instructions, see Conﬁgure application layer DDoS protections. To manually delete the service-linked role using IAM Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForAWSShield service-linked role. For more information, see Deleting a Service-Linked Role in the IAM User Guide. Supported Regions for Shield Advanced Service-Linked Roles Shield Advanced supports using service-linked roles in all of the Regions where the service is available. For more information, see Shield Advanced endpoints and quotas. Using IAM with Shield 987 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Logging and monitoring in Shield This section explains how to use AWS tools for monitoring and responding to events in AWS Shield. Monitoring is an important part of maintaining the reliability, availability, and performance of Shield and your AWS solutions. You should collect monitoring data from all parts of your AWS solution so that you can more easily debug a multi-point failure if one occurs. AWS provides several tools for monitoring your Shield resources and responding to potential events: Amazon CloudWatch Alarms Using CloudWatch alarms, you watch a single metric over a time period that you specify. If the metric exceeds a given threshold, CloudWatch sends a notiﬁcation to an Amazon SNS topic or AWS Auto Scaling policy. For more information, see Monitoring with Amazon CloudWatch. AWS CloudTrail Logs CloudTrail provides a record of actions taken by a user, role, or an AWS service in Shield. Using the information collected by CloudTrail, you can determine the request that was made to Shield, the IP address from which the request was made, who made the request, when it was made, and additional details. For more information, see Logging API calls with AWS CloudTrail. Logging and monitoring 988 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Validating compliance in Shield This section explains your compliance responsibility when using AWS Shield. To learn whether an AWS service is within the scope of speciﬁc compliance programs, see AWS services in Scope by Compliance Program and choose the compliance program that you are interested in. For general information, see AWS Compliance Programs. You can download third-party audit reports using AWS Artifact. For more information, see Downloading Reports in AWS Artifact. Your compliance responsibility when using AWS services is determined by the sensitivity of your data, your company's compliance objectives, and applicable laws and regulations. AWS provides the following resources to help with compliance: • Security Compliance & Governance – These solution implementation guides discuss architectural considerations and provide steps for deploying security and compliance features. • HIPAA Eligible Services Reference – Lists HIPAA eligible services. Not all AWS services are HIPAA eligible. • AWS Compliance Resources – This collection of workbooks and guides might apply to your industry and location. • AWS Customer Compliance Guides – Understand the shared responsibility model through the lens of compliance. The guides summarize the best practices for securing AWS services and map the guidance to security controls across multiple frameworks (including National Institute of Standards and Technology (NIST), Payment Card Industry Security Standards Council (PCI), and International Organization for Standardization (ISO)). • Evaluating Resources with Rules in the AWS Conﬁg Developer Guide – The AWS Conﬁg service assesses how well your resource conﬁgurations comply with internal practices, industry guidelines, and regulations. • AWS Security Hub
waf-dg-363	waf-dg.pdf	363	and guides might apply to your industry and location. • AWS Customer Compliance Guides – Understand the shared responsibility model through the lens of compliance. The guides summarize the best practices for securing AWS services and map the guidance to security controls across multiple frameworks (including National Institute of Standards and Technology (NIST), Payment Card Industry Security Standards Council (PCI), and International Organization for Standardization (ISO)). • Evaluating Resources with Rules in the AWS Conﬁg Developer Guide – The AWS Conﬁg service assesses how well your resource conﬁgurations comply with internal practices, industry guidelines, and regulations. • AWS Security Hub – This AWS service provides a comprehensive view of your security state within AWS. Security Hub uses security controls to evaluate your AWS resources and to check your compliance against security industry standards and best practices. For a list of supported services and controls, see Security Hub controls reference. • Amazon GuardDuty – This AWS service detects potential threats to your AWS accounts, workloads, containers, and data by monitoring your environment for suspicious and malicious activities. GuardDuty can help you address various compliance requirements, like PCI DSS, by meeting intrusion detection requirements mandated by certain compliance frameworks. Validating compliance 989 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • AWS Audit Manager – This AWS service helps you continuously audit your AWS usage to simplify how you manage risk and compliance with regulations and industry standards. Building for resilience in Shield This section explains how AWS architecture supports data redundancy for AWS Shield. The AWS global infrastructure is built around AWS Regions and Availability Zones. AWS Regions provide multiple physically separated and isolated Availability Zones, which are connected with low-latency, high-throughput, and highly redundant networking. With Availability Zones, you can design and operate applications and databases that automatically fail over between Availability Zones without interruption. Availability Zones are more highly available, fault tolerant, and scalable than traditional single or multiple data center infrastructures. For more information about AWS Regions and Availability Zones, see AWS Global Infrastructure. Infrastructure security in AWS Shield This section explains how AWS Shield isolates service traﬃc. As a managed service, AWS Shield is protected by AWS global network security. For information about AWS security services and how AWS protects infrastructure, see AWS Cloud Security. To design your AWS environment using the best practices for infrastructure security, see Infrastructure Protection in Security Pillar AWS Well‐Architected Framework. You use AWS published API calls to access Shield through the network. Clients must support the following: • Transport Layer Security (TLS). We require TLS 1.2 and recommend TLS 1.3. • Cipher suites with perfect forward secrecy (PFS) such as DHE (Ephemeral Diﬃe-Hellman) or ECDHE (Elliptic Curve Ephemeral Diﬃe-Hellman). Most modern systems such as Java 7 and later support these modes. Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the AWS Security Token Service (AWS STS) to generate temporary security credentials to sign requests. Building for resilience 990 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide AWS Shield Advanced quotas AWS Shield Advanced has default quotas on the number of entities per Region. You can request an increase in these quotas. Resource Maximum number of protected resources for each resource type that AWS Shield Advanced oﬀers protection for, per account. Maximum number of protection groups, per account. Default quota 1,000 100 Maximum number of individual protected resources that you can speciﬁca 1,000 lly include in a protection group. In the API, this applies to the Members that you specify when you set the protection group Pattern to ARBITRARY . In the console, this applies to the resources that you select for the protection grouping Choose from protected resources. AWS Shield Advanced quotas 991 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide AWS Firewall Manager AWS Firewall Manager simpliﬁes your administration and maintenance tasks across multiple accounts and resources for a variety of protections, including AWS WAF, AWS Shield Advanced, Amazon VPC security groups and network ACLs, AWS Network Firewall, and Amazon Route 53 Resolver DNS Firewall. With Firewall Manager, you set up your protections just once and the service automatically applies them across your accounts and resources, even as you add new accounts and resources. Firewall Manager provides these beneﬁts: • Helps to protect resources across accounts • Helps to protect all resources of a particular type, such as all Amazon CloudFront distributions • Helps to protect all resources with speciﬁc tags • Automatically adds protection to resources that are added to your account • Allows you to subscribe all member accounts in an AWS Organizations organization to AWS Shield Advanced, and automatically subscribes new in-scope accounts that join the organization • Allows
waf-dg-364	waf-dg.pdf	364	protections just once and the service automatically applies them across your accounts and resources, even as you add new accounts and resources. Firewall Manager provides these beneﬁts: • Helps to protect resources across accounts • Helps to protect all resources of a particular type, such as all Amazon CloudFront distributions • Helps to protect all resources with speciﬁc tags • Automatically adds protection to resources that are added to your account • Allows you to subscribe all member accounts in an AWS Organizations organization to AWS Shield Advanced, and automatically subscribes new in-scope accounts that join the organization • Allows you to apply security group rules to all member accounts or speciﬁc subsets of accounts in an AWS Organizations organization, and automatically applies the rules to new in-scope accounts that join the organization • Lets you use your own rules, or purchase managed rules from AWS Marketplace Firewall Manager is particularly useful when you want to protect your entire organization rather than a small number of speciﬁc accounts and resources, or if you frequently add new resources that you want to protect. Firewall Manager also provides centralized monitoring of DDoS attacks across your organization. Note Charges incurred by AWS Firewall Manager are for the underlying services, such as AWS WAF and AWS Conﬁg. For more information, see AWS Firewall Manager Pricing. Topics • AWS Firewall Manager prerequisites 992 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Using AWS Firewall Manager administrators • Setting up AWS Firewall Manager policies • Using AWS Firewall Manager policies • Using Firewall Manager managed lists • Grouping your resources in Firewall Manager • Viewing compliance information for an AWS Firewall Manager policy • AWS Firewall Manager integration with AWS Security Hub • Security in your use of the AWS Firewall Manager service • AWS Firewall Manager quotas AWS Firewall Manager prerequisites This topic shows you how to get ready to administer AWS Firewall Manager. You use one Firewall Manager administrator account to manage all Firewall Manager security policies for your organization in AWS Organizations. Except where noted, perform the prerequisite steps using the account that you will use as the Firewall Manager administrator. Before you use Firewall Manager for the ﬁrst time, perform the following steps in sequence. Topics • Joining and conﬁguring AWS Organizations for using Firewall Manager • Creating an AWS Firewall Manager default administrator account • Enabling AWS Conﬁg for using Firewall Manager • Subscribing in the AWS Marketplace and conﬁguring third-party settings for Firewall Manager third-party policies • Enabling resource sharing for Network Firewall and DNS Firewall policies with AWS RAM • Using AWS Firewall Manager in Regions that are disabled by default Joining and conﬁguring AWS Organizations for using Firewall Manager To use Firewall Manager, your account must be a member of the organization in the AWS Organizations service where you want to use your Firewall Manager policies. AWS Firewall Manager prerequisites 993 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note For information about Organizations, see AWS Organizations User Guide. To establish the required AWS Organizations membership and conﬁguration 1. Choose an account to use as the Firewall Manager administrator for the organization in Organizations. 2. If your chosen account isn't already a member of the organization, have it join. Follow the guidance at Inviting an AWS account to join your organization. 3. AWS Organizations has two available feature sets: consolidated billing features and all features. To use Firewall Manager, your organization must be enabled for all features. If your organization is conﬁgured only for consolidated billing, follow the guidance at Enabling All Features in Your Organization. Creating an AWS Firewall Manager default administrator account This page provides instructions for creating an AWS Firewall Manager default administrator account. Note This procedure uses the account and organization that you chose and conﬁgured in the preceding step. Only the organization's management account can create Firewall Manager default administrator accounts. The ﬁrst administrator account that you create is the default admininstrator account. The default administrator account can manage third-party ﬁrewalls and has full administrative scope. When you set the default administrator account, Firewall Manager automatically sets it as an AWS Organizations delegated administrator for Firewall Manager. This allows Firewall Manager to access information about the organizational units (OUs) in the organization. You can use OUs to specify the scope of your Firewall Manager policies. For more information about setting policy scope, see the guidance for the individual policy types under Creating an AWS Firewall Manager policy. For more information about Organizations and management accounts, see Managing the AWS Accounts in Your Organization. Creating an AWS Firewall Manager default administrator account 994 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Required settings for the organization's management account The organization's management account must have
waf-dg-365	waf-dg.pdf	365	Manager. This allows Firewall Manager to access information about the organizational units (OUs) in the organization. You can use OUs to specify the scope of your Firewall Manager policies. For more information about setting policy scope, see the guidance for the individual policy types under Creating an AWS Firewall Manager policy. For more information about Organizations and management accounts, see Managing the AWS Accounts in Your Organization. Creating an AWS Firewall Manager default administrator account 994 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Required settings for the organization's management account The organization's management account must have the following settings in order to onboard the organization to Firewall Manager and create a default administrator: • It must be a member of the organization in AWS Organizations where you want to apply your Firewall Manager policies. To set the default administrator account 1. Sign in to the Firewall Manager AWS Management Console using an existing AWS Organizations management account. 2. Open the Firewall Manager console at https://console.aws.amazon.com/wafv2/fmsv2. 3. 4. In the navigation pane, choose Settings. Type the AWS account ID of the account that you've chosen to use as the Firewall Manager administrator. Note The default administrator has full administrative scope. Full administrative scope means that this account can apply policies to all accounts and organizational units (OUs) within the organization, take actions in all Regions, and manage all Firewall Manager policy types. 5. Choose Create administrator account to create the account. For more information about managing the Firewall Manager administrator account, see Using AWS Firewall Manager administrators. Enabling AWS Conﬁg for using Firewall Manager To use Firewall Manager, you must enable AWS Conﬁg. Note You incur charges for your AWS Conﬁg settings, according to AWS Conﬁg pricing. For more information, see Getting Started with AWS Conﬁg. Enabling AWS Conﬁg for using Firewall Manager 995 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note In order for Firewall Manager to monitor policy compliance, AWS Conﬁg must continuously record conﬁguration changes for protected resources. In your AWS Conﬁg conﬁguration, the recording frequency must be set to Continuous, which is the default setting. To enable AWS Conﬁg for Firewall Manager 1. Enable AWS Conﬁg for each of your AWS Organizations member accounts, including the Firewall Manager administrator account. For more information, see Getting Started with AWS Conﬁg. 2. Enable AWS Conﬁg for each AWS Region that contains the resources that you want to protect. You can enable AWS Conﬁg manually, or you can use the AWS CloudFormation template "Enable AWS Conﬁg" at AWS CloudFormation StackSets Sample Templates. If you don't want to enable AWS Conﬁg for all resources, then you must enable the following according to the type of Firewall Manager policies that you use: • WAF policy – Enable Conﬁg for the resource types CloudFront Distribution, Application Load Balancer (choose ElasticLoadBalancingV2 from the list), API Gateway, WAF WebACL, WAF Regional WebACL, and WAFv2 WebACL. To enable AWS Conﬁg to protect a CloudFront distribution, you must be in the US East (N. Virginia) Region. Other Regions don't have CloudFront as an option. • Shield policy – Enable Conﬁg for the resource types Shield Protection, ShieldRegional Protection, Application Load Balancer, EC2 EIP, WAF WebACL, WAF Regional WebACL, and WAFv2 WebACL. • Security group policy – Enable Conﬁg for the resource types EC2 SecurityGroup, EC2 Instance, and EC2 NetworkInterface. • Network ACL policy – Enable Conﬁg for the resource types Amazon EC2 Subnet and Amazon EC2 network ACL. • Network Firewall policy – Enable Conﬁg for the resource types NetworkFirewall FirewallPolicy, NetworkFirewall RuleGroup, EC2 VPC, EC2 InternetGateway, EC2 RouteTable, and EC2 Subnet. • DNS Firewall policy – Enable Conﬁg for the resource type EC2 VPC. Enabling AWS Conﬁg for using Firewall Manager 996 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Third-party ﬁrewall policy – Enable Conﬁg for the resource types Amazon EC2 VPC, Amazon EC2 InternetGateway, Amazon EC2 RouteTable, Amazon EC2 Subnet, and Amazon EC2 VPCEndpoint. Note If you conﬁgure your AWS Conﬁg recorder to use a custom IAM role, you need to make sure the IAM policy has the proper permissions to record the Firewall Manager policy's required resource types. Without the proper permissions, the required resources may not be recorded which prevents Firewall Manager from properly protecting your resources. Firewall Manager doesn't have visibility into these permission misconﬁgurations. For information about using IAM with AWS Conﬁg, see IAM for AWS Conﬁg. Subscribing in the AWS Marketplace and conﬁguring third-party settings for Firewall Manager third-party policies Complete the following prerequisites to set up Firewall Manager third-party ﬁrewall policies. Fortigate Cloud Native Firewall (CNF) as a Service policy prerequisites To use Fortigate CNF for Firewall Manager 1. Subscribe to the Fortigate Cloud Native Firewall (CNF) as a Service service in the AWS Marketplace. 2.
waf-dg-366	waf-dg.pdf	366	permissions, the required resources may not be recorded which prevents Firewall Manager from properly protecting your resources. Firewall Manager doesn't have visibility into these permission misconﬁgurations. For information about using IAM with AWS Conﬁg, see IAM for AWS Conﬁg. Subscribing in the AWS Marketplace and conﬁguring third-party settings for Firewall Manager third-party policies Complete the following prerequisites to set up Firewall Manager third-party ﬁrewall policies. Fortigate Cloud Native Firewall (CNF) as a Service policy prerequisites To use Fortigate CNF for Firewall Manager 1. Subscribe to the Fortigate Cloud Native Firewall (CNF) as a Service service in the AWS Marketplace. 2. First, register a tenant on the Fortigate CNF product portal. Then Add your Firewall Manager administrator account under your tenant on the Fortigate CNF product portal. For more information, see the Fortigate CNF documentation. For information about working with Fortigate CNF policies, see Using Fortigate Cloud Native Firewall (CNF) as a Service policies for Firewall Manager. Subscribing in the AWS Marketplace and conﬁguring third-party settings for Firewall Manager third- party policies 997 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Palo Alto Networks Cloud Next Generation Firewall policy prerequisites To use Palo Alto Networks Cloud NGFW for Firewall Manager 1. Subscribe to the Palo Alto Networks Cloud Next Generation Firewall Pay-As-You-Go service in the AWS Marketplace. 2. Complete the Palo Alto Networks Cloud NGFW deployment steps listed in the Deploy Palo Alto Networks Cloud NGFW for AWS with the AWS Firewall Manager topic in the Palo Alto Networks Cloud Next Generation Firewall for AWS deployment guide. For information about working with Palo Alto Networks Cloud NGFW policies, see Using Palo Alto Networks Cloud NGFW policies for Firewall Manager. Enabling resource sharing for Network Firewall and DNS Firewall policies with AWS RAM To manage Firewall Manager Network Firewall and DNS Firewall policies, you must enable sharing with AWS Organizations in AWS Resource Access Manager. This allows Firewall Manager to deploy protections across your accounts when you create these policy types. To enable sharing with AWS Organizations in AWS Resource Access Manager • Follow the guidance at Enable Sharing with AWS Organizations in the AWS Resource Access Manager User Guide. If you run into problems with resource sharing, see the guidance at Resource sharing for Network Firewall and DNS Firewall policies. Using AWS Firewall Manager in Regions that are disabled by default To use Firewall Manager in a Region that's disabled by default, you must enable the Region for both the management account of your AWS organization and the Firewall Manager default administrator account. For information about Regions that are disabled by default and how to enable them, see Managing AWS Regions in the AWS General Reference. Enabling resource sharing for Network Firewall and DNS Firewall policies with AWS RAM 998 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide To enable a disabled Region • For both the Organizations management account and the Firewall Manager default administrator account, follow the guidance at Enabling a Region in the AWS General Reference. After you follow these steps, you can conﬁgure Firewall Manager to begin protecting your resources. For more information, see Setting up AWS Firewall Manager AWS WAF policies. Using AWS Firewall Manager administrators This page explains what Firewall Manager administrators are and deﬁnes related terms. With AWS Firewall Manager you can have one or multiple administrators who can manage the ﬁrewall resources of your organization. If you want to use multiple Firewall Manager administrators in your organization, you can apply administrative scope conditions to each administrator to deﬁne the resources that they can manage. This gives you the ﬂexibility to have diﬀerent administrator roles within your organization, and helps you maintain the principal of least privileged access. For example, you can have one administrator manage a set of organizational units (OUs) for your organization, while delegating another administrator to manage only speciﬁc Firewall Manager policy types. For more information about Organizations and management accounts, see Managing the AWS Accounts in Your Organization. For the maximum number of administrators that you can have per organization, see AWS Firewall Manager quotas Getting started using Firewall Manager administrators Before you begin using Firewall Manager administrators, you must complete the prerequisites listed in AWS Firewall Manager prerequisites. In the prerequisites, you'll onboard an AWS Organizations organization to Firewall Manager and create a default administrator account for Firewall Manager. A default administrator account has the ability to manage third-party ﬁrewalls and has full administrative scope. Administrative scope Administrative scope deﬁnes the resources that the Firewall Manager administrator can manage. After an AWS Organizations management account onboards an organization to Firewall Manager, the management account can create additional Firewall Manager administrators with diﬀerent Using Firewall Manager administrators 999 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide administrative scopes. An AWS
waf-dg-367	waf-dg.pdf	367	listed in AWS Firewall Manager prerequisites. In the prerequisites, you'll onboard an AWS Organizations organization to Firewall Manager and create a default administrator account for Firewall Manager. A default administrator account has the ability to manage third-party ﬁrewalls and has full administrative scope. Administrative scope Administrative scope deﬁnes the resources that the Firewall Manager administrator can manage. After an AWS Organizations management account onboards an organization to Firewall Manager, the management account can create additional Firewall Manager administrators with diﬀerent Using Firewall Manager administrators 999 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide administrative scopes. An AWS Organizations management account can either grant the administrator full or restricted administrative scope. Full scope gives the administrator full access to all of the preceding resource types. Restricted scope refers to granting administrative permission to only a subset of the preceding resources. We recommend that you only grant administrators the permissions they need to perform the duties of their role. You can apply any combination of these administrative scope conditions to an administrator: • Accounts or OUs in your organization that the administrator can apply policies to. • Regions that the administrator can perform actions in. • Firewall Manager policy types that the administrator can manage. Administrator roles There are two types of administrator roles in Firewall Manager: a default administrator, and Firewall Manager administrators. • Default administrator - The organization's management account creates a Firewall Manager default administrator account when they onboard their organization to Firewall Manager while completing the AWS Firewall Manager prerequisites. The default administrator can manage third-party ﬁrewalls and has full administrative scope, but is otherwise at the same peer level as other administrators, if you choose to have multiple administrators. • Firewall Manager administrators - A Firewall Manager administrator can manage the resources that the AWS Organizations management account designates for them in their administrative scope conﬁguration. For the maximum number of administrators that you can have per organization, see AWS Firewall Manager quotas. Upon creation of a Firewall Manager administrator account, the service checks with AWS Organizations to see if the account is already a delegated administrator for Firewall Manager within the organization. If not, then Firewall Manager calls Organizations to set the account as a delegated administrator for Firewall Manager. For information about Organizations delegated administrators, see AWS Organizations terminology and concepts in the AWS Organizations User Guide. Existing administrators If you are an existing Firewall Manager customer and have set already set an administrator, then this existing administrator will be the Firewall Manager default administrator. There should be no impacts to your existing ﬂow. If you wish to add more administrators, you can do so by following the procedures in this chapter. Using Firewall Manager administrators 1000 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Creating a Firewall Manager administrator account The following procedure describes how to create a Firewall Manager administrator account using the Firewall Manager console. Note Only an organization's managment account can create Firewall Manager administrator accounts. To create a Firewall Manager administrator account 1. Sign in to the Firewall Manager AWS Management Console using an existing AWS Organizations management account. 2. Open the Firewall Manager console at https://console.aws.amazon.com/wafv2/fmsv2. 3. In the navigation pane, choose Settings. 4. Choose Create administrator account. 5. In the Details pane, for AWS account ID type the AWS ID of a member account that you'd like to add as a Firewall Manager administrator. 6. For Administrative scope, choose one of the following options: • Full – This grants the administrator the ability to apply policies to all accounts and organizational units (OUs) within the organization, take actions in all Regions, and apply all Firewall Manager policy types, except for third-party ﬁrewalls. Only the default administrator can create and manage third-party ﬁrewalls. Take caution if granting this level of permissions to the administrator. In the spirit of least privilege, we recommend only granting the administrator the permissions they need to perform the duties of their role. • Restricted – If applying a Restricted scope, then in Conﬁgure administrative scope conﬁgure the accounts and organizational units, Regions, and policy types that the account can manage. For Accounts and organizational units, choose the options as follows: • If you want to apply policies to all accounts or organizational units in your organization, choose Include all accounts under my AWS organization. • If you want to apply policies only to speciﬁc accounts or accounts that are in speciﬁc AWS Organizations organizational units (OUs), choose Include only the speciﬁed accounts Creating a Firewall Manager administrator account 1001 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide and organizational units, and then add the accounts and OUs that you want to include. Specifying an OU is the equivalent of specifying all accounts in the OU
waf-dg-368	waf-dg.pdf	368	as follows: • If you want to apply policies to all accounts or organizational units in your organization, choose Include all accounts under my AWS organization. • If you want to apply policies only to speciﬁc accounts or accounts that are in speciﬁc AWS Organizations organizational units (OUs), choose Include only the speciﬁed accounts Creating a Firewall Manager administrator account 1001 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide and organizational units, and then add the accounts and OUs that you want to include. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. • If you want to apply policies to all but a speciﬁc set of accounts or AWS Organizations organizational units (OUs), choose Exclude the speciﬁed accounts and organizational units, and include all others, and then add the accounts and OUs that you want to exclude. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. For Regions, choose the options as follows: • If you want to allow the administrator to perform actions in all available Regions, choose Include all Regions. • If you want the administrator to perform actions only in speciﬁc Regions, choose Include only the speciﬁed Regions, and then specify the Regions that you want to include. Note To include a Region that is disabled by default, you must enable the Region for both the AWS Organizations organization management account and the default administration account. For information about enabling Regions for an account, see Enable a Region in the Amazon Web Services General Reference. For Policy types, choose the options as follows:. • If you want to allow the administrator to manage all policy types, choose Include all policy types. • If you want the administrator to manage only speciﬁc policy types, choose Include only the speciﬁed policy types, and then specify the policy types that you want to include. 7. Choose Create administrator account to create the administrator account. Upon creation, Firewall Manager calls AWS Organizations to see if the administrator is already a delegated administrator for your organization. If not, Firewall Manager will designate the account as a delegated administrator. For information about delegated administrators in Organizations see AWS Organizations terminology and concepts in the AWS Organizations User Guide. If you apply Restricted administrative scope, Firewall Manager automatically evaluates any new resources against your settings. For example, if you include only speciﬁc accounts, Firewall Manager Creating a Firewall Manager administrator account 1002 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide doesn't apply the policy to any new accounts. As another example, if you include an OU, when you add an account to the OU or to any of its child OUs, Firewall Manager automatically includes the account within the administrative scope. Updating a Firewall Manager administrator account The following procedure describes how to update a Firewall Manager administrator account using the Firewall Manager console. Note To update an administrator's scope to include a Region that's disabled by default, you must enable the Region for both the AWS Organizations organization management account and the default administration account. For information about enabling Regions for an account, see Enable a Region in the Amazon Web Services General Reference. Only an organization's managment account can update Firewall Manager administrator accounts. To update an administrator account (console) 1. Sign in to the Firewall Manager AWS Management Console using an existing AWS Organizations management account. 2. Open the Firewall Manager console at https://console.aws.amazon.com/wafv2/fmsv2. 3. 4. 5. In the navigation pane, choose Settings. in the Firewall Manager administrators table, choose the account that you'd like to update. Select Edit to change details of administrator's account. You can't change the account ID. 6. Choose Save to save your changes. Revoking a Firewall Manager administrator account The following procedure describes how to revoke a Firewall Manager administrator account. If you are the default administrator, before you can revoke your account all of the Firewall Manager administrator accounts within your organization must ﬁrst revoke their own accounts. Updating a Firewall Manager administrator account 1003 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note Only an individual Firewall Manager administrator can revoke their own administrator account. To revoke an administrator account (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS 2. 3. Firewall Manager prerequisites. In the navigation pane, choose Settings. In the Administrator account pane, select Revoke administrator
waf-dg-369	waf-dg.pdf	369	your organization must ﬁrst revoke their own accounts. Updating a Firewall Manager administrator account 1003 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note Only an individual Firewall Manager administrator can revoke their own administrator account. To revoke an administrator account (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS 2. 3. Firewall Manager prerequisites. In the navigation pane, choose Settings. In the Administrator account pane, select Revoke administrator account to revoke your account. Important When you revoke administrator privileges from an administrator account, all Firewall Manager policies created by that account are deleted. Changing the default Firewall Manager administrator account The following procedure describes how to change the default Firewall Manager administrator account. You can designate only one account in an organization as the default Firewall Manager administrator account. The default administrator account follows the principle of ﬁrst in, last out. To designate a diﬀerent default administrator account, each individual administrator account must ﬁrst revoke their own account. Then, the existing default administrator can revoke their own account, which also will oﬀboard the organization from Firewall Manager. When an administrator revokes their account, all Firewall Manager policies created by that account are deleted. To designate a new default administrator account, you then must sign into Firewall Manager with the AWS Organizations management account to designate a new administrator account. To change the default administrator account for an organization, perform the following procedure. Changing the default administrator account 1004 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide To change the default administrator account 1. Sign in to the Firewall Manager AWS Management Console using an existing AWS Organizations management account. 2. Open the Firewall Manager console at https://console.aws.amazon.com/wafv2/fmsv2. 3. 4. In the navigation pane, choose Settings. Type the ID of the account that you've chosen to use as the Firewall Manager administrator. Note This account is given permission to create and manage Firewall Manager policies across all accounts within your organization. 5. Choose Create administrator account. 6. Type the AWS ID of the account that you've chosen to use as the Firewall Manager administrator. Note This account is given full administrative scope. Full administrative scope means that this account can apply policies to all accounts and organizational units (OUs) within the organization, take actions in all Regions, and manage all Firewall Manager policy types. 7. Choose Create administrator account to create the default administrator account. Disqualifying changes to a Firewall Manager administrator account Some changes to an administrator account can disqualify it from remaining an administrator account. This section describes the changes that can disqualify the an administrator account, and how AWS and Firewall Manager handle these changes. Account removed from the organization in AWS Organizations If the AWS Firewall Manager administrator account is removed from the organization in AWS Organizations, it can no longer administer policies for the organization. Firewall Manager takes one of the following actions: Disqualifying changes to an administrator account 1005 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Account with no policies – If the Firewall Manager administrator account has no Firewall Manager policies, Firewall Manager revokes the administrator account. • Account with Firewall Manager policies – If the Firewall Manager administrator account has Firewall Manager policies, Firewall Manager sends an email to inform you of the situation and to provide options that you can take, with the help of your AWS sales account representative. Account closed If you close the account that you're using for the AWS Firewall Manager administrator, AWS and Firewall Manager handle the closure as follows: • AWS revokes the account’s administrator access from Firewall Manager and Firewall Manager deactivates any policies that were managed by the administrator account. The protections that were provided by those policies are stopped across the organization. • AWS retains the Firewall Manager policy data for the account for 90 days from the eﬀective date of the administrator account closure. During this 90-day period, you can reopen the closed account. • If you reopen the closed account during the 90-day period, AWS reassigns the account as the Firewall Manager administrator and recovers the Firewall Manager policy data for the account. • Otherwise, at the end of the 90-day period, AWS permanently deletes all Firewall Manager policy data for the account. Setting up AWS Firewall Manager policies You can use AWS Firewall Manager to enable a number of diﬀerent types of security policies. The steps for getting set up are slightly diﬀerent for each. Topics • Setting up AWS Firewall Manager AWS WAF policies • Setting up AWS Firewall Manager AWS Shield Advanced policies • Setting up AWS Firewall
waf-dg-370	waf-dg.pdf	370	the 90-day period, AWS reassigns the account as the Firewall Manager administrator and recovers the Firewall Manager policy data for the account. • Otherwise, at the end of the 90-day period, AWS permanently deletes all Firewall Manager policy data for the account. Setting up AWS Firewall Manager policies You can use AWS Firewall Manager to enable a number of diﬀerent types of security policies. The steps for getting set up are slightly diﬀerent for each. Topics • Setting up AWS Firewall Manager AWS WAF policies • Setting up AWS Firewall Manager AWS Shield Advanced policies • Setting up AWS Firewall Manager Amazon VPC security group policies • Setting up AWS Firewall Manager Amazon VPC network ACL policies • Setting up AWS Firewall Manager AWS Network Firewall policies • Setting up AWS Firewall Manager DNS Firewall policies Setting up AWS Firewall Manager policies 1006 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Setting up AWS Firewall Manager Palo Alto Networks Cloud Next Generation Firewall policies • Setting up AWS Firewall Manager Fortigate CNF policies Setting up AWS Firewall Manager AWS WAF policies To use AWS Firewall Manager to enable AWS WAF rules across your organization, perform the following steps in sequence. Topics • Step 1: Completing the prerequisites • Step 2: Creating and applying an AWS WAF policy • Step 3: Cleaning Up Step 1: Completing the prerequisites There are several mandatory steps to prepare your account for AWS Firewall Manager. Those steps are described in AWS Firewall Manager prerequisites. Complete all of the prerequisites before proceeding to Step 2: Creating and applying an AWS WAF policy. Step 2: Creating and applying an AWS WAF policy A Firewall Manager AWS WAF policy contains the rule groups that you want to apply to your resources. Firewall Manager creates a Firewall Manager web ACL in each account where you apply the policy. The individual account managers can add rules and rule groups to the resulting web ACL, in addition to the rule groups that you deﬁne here. For information about Firewall Manager AWS WAF policies, see Using AWS WAF policies with Firewall Manager. To create a Firewall Manager AWS WAF policy (console) Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 1. In the navigation pane, choose Security policies. 2. Choose Create policy. Setting up AWS WAF policies 1007 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 3. 4. For Policy type, choose AWS WAF. For Region, choose an AWS Region. To protect Amazon CloudFront distributions, choose Global. To protect resources in multiple Regions (other than CloudFront distributions), you must create separate Firewall Manager policies for each Region. 5. Choose Next. 6. For Policy name, enter a descriptive name. Firewall Manager includes the policy name in the names of the web ACLs that it manages. The web ACL names have FMManagedWebACLV2- followed by the policy name that you enter here, -, and the web ACL creation timestamp, in UTC milliseconds. For example, FMManagedWebACLV2-MyWAFPolicyName-1621880374078. Important Web ACL names can't change after creation. If you update your policy's name, Firewall Manager won't update the associated web ACL name. To have Firewall Manager create a web ACL with a diﬀerent name, you must create a new policy. 7. Under Policy rules, for First rule groups, choose Add rule groups. Expand the AWS managed rule groups. For Core rule set, toggle Add to web ACL. For AWS known bad inputs, toggle Add to web ACL. Choose Add rules. For Last rule groups, choose Add rule groups. Expand the AWS managed rule groups and for the Amazon IP reputation list, toggle Add to web ACL. Choose Add rules. Under First rule groups, select Core rule set and choose Move down. AWS WAF evaluates web requests against the AWS known bad inputs rule group before it evaluates against the Core rule set. You can also create your own AWS WAF rule groups if you want, using the AWS WAF console. Any rule groups that you create show up under Your rule groups in the Describe policy : Add rule groups page. The ﬁrst and last AWS WAF rule groups that you manage through Firewall Manager have names that begin with PREFMManaged- or POSTFMManaged-, respectively, followed by the Firewall Manager policy name, and the rule group creation timestamp, in UTC milliseconds. For example, PREFMManaged-MyWAFPolicyName-1621880555123. 8. Leave the default action for the web ACL at Allow. Setting up AWS WAF policies 1008 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 9. Leave the Policy action at the default, to not automatically remediate noncompliant resources. You can change the option later. 10. Choose Next.
waf-dg-371	waf-dg.pdf	371	Describe policy : Add rule groups page. The ﬁrst and last AWS WAF rule groups that you manage through Firewall Manager have names that begin with PREFMManaged- or POSTFMManaged-, respectively, followed by the Firewall Manager policy name, and the rule group creation timestamp, in UTC milliseconds. For example, PREFMManaged-MyWAFPolicyName-1621880555123. 8. Leave the default action for the web ACL at Allow. Setting up AWS WAF policies 1008 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 9. Leave the Policy action at the default, to not automatically remediate noncompliant resources. You can change the option later. 10. Choose Next. 11. For Policy scope, you provide the settings for the accounts, resource types, and tagging that identify the resources you want to apply the policy to. For this tutorial, leave the AWS accounts and Resources settings, and choose one or more resource types. 12. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 13. Choose Next. 14. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 15. Choose Next. 16. Review the new policy settings and return to any pages where you need to any adjustments. Check to be sure that Policy actions is set to Identify resources that don’t comply with the policy rules, but don’t auto remediate. This allows you to review the changes that your policy would make before you enable them. 17. When you are satisﬁed with the policy, choose Create policy. In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy Step 3: Cleaning Up To avoid extraneous charges, delete any unnecessary policies and resources. Setting up AWS WAF policies 1009 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide To delete a policy (console) 1. On the AWS Firewall Manager policies page, choose the radio button next to the policy name, and then choose Delete. 2. In the Delete conﬁrmation box, select Delete all policy resources, and then choose Delete again. AWS WAF removes the policy and any associated resources, like web ACLs, that it created in your account. The changes might take a few minutes to propagate to all accounts. Setting up AWS Firewall Manager AWS Shield Advanced policies You can use AWS Firewall Manager to enable AWS Shield Advanced protections across your organization. Important Firewall Manager doesn't support Amazon Route 53 or AWS Global Accelerator. If you need to protect these resources with Shield Advanced, you can't use a Firewall Manager policy. Instead, follow the instructions in Adding AWS Shield Advanced protection to AWS resources. To use Firewall Manager to enable Shield Advanced protection, perform the following steps in sequence. Topics • Step 1: Completing the prerequisites • Step 2: Creating and applying a Shield Advanced policy • Step 3: (Optional) Authorizing the Shield Response Team (SRT) • Step 4: Conﬁguring Amazon SNS notiﬁcations and Amazon CloudWatch alarms Step 1: Completing the prerequisites There are several mandatory steps to prepare your account for AWS Firewall Manager. Those steps are described in AWS Firewall Manager prerequisites. Complete all the prerequisites before proceeding to Step 2: Creating and applying a Shield Advanced policy. Setting up AWS Shield Advanced policies 1010 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Step 2: Creating and applying a Shield Advanced policy After completing the prerequisites, you create an AWS Firewall Manager Shield Advanced policy. A Firewall Manager Shield Advanced policy contains the accounts and resources that you want to protect with Shield Advanced. Important Firewall Manager does not support Amazon Route 53 or AWS Global Accelerator. If you need to protect these resources with Shield Advanced, you can't use a Firewall Manager policy. Instead, follow the instructions in Adding AWS Shield Advanced protection to AWS resources. To create a Firewall Manager Shield Advanced policy (console) 1. Sign in to the AWS Management Console using
waf-dg-372	waf-dg.pdf	372	Creating and applying a Shield Advanced policy After completing the prerequisites, you create an AWS Firewall Manager Shield Advanced policy. A Firewall Manager Shield Advanced policy contains the accounts and resources that you want to protect with Shield Advanced. Important Firewall Manager does not support Amazon Route 53 or AWS Global Accelerator. If you need to protect these resources with Shield Advanced, you can't use a Firewall Manager policy. Instead, follow the instructions in Adding AWS Shield Advanced protection to AWS resources. To create a Firewall Manager Shield Advanced policy (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. In the navigation pane, choose Security policies. 3. Choose Create policy. 4. For Policy type, choose Shield Advanced. To create a Shield Advanced policy, your Firewall Manager administrator account must be subscribed to Shield Advanced. If you are not subscribed, you are prompted to do so. For information about the cost for subscribing, see AWS Shield Advanced Pricing. Note You don't need to manually subscribe each member account to Shield Advanced. Firewall Manager does this for you when it creates the policy. Each account must Setting up AWS Shield Advanced policies 1011 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide remain subscribed for Firewall Manager and Shield Advanced to continue to protect resources in the account. 5. For Region, choose an AWS Region. To protect Amazon CloudFront resources, choose Global. To protect resources in multiple Regions (other than CloudFront resources), you must create separate Firewall Manager policies for each Region. 6. Choose Next. 7. 8. For Name, enter a descriptive name. (Global Region only) For Global Region policies, you can choose whether you want to manage Shield Advanced automatic application layer DDoS mitigation. For this tutorial, leave this choice at the default setting of Ignore. 9. For Policy action, choose the option that doesn't automatically remediate. 10. Choose Next. 11. AWS accounts this policy applies to allows you to narrow the scope of your policy by specifying accounts to include or exclude. For this tutorial, choose Include all accounts under my organization. 12. Choose the types of resources that you want to protect. Firewall Manager doesn't support Amazon Route 53 or AWS Global Accelerator. If you need to protect these resources with Shield Advanced, you can't use a Firewall Manager policy. Instead, follow the Shield Advanced guidance at Adding AWS Shield Advanced protection to AWS resources. 13. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 14. Choose Next. 15. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 16. Choose Next. Setting up AWS Shield Advanced policies 1012 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 17. Review the new policy settings and return to any pages where you need to any adjustments. Check to be sure that Policy actions is set to Identify resources that don’t comply with the policy rules, but don’t auto remediate. This allows you to review the changes that your policy would make before you enable them. 18. When you are satisﬁed with the policy, choose Create policy. In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy Continue to Step 3: (Optional) Authorizing the Shield Response Team (SRT). Step 3: (Optional) Authorizing the Shield Response Team (SRT) One of the beneﬁts of AWS Shield Advanced is support from the Shield Response Team (SRT). When you experience a potential DDoS attack, you can contact the AWS Support Center. If necessary, the Support Center escalates your issue to the SRT. The SRT helps
waf-dg-373	waf-dg.pdf	373	the Pending status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy Continue to Step 3: (Optional) Authorizing the Shield Response Team (SRT). Step 3: (Optional) Authorizing the Shield Response Team (SRT) One of the beneﬁts of AWS Shield Advanced is support from the Shield Response Team (SRT). When you experience a potential DDoS attack, you can contact the AWS Support Center. If necessary, the Support Center escalates your issue to the SRT. The SRT helps you analyze the suspicious activity and assists you in mitigating the issue. This mitigation often involves creating or updating AWS WAF rules and web ACLs in your account. The SRT can inspect your AWS WAF conﬁguration and create or update AWS WAF rules and web ACLs for you, but the team needs your authorization to do so. We recommend that as part of setting up AWS Shield Advanced, you proactively provide the SRT with the needed authorization. Providing authorization ahead of time helps prevent mitigation delays in the event of an actual attack. You authorize and contact the SRT at the account level. That is, the account owner, not the Firewall Manager administrator, must perform the following steps to authorize the SRT to mitigate potential attacks. The Firewall Manager administrator can authorize the SRT only for accounts that they own. Likewise, only the account owner can contact the SRT for support. Note To use the services of the SRT, you must be subscribed to the Business Support plan or the Enterprise Support plan. Setting up AWS Shield Advanced policies 1013 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide To authorize the SRT to mitigate potential attacks on your behalf, follow the instructions in Managed DDoS event response with Shield Response Team (SRT) support. You can change SRT access and permissions at any time by using the same steps. Continue to Step 4: Conﬁguring Amazon SNS notiﬁcations and Amazon CloudWatch alarms. Step 4: Conﬁguring Amazon SNS notiﬁcations and Amazon CloudWatch alarms You can continue from this step without conﬁguring Amazon SNS notiﬁcations or CloudWatch alarms. However, conﬁguring these alarms and notiﬁcations signiﬁcantly increases your visibility into possible DDoS events. You can monitor your protected resources for potential DDoS activity using Amazon SNS. To receive notiﬁcation of possible attacks, create an Amazon SNS topic for each Region. Important Amazon SNS notiﬁcations of potential DDoS activity are not sent in real time and can be delayed. To enable real-time notiﬁcations of potential DDoS activity, you can use a CloudWatch alarm. Your alarm must be based on the DDoSDetected metric from the account in which the protected resource exists. To create an Amazon SNS topic in Firewall Manager (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. In the navigation pane, under AWS FMS, choose Settings. 3. Choose Create new topic. 4. Enter a topic name. Setting up AWS Shield Advanced policies 1014 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 5. Enter an email address that the Amazon SNS messages will be sent to, and then choose Add email address. 6. Choose Update SNS conﬁguration. Conﬁguring Amazon CloudWatch alarms Shield Advanced records detection, mitigation, and top contributor metrics in CloudWatch that you can monitor. For more information, see AWS Shield Advanced metrics. CloudWatch incurs additional costs. For CloudWatch pricing, see Amazon CloudWatch Pricing. To create a CloudWatch alarm, follow the instructions in Using Amazon CloudWatch Alarms. By default, Shield Advanced conﬁgures CloudWatch to alert you after just one indicator of a potential DDoS event. If needed, you can use the CloudWatch console to change this setting to alert you only after multiple indicators are detected. Note In addition to the alarms, you can also use a CloudWatch dashboard to monitor potential DDoS activity. The dashboard collects and processes raw data from Shield Advanced into readable, near real-time metrics. You can use statistics in Amazon CloudWatch to gain a perspective on how your web application or service is performing. For more information, see What is CloudWatch in the Amazon CloudWatch User Guide. For instructions about creating a CloudWatch dashboard, see Monitoring with Amazon CloudWatch. For information about speciﬁc Shield Advanced metrics that you can add to your dashboard, see AWS Shield Advanced metrics. When you've completed your Shield Advanced conﬁguration, familiarize yourself with your options for viewing events at Visibility into DDoS events with Shield Advanced. Setting up AWS Firewall
waf-dg-374	waf-dg.pdf	374	data from Shield Advanced into readable, near real-time metrics. You can use statistics in Amazon CloudWatch to gain a perspective on how your web application or service is performing. For more information, see What is CloudWatch in the Amazon CloudWatch User Guide. For instructions about creating a CloudWatch dashboard, see Monitoring with Amazon CloudWatch. For information about speciﬁc Shield Advanced metrics that you can add to your dashboard, see AWS Shield Advanced metrics. When you've completed your Shield Advanced conﬁguration, familiarize yourself with your options for viewing events at Visibility into DDoS events with Shield Advanced. Setting up AWS Firewall Manager Amazon VPC security group policies To use AWS Firewall Manager to enable Amazon VPC security groups across your organization, perform the following steps in sequence. Topics • Step 1: Completing the prerequisites Setting up Amazon VPC security group policies 1015 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Step 2: Creating a security group to use in your policy • Step 3: Creating and applying a common security group policy Step 1: Completing the prerequisites There are several mandatory steps to prepare your account for AWS Firewall Manager. Those steps are described in AWS Firewall Manager prerequisites. Complete all the prerequisites before proceeding to Step 2: Creating a security group to use in your policy. Step 2: Creating a security group to use in your policy In this step, you create a security group that you could apply across your organization using Firewall Manager. Note For this tutorial, you won't apply your security group policy to the resources in your organization. You'll just create the policy and see what would happen if you applied the policy's security group to your resources. You do this by disabling automatic remediation on the policy. If you already have a general security group deﬁned, skip this step and go to Step 3: Creating and applying a common security group policy. To create a security group to use in a Firewall Manager common security group policy • Create a security group that you could apply to all accounts and resources in your organization, following the guidance under Security Groups for Your VPC in the Amazon VPC User Guide. For information on the security group rules options, see Security Group Rules Reference. You are now ready to go to Step 3: Creating and applying a common security group policy. Step 3: Creating and applying a common security group policy After completing the prerequisites, you create an AWS Firewall Manager common security group policy. A common security group policy provides a centrally controlled security group for your entire AWS organization. It also deﬁnes the AWS accounts and resources that the security group Setting up Amazon VPC security group policies 1016 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide applies to. In addition to common security group policies, Firewall Manager supports content audit security group policies, to manage the security group rules in use in your organization, and usage audit security group policies, to manage unused and redundant security groups. For more information, see Using security group policies in Firewall Manager to manage Amazon VPC security groups. For this tutorial, you create a common security group policy and set its action to not automatically remediate. This allows you to see what eﬀect the policy would have without making changes to your AWS organization. To create a Firewall Manager common security group policy (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. 3. In the navigation pane, choose Security policies. If you have not met the prerequisites, the console displays instructions about how to ﬁx any issues. Follow the instructions, and then return to this step, to create a common security group policy. 4. Choose Create policy. 5. 6. 7. For Policy type, choose Security group. For Security group policy type, choose Common security groups. For Region, choose an AWS Region. 8. Choose Next. 9. For Policy name, enter a descriptive name. 10. Policy rules allow you to choose how the security groups in this policy are applied and maintained. For this tutorial, leave the options unchecked. 11. Choose Add primary security group, select the security group that you created for this tutorial, and choose Add security group. Setting up Amazon VPC security group policies 1017 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 12. For Policy action, choose Identify resources that don’t comply with the policy rules, but don’t auto remediate. 13. Choose Next. 14. AWS accounts aﬀected by
waf-dg-375	waf-dg.pdf	375	Next. 9. For Policy name, enter a descriptive name. 10. Policy rules allow you to choose how the security groups in this policy are applied and maintained. For this tutorial, leave the options unchecked. 11. Choose Add primary security group, select the security group that you created for this tutorial, and choose Add security group. Setting up Amazon VPC security group policies 1017 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 12. For Policy action, choose Identify resources that don’t comply with the policy rules, but don’t auto remediate. 13. Choose Next. 14. AWS accounts aﬀected by this policy allows you to narrow the scope of your policy by specifying accounts to include or exclude. For this tutorial, choose Include all accounts under my organization. 15. For Resource type, choose one or more types, according to the resources you have deﬁned for your AWS organization. 16. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 17. Choose Next. 18. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 19. Choose Next. 20. Review the new policy settings and return to any pages where you need to any adjustments. Check to be sure that Policy actions is set to Identify resources that don’t comply with the policy rules, but don’t auto remediate. This allows you to review the changes that your policy would make before you enable them. 21. When you are satisﬁed with the policy, choose Create policy. In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy Setting up Amazon VPC security group policies 1018 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 22. When you are ﬁnished exploring, if you don't want to keep the policy you created for this tutorial, choose the policy name, choose Delete, choose Clean up resources created by this policy., and ﬁnally choose Delete. For more information about Firewall Manager security group policies, see Using security group policies in Firewall Manager to manage Amazon VPC security groups. Setting up AWS Firewall Manager Amazon VPC network ACL policies To use AWS Firewall Manager to enable network ACLs across your organization, perform the steps in this section in sequence. For information about network ACLs, see Control traﬃc to subnets using network ACLs in the Amazon VPC User Guide. Topics • Step 1: Completing the prerequisites • Step 2: Creating a network ACL policy Step 1: Completing the prerequisites There are several mandatory steps to prepare your account for AWS Firewall Manager. Those steps are described in AWS Firewall Manager prerequisites. Complete all the prerequisites before proceeding to Step 2: Creating a network ACL policy. Step 2: Creating a network ACL policy After completing the prerequisites, you create a Firewall Manager network ACL policy. A network ACL policy provides a centrally controlled network ACL deﬁnition for your entire AWS organization. It also deﬁnes the AWS accounts and subnets that the network ACL applies to. For information about Firewall Manager network ACL policies, see Network ACL policies. For general information about Firewall Manager network ACL policies, see Network ACL policies. Note For this tutorial, you won't apply your network ACL policy to the subnets in your organization. You'll just create the policy and see what would happen if you applied the Setting up Amazon VPC network ACL policies 1019 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide policy's network ACL to your subnets. You do this by disabling automatic remediation on the policy. To create a Firewall Manager network ACL policy (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall
waf-dg-376	waf-dg.pdf	376	and see what would happen if you applied the Setting up Amazon VPC network ACL policies 1019 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide policy's network ACL to your subnets. You do this by disabling automatic remediation on the policy. To create a Firewall Manager network ACL policy (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. 3. In the navigation pane, choose Security policies. If you have not met the prerequisites, the console displays instructions about how to ﬁx any issues. Follow the instructions, and then return to this step, to create a network ACL policy. 4. Choose Create policy. 5. 6. For Region, choose an AWS Region. For Policy type, choose Network ACL. 7. Choose Next. 8. 9. For Policy name, enter a descriptive name. For Network ACL policy rules, deﬁne the ﬁrst and last rules for both inbound and outbound traﬃc. You deﬁne network ACL rules in Firewall Manager similar to how you deﬁne them through Amazon VPC. The only diﬀerence is that, instead of assigning rule numbers yourself, you assign the order to run each set of rules, and then Firewall Manager assigns the numbers for you when you save the policy. You can deﬁne up to 5 inbound rules, divided in any way between ﬁrst and last, and you can deﬁne up to 5 outbound rules. For guidance specifying network ACL rules, see Add and delete network ACL rules in the Amazon VPC User Guide. Setting up Amazon VPC network ACL policies 1020 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide The rules that you deﬁne in the Firewall Manager policy specify the minimum rule conﬁguration that a network ACL must have to be compliant with the network ACL policy. For example, a network ACL's inbound rules cannot be compliant with the policy unless they start with as the policy's inbound ﬁrst rules, in the same order as they're speciﬁed in the policy. For more information, see Network ACL policies. 10. For Policy action, choose Identify resources that don’t comply with the policy rules, but don’t auto remediate. 11. Choose Next. 12. AWS accounts aﬀected by this policy allows you to narrow the scope of your policy by specifying accounts to include or exclude. For this tutorial, choose Include all accounts under my organization. The Resource type for a network ACL policy is always subnet. 13. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 14. Choose Next. 15. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 16. Choose Next. 17. Review the new policy settings and return to any pages where you need to any adjustments. Check to be sure that Policy actions is set to Identify resources that don’t comply with the policy rules, but don’t auto remediate. This allows you to review the changes that your policy would make before you enable them. 18. When you are satisﬁed with the policy, choose Create policy. In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending Setting up Amazon VPC network ACL policies 1021 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy 19. When you are ﬁnished exploring, if you don't want to keep the policy that you created for this tutorial, choose the policy name, choose Delete, choose Clean up resources created by this policy., and ﬁnally choose Delete. For more information about Firewall Manager network ACL policies, see Network ACL policies. Setting up AWS Firewall Manager AWS Network Firewall policies To use AWS Firewall
waf-dg-377	waf-dg.pdf	377	Developer Guide status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy 19. When you are ﬁnished exploring, if you don't want to keep the policy that you created for this tutorial, choose the policy name, choose Delete, choose Clean up resources created by this policy., and ﬁnally choose Delete. For more information about Firewall Manager network ACL policies, see Network ACL policies. Setting up AWS Firewall Manager AWS Network Firewall policies To use AWS Firewall Manager to enable an AWS Network Firewall ﬁrewall across your organization, perform the following steps in sequence. For information about Firewall Manager Network Firewall policies, see Using AWS Network Firewall policies in Firewall Manager. Topics • Step 1: Completing the prerequisites • Step 2: Creating a Network Firewall rule group to use in your policy • Step 3: Creating and applying a Network Firewall policy Step 1: Completing the prerequisites There are several mandatory steps to prepare your account for AWS Firewall Manager. Those steps are described in AWS Firewall Manager prerequisites. Complete all the prerequisites before proceeding to the next step. Step 2: Creating a Network Firewall rule group to use in your policy To follow this tutorial, you should be familiar with AWS Network Firewall and know how to conﬁgure its rule groups and ﬁrewall policies. You must have at least one rule group in Network Firewall that will be used in your AWS Firewall Manager policy. If you haven't already created a rule group in Network Firewall, do so now. For information about using Network Firewall, see the AWS Network Firewall Developer Guide. Setting up AWS Network Firewall policies 1022 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Step 3: Creating and applying a Network Firewall policy After completing the prerequisites, you create an AWS Firewall Manager Network Firewall policy. A Network Firewall policy provides a centrally controlled AWS Network Firewall ﬁrewall for your entire AWS organization. It also deﬁnes the AWS accounts and resources that the ﬁrewall applies to. For more information about how Firewall Manager manages your Network Firewall policies, see Using AWS Network Firewall policies in Firewall Manager. To create a Firewall Manager Network Firewall policy (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. 3. In the navigation pane, choose Security policies. If you haven't met the prerequisites, the console displays instructions about how to ﬁx any issues. Follow the instructions, and then return to this step, to create a Network Firewall policy. 4. Choose Create security policy. 5. 6. For Policy type, choose AWS Network Firewall. For Region, choose an AWS Region. 7. Choose Next. 8. 9. For Policy name, enter a descriptive name. The policy conﬁguration allows you to deﬁne the ﬁrewall policy. This is the same process as the one you use in the AWS Network Firewall console. You add the rule groups that you want to use in your policy and provide the default stateless actions. For this tutorial, conﬁgure this policy as you would a ﬁrewall policy in Network Firewall. Setting up AWS Network Firewall policies 1023 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note Auto remediation happens automatically for AWS Firewall Manager Network Firewall policies, so you won't see an option to choose not to auto remediate here. 10. Choose Next. 11. For Firewall endpoints, choose Multiple ﬁrewall endpoints. This option provides high availability for your ﬁrewall. When you create the policy, Firewall Manager creates a ﬁrewall subnet in each Availability Zone where you have public subnets to protect. 12. For AWS Network Firewall route conﬁguration, choose Monitor to have Firewall Manager monitor your VPCs for route conﬁguration violations and alert you with remediation suggestions to help you to bring the routes into compliance. Optionally, if you don't want to have your route conﬁgurations monitored by Firewall Manager and receive these alerts, choose Oﬀ. Note Monitoring provides you with details about non-compliant resources due to faulty route conﬁguration, and suggests remediation actions from the Firewall Manager GetViolationDetails API. For example, Network Firewall alerts you if traﬃc is not routed through the ﬁrewall endpoints that are created by your policy. Warning If you choose Monitor, you can't change it to Oﬀ in the future for the same policy. You must create a new policy. 13. For Traﬃc type, select Add to ﬁrewall policy to route traﬃc through the internet gateway. 14. AWS accounts
waf-dg-378	waf-dg.pdf	378	route conﬁgurations monitored by Firewall Manager and receive these alerts, choose Oﬀ. Note Monitoring provides you with details about non-compliant resources due to faulty route conﬁguration, and suggests remediation actions from the Firewall Manager GetViolationDetails API. For example, Network Firewall alerts you if traﬃc is not routed through the ﬁrewall endpoints that are created by your policy. Warning If you choose Monitor, you can't change it to Oﬀ in the future for the same policy. You must create a new policy. 13. For Traﬃc type, select Add to ﬁrewall policy to route traﬃc through the internet gateway. 14. AWS accounts aﬀected by this policy allows you to narrow the scope of your policy by specifying accounts to include or exclude. For this tutorial, choose Include all accounts under my organization. The Resource type for a Network Firewall policy is always VPC. 15. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and Setting up AWS Network Firewall policies 1024 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 16. Choose Next. 17. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 18. Choose Next. 19. Review the new policy settings and return to any pages where you need to any adjustments. Check to be sure that Policy actions is set to Identify resources that don’t comply with the policy rules, but don’t auto remediate. This allows you to review the changes that your policy would make before you enable them. 20. When you are satisﬁed with the policy, choose Create policy. In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy 21. When you are ﬁnished exploring, if you don't want to keep the policy that you created for this tutorial, choose the policy name, choose Delete, choose Clean up resources created by this policy., and ﬁnally choose Delete. For more information about Firewall Manager Network Firewall policies, see Using AWS Network Firewall policies in Firewall Manager. Setting up AWS Firewall Manager DNS Firewall policies To use AWS Firewall Manager to enable Amazon Route 53 Resolver DNS Firewall across your organization, perform the following steps in sequence. For information about Firewall Manager DNS Firewall policies, see Using Amazon Route 53 Resolver DNS Firewall policies in Firewall Manager. Setting up DNS Firewall policies 1025 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Topics • Step 1: Completing the prerequisites • Step 2: Creating your DNS Firewall rule groups to use in your policy • Step 3: Creating and applying a DNS Firewall policy Step 1: Completing the prerequisites There are several mandatory steps to prepare your account for AWS Firewall Manager. Those steps are described in AWS Firewall Manager prerequisites. Complete all the prerequisites before proceeding to the next step. Step 2: Creating your DNS Firewall rule groups to use in your policy To follow this tutorial, you should be familiar with Amazon Route 53 Resolver DNS Firewall and know how to conﬁgure its rule groups. You must have least one rule group in DNS Firewall that will be used in your AWS Firewall Manager policy. If you haven't already created a rule group in DNS Firewall, do so now. For information about using DNS Firewall, see Amazon Route 53 Resolver DNS Firewall in the Amazon Route 53 Developer Guide. Step 3: Creating and applying a DNS Firewall policy After completing the prerequisites, you create an AWS Firewall Manager DNS Firewall policy. A DNS Firewall policy provides a set of centrally controlled DNS Firewall rule group associations for your entire AWS organization. It also deﬁnes the AWS accounts and resources that the ﬁrewall applies to. For more information about how Firewall Manager manages your DNS Firewall rule group associations, see Using Amazon Route 53 Resolver DNS Firewall policies in Firewall Manager. To create a Firewall Manager DNS Firewall
waf-dg-379	waf-dg.pdf	379	Route 53 Resolver DNS Firewall in the Amazon Route 53 Developer Guide. Step 3: Creating and applying a DNS Firewall policy After completing the prerequisites, you create an AWS Firewall Manager DNS Firewall policy. A DNS Firewall policy provides a set of centrally controlled DNS Firewall rule group associations for your entire AWS organization. It also deﬁnes the AWS accounts and resources that the ﬁrewall applies to. For more information about how Firewall Manager manages your DNS Firewall rule group associations, see Using Amazon Route 53 Resolver DNS Firewall policies in Firewall Manager. To create a Firewall Manager DNS Firewall policy (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. In the navigation pane, choose Security policies. Setting up DNS Firewall policies 1026 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 3. If you haven't met the prerequisites, the console displays instructions about how to ﬁx any issues. Follow the instructions, and then return to this step, to create a DNS Firewall policy. 4. Choose Create security policy. 5. 6. For Policy type, choose Amazon Route 53 Resolver DNS Firewall. For Region, choose an AWS Region. 7. Choose Next. 8. 9. For Policy name, enter a descriptive name. The policy conﬁguration allows you to deﬁne the DNS Firewall rule group associations that you want to manage from Firewall Manager. You add the rule groups that you want to use in your policy. You can deﬁne an association to evaluate ﬁrst for your VPCs and one to evaluate last. For this tutorial, add one or two rule group associations, depending on your needs. 10. Choose Next. 11. AWS accounts aﬀected by this policy allows you to narrow the scope of your policy by specifying accounts to include or exclude. For this tutorial, choose Include all accounts under my organization. The Resource type for a DNS Firewall policy is always VPC. 12. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 13. Choose Next. 14. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 15. Choose Next. 16. Review the new policy settings and return to any pages where you need to any adjustments. Check to be sure that Policy actions is set to Identify resources that don’t comply with the policy rules, but don’t auto remediate. This allows you to review the changes that your policy would make before you enable them. 17. When you are satisﬁed with the policy, choose Create policy. Setting up DNS Firewall policies 1027 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy 18. When you are ﬁnished exploring, if you don't want to keep the policy that you created for this tutorial, choose the policy name, choose Delete, choose Clean up resources created by this policy., and ﬁnally choose Delete. For more information about Firewall Manager DNS Firewall policies, see Using Amazon Route 53 Resolver DNS Firewall policies in Firewall Manager. Setting up AWS Firewall Manager Palo Alto Networks Cloud Next Generation Firewall policies To use AWS Firewall Manager to enable Palo Alto Networks Cloud Next Generation Firewall (NGFW) policies, perform the following steps in sequence. For information about Palo Alto Networks Cloud NGFW policies, see Using Palo Alto Networks Cloud NGFW policies for Firewall Manager. Topics • Step 1: Completing the general prerequisites • Step 2: Completing the Palo Alto Networks Cloud NGFW policy prerequisites • Step 3: Creating and applying a Palo Alto Networks Cloud NGFW policy Step 1: Completing the general prerequisites There are several mandatory steps to prepare your account for AWS Firewall Manager. Those
waf-dg-380	waf-dg.pdf	380	Cloud Next Generation Firewall policies To use AWS Firewall Manager to enable Palo Alto Networks Cloud Next Generation Firewall (NGFW) policies, perform the following steps in sequence. For information about Palo Alto Networks Cloud NGFW policies, see Using Palo Alto Networks Cloud NGFW policies for Firewall Manager. Topics • Step 1: Completing the general prerequisites • Step 2: Completing the Palo Alto Networks Cloud NGFW policy prerequisites • Step 3: Creating and applying a Palo Alto Networks Cloud NGFW policy Step 1: Completing the general prerequisites There are several mandatory steps to prepare your account for AWS Firewall Manager. Those steps are described in AWS Firewall Manager prerequisites. Complete all the prerequisites before proceeding to the next step. Step 2: Completing the Palo Alto Networks Cloud NGFW policy prerequisites There are a couple of additional mandatory steps that you must complete in order to use Palo Alto Networks Cloud NGFW policies. Those steps are described in Palo Alto Networks Cloud Next Setting up Palo Alto Networks Cloud NGFW policies 1028 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Generation Firewall policy prerequisites. Complete all the prerequisites before proceeding to the next step. Step 3: Creating and applying a Palo Alto Networks Cloud NGFW policy After completing the prerequisites, you create an AWS Firewall Manager Palo Alto Networks Cloud NGFW policy. For more information about Firewall Manager policies for Palo Alto Networks Cloud NGFW, see Using Palo Alto Networks Cloud NGFW policies for Firewall Manager. To create a Firewall Manager policy for Palo Alto Networks Cloud NGFW (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. In the navigation pane, choose Security policies. 3. Choose Create policy. 4. 5. For Policy type, choose Palo Alto Networks Cloud NGFW. If you haven't already subscribed to the Palo Alto Networks Cloud NGFW service in the AWS Marketplace, you'll need to do that ﬁrst. To subscribe in the AWS Marketplace, choose View AWS Marketplace details. For Deployment model, choose either the Distributed model or Centralized model. The deployment model determines how Firewall Manager manages endpoints for the policy. With the distributed model, Firewall Manager maintains ﬁrewall endpoints in each VPC that's within policy scope. With the centralized model, Firewall Manager maintains a single endpoint in an inspection VPC. 6. For Region, choose an AWS Region. To protect resources in multiple Regions, you must create separate policies for each Region. 7. Choose Next. 8. For Policy name, enter a descriptive name. Setting up Palo Alto Networks Cloud NGFW policies 1029 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 9. In the policy conﬁguration, choose the Palo Alto Networks Cloud NGFW ﬁrewall policy to associate with this policy. The list of Palo Alto Networks Cloud NGFW ﬁrewall policies contains all of the Palo Alto Networks Cloud NGFW ﬁrewall policies that are associated with your Palo Alto Networks Cloud NGFW tenant. For information about creating and managing Palo Alto Networks Cloud NGFW ﬁrewall policies, see the Deploy Palo Alto Networks Cloud NGFW for AWS with the AWS Firewall Manager topic in the Palo Alto Networks Cloud NGFW for AWS deployment guide. 10. For Palo Alto Networks Cloud NGFW logging - optional, optionally choose which Palo Alto Networks Cloud NGFW log type(s) to log for your policy. For information about Palo Alto Networks Cloud NGFW log types, see Conﬁgure Logging for Palo Alto Networks Cloud NGFW on AWS in the Palo Alto Networks Cloud NGFW for AWS deployment guide. For log destination, specify when Firewall Manager should write logs to. 11. Choose Next. 12. Under Conﬁgure third-party ﬁrewall endpoint do one of the following, depending on whether you're using the distributed or centralized deployment model to create your ﬁrewall endpoints: • If you're using the distributed deployment model for this policy, under Availability Zones, select which Availability Zones to create ﬁrewall endpoints in. You can select Availability Zones by Availability Zone name or by Availability Zone ID. • If you're using the centralized deployment model for this policy, in AWS Firewall Manager endpoint conﬁguration under Inspection VPC conﬁguration, enter the AWS account ID of the owner of the inspection VPC, and the VPC ID of the inspection VPC. • Under Availability Zones, select which Availability Zones to create ﬁrewall endpoints in. You can select Availability Zones by Availability Zone name or by Availability Zone ID. 13. Choose Next. 14. For Policy scope, under AWS accounts this policy applies to, choose the option as follows: • If you want to apply the policy to all
waf-dg-381	waf-dg.pdf	381	Availability Zone ID. • If you're using the centralized deployment model for this policy, in AWS Firewall Manager endpoint conﬁguration under Inspection VPC conﬁguration, enter the AWS account ID of the owner of the inspection VPC, and the VPC ID of the inspection VPC. • Under Availability Zones, select which Availability Zones to create ﬁrewall endpoints in. You can select Availability Zones by Availability Zone name or by Availability Zone ID. 13. Choose Next. 14. For Policy scope, under AWS accounts this policy applies to, choose the option as follows: • If you want to apply the policy to all accounts in your organization, leave the default selection, Include all accounts under my AWS organization. • If you want to apply the policy only to speciﬁc accounts or accounts that are in speciﬁc AWS Organizations organizational units (OUs), choose Include only the speciﬁed accounts and organizational units, and then add the accounts and OUs that you want to include. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. Setting up Palo Alto Networks Cloud NGFW policies 1030 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • If you want to apply the policy to all but a speciﬁc set of accounts or AWS Organizations organizational units (OUs), choose Exclude the speciﬁed accounts and organizational units, and include all others, and then add the accounts and OUs that you want to exclude. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. You can only choose one of the options. After you apply the policy, Firewall Manager automatically evaluates any new accounts against your settings. For example, if you include only speciﬁc accounts, Firewall Manager doesn't apply the policy to any new accounts. As another example, if you include an OU, when you add an account to the OU or to any of its child OUs, Firewall Manager automatically applies the policy to the new account. The Resource type for Network Firewall policies is VPC. 15. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 16. For Grant cross-account access, choose Download AWS CloudFormation template. This downloads an AWS CloudFormation template that you can use to create an AWS CloudFormation stack. This stack creates an AWS Identity and Access Management role that grants Firewall Manager cross-account permissions to manage Palo Alto Networks Cloud NGFW resources. For information about stacks, see Working with stacks in the AWS CloudFormation User Guide. 17. Choose Next. 18. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 19. Choose Next. 20. Review the new policy settings and return to any pages where you need to any adjustments. Setting up Palo Alto Networks Cloud NGFW policies 1031 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Check to be sure that Policy actions is set to Identify resources that don’t comply with the policy rules, but don’t auto remediate. This allows you to review the changes that your policy would make before you enable them. 21. When you are satisﬁed with the policy, choose Create policy. In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy For more information about Firewall Manager Palo Alto Networks Cloud NGFW policies, see Using Palo Alto Networks Cloud NGFW policies for Firewall Manager. Setting up AWS Firewall Manager Fortigate CNF policies Fortigate Cloud Native Firewall (CNF) as a Service is a third-party ﬁrewall service that you can use for your AWS Firewall Manager policies. With Fortigate CNF for Firewall Manager, you can create and centrally deploy Fortigate CNF resources and
waf-dg-382	waf-dg.pdf	382	account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy For more information about Firewall Manager Palo Alto Networks Cloud NGFW policies, see Using Palo Alto Networks Cloud NGFW policies for Firewall Manager. Setting up AWS Firewall Manager Fortigate CNF policies Fortigate Cloud Native Firewall (CNF) as a Service is a third-party ﬁrewall service that you can use for your AWS Firewall Manager policies. With Fortigate CNF for Firewall Manager, you can create and centrally deploy Fortigate CNF resources and policy sets across all of your AWS accounts. To use AWS Firewall Manager to enable Fortigate CNF policies, perform the following steps in sequence. For more information about Fortigate CNF policies, see Using Fortigate Cloud Native Firewall (CNF) as a Service policies for Firewall Manager. Topics • Step 1: Completing the general prerequisites • Step 2: Completing the Fortigate CNF policy prerequisites • Step 3: Creating and applying a Fortigate CNF policy Step 1: Completing the general prerequisites There are several mandatory steps to prepare your account for AWS Firewall Manager. Those steps are described in AWS Firewall Manager prerequisites. Complete all the prerequisites before proceeding to the next step. Setting up Fortigate CNF policies 1032 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Step 2: Completing the Fortigate CNF policy prerequisites There are additional mandatory steps that you must complete in order to use Fortigate CNF policies. Those steps are described in Fortigate Cloud Native Firewall (CNF) as a Service policy prerequisites. Complete all the prerequisites before proceeding to the next step. Step 3: Creating and applying a Fortigate CNF policy After completing the prerequisites, you create an AWS Firewall Manager Fortigate CNF policy. For more information about Firewall Manager policies for Fortigate CNF, see Using Fortigate Cloud Native Firewall (CNF) as a Service policies for Firewall Manager. To create a Firewall Manager policy for Fortigate CNF (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. In the navigation pane, choose Security policies. 3. Choose Create policy. 4. 5. For Policy type, choose Fortigate CNF. If you haven't already subscribed to the Fortigate CNF service in the AWS Marketplace, you'll need to do that ﬁrst. To subscribe in the AWS Marketplace, choose View AWS Marketplace details. For Deployment model, choose either the Distributed model or Centralized model. The deployment model determines how Firewall Manager manages endpoints for the policy. With the distributed model, Firewall Manager maintains ﬁrewall endpoints in each VPC that's within policy scope. With the centralized model, Firewall Manager maintains a single endpoint in an inspection VPC. 6. For Region, choose an AWS Region. To protect resources in multiple Regions, you must create separate policies for each Region. 7. Choose Next. Setting up Fortigate CNF policies 1033 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 8. 9. In the policy conﬁguration, choose the Fortigate CNF ﬁrewall policy to associate with this policy. The list of Fortigate CNF ﬁrewall policies contains all of the Fortigate CNF ﬁrewall policies that are associated with your Fortigate CNF tenant. For information about creating and managing Fortigate CNF ﬁrewall policies, see the Fortigate CNF documentation. 10. Choose Next. 11. Under Conﬁgure third-party ﬁrewall endpoint do one of the following, depending on whether you're using the distributed or centralized deployment model to create your ﬁrewall endpoints: • If you're using the distributed deployment model for this policy, under Availability Zones, select which Availability Zones to create ﬁrewall endpoints in. You can select Availability Zones by Availability Zone name or by Availability Zone ID. • If you're using the centralized deployment model for this policy, in AWS Firewall Manager endpoint conﬁguration under Inspection VPC conﬁguration, enter the AWS account ID of the owner of the inspection VPC, and the VPC ID of the inspection VPC. • Under Availability Zones, select which Availability Zones to create ﬁrewall endpoints in. You can select Availability Zones by Availability Zone name or by Availability Zone ID. 12. Choose Next. 13. For Policy scope, under AWS accounts this policy applies to, choose the option as follows: • If you want to apply the policy to all accounts in your organization, leave the default selection, Include all accounts under my AWS organization. • If you want to apply the policy only to speciﬁc accounts or accounts that are in speciﬁc AWS Organizations organizational units (OUs), choose Include only the speciﬁed accounts and organizational units, and then
waf-dg-383	waf-dg.pdf	383	which Availability Zones to create ﬁrewall endpoints in. You can select Availability Zones by Availability Zone name or by Availability Zone ID. 12. Choose Next. 13. For Policy scope, under AWS accounts this policy applies to, choose the option as follows: • If you want to apply the policy to all accounts in your organization, leave the default selection, Include all accounts under my AWS organization. • If you want to apply the policy only to speciﬁc accounts or accounts that are in speciﬁc AWS Organizations organizational units (OUs), choose Include only the speciﬁed accounts and organizational units, and then add the accounts and OUs that you want to include. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. • If you want to apply the policy to all but a speciﬁc set of accounts or AWS Organizations organizational units (OUs), choose Exclude the speciﬁed accounts and organizational units, and include all others, and then add the accounts and OUs that you want to exclude. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. You can only choose one of the options. Setting up Fortigate CNF policies 1034 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide After you apply the policy, Firewall Manager automatically evaluates any new accounts against your settings. For example, if you include only speciﬁc accounts, Firewall Manager doesn't apply the policy to any new accounts. As another example, if you include an OU, when you add an account to the OU or to any of its child OUs, Firewall Manager automatically applies the policy to the new account. The Resource type for Fortigate CNF policies is VPC. 14. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 15. For Grant cross-account access, choose Download AWS CloudFormation template. This downloads an AWS CloudFormation template that you can use to create an AWS CloudFormation stack. This stack creates an AWS Identity and Access Management role that grants Firewall Manager cross-account permissions to manage Fortigate CNF resources. For information about stacks, see Working with stacks in the AWS CloudFormation User Guide. To create a stack, you'll need the account ID from the Fortigate CNF portal. 16. Choose Next. 17. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 18. Choose Next. 19. Review the new policy settings and return to any pages where you need to any adjustments. Check to be sure that Policy actions is set to Identify resources that don’t comply with the policy rules, but don’t auto remediate. This allows you to review the changes that your policy would make before you enable them. 20. When you are satisﬁed with the policy, choose Create policy. In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending status is replaced with account counts, you can choose the policy name to explore the Setting up Fortigate CNF policies 1035 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy For more information about Firewall Manager Fortigate CNF policies, see Using Fortigate Cloud Native Firewall (CNF) as a Service policies for Firewall Manager. Using AWS Firewall Manager policies AWS Firewall Manager provides the following types of policies. For each policy type, you deﬁne the: • AWS WAF policy – Firewall Manager supports AWS WAF and AWS WAF Classic policies. For both versions, you deﬁne which resources are protected by the policy. • The AWS WAF policy type takes sets of rule groups to run ﬁrst and last in the web ACL. Then, in the accounts where you apply the web ACL, the account owner can add rules and rule groups to run in between
waf-dg-384	waf-dg.pdf	384	Firewall (CNF) as a Service policies for Firewall Manager. Using AWS Firewall Manager policies AWS Firewall Manager provides the following types of policies. For each policy type, you deﬁne the: • AWS WAF policy – Firewall Manager supports AWS WAF and AWS WAF Classic policies. For both versions, you deﬁne which resources are protected by the policy. • The AWS WAF policy type takes sets of rule groups to run ﬁrst and last in the web ACL. Then, in the accounts where you apply the web ACL, the account owner can add rules and rule groups to run in between the two sets. • The AWS WAF Classic policy type takes a single rule group to run in the web ACL. • Shield Advanced policy – This policy type applies Shield Advanced protections throughout your organization for the resource types that you specify. • Amazon VPC security group policy – This policy type gives you control over security groups that are in use throughout your organization and lets you enforce a baseline set of rules across your organization. • Amazon VPC network access control list (ACL) policy – This policy type gives you control over network ACLs that are in use throughout your organization and lets you enforce a baseline set of network ACLs across your organization. • Network Firewall policy – This policy type applies AWS Network Firewall protection to your organization's VPCs. • Amazon Route 53 Resolver DNS Firewall policy – This policy applies DNS Firewall protections to your organization's VPCs. • Third-party ﬁrewall policy – This policy type applies third-party ﬁrewall protections. Third- party ﬁrewalls are available by subscription through the AWS Marketplace console at AWS Marketplace. • Palo Alto Networks Cloud NGFW policy – This policy type applies Palo Alto Networks Cloud Next Generation Firewall (NGFW) protections and Palo Alto Networks Cloud NGFW rulestacks to your organization's VPCs. Using AWS Firewall Manager policies 1036 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Fortigate Cloud Native Firewall (CNF) as a Service policy – This policy type applies Fortigate Cloud Native Firewall (CNF) as a Service protections. Fortigate CNF is a cloud-centered solution that blocks Zero-Day threats and secures cloud infrastructures with industry-leading advanced threat prevention, smart web application ﬁrewalls (WAF), and API protection. A Firewall Manager policy is speciﬁc to the individual policy type. If you want to enforce multiple policy types across accounts, you can create multiple policies. You can create more than one policy for each type. If you add a new account to an organization that you created with AWS Organizations, Firewall Manager automatically applies the policy to the resources in that account that are within scope of the policy. General settings for AWS Firewall Manager policies AWS Firewall Manager managed policies have some common settings and behaviors. For all, you specify a name and deﬁne the scope of the policy, and you can use resource tagging to control policy scope. You can choose to view the accounts and resources that are out of compliance without taking corrective action or to automatically remediate noncompliant resources. For information about policy scope, see Using the AWS Firewall Manager policy scope. Creating an AWS Firewall Manager policy The steps for creating a policy vary between the diﬀerent policy types. Make sure to use the procedure for the type of policy that you need. Important AWS Firewall Manager doesn't support Amazon Route 53 or AWS Global Accelerator. If you want to protect these resources with Shield Advanced, you can't use a Firewall Manager policy. Instead, follow the instructions in Adding AWS Shield Advanced protection to AWS resources. Topics • Creating an AWS Firewall Manager policy for AWS WAF General settings 1037 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • Creating an AWS Firewall Manager policy for AWS WAF Classic • Creating an AWS Firewall Manager policy for AWS Shield Advanced • Creating an AWS Firewall Manager common security group policy • Creating an AWS Firewall Manager content audit security group policy • Creating an AWS Firewall Manager usage audit security group policy • Creating an AWS Firewall Manager network ACL policy • Creating an AWS Firewall Manager policy for AWS Network Firewall • Creating an AWS Firewall Manager policy for Amazon Route 53 Resolver DNS Firewall • Creating an AWS Firewall Manager policy for Palo Alto Networks Cloud NGFW • Creating an AWS Firewall Manager policy for Fortigate Cloud Native Firewall (CNF) as a Service Creating an AWS Firewall Manager policy for AWS WAF In a Firewall Manager AWS WAF policy, you can use managed rule groups, which AWS and AWS Marketplace sellers create and maintain for you. You can also create and use your own rule groups. For more information about rule groups, see AWS WAF rule groups. If
waf-dg-385	waf-dg.pdf	385	Network Firewall • Creating an AWS Firewall Manager policy for Amazon Route 53 Resolver DNS Firewall • Creating an AWS Firewall Manager policy for Palo Alto Networks Cloud NGFW • Creating an AWS Firewall Manager policy for Fortigate Cloud Native Firewall (CNF) as a Service Creating an AWS Firewall Manager policy for AWS WAF In a Firewall Manager AWS WAF policy, you can use managed rule groups, which AWS and AWS Marketplace sellers create and maintain for you. You can also create and use your own rule groups. For more information about rule groups, see AWS WAF rule groups. If you want to use your own rule groups, create those before you create your Firewall Manager AWS WAF policy. For guidance, see Managing your own rule groups. To use an individual custom rule, you must deﬁne your own rule group, deﬁne your rule within that, and then use the rule group in your policy. For information about Firewall Manager AWS WAF policies, see Using AWS WAF policies with Firewall Manager. To create a Firewall Manager policy for AWS WAF (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Creating a policy 1038 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 2. In the navigation pane, choose Security policies. 3. Choose Create policy. 4. 5. For Policy type, choose AWS WAF. For Region, choose an AWS Region. To protect Amazon CloudFront distributions, choose Global. To protect resources in multiple Regions (other than CloudFront distributions), you must create separate Firewall Manager policies for each Region. 6. Choose Next. 7. For Policy name, enter a descriptive name. Firewall Manager includes the policy name in the names of the web ACLs that it manages. The web ACL names have FMManagedWebACLV2- followed by the policy name that you enter here, -, and the web ACL creation timestamp, in UTC milliseconds. For example, FMManagedWebACLV2-MyWAFPolicyName-1621880374078. 8. For Web request body inspection, optionally change the body size limit. For information about body inspection size limits, including pricing considerations, see Managing body inspection size limits for AWS WAF in the AWS WAF Developer Guide. 9. Under Policy rules, add the rule groups that you want AWS WAF to evaluate ﬁrst and last in the web ACL. To use AWS WAF managed rule group versioning, toggle Enable versioning. The individual account managers can add rules and rule groups in between your ﬁrst rule groups and your last rule groups. For more information about using AWS WAF rule groups in Firewall Manager policies for AWS WAF, see Using AWS WAF policies with Firewall Manager. (Optional) To customize how your web ACL uses the rule group, choose Edit. The following are common customization settings: • For managed rule groups, override the rule actions for some or all rules. If you don't deﬁne an override action for a rule, the evaluation uses the rule action that's deﬁned inside the rule group. For information about this option, see Overriding rule group actions in AWS WAF in the AWS WAF Developer Guide. • Some managed rule groups require you to provide additional conﬁguration. See the documentation from your managed rule group provider. For information speciﬁc to the AWS Managed Rules rule groups, see AWS Managed Rules for AWS WAF in the AWS WAF Developer Guide. When you're ﬁnished with your settings, choose Save rule. Creating a policy 1039 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 10. Set the default action for the web ACL. This is the action that AWS WAF takes when a web request doesn't match any of the rules in the web ACL. You can add custom headers with the Allow action, or custom responses for the Block action. For more information about default web ACL actions, see Setting the web ACL default action in AWS WAF. For information about setting custom web requests and responses, see Customized web requests and responses in AWS WAF. 11. For Logging conﬁguration, choose Enable logging to turn on logging. Logging provides detailed information about traﬃc that is analyzed by your web ACL. Choose the Logging destination, and then choose the logging destination that you conﬁgured. You must choose a logging destination whose name begins with aws-waf-logs-. For information about conﬁguring an AWS WAF logging destination, see Using AWS WAF policies with Firewall Manager. 12. (Optional) If you don't want certain ﬁelds and their values included in the logs, redact those ﬁelds. Choose the ﬁeld to redact, and then choose Add. Repeat as necessary to redact additional ﬁelds. The redacted ﬁelds appear
waf-dg-386	waf-dg.pdf	386	conﬁguration, choose Enable logging to turn on logging. Logging provides detailed information about traﬃc that is analyzed by your web ACL. Choose the Logging destination, and then choose the logging destination that you conﬁgured. You must choose a logging destination whose name begins with aws-waf-logs-. For information about conﬁguring an AWS WAF logging destination, see Using AWS WAF policies with Firewall Manager. 12. (Optional) If you don't want certain ﬁelds and their values included in the logs, redact those ﬁelds. Choose the ﬁeld to redact, and then choose Add. Repeat as necessary to redact additional ﬁelds. The redacted ﬁelds appear as REDACTED in the logs. For example, if you redact the URI ﬁeld, the URI ﬁeld in the logs will be REDACTED. 13. (Optional) If you don't want to send all requests to the logs, add your ﬁltering criteria and behavior. Under Filter logs, for each ﬁlter that you want to apply, choose Add ﬁlter, then choose your ﬁltering criteria and specify whether you want to keep or drop requests that match the criteria. When you ﬁnish adding ﬁlters, if needed, modify the Default logging behavior. For more information, see Finding your web ACL records in the AWS WAF Developer Guide. 14. You can deﬁne a Token domain list to enable token sharing between protected applications. Tokens are used by the CAPTCHA and Challenge actions and by the application integration SDKs that you implement when you use the AWS Managed Rules rule groups for AWS WAF Fraud Control account takeover prevention (ATP) and AWS WAF Bot Control. Public suﬃxes aren't allowed. For example, you can't use gov.au or co.uk as a token domain. By default, AWS WAF accepts tokens only for the domain of the protected resource. If you add token domains in this list, AWS WAF accepts tokens for all domains in the list and for the domain of the associated resource. For more information, see AWS WAF web ACL token domain list conﬁguration in the AWS WAF Developer Guide. You can only change the web ACL's CAPTCHA and challenge immunity times when you edit an existing web ACL. You can ﬁnd these settings under the Firewall Manager Policy details page. For information about these settings, see Setting timestamp expiration and token Creating a policy 1040 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide immunity times in AWS WAF. If you update the Association conﬁg, CAPTCHA, Challenge, or Token domain list settings in an existing policy, Firewall Manager will overwrite the your local web ACLs with the new values. However, if you don't update the policy's Association conﬁg, CAPTCHA, Challenge, or Token domain list settings, then the values in your local web ACLs will remain unchanged. For information about this option, see CAPTCHA and Challenge in AWS WAF in the AWS WAF Developer Guide. 15. Under Web ACL management, choose how Firewall Manager manages web ACL creation and clean up. a. For Manage unassociated web ACLs, choose whether Firewall Manager manages unassociated web ACLs. With this option, Firewall Manager creates web ACLs for the accounts within policy scope only if the web ACLs will be used by at least one resource. When an account comes into policy scope, Firewall Manager automatically creates a web ACL in the account if at least one resource will use it. When you enable this option, Firewall Manager performs a one-time cleanup of unassociated web ACLs in your account. The cleanup process can take several hours. If a resource leaves policy scope after Firewall Manager creates a web ACL, Firewall Manager disassociates the resource from the web ACL, but doesn't clean up the unassociated web ACL. Firewall Manager only cleans up unassociated web ACLs when you ﬁrst enable management of unassociated web ACLs in the policy. b. For Web ACL source, specify whether to create all new web ACLs for in-scope resources or to retroﬁt existing web ACLs where possible. Firewall Manager can retroﬁt web ACLs that are owned by in-scope accounts. The default behavior is to create all new web ACLs. If you choose this, all web ACLs managed by Firewall Manager will have names that begin with FMManagedWebACLV2. If you choose to retroﬁt existing web ACLs, the retroﬁtted web ACLs will have their original names and the ones created by Firewall Manager will have names that begin with FMManagedWebACLV2. 16. For Policy action, if you want to create a web ACL in each applicable account within the organization, but not apply the web ACL to any resources yet, choose Identify resources that don't comply with the policy rules, but don't auto remediate and don't choose Manage unassociated web ACLs. You can change these options later. If instead you want to automatically apply the policy to existing in-scope resources, choose Auto remediate any noncompliant resources. If Manage unassociated web ACLs
waf-dg-387	waf-dg.pdf	387	ACLs will have their original names and the ones created by Firewall Manager will have names that begin with FMManagedWebACLV2. 16. For Policy action, if you want to create a web ACL in each applicable account within the organization, but not apply the web ACL to any resources yet, choose Identify resources that don't comply with the policy rules, but don't auto remediate and don't choose Manage unassociated web ACLs. You can change these options later. If instead you want to automatically apply the policy to existing in-scope resources, choose Auto remediate any noncompliant resources. If Manage unassociated web ACLs is disabled, Creating a policy 1041 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide the Auto remediate any noncompliant resources option creates a web ACL in each applicable account within the organization and associates the web ACL with the resources in the accounts. If Manage unassociated web ACLs is enabled, the Auto remediate any noncompliant resources option only creates and associates a web ACL in accounts that have resources eligible for association to the web ACL. When you choose Auto remediate any noncompliant resources, you can also choose to remove existing web ACL associations from in-scope resources, for the web ACLs that aren't managed by another active Firewall Manager policy. If you choose this option, Firewall Manager ﬁrst associates the policy's web ACL with the resources, and then removes the prior associations. If a resource has an association with another web ACL that's managed by a diﬀerent active Firewall Manager policy, this choice doesn't aﬀect that association. 17. Choose Next. 18. For AWS accounts this policy applies to, choose the option as follows: • If you want to apply the policy to all accounts in your organization, leave the default selection, Include all accounts under my AWS organization. • If you want to apply the policy only to speciﬁc accounts or accounts that are in speciﬁc AWS Organizations organizational units (OUs), choose Include only the speciﬁed accounts and organizational units, and then add the accounts and OUs that you want to include. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. • If you want to apply the policy to all but a speciﬁc set of accounts or AWS Organizations organizational units (OUs), choose Exclude the speciﬁed accounts and organizational units, and include all others, and then add the accounts and OUs that you want to exclude. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. You can only choose one of the options. After you apply the policy, Firewall Manager automatically evaluates any new accounts against your settings. For example, if you include only speciﬁc accounts, Firewall Manager doesn't apply the policy to any new accounts. As another example, if you include an OU, when you add an account to the OU or to any of its child OUs, Firewall Manager automatically applies the policy to the new account. 19. For Resource type, choose the types of resources that you want to protect. Creating a policy 1042 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 20. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 21. Choose Next. 22. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 23. Choose Next. 24. Review the new policy settings and return to any pages where you need to any adjustments. When you are satisﬁed with the policy, choose Create policy. In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy Creating an AWS Firewall Manager policy for AWS
waf-dg-388	waf-dg.pdf	388	need to any adjustments. When you are satisﬁed with the policy, choose Create policy. In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy Creating an AWS Firewall Manager policy for AWS WAF Classic To create a Firewall Manager policy for AWS WAF Classic (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. In the navigation pane, choose Security policies. Creating a policy 1043 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 3. Choose Create policy. 4. 5. For Policy type, choose AWS WAF Classic. If you already created the AWS WAF Classic rule group that you want to add to the policy, choose Create an AWS Firewall Manager policy and add existing rule groups. If you want to create a new rule group, choose Create a Firewall Manager policy and add a new rule group. 6. For Region, choose an AWS Region. To protect Amazon CloudFront resources, choose Global. To protect resources in multiple Regions (other than CloudFront resources), you must create separate Firewall Manager policies for each Region. 7. Choose Next. 8. If you are creating a rule group, follow the instructions in Creating an AWS WAF Classic rule group. After you create the rule group, continue with the following steps. 9. Enter a policy name. 10. If you are adding an existing rule group, use the dropdown menu to select a rule group to add, and then choose Add rule group. 11. A policy has two possible actions: Action set by rule group and Count. If you want to test the policy and rule group, set the action to Count. This action overrides any block action speciﬁed by the rules in the rule group. That is, if the policy's action is set to Count, those requests are only counted and not blocked. Conversely, if you set the policy's action to Action set by rule group, actions of the rule group rules are used. Choose the appropriate action. 12. Choose Next. 13. For AWS accounts this policy applies to, choose the option as follows: • If you want to apply the policy to all accounts in your organization, leave the default selection, Include all accounts under my AWS organization. • If you want to apply the policy only to speciﬁc accounts or accounts that are in speciﬁc AWS Organizations organizational units (OUs), choose Include only the speciﬁed accounts and organizational units, and then add the accounts and OUs that you want to include. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. • If you want to apply the policy to all but a speciﬁc set of accounts or AWS Organizations organizational units (OUs), choose Exclude the speciﬁed accounts and organizational units, and include all others, and then add the accounts and OUs that you want to exclude. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. Creating a policy 1044 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide You can only choose one of the options. After you apply the policy, Firewall Manager automatically evaluates any new accounts against your settings. For example, if you include only speciﬁc accounts, Firewall Manager doesn't apply the policy to any new accounts. As another example, if you include an OU, when you add an account to the OU or to any of its child OUs, Firewall Manager automatically applies the policy to the new account. 14. Choose the type of resource that you want to protect. 15. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for
waf-dg-389	waf-dg.pdf	389	when you add an account to the OU or to any of its child OUs, Firewall Manager automatically applies the policy to the new account. 14. Choose the type of resource that you want to protect. 15. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 16. If you want to automatically apply the policy to existing resources, choose Create and apply this policy to existing and new resources. This option creates a web ACL in each applicable account within an AWS organization and associates the web ACL with the resources in the accounts. This option also applies the policy to all new resources that match the preceding criteria (resource type and tags). Alternatively, if you choose Create policy but do not apply the policy to existing or new resources, Firewall Manager creates a web ACL in each applicable account within the organization, but doesn't apply the web ACL to any resources. You must apply the policy to resources later. Choose the appropriate option. 17. For Replace existing associated web ACLs, you can choose to remove any web ACL associations that are currently deﬁned for in-scope resources, and then replace them with associations to the web ACLs that you are creating with this policy. By default, Firewall Manager doesn't remove existing web ACL associations before it adds the new ones. If you want to remove the existing ones, choose this option. 18. Choose Next. 19. Review the new policy. To make any changes, choose Edit. When you are satisﬁed with the policy, choose Create and apply policy. Creating a policy 1045 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Creating an AWS Firewall Manager policy for AWS Shield Advanced To create a Firewall Manager policy for Shield Advanced (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. In the navigation pane, choose Security policies. 3. Choose Create policy. 4. For Policy type, choose Shield Advanced. To create a Shield Advanced policy, you must be subscribed to Shield Advanced. If you are not subscribed, you are prompted to do so. For information about the cost for subscribing, see AWS Shield Advanced Pricing. 5. For Region, choose an AWS Region. To protect Amazon CloudFront distributions, choose Global. For Region choices other than Global, to protect resources in multiple Regions, you must create a separate Firewall Manager policy for each Region. 6. Choose Next. 7. 8. For Name, enter a descriptive name. For Global Region policies only, you can choose whether you want to manage Shield Advanced automatic application layer DDoS mitigation. For information about this Shield Advanced feature, see Automating application layer DDoS mitigation with Shield Advanced . You can choose to enable or disable automatic mitigation, or you can choose to ignore it. If you choose to ignore it, Firewall Manager doesn't manage automatic mitigation at all for the Shield Advanced protections. For more information about these policy options, see Using Automatic application layer DDoS mitigation with Firewall Manager Shield Advanced policies. Creating a policy 1046 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 9. Under Web ACL management, if you want Firewall Manager to manage unassociated web ACLs, then enable Manage unassociated web ACLs. With this option, Firewall Manager creates web ACLs in the accounts within policy scope only if the web ACLs will be used by at least one resource. If at any time an account comes into policy scope, Firewall Manager automatically creates a web ACL in the account if at least one resource will use the web ACL. Upon enablement of this option, Firewall Manager performs a one-time cleanup of unassociated web ACLs in your account. The cleanup process can take several hours. If a resource leaves policy scope after Firewall Manager creates a web ACL, Firewall Manager will not disassociate the resource from the web ACL. To include the web ACL in the one-time cleanup, you must ﬁrst manually disassociate the resources from the web ACL and then enable Manage unassociated web ACLs. 10. For Policy action, we recommend creating
waf-dg-390	waf-dg.pdf	390	creates a web ACL in the account if at least one resource will use the web ACL. Upon enablement of this option, Firewall Manager performs a one-time cleanup of unassociated web ACLs in your account. The cleanup process can take several hours. If a resource leaves policy scope after Firewall Manager creates a web ACL, Firewall Manager will not disassociate the resource from the web ACL. To include the web ACL in the one-time cleanup, you must ﬁrst manually disassociate the resources from the web ACL and then enable Manage unassociated web ACLs. 10. For Policy action, we recommend creating the policy with the option that doesn't automatically remediate noncompliant resources. When you disable automatic remediation, you can assess the eﬀects of your new policy before you apply it. When you are satisﬁed that the changes are what you want, then edit the policy and change the policy action to enable automatic remediation. If instead you want to automatically apply the policy to existing in-scope resources, choose Auto remediate any noncompliant resources. This option applies Shield Advanced protections for each applicable account within the AWS organization and each applicable resource in the accounts. For Global Region policies only, if you choose Auto remediate any noncompliant resources, you can also choose to have Firewall Manager automatically replace any existing AWS WAF Classic web ACL associations with new associations to web ACLs that were created using the latest version of AWS WAF (v2). If you choose this, Firewall Manager removes the associations with the earlier version web ACLs and creates new associations with latest version web ACLs, after creating new empty web ACLs in any in-scope accounts that don't already have them for the policy. For more information about this option, see Replace AWS WAF Classic web ACLs with latest version web ACLs. 11. Choose Next. 12. For AWS accounts this policy applies to, choose the option as follows: • If you want to apply the policy to all accounts in your organization, keep the default selection, Include all accounts under my AWS organization. • If you want to apply the policy only to speciﬁc accounts or accounts that are in speciﬁc AWS Organizations organizational units (OUs), choose Include only the speciﬁed accounts Creating a policy 1047 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide and organizational units, and then add the accounts and OUs that you want to include. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. • If you want to apply the policy to all but a speciﬁc set of accounts or AWS Organizations organizational units (OUs), choose Exclude the speciﬁed accounts and organizational units, and include all others, and then add the accounts and OUs that you want to exclude. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. You can only choose one of the options. After you apply the policy, Firewall Manager automatically evaluates any new accounts against your settings. For example, if you include only speciﬁc accounts, Firewall Manager doesn't apply the policy to any new accounts. As another example, if you include an OU, when you add an account to the OU or to any of its child OUs, Firewall Manager automatically applies the policy to the new account. 13. Choose the type of resource that you want to protect. Firewall Manager does not support Amazon Route 53 or AWS Global Accelerator. If you need to use Shield Advanced to protect resources from these services, you can't use a Firewall Manager policy. Instead, follow the Shield Advanced guidance at Adding AWS Shield Advanced protection to AWS resources. 14. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 15. Choose Next. 16. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 17. Choose Next. 18. Review the new policy settings and return to any pages where you need to any adjustments. Creating a policy 1048 AWS WAF, AWS Firewall Manager, and AWS
waf-dg-391	waf-dg.pdf	391	have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 15. Choose Next. 16. For Policy tags, add any identifying tags that you want to add to the Firewall Manager policy resource. For more information about tags, see Working with Tag Editor. 17. Choose Next. 18. Review the new policy settings and return to any pages where you need to any adjustments. Creating a policy 1048 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide When you are satisﬁed with the policy, choose Create policy. In the AWS Firewall Manager policies pane, your policy should be listed. It will probably indicate Pending under the accounts headings and it will indicate the status of the Automatic remediation setting. The creation of a policy can take several minutes. After the Pending status is replaced with account counts, you can choose the policy name to explore the compliance status of the accounts and resources. For information, see Viewing compliance information for an AWS Firewall Manager policy Creating an AWS Firewall Manager common security group policy For information about how common security group policies work, see Using common security group policies with Firewall Manager. To create a common security group policy, you must have a security group already created in your Firewall Manager administrator account that you want to use as the primary for your policy. You can manage security groups through Amazon Virtual Private Cloud (Amazon VPC) or Amazon Elastic Compute Cloud (Amazon EC2). For information, see Working with Security Groups in the Amazon VPC User Guide. To create a common security group policy (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. In the navigation pane, choose Security policies. 3. Choose Create policy. 4. 5. 6. For Policy type, choose Security group. For Security group policy type, choose Common security groups. For Region, choose an AWS Region. Creating a policy 1049 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 7. Choose Next. 8. 9. For Policy name, enter a friendly name. For Policy rules, do the following: a. From the rules option, choose the restrictions that you want to apply to the security group rules and the resources that are within policy scope. If you choose Distribute tags from the primary security group to the security groups created by this policy, then you must also select Identify and report when the security groups created by this policy become non-compliant. Important Firewall Manager won't distribute system tags added by AWS services into the replica security groups. System tags begin with the aws: preﬁx. Additionally, Firewall Manager won't update the tags of existing security groups or create new security groups if the policy has tags that conﬂict with the organization's tag policy. For information about tag policies, see Tag policies in the AWS Organizations User Guide. If you choose Distribute security group references from the primary security group to the security groups created by this policy, Firewall Manager only distributes the security group references if they have an active peering connection in Amazon VPC. For information about this option, see Policy rules settings. b. For Primary security groups, choose Add security groups, and then choose the security groups that you want to use. Firewall Manager populates the list of security groups from all Amazon VPC instances in the Firewall Manager administrator account. By default, the maximum number of primary security groups per policy is 3. For information about this setting, see AWS Firewall Manager quotas. c. For Policy action, we recommend creating the policy with the option that doesn't automatically remediate. This allows you to assess the eﬀects of your new policy before you apply it. When you are satisﬁed that the changes are what you want, then edit the policy and change the policy action to enable automatic remediation of noncompliant resources. 10. Choose Next. Creating a policy 1050 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 11. For AWS accounts this policy applies to, choose the option as follows: • If you want to apply the policy to all accounts in your organization, leave the default selection, Include all accounts under my AWS organization. • If you want to apply the policy only to speciﬁc accounts or accounts that are in speciﬁc AWS Organizations organizational units (OUs), choose Include only the speciﬁed accounts and organizational units, and then add
waf-dg-392	waf-dg.pdf	392	policy action to enable automatic remediation of noncompliant resources. 10. Choose Next. Creating a policy 1050 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide 11. For AWS accounts this policy applies to, choose the option as follows: • If you want to apply the policy to all accounts in your organization, leave the default selection, Include all accounts under my AWS organization. • If you want to apply the policy only to speciﬁc accounts or accounts that are in speciﬁc AWS Organizations organizational units (OUs), choose Include only the speciﬁed accounts and organizational units, and then add the accounts and OUs that you want to include. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. • If you want to apply the policy to all but a speciﬁc set of accounts or AWS Organizations organizational units (OUs), choose Exclude the speciﬁed accounts and organizational units, and include all others, and then add the accounts and OUs that you want to exclude. Specifying an OU is the equivalent of specifying all accounts in the OU and in any of its child OUs, including any child OUs and accounts that are added at a later time. You can only choose one of the options. After you apply the policy, Firewall Manager automatically evaluates any new accounts against your settings. For example, if you include only speciﬁc accounts, Firewall Manager doesn't apply the policy to any new accounts. As another example, if you include an OU, when you add an account to the OU or to any of its child OUs, Firewall Manager automatically applies the policy to the new account. 12. For Resource type, choose the types of resources that you want to protect. For the resource type EC2 instance, you can choose to remediate all Amazon EC2 instances or only remediate instances that have just the default, primary elastic network interface (ENI). For the latter option, Firewall Manager doesn't remediate instances that have additional ENI attachments. Instead, when automatic remediation is enabled, Firewall Manager only marks the compliance status of these EC2 instances, and doesn't apply any remediation actions. See additional caveats and limitations for the Amazon EC2 resource type at Security group policy caveats and limitations. 13. For Resources, you can narrow the scope of the policy using tagging, by either including or excluding resources with the tags that you specify. You can use inclusion or exclusion, and not both. For more information about tags to deﬁne policy scope, see Using the AWS Firewall Manager policy scope. Creating a policy 1051 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Resource tags can only have non-null values. If you omit the value for a tag, Firewall Manager saves the tag with an empty string value: "". Resource tags only match with tags that have the same key and the same value. 14. For Shared VPC resources, if you want to apply the policy to resources in shared VPCs, in addition to the VPCs that the accounts own, select Include resources from shared VPCs. 15. Choose Next. 16. Review the policy settings to be sure they're what you want, and then choose Create policy. Firewall Manager creates a replica of the primary security group in every Amazon VPC instance contained within the in-scope accounts up to the supported Amazon VPC maximum quota per account. Firewall Manager associates the replica security groups to the resources that are within policy scope for each in-scope account. For more information about how this policy works, see Using common security group policies with Firewall Manager. Creating an AWS Firewall Manager content audit security group policy For information about how content audit security group policies work, see Using content audit security group policies with Firewall Manager. For some content audit policy settings, you must provide an audit security group for Firewall Manager to use as a template. For example, you might have an audit security group that contains all of the rules that you don't allow in any security group. You must create these audit security groups using your Firewall Manager administrator account, before you can use them in your policy. You can manage security groups through Amazon Virtual Private Cloud (Amazon VPC) or Amazon Elastic Compute Cloud (Amazon EC2). For information, see Working with Security Groups in the Amazon VPC User Guide. To create a content audit security group policy (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Creating a policy 1052 AWS WAF, AWS
waf-dg-393	waf-dg.pdf	393	your Firewall Manager administrator account, before you can use them in your policy. You can manage security groups through Amazon Virtual Private Cloud (Amazon VPC) or Amazon Elastic Compute Cloud (Amazon EC2). For information, see Working with Security Groups in the Amazon VPC User Guide. To create a content audit security group policy (console) 1. Sign in to the AWS Management Console using your Firewall Manager administrator account, and then open the Firewall Manager console at https://console.aws.amazon.com/wafv2/ fmsv2. For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. Creating a policy 1052 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide Note For information about setting up a Firewall Manager administrator account, see AWS Firewall Manager prerequisites. 2. In the navigation pane, choose Security policies. 3. Choose Create policy. 4. 5. 6. For Policy type, choose Security group. For Security group policy type, choose Auditing and enforcement of security group rules. For Region, choose an AWS Region. 7. Choose Next. 8. 9. For Policy name, enter a friendly name. For Policy rules, choose the managed or custom policy rules option that you want to use. a. For Conﬁgure managed audit policy rules, do the following: i. ii. For Conﬁgure security group rules to audit, select the type of security group rules that you want your audit policy to apply to. If you want to do things like audit rules based on the protocols, ports, and CIDR range settings that in your security groups, choose Audit overly permissive security group rules and select the options that you want. For the selection Rule allows all traﬃc, you can provide a custom application list to designate the applications that you want to audit. For information about custom application lists and how to use them in your policy, see Using managed lists and Using managed lists. For selections that use protocol lists, you can use existing lists and you can create new lists. For information about protocol lists and how to use them in your policy, see Using managed lists and Using managed lists. iii. If you want to audit high-risk based on their access to either reserved or non-reserved CIDR ranges, choose Audit high risk applications and select the options that you want. Creating a policy 1053 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide The following selections are mutually exclusive: Applications that can access only reserved CIDR ranges and Applications allowed to access non-reserved CIDR ranges. You can select at most one of them in any policy. For selections that use application lists, you can use existing lists and you can create new lists. For information about application lists and how to use them in your policy, see Using managed lists and Using managed lists. iv. Use the Overrides settings to explicitly override other settings in the policy. You can choose to always allow or always deny speciﬁc security group rules, regardless of whether they comply with the other options that you've set for the policy. For this option, you provide an audit security group as your allowed rules or denied rules template. For Audit security groups, choose Add audit security groups, and then choose the security group that you want to use. Firewall Manager populates the list of audit security groups from all Amazon VPC instances in the Firewall Manager administrator account. The default maximum quota for the number of audit security groups for a policy is one. For information about increasing the quota, see AWS Firewall Manager quotas. b. For Conﬁgure custom policy rules, do the following: i. From the rules options, choose whether to allow only the rules deﬁned in the audit security groups or deny all the rules. For information about this choice, see Using content audit security group policies with Firewall Manager. ii. For Audit security groups, choose Add audit security groups, and then choose the security group that you want to use. Firewall Manager populates the list of audit security groups from all Amazon VPC instances in the Firewall Manager administrator account. The default maximum quota for the number of audit security groups for a policy is one. For information about increasing the quota, see AWS Firewall Manager quotas. iii. For Policy action, you must create the policy with the option that doesn't automatically remediate. This allows you to assess the eﬀects of your new policy before you apply it. When you are satisﬁed that the changes are what you want, edit the policy and change the policy action to enable automatic remediation of noncompliant resources. 10. Choose Next. 11. For AWS accounts this policy applies to, choose the option as follows: Creating a policy 1054 AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide • If you want to apply the policy to

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.