What Should I Do If the Result of a Logstash Connectivity Test Is Unavailable?

When using a CSS Logstash cluster to migrate data, if the connectivity test between Logstash and the data source or destination returns Unavailable, the most probable cause is incorrect network configuration. This section describes how to check network configurations in different environments to resolve connectivity issues.

• Within the same VPC
  If Logstash and the data source or destination are in the same VPC, the following conditions must be met:

  • The security group used by the Logstash cluster allows outbound traffic for all protocols.
  • The security group used by the Logstash cluster allows inbound traffic for the ICMP protocol as well as the TCP ports used by the peer addresses.

  For details, see Adding a Security Group Rule.

• Within different VPCs
  If Logstash and the data source or destination are in different VPCs, the following conditions must be met:

  • The security group used by the Logstash cluster allows outbound traffic for all protocols.
  • The security group used by the Logstash cluster allows inbound traffic for the ICMP protocol as well as the TCP ports used by the peer addresses.
  • A route has been configured between the Logstash cluster and the peer VPC.

  For details, see Adding a Security Group Rule and Configuring Routes for a Logstash Cluster.

• Within different LANs (they must communicate across the public network):

  If Logstash and the data source or destination are in different LANs, the following condition must be met: A public IP address has been configured for the Logstash cluster to ensure it can be accessed from the Internet.

  For details, see Configuring Public Network Access.