What should a SysOps administrator do to resolve this issue?
Configure an Amazon CloudFront distribution with the ALB as the origin.
Enable sticky sessions (session affinity) for the target group of EC2 instances.
Redeploy the EC2 instances in a spread placement group.
Replace the ALB with a Network Load Balancer.
Explanations:
A CloudFront distribution with the ALB as the origin can help with content delivery performance but will not solve session persistence issues, which are likely causing the login prompts.
Enabling sticky sessions (session affinity) allows the ALB to route subsequent requests from a user to the same EC2 instance, ensuring session continuity and resolving login prompt issues.
A spread placement group helps distribute instances across distinct hardware to improve fault tolerance but does not address session management, which is likely causing the login issue.
A Network Load Balancer is better suited for handling TCP traffic and would not resolve session persistence issues. The ALB is better suited for handling HTTP/HTTPS traffic with session affinity.
As I understand it, the answer is:
Enable sticky sessions (session affinity) for the target group of EC2 instances.
I calculate that the answer is:
Enable sticky sessions (session affinity) for the target group of EC2 instances.