- Más nuevo
- Más votos
- Más comentarios
Hello.
What settings are you making in the ALB security group and EC2 security group?
Maybe the security group doesn't allow the necessary communication?
Also, have you successfully set the domain in ALB?
Is it possible to resolve names using the dig command?
both inbound and outbound for ALB security group has the source 0.0.0.0/0 with the correct ports found in Inbound. Same goes for the EC2 security Group. It is weird since there are no changes on this part since but it might be affected by API deployment in Elastic Beanstalk which should not be the case. Do you recommend to rebuild the environment but I'm hesitant since it might ruin the environment itself which happened to me before.
Is there a problem with the DNS settings used on the LAN?
it seems that Domain is not handled by AWS but and external one. I thought ACM is the one handle the Custom domain but it only handles the certificate. No Domain found in in Route 53.
Contenido relevante
- ¿Cómo puedo transferir variables de mi entorno de Elastic Beanstalk a instancias de Linux y Windows?OFICIAL DE AWSActualizada hace 2 años
- ¿Cómo puedo solucionar una advertencia de estado amarillo o rojo en mi entorno de Elastic Beanstalk?OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 9 meses
- OFICIAL DE AWSActualizada hace 2 años
Also tried nslookup it works in Wi-Fi but in LAN it does not.