# Pmm user creation doesn't work on MySQL 8.0.20

**URL:** <https://forums.percona.com/t/pmm-user-creation-doesnt-work-on-mysql-8-0-20/11406>\
**Category:** PMM 2.x\
**Created:** [July 16, 2021, 12:05pm UTC](https://forums.percona.com/t/pmm-user-creation-doesnt-work-on-mysql-8-0-20/11406 "2021-07-16T12:05:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fuzzybase](https://avatars.discourse-cdn.com/v4/letter/f/f6c823/32.png) [@fuzzybase](https://forums.percona.com/u/fuzzybase)\
**Post date:** [July 16, 2021, 12:05pm UTC](https://forums.percona.com/t/pmm-user-creation-doesnt-work-on-mysql-8-0-20/11406/1 "2021-07-16T12:05:46Z")

</div>

I installed PMM through the AWS marketplace and after completing the PMM server side instructions, am following along with the client side ones on this page:

> **[Percona Monitoring and Management - Amazon RDS](https://docs.percona.com/percona-monitoring-and-management/setting-up/client/aws.html)**
>
> Documentation

However, the command given for creating the pmm user on the RDS instance simply doesn’t work:

> GRANT SELECT, PROCESS, REPLICATION CLIENT ON _._ TO ‘pmm’@‘%’ IDENTIFIED BY ‘pass’ WITH MAX\_USER\_CONNECTIONS 10;

I get the following response:

> ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'MAX\_USER\_CONNECTIONS 10 IDENTIFIED BY ‘password’ at line 1

I have tried various combinations of the command to figure out a fix, but without success.

Could someone please suggest the right syntax?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Vadim\_Yalovets](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/vadim_yalovets/32/43_2.png) [@Vadim\_Yalovets](https://forums.percona.com/u/Vadim_Yalovets)\
**Post date:** [July 16, 2021, 3:33pm UTC](https://forums.percona.com/t/pmm-user-creation-doesnt-work-on-mysql-8-0-20/11406/2 "2021-07-16T15:33:36Z")

</div>

Hi @fuzzybase

Please use next requests:

```auto
CREATE USER 'pmm'@'%' IDENTIFIED BY 'pass';
GRANT SELECT, PROCESS, REPLICATION CLIENT ON *.* TO 'pmm'@'%';
ALTER USER 'pmm'@'%' WITH MAX_USER_CONNECTIONS 10;

```

 ![Screenshot_20210716_184020](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/f/f8d4cdb60c52208111d7fad26be5ef713e1910b8.png)

---

<div class="post-metadata">

**Author:** ![fuzzybase](https://avatars.discourse-cdn.com/v4/letter/f/f6c823/32.png) [@fuzzybase](https://forums.percona.com/u/fuzzybase)\
**Post date:** [July 16, 2021, 4:49pm UTC](https://forums.percona.com/t/pmm-user-creation-doesnt-work-on-mysql-8-0-20/11406/3 "2021-07-16T16:49:03Z")

</div>

Hi @Vadim_Yalovets, thank you very much for those commands. I was able to complete the steps finally. 🙂

Should I also run the following as per the documentation in the link?

> GRANT SELECT, UPDATE, DELETE, DROP ON performance\_schema.\* TO ‘pmm’@‘%’;

---

<div class="post-metadata">

**Author:** ![steve.hoffman](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/steve.hoffman/32/66_2.png) [@steve.hoffman](https://forums.percona.com/u/steve.hoffman)\
**Post date:** [July 16, 2021, 8:37pm UTC](https://forums.percona.com/t/pmm-user-creation-doesnt-work-on-mysql-8-0-20/11406/4 "2021-07-16T20:37:55Z")

</div>

That depends on how you are intending to get Query Analytics data from your RDS instance. I believe by default we will use Performance Schema so I’d say yes (technically I believe you’ll get QAN data anyway as the grant you already ran gives select privs to read the tables but I believe PMM does some housekeeping that the other permissions in the second grant handle).

---

<div class="post-metadata">

**Author:** ![fuzzybase](https://avatars.discourse-cdn.com/v4/letter/f/f6c823/32.png) [@fuzzybase](https://forums.percona.com/u/fuzzybase)\
**Post date:** [July 17, 2021, 2:39am UTC](https://forums.percona.com/t/pmm-user-creation-doesnt-work-on-mysql-8-0-20/11406/5 "2021-07-17T02:39:44Z")

</div>

Thank you for the technical explanation. Helps me to understand the reasoning behind that grant. Will go ahead and run that, too.