2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
That should work, I would troubleshoot it in this order:
- Is the Fargate task in a public subnet? (If not, you need to be on a VPN)
- Are you testing with the public IP? (If not, you need to be on a VPN)
- Are you using the correct port? (ALB often reroutes from 443 to 80 after SSL resolution, if you bypass the ALB, you need to go straight to 80)
- Is the Security group open to your IP and port?
Good luck :)
con risposta 2 anni fa
0
To use a static IP or Elastic IP with fargate tasks you must first create a Fargate service with an ALB or NLB and then attach the Elastic IP of the task to the load balancer.
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa