---
title: Creating a new user
description: If you do not have a user as mentioned in the PingIntelligence automated deployment preparation section, complete the following steps on all the provisioned host machines.
component: pingintelligence
version: 5.2
page_id: pingintelligence:installing_pingintelligence_for_apis:pingintelligence_creating_new_user
canonical_url: https://docs.pingidentity.com/pingintelligence/5.2/installing_pingintelligence_for_apis/pingintelligence_creating_new_user.html
revdate: April 3, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
  troubleshooting: Troubleshooting:
---

# Creating a new user

## About this task

If you do not have a user as mentioned in the [PingIntelligence automated deployment preparation](pingintelligence_automated_deployment_preparation.html) section, complete the following steps on all the provisioned host machines.

If you already have a user as described in [Creating a new SSH user and configuring user authentication](pingintelligence_creating_new_ssh_user_configuring_user_authentication.html), start with [Copying the PingIntelligence license](pingintelligence_copying_license.html).

## Steps

1. Create an `ec2-user`.

   The `hosts` file in the automation package has `ec2-user` as the default user.

   1. **Optional:** To create your own username, run the `#useradd ec2-user` command.

2. Change the password by running the `#passwd ec2-user` command.

   |   |                                                                                    |
   | - | ---------------------------------------------------------------------------------- |
   |   | If you're installing PingIntelligence software as a non-sudo user, skip steps 3-5. |

3. Add the user to the wheel group by running the `#usermod -aG wheel ec2-user` command.

4. Configure passwordless `sudo` access:

   ```
   #visudo
   %wheel ALL=(ALL) NOPASSWD: ALL
   ```

5. Verify the `/etc/ssh/sshd_config` file for `PubKeyAuthentication`.

   ### Troubleshooting:

   If it is set to `no`, then set it to `yes` and restart `sshd` service by the `#systemctl restart sshd` command.