---
title: "Obtaining & configuring valid certificates for your Infrasense Sensor"
canonical: "https://thoughtdata.refined.site/space/TUD/55186534/Obtaining%20%26%20configuring%20valid%20certificates%20for%20your%20Infrasense%20Sensor"
format: markdown
---
## Obtaining  & configuring valid certificate on your Infrasense

By default, ThoughtData's Infrasense/APM server runs HTTPs and uses self signed certificates for its SSL communications. For internal ThoughtData's APM agents in your IT network, if you are fine with self signed certificates there is no change required and everything works out of box and you may skip this configuration.

If your security policies require you to have a proper SSL certificate assigned to your Infrasense sensor. You would need to get a valid and signed SSL certificate.

**Note:** Valid certificates are only required for HTTPs communication between Infrasense sensor and ThoughtData's APM and RUM agents. For normal Infrasense operations for Infrastructure monitoring using SSH/SNMP methods or even Synthetic monitoring, this configuration is not required

**Note:** If you are using RUM agent and if your users are connecting to your website or web application server over internet, you must put a valid and properly signed certificate for your sensor for RUM agents to securely communicate with the Infrasense sensor.

There are various methods to get a valid certificate to your Infrasense sensor. You may use any method of your choice. Also note that, in order to obtain a proper and valid certificate a valid DNS name associated with the Infrasense sensor is also required.

One of the popular choices to get a free valid SSL certificate is from letsencrypt service. Follow the external link below for a step by step guide if you choose to follow this method.

[Certbot Instructions | Certbot (eff.org)](https://certbot.eff.org/instructions)

ThoughtData neither promotes or recommends letsencrypt. The choice of obtaining the valid certificate for your Infrasense sensor is entirely up to you. 

A valid certificate usually contains 2 files a "Key File" and a "Cert file". Both have a ".pem" file extension. Once you have obtained these files, copy it to your Infrasense sensor machine into **"/usr/local/thoughtdata/infrasense/bin/td_apm_server/cert"** and follow the the below steps to configure your Infrasense to work with valid certificates.

Check the out of box self signed certificate files by running **"ls -lrt"**

![image](media://3ee3f1cb-9225-441d-aaac-6dc1ff5d1b7e)

 check self signed certificate

Copy the certificate files you have obtained for the Infrasense sensor to the same path **"/usr/local/thoughtdata/infrasense/bin/td_apm_server/cert"**

Go to **"cd ****/usr/local/thoughtdata/infrasense/bin/td_apm_server****" **directory.

Edit **conf.ini **file by running **"vi conf.ini"** 

![image](media://0a7b2c11-384b-4163-a5ac-e3b9ccd9abf5)

 Edit conf.ini to change the names and full path of the valid certificate files

In the parameter **"cert_key", **replace the full path of the new valid key file.

In the parameter **"cert_file", **replace the full path of the new valid cert file.

Save and exit the file by pressing "Esc" ":" "wq". 

Stop and start ThoughtData Infrasense and APM server processes by running "**service infrasense stop**" and "**service infrasense start"**

This completes the configuration required for setting up proper valid certificates for ThoughtData's Infrasense sensor.