- Newest
- Most votes
- Most comments
Hello,
I understand you have questions regarding credits in AWS Shield Advanced. From what I know Shield Advanced does not include credits for AWS ElastiCache Charges in the events of a DDoS attack.
Here is a list of charges that you can receive credits from: 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, and usage spikes on protected Amazon Elastic Compute Cloud (Amazon EC2) instances.
This link goes more in detail about requesting credits: https://docs.aws.amazon.com/waf/latest/developerguide/request-refund.html
Please contact if you have any further questions, and feel free to reach out to us via a support case to facilitate a discussion on the specifics of your resources.
To be more precise, 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 Amazon Elastic Compute Cloud (Amazon EC2) instances that were created by an auto-scaling policy in response to the attack that are behind a Protected Resource
I believe that as an Elasticache cluster using on-demand nodes has EC2 costs built into pricing, that you should be able to recoup the equivalent basic EC2 costs of your caching node types, however I have yet to see this tested in a 'real' cost protection request.
Relevant content
- asked 5 months ago
- asked 5 years ago
- asked 9 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago