| title | tags | metaDescription | freshnessValidatedDate | |||||
|---|---|---|---|---|---|---|---|---|
Automated monitoring of EC2 instances |
|
Automated monitoring of EC2 instances |
never |
New Relic's EC2 integration installs our infrastructure agent on your instances. It uses a CloudFormation template. The agent is a lightweight executable file that collects data about your instances. It also forwards data from infrastructure integrations to New Relic and forwards log data for log analytics. This document walks you through the prerequistes and steps to install the infrastructure agent on EC2 instances.
- Necessary IAM role for installing the CloudFormation template.
- Enable the public IP address in the EC2 instances.
- Install the SSM agent on the Amazon Machine Image (AMI) of the instance. Note: Most AMIs already include the SSM agent by default. See list of AMIs with SSM agent preinstalled here.
- The EC2 instance has the necessary permissions to interact with SSM and the instance profile or role is attached with the policy
AmazonSSMManagedInstanceCore. - The VPC subnet associated with the instance has a route table connected to an internet gateway.
- Finally, have a New Relic account and its valid license key. See how to get New Relic license key if you need more information.
To deploy this template in many regions, accounts, and organisational units, you need have these permissions.
- Follow all the prerequisites mentioned above.
- Deploy the CloudFormation template on your account and fill in required fields. Tag key value pair associated with the EC2 instances where you want to installa the New Relic infrastructure agent. The New Relic infrastructure agent is only installed on instances that have that specific key-value pair tag. Without a specific key-value pair tag, it will install on all by default.
- Once the deployment finishes, you can check detailed logs and metrics of qualified old and new EC2 instances of an AWS account in New Relic.