When an administrator attempts to log in to the Self Service Password Reset Administration Portal, the 404 error message is displayed due to any of the following reasons:
Reason 1: If the Application Load Balancer is not created through the Helm Installation. See Workaround 1.
Reason 2: If the pods are not created during the Helm installation process. To resolve this issue, ensure that subnets are correctly tagged to enable proper creation and management of load balancers. See Workaround 2.
Reason 3: If the listener configuration in the application load balancer are not correctly and consistently routing the traffic to the Stateful application. See Workaround 3.
Workaround 1: To resolve the pod creation issue, perform the following steps:
Run the following command to check the status of Pods:
kubctl get pods
If the Status field in the output displays Pending for a longer time, perform Step 6 to Step 8.
Log in to AWS Management Console and navigate to the EC2 dashboard.
In the left navigation menu, click Load Balancers.
Check if the Application Load Balancer has been created. If not listed, proceed with the following steps.
Ensure to create the EFS entry in the same subnet as your VPC/EC2 subnets. Delete any other EFS subnets that do not match your VPC/EC2 subnets.
Uninstall the Helm. Refer Uninstalling Self Service Password Reset Helm deployment.
Re-install the Helm. Perform Step 6 to Step 9 described in Deploying Self Service Password Reset container on amazon EKS with EC2 instances.
Workaround 2: To resolve the Application Load Balancer issue, perform the following steps:
Log in to AWS Management Console and navigate to the EC2 dashboard.
In the left navigation menu, click Load Balancers.
Check if the Application Load Balancer has been created. If it is not listed, proceed with the following steps.
Ensure to create the EFS entry in the same subnet as your VPC/EC2 subnets. Delete any other EFS subnets that do not match your VPC/EC2 subnets.
In the left navigation menu, click to Virtual private cloud.
In the left navigation menu, click Subnet, and then click your private subnet.
Navigate to Tags, and click Manage tags.
Click Add new tag and enter kubernetes.io/role/internal-elb in the Enter key box.
In the Enter value box, enter 1.
Click Save.
Repeat the above steps for all private subnets.
Click your public subnet.
Navigate to Tags, and click Manage tags.
Click Add new tag and enter kubernetes.io/role/elb in the Enter key box.
In the Enter value box, enter 1.
Click Save.
Repeat the above steps for all public subnets.
Uninstall the Helm. Refer Uninstalling Self Service Password Reset Helm deployment.
Re-install the Helm. Perform Step 6 to Step 9 described in Deploying Self Service Password Reset container on amazon EKS with EC2 instances.
Workaround 3: To edit the listeners configuration in the load balancer, perform the following steps:
Log in to AWS Console and navigate to the EC2 dashboard.
Click Load Balancers.
Select the load balancer.
Navigate to Listeners and rules.
Click HTTPS:443 protocol.
In the upper right corner of the HTTPS:443 pane, click Actions, and then click Edit listener.
Navigate to Routing actions and select Forward to target groups option.
In the Target Groups list, click the existing target group.
Select the Turn on target group stickiness check box.
In the Stickiness duration field, enter 1.
In the Unit of time list, click days.
Click Save changes.
Configure Application Load Balancer with Rout 53. For more information, see Routing traffic to an ELB load balancer section in the Amazon Route 53 Developer Guide.