Registered · Cross-platform

5044 Logstash Beats

TCP Yes
UDP —
SCTP —
DCCP —

What it is

Elastic Beats/Lumberjack ingestion.

When / why

Filebeat/Winlogbeat shipping to Logstash.

Protocol status detail

TransportStatusMeaning
TCP Yes Assigned by IANA and standardized, specified, or widely used on this port.
UDP — Not applicable for this transport.
SCTP — Not applicable for this transport.
DCCP — Not applicable for this transport.

Port range

Registered (1024–49151). Assigned by IANA on request; usable without elevated privileges on most systems.

Browse all ports →

Firewall rules for port 5044

Copy-ready inbound rules for the active transports. Replace every <source> placeholder with the specific host, subnet, or CIDR that should reach this port.

ufw

sudo ufw allow proto tcp from <source> to any port 5044

Allow TCP 5044 (Logstash Beats). Replace <source> with the network/host that should reach it.

firewalld

sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<source>" port port="5044" protocol="tcp" accept'

Allow TCP 5044 (Logstash Beats) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

nft add rule inet filter input ip saddr <source> tcp dport 5044 accept

Allow TCP 5044 (Logstash Beats). Assumes table 'inet filter' with an 'input' chain.

iptables

sudo iptables -A INPUT -p tcp -s <source> --dport 5044 -j ACCEPT

Allow TCP 5044 (Logstash Beats). Persist with iptables-save/netfilter-persistent.

Azure NSG

az network nsg rule create -g <resource-group> --nsg-name <nsg> -n Allow-logstashbeats-5044 --priority 1000 --access Allow --direction Inbound --protocol TCP --source-address-prefixes <source> --destination-port-ranges 5044

Inbound rule for 5044 (Logstash Beats). Set <source> to a CIDR; lower priority number = higher precedence.

AWS Security Group

aws ec2 authorize-security-group-ingress --group-id <sg-id> --ip-permissions IpProtocol=tcp,FromPort=5044,ToPort=5044,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound TCP 5044 (Logstash Beats). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

gcloud compute firewall-rules create allow-logstashbeats-5044 --direction=INGRESS --action=ALLOW --rules=tcp:5044 --source-ranges=<source-cidr> --network=<network>

Ingress rule for 5044 (Logstash Beats). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow Logstash Beats 5044/TCP" dir=in action=allow protocol=TCP localport=5044 remoteip=<source>

Inbound TCP 5044 (Logstash Beats). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow Logstash Beats 5044/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 5044 -RemoteAddress <source>

Inbound TCP 5044 (Logstash Beats). Replace <source> with a host or subnet.

Rules are generated only for transports marked active for this port. They default to an inbound allow with an explicit source placeholder — never any. Review direction, scope, and rule precedence before applying in production.