MISP codebase - Shared file-system between cluster nodes - Load-balancing between cluster nodes - Auto-scaling for availability and performance - Use encryption for both in-transit and at-rest - Leverage WAF and DoS protection
and scale databases - Automation for hardware provisioning, setup, patching and backups - Supports several engines (including MySQL) - DR via auto-updating DNS endpoint - Read replica (more on this later) $ cat aws-rds.txt
file system - Amazon maintains mount helper for most distros - Easy to mount via TLS - No upfront requirements for provisioning - Will hold MISP codebase (/var/www/MISP) $ cat aws-efs.txt
(think VMs) in AWS - Friendly GNU/Linux ecosystem - These instances will be our cluster nodes - Part of our Auto-Scaling Group (ASG) - Holds AWS SES configuration, PHP, Apache and MISP in AWS EFS mount point (/var/www/MISP) - Will be the source for the AMI that will be used on auto-scaling by other cluster nodes $ cat aws-ec2.txt
for access to our EC2 instances - Distributes traffic across multiple targets - Keeps an eye on instance health - Interacts with our auto-scaling group - Source for our CDN? $ cat aws-elb.txt
- Inline/Always-on detection and mitigation - Turned on by default (AWS Shield Standard) - AWS Shield Advanced supported for both ALB and Cloudfront $ cat aws-shield.txt
EFS share - Create instance in RDS - Create OS and mount EFS; Configure; Tweak it - Create an AMI that will be used for future nodes - Install MISP in EFS - DB Connect to RDS - Create ASG $ cat INSTALL.txt
.html file (ping.html) - Health check type: Elastic Load Balancer - ELB Health Check fails: - New instance is spawned based on AMI - Failed instance is terminated $ cat chaos-apache.txt