# The node information of the aws rds recently created in pmm is not visible

**URL:** <https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595>\
**Category:** Uncategorized\
**Created:** [August 26, 2024, 8:49am UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595 "2024-08-26T08:49:39Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_lee](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/anonymous_lee/32/12659_2.png) [@anonymous\_lee](https://forums.percona.com/u/anonymous_lee)\
**Post date:** [August 26, 2024, 8:49am UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595/1 "2024-08-26T08:49:39Z")

</div>

Hello everyone  
The node information of the aws rds recently created in pmm is not visible.  
Some CPU-related information is visible, but memory-related information is not visible.  
Below is a portion of rds.log.(pmm-server\_2024-08-26\_07-11\client\pmm-agent\RDS\_EXPORTER pmm-server)  
…  
time=“2024-08-26T07:10:40.537+00:00” level=error msg=“ts=2024-08-26T07:10:40.535Z caller=scraper.go:89 level=error component=basic metric=ReadIOPS error="InvalidClientTokenId: The security token included in the request is invalid.\n\tstatus code: 403, request id: d46279c3-a7d2-4048-a427-dc9e526e70c4"” agentID=pmm-server/rds component=agent-process type=rds\_exporter  
time=“2024-08-26T07:10:40.542+00:00” level=error msg=“ts=2024-08-26T07:10:40.540Z caller=scraper.go:89 level=error component=basic metric=BinLogDiskUsage error="InvalidClientTokenId: The security token included in the request is invalid.\n\tstatus code: 403, request id: c71f6330-c771-43a1-8a36-1a82376baa33"” agentID=pmm-server/rds component=agent-process type=rds\_exporter  
time=“2024-08-26T07:10:55.140+00:00” level=error msg=“ts=2024-08-26T07:10:55.139Z caller=scraper.go:145 level=error component=enhanced msg="Failed to filter log events." error="ResourceNotFoundException: The specified log stream does not exist."” agentID=pmm-server/rds component=agent-process type=rds\_exporter  
time=“2024-08-26T07:10:55.235+00:00” level=error msg=“ts=2024-08-26T07:10:55.235Z caller=scraper.go:145 level=error component=enhanced msg="Failed to filter log events." error="UnrecognizedClientException: The security token included in the request is invalid."” agentID=pmm-server/rds component=agent-process type=rds\_exporter  
time=“2024-08-26T07:10:55.674+00:00” level=error msg=“ts=2024-08-26T07:10:55.673Z caller=scraper.go:145 level=error component=enhanced msg="Failed to filter log events." error="ResourceNotFoundException: The specified log stream does not exist."” agentID=pmm-server/rds component=agent-process type=rds\_exporter  
…  
Please let me know if there is a solution

PMMVersion: 2.40.1  
[rds.log](https://forums.percona.com/uploads/short-url/gBdI0BNYgVqS5Suw8b0HOss4BMx.log) (375.5 KB)

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [August 26, 2024, 2:53pm UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595/2 "2024-08-26T14:53:12Z")

</div>

> [@anonymous\_lee](#):
>
> InvalidClientTokenId: The security token included in the request is invalid

Verify your IAM security token/key have access to the RDS metrics, and CloudWatch.

---

<div class="post-metadata">

**Author:** ![anonymous\_lee](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/anonymous_lee/32/12659_2.png) [@anonymous\_lee](https://forums.percona.com/u/anonymous_lee)\
**Post date:** [August 28, 2024, 12:48am UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595/3 "2024-08-28T00:48:44Z")

</div>

thank u for your advice~~~  
i’ll check out the IAM security token/key and CloudWatch.

---

<div class="post-metadata">

**Author:** ![anonymous\_lee](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/anonymous_lee/32/12659_2.png) [@anonymous\_lee](https://forums.percona.com/u/anonymous_lee)\
**Post date:** [August 29, 2024, 1:58am UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595/4 "2024-08-29T01:58:46Z")

</div>

Hi everyone.  
I checked the information you provided above and confirmed that there were no particular problems. Afterwards, I checked rds.log again and found the following message.  
How to solve it

time=“2024-08-29T01:34:05.885+00:00” level=error msg=“ts=2024-08-29T01:34:05.885Z caller=scraper.go:145 level=error component=enhanced msg="Failed to filter log events." error="ResourceNotFoundException: The specified log stream does not exist."” agentID=pmm-server/rds component=agent-process type=rds\_exporter  
time=“2024-08-29T01:34:06.097+00:00” level=error msg=“ts=2024-08-29T01:34:06.097Z caller=scraper.go:145 level=error component=enhanced msg="Failed to filter log events." error="ResourceNotFoundException: The specified log stream does not exist."” agentID=pmm-server/rds component=agent-process type=rds\_exporter  
time=“2024-08-29T01:34:27.845+00:00” level=error msg=“ts=2024-08-29T01:34:27.844Z caller=collector.go:78 level=error component=basic msg="No scraper for ap-northeast-2/rds-helpdesk-prd (AKIAT74SYTYET5F27BF2), skipping."” agentID=pmm-server/rds component=agent-process type=rds\_exporter

---

<div class="post-metadata">

**Author:** ![lalit.choudhary](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lalit.choudhary/32/51_2.png) [@lalit.choudhary](https://forums.percona.com/u/lalit.choudhary)\
**Post date:** [August 29, 2024, 7:29am UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595/5 "2024-08-29T07:29:44Z")

</div>

> [@anonymous\_lee](#):
>
> InvalidClientTokenId: The security token included in the request is invalid

This could be related to [[PMM-12426] - Percona JIRA](https://perconadev.atlassian.net/browse/PMM-12426)

Please try the below workaround,

> As a good workaround here - use AMI roles for the PMM server and rotate them instead of credentials.
> 
> [Amazon RDS - Percona Monitoring and Management](https://docs.percona.com/percona-monitoring-and-management/setting-up/client/aws.html#creating-an-access-key-for-an-iam-user)

---

<div class="post-metadata">

**Author:** ![anonymous\_lee](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/anonymous_lee/32/12659_2.png) [@anonymous\_lee](https://forums.percona.com/u/anonymous_lee)\
**Post date:** [September 4, 2024, 3:58am UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595/6 "2024-09-04T03:58:46Z")

</div>

As you said, I deleted the rds from the inventory list and reconnected it. It worked fine at first, but when I looked at the memory and CPU information as shown in the picture, only the CPU information was displayed.  
Also, no information was displayed in the node overview.  
I also attached the rds.log and node overview information  
[rds.log](https://forums.percona.com/uploads/short-url/gBdI0BNYgVqS5Suw8b0HOss4BMx.log) (375.5 KB)  
.  
 ![cpu_memory](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/3/a/3ad4a1491bb512c09f440c40d6bae5e065b73480.png)

 ![node_overview](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/7/a/7a094655debc6d26ce2372dd938fc5be66de2db4.png)

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [September 4, 2024, 5:18pm UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595/7 "2024-09-04T17:18:56Z")

</div>

Do you have extended metrics enabled for this RDS instance? CloudWatch metrics enabled too? CPU/Disk/Memory information for RDS is pulled from CloudWatch. If these are not enabled, then PMM has nothing to fetch.

---

<div class="post-metadata">

**Author:** ![anonymous\_lee](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/anonymous_lee/32/12659_2.png) [@anonymous\_lee](https://forums.percona.com/u/anonymous_lee)\
**Post date:** [September 6, 2024, 5:23am UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595/8 "2024-09-06T05:23:37Z")

</div>

extended metrics are enabled for this RDS instance, and CloudWatch metrics are also enabled.  
When I deleted it from inventory and reconnected, the memory information came out normally at first, but then it stopped coming out.  
Also, this does not appear the same in other rds instances.

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [September 6, 2024, 1:45pm UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595/9 "2024-09-06T13:45:02Z")

</div>

Your entire log file is filled with “InvalidClientTokenId: The security token included in the request is invalid.” Please verify your AWS credentials and the policy associated with them.

---

<div class="post-metadata">

**Author:** ![anonymous\_lee](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/anonymous_lee/32/12659_2.png) [@anonymous\_lee](https://forums.percona.com/u/anonymous_lee)\
**Post date:** [September 9, 2024, 1:09am UTC](https://forums.percona.com/t/the-node-information-of-the-aws-rds-recently-created-in-pmm-is-not-visible/32595/10 "2024-09-09T01:09:35Z")

</div>

I uploaded rds.log again today. If you look, there is no InvalidClientTokenId message in rds.log. Thank you for your help.  
[rds.log](https://forums.percona.com/uploads/short-url/3KtMSC5QrlKd1A0NH61j8VAr06Z.log) (316 KB)
