AWS introduced CloudFront Virtual Private Cloud (VPC) Origins to enable delivery from applications in private VPC subnets without access to the internet.
Deploying Fider as a private application enhances security by hiding backend services and using CloudFront as the sole entry point.
Creating an Internal Application Load Balancer involves setting it up in private subnets and configuring security groups to only allow CloudFront's IP ranges.
CloudFront VPC origin creation involves selecting an internal ALB's ARN with HTTPS protocol for optimized performance and improved security.
Creating a CloudFront Distribution includes setting up origin shield, cache behavior, security headers, and enabling Web Application Firewall for added protection.
Spinning up ECS and RDS infrastructure is essential for deploying applications securely within the AWS environment.
Monitoring CloudFront and WAF logs is crucial for analyzing performance metrics, response times, and fine-tuning security rules to prevent attacks.
Considerations like using VPC Endpoints for external OAuth providers, potential attack vectors with CloudFront and ALB, and mTLS support in Fider should be taken into account for enhanced security.
AWS WAF now supports sending logs to CloudWatch logs, providing insights into rule evaluation outcomes and sampled requests for analysis.
Enabling logging for AWS WAF helps in monitoring and analyzing rule performance and evaluating the level of protection based on specific needs.
Implementing CloudFront VPC Origin and following recommended security practices ensure a secure deployment of Fider as a private application on AWS.