It’s (becoming) a cloud-centric world.
Workloads are moving from on-prem to one or more of the big clouds (namely AWS, GCP, Azure, IBM, and Oracle). If your organization has made the move, have you ever wondered whether you’ve actually achieved the performance, reliability and efficiency gains that the cloud promises, or if your data stays secure, or if your ops costs have actually decreased?
The answers can often be found with network visibility.
This summer, Kentik extended our analytics platform to support visibility within public cloud environments via VPC Flow Logs. Our initial integration used VPC Flow Logs from Google Cloud Platform as a data source and fully exposed GCP-specific tags like regions, zones, and VM names as dimensions within the Kentik UI (read our Solution Brief).
Today, we are excited to extend our support to AWS.
Cloud providers have taken away the burden of the traditional hardware layer most organizations are used to. On the one hand, this helps organizations reduce the related overhead of taking care of hardware. However, many cloud customers are then challenged by a lack of visibility into what is going on with their traffic patterns going into and out of their cloud network. With an increasing amount of requests from cloud adopters looking to monitor traffic in their VPC, Amazon, Google and Microsoft have all supported a Flow Logs feature. (You can read more about the three providers’ flow logs in our recent blog post “What Are VPC Flow Logs and How Can They Improve Your Cloud?”)
AWS VPC Flow Logs capture information about IP traffic flowing in and out of interfaces that are part of an AWS VPC. These flow logs can be used to analyze and troubleshoot issues within a cloud environment in a few key ways:
Below is a sample flow log record which contains
<version> <account-id> <interface-id> <srcaddr> <dstaddr> <srcport>
<dstport> <protocol> <packets> <bytes> <start> <end> <action> <log-status>
Image source: AWS
The following is an example of a flow log record in which SSH traffic (destination port 22, TCP protocol) to network interface eni-abc123de in account 123456789010 was allowed:
You can find more details, including the structure of each flow record and possible limitations in the AWS user guide.
In a previous blog about GCP VPC Flow Logs, we talked about how Kentik can help multiple stakeholders within organizations to stop flying blind on their cloud initiatives, including:
These use cases and value hold strongly for us with AWS VPC Flow Logs, too. Additionally, with Kentik:
And you can do these all together under one unified view, enabling deep network visibility for greater business context to help deliver a greater customer experience and grow revenue.
It’s straightforward to setup Kentik for AWS. To export VPC Flow Logs to the Kentik platform, just follow these four steps:
Also, visit us at AWS re:Invent Booth #112 to learn more about our cloud visibility offerings.