ℹ️ Information: In this section, we’ll verify that our application is properly deployed behind the Application Load Balancer and functioning as expected. This testing phase ensures our infrastructure is correctly configured before proceeding to auto scaling implementation.
To test the deployment:
💡 Pro Tip: The DNS name of your Application Load Balancer follows the format name-1234567890.region.elb.amazonaws.com
and is globally resolvable, allowing access from anywhere with internet connectivity.
Upon successful connection, you should see the FCJ Management application interface:
To verify complete functionality, test the application’s data manipulation capabilities:
⚠️ Warning: If you encounter any errors during testing, verify that your security groups are properly configured to allow traffic on port 5000 and that your target group health checks are passing.
ℹ️ Information: In subsequent testing steps, we’ll focus on monitoring application metrics through Amazon CloudWatch. While reviewing these metrics, pay attention to any performance degradation that might occur during periods of increased load.
🔒 Security Note: All traffic to your application is now flowing through the Application Load Balancer, which provides an additional security layer by isolating your EC2 instances from direct internet access. Consider implementing AWS WAF with your ALB for additional protection against common web exploits.