1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
2
The IPs from the printscreen belongs an Application Load Balancer (ALB), at least the filter it is using.
ALB doesn't have static IPs, like Network Load Balancer (NLB).
Network Interfaces for NLB will have a description with pattern "ELB net/xxxxxxxxxxxxxx"
Network Interfaces for ALB will have a description with pattern "ELB app/xxxxxxxxxxxxxx"
respondido hace un año
Hi Leonardo!
thanks for your reply and explanation! It is helpful! :) We had a problem that target server standing behind this LB haven't got a traffic because firewall rules disallowed new IP. We solved it by changing a rule from type of IP to type of Security group. Security group is static.
Best, Dmitry
Contenido relevante
- OFICIAL DE AWSActualizada hace 8 meses
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 2 años
Have you redeployed/reprovisioned it with different info?
Hi Dmitry,
I would not expect this behavior at all. Do you have AWS config activated in your account? Can you verify in the configuration timeline that this modification was indeed induced by the service?
@alatech, no we haven't redeployed/reprovisioned anything.
Hi Andreas,
thanks for your reply. No, we haven't enabled AWS Config, it seems it might help, I tried it, I selected
AWS EC2 NetworkInterface
as a target resource, but I have stuck on choosing AWS Managed Rules for it - the urls looks strange and not relevant on what we need to track - we need to track address change, but all rules are bout checking dropping HTTP headers, checking SSL certificates etc. How I should correctly set this up to catch this type of change (IP change)?Thanks, Dmitry