• EnglishEspañol日本語한국어Português
  • Log inStart now

Set up Amazon VPC Flow Logs monitoring

Amazon Virtual Private Cloud Flow (VPC) Logs via Amazon Kinesis Data Firehose help you reduce the friction of sending logs to New Relic. With VPC flow logs from across your AWS estates, you can quickly understand key insights for performance analytics and troubleshooting network connectivity.

Add Amazon VPC Flow Logs to your New Relic account.

Amazon Virtual Private Cloud (VPC) enables you to launch AWS resources into an isolated and secure virtual network with the benefits of using scalable AWS infrastructure.

Add Amazon VPC Flow Logs


New Relic prerequisites

AWS prerequisites


Amazon VPC Flow Logs via Kinesis Data Firehose isn't supported for FedRAMP customers yet. In the meantime, you can use our FedRAMP ingest APIs.

IAM roles

If you set up the flow logs integration using the AWS CLI, you must provide one or two IAM roles for different infrastructure components. If you use CloudFormation, you can either provide your own roles or let the template define new roles.

The necessary roles should have at least the following permissions:

Formatting your logs in New Relic

To use the curated flow log exploration and entity linking, you must follow this format for the VPC flow logs:

${version} ${account-id} ${region} ${az-id} ${sublocation-type} ${vpc-id} ${subnet-id} ${instance-id} ${interface-id} ${srcaddr} ${pkt-srcaddr} ${pkt-src-aws-service} ${dstaddr} ${pkt-dstaddr} ${pkt-dst-aws-service} ${srcport} ${dstport} ${protocol} ${packets} ${bytes} ${flow-direction} ${traffic-path} ${start} ${end} ${action} ${log-status}


If you want to learn more about the log fields, check the available fields in the VPC Amazon documentation.

You must use a log partition for VPC flow logs named Log_VPC_Flows_AWS. If you use the guided install, this is handled automatically.

Set up Amazon VPC Flow Logs monitoring in New Relic

Follow the guided wizard to install Amazon VPC Flow Logs:

  1. Start the guided install process.
  2. From the Select an account dropdown, choose the New Relic account you want to send Amazon VPC Flow Logs to, and click Continue.
  3. In the Select your data section, choose Amazon VPC Flow Logs and click Continue.
  4. In the Select your install method section, continue with CLI and click Continue.

After these steps, a new wizard pops-up to help you set up the sending of Amazon VPC Flow Logs to New Relic through the AWS Kinesis Firehose service.

  1. In the Choose Setup Options section:

    • Verify your setup method is correct.
    • Select the AWS region that will send VPC flow logs to New Relic.
    • Optionally, if you are reusing a Kinesis Data Firehose, select the I already have a Kinesis Firehose to New Relic checkbox and continue to the Define flow logs section.
    • Click Continue.
  2. In the Define Kinesis Firehose section:

    • In the Kinesis Firehose Name field, make sure the generated name is correct.
    • In the Firehose Backup Bucket field, enter the ARN of the S3 bucket to be used to store messages that fail delivery. The ARN must follow this format: arn:my_string.
    • In the Firehose IAM Role field, enter the ARN of the IAM role to be used by Kinesis Data Firehose. The ARN must follow this format: arn:my_string.
    • Click Continue.
    • Optionally, if you want to sample VPC flow logs, select the Use Sampling checkbox and:
  3. In the Generate Kinesis Firehose section, click Generate CLI Command and:


    We automatically generate a new to be used for this data ingest. To regenerate a key, click Generate and use a new key.

    If you want to re-use an existing key, update the AccessKey value in the first step.

    • Copy the contents of the code block for Create your Kinesis Data Firehose and paste run it in the AWS CLI.
    • To check if your Kinesis Firehose is created, run the command from the second step in the AWS CLI. If no ARN is returned, wait 30 seconds and try again.
    • Copy the returned ARN for the Kinesis Firehose and paste it into the Kinesis Data Firehose ARN field in the format arn:my_string. Then, click Continue.

    Generate Kinesis Firehose step in the guided install.

  4. In the Define Flow Logs section, do the following:

    • From the Traffic Type dropdown, select whether to send only accepted, only rejected, or all flow log entries.
    • In the Flow Source ID field, enter the VPC ID (vpc-MY_STRING) or the subnet ID (subnet-MY_STRING) for which Amazon VPC Flow Logs should be created.
    • The Flow Source Type field will be automatically populated, so click Continue.
  5. In the Create Flow Logs section, click Generate CLI Command and copy the contents of the syntax block. Then, run it in the AWS CLI to begin generating flow logs for the specified resources.

  6. Click Continue to start exploring Amazon VPC Flow Logs in the network monitoring section of New Relic.

  7. Visualize your network performance data in New Relic.

Did this doc help with your installation?

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.