Denial Of Service on Aws
How Denial Of Service Manifests in Aws
Denial of Service (DoS) attacks in Aws applications exploit the platform's scalability and distributed nature to overwhelm services and exhaust resources. The serverless architecture, while cost-effective, introduces unique DoS vectors that traditional monolithic applications don't face.
Resource exhaustion attacks target Aws Lambda's concurrency limits. Each Lambda function has a regional concurrency limit (default 1000 per region, adjustable up to 10,000). An attacker can trigger rapid, concurrent executions to exhaust these limits, causing legitimate requests to queue or fail with TooManyRequestsException. This manifests as:
Aws-Specific Detection
Detecting DoS attacks in Aws requires monitoring specific metrics and patterns across the serverless stack. CloudTrail logs provide the foundational audit trail, but specialized monitoring is essential.
CloudWatch metrics reveal the telltale signs. For Lambda functions, monitor:
Related CWEs: resourceConsumption
CWE ID Name Severity CWE-400 Uncontrolled Resource Consumption HIGH CWE-770 Allocation of Resources Without Limits MEDIUM CWE-799 Improper Control of Interaction Frequency MEDIUM CWE-835 Infinite Loop HIGH CWE-1050 Excessive Platform Resource Consumption MEDIUM