Skip to main content

Load Averages slowly increase unless I disable CSF (Load Balanced AWS)

Comments

6 comments

  • cPanelAnthony
    Hello! Could you review the information in the
    0
  • CBAWS
    I finally figured it out. IP tables were showing bunch of AWS private IPs being blocked on EBS port (2049). Once the port/IP added to allowed list, everything started to work normal. I even enabled SELinux and ran hardening scripts with success. Thanks.
    0
  • cPRex Jurassic Moderator
    I'm glad you were able to track that down!
    0
  • IndicHosts.net
    I finally figured it out. IP tables were showing bunch of AWS private IPs being blocked on EBS port (2049). Once the port/IP added to allowed list, everything started to work normal. I even enabled SELinux and ran hardening scripts with success. Thanks.

    Why are you using CSF on the application nodes when you can use the EC2 firewall instead?
    0
  • CBAWS
    Why are you using CSF on the application nodes when you can use the EC2 firewall instead?

    Good question. While both overlaps in some areas I feel like CSF/LFD offers extra layer of security with IP tables, rules against injection attempts, login attempts from blacklisted IPs etc. Can any of these be done in AWS firewall? Curiously asking...
    0
  • IndicHosts.net
    Good question. While both overlaps in some areas I feel like CSF/LFD offers extra layer of security with IP tables, rules against injection attempts, login attempts from blacklisted IPs etc. Can any of these be done in AWS firewall? Curiously asking...

    The application server of an LBC should only have port 443 and maybe 80 open to the public. We do not have any public login interfaces on LBC application server. AWS firewall actually does not have any impact on your CPU usage/credits and does a better job than CSF in production.
    0

Please sign in to leave a comment.