Why Can’t I Connect to My EC2 Instance or RDS? Determining the Issue.

BY:

Mar 26, 2019

Using VPC Flow Logs to Troubleshoot Network Connectivity to Your EC2 Instance

Anthony Palmer, Senior Cloud Engineer at CloudHesive

Here at CloudHesive we encounter all types of AWS questions from our customers. One of the most common questions our engineering and support staff encounter daily is, “Why can’t I connect to my EC2 instance?” or “Why can’t I connect to my RDS?

The first thought from any AWS engineer should be security groups, maybe on a rare occasion it is a route table issue. So how do we go about and determine what the actual issue is? Lucky for us, AWS logs all network traffic in VPC flow logs. Combine the VPC flow logs with a custom CloudWatch filter and you can easily trace packets across your AWS environment.

Step 1: Identify the ENI (Elastic Network Interface) of the destination EC2

From the EC2 screen take note of the Interface ID for the Network Interface as well as the IP address. In this example we will be accessing a sandbox server from over the internet.

Step 2: Select the Network Interface and go to Flow Logs

*If Flow Logs are not enabled this tip won’t work

Step 3: Drill into the VPC Flow Logs and search for your ENI within CloudWatch

Step 4: Input a custom filter within search bar

[version, accountid, interfaceid, srcaddr, dstaddr, srcport, dstport, protocol, packets, bytes, start, end, action, logstatus]

Step 5: Adjust the filter to troubleshoot connectivity

In this example we are trying to SSH into a Linux server from the AWS Workspace. We have removed all security group entries, so our access should be denied when SSH is attempted. The filter below filters on the source address, being the public IP of our Workspace and the port being 22 or SSH.

[version, accountid, interfaceid, srcaddr=52.2.120.210, dstaddr, srcport, dstport=22, protocol, packets, bytes, start, end, action, logstatus]

Step 6: Adjust the security group then the CloudWatch filter

Step 6: Adjust the security group then the CloudWatch filter

Now we can SSH into the Linux server.

Now we can SSH into the Linux server.

The CloudWatch flow logs now show an ACCEPT!

If you’re still unclear on how to connect your EC2 or RCD, reach out to the CloudHesive team today. Give us a call today at 800-860-2040 or fill out our online contact form.

[/fusion_text][/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]

Related Blogs

  • Cold Transfers with Amazon Connect" alt="">
    Managing Cold Transfers with Amazon Connect

    There’s a right way and a wrong way to set up call transfers in Amazon Connect, and it could make all the difference between a customer’s experience with your contact center. One of the most...

    Learn More
  • Amazon Connect’s integration with Service Cloud" alt="">
    Amazon Connect, Service Cloud Voice and Salesforce CTI Enable Total Customer-Facing Integration

    Why Amazon Connect’s integration with Salesforce Service Cloud Voice dramatically improves customer service and communication Customers are the root of your business. Being able to connect with...

    Learn More
  • " alt="">
    AWS Contact Center Intelligence

    Mid August, AWS announced AWS Contact Center Intelligence(CCI). AWS CCI enables customers to build powerful chatbots and AI-driven Interactive Voice Response (IVR) solutions, including self-service...

    Learn More