# AWS cross account  Add service discover using EC2 role 

**URL:** <https://forums.percona.com/t/aws-cross-account-add-service-discover-using-ec2-role/26560>\
**Category:** General Questions\
**Tags:** percona\
**Created:** [November 15, 2023, 2:07pm UTC](https://forums.percona.com/t/aws-cross-account-add-service-discover-using-ec2-role/26560 "2023-11-15T14:07:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AMJAD\_JEBREEN](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/amjad_jebreen/32/13761_2.png) [@AMJAD\_JEBREEN](https://forums.percona.com/u/AMJAD_JEBREEN)\
**Post date:** [November 15, 2023, 2:07pm UTC](https://forums.percona.com/t/aws-cross-account-add-service-discover-using-ec2-role/26560/1 "2023-11-15T14:07:50Z")

</div>

'm encountering an issue while utilizing Percona Monitoring and Management (PMM) on AWS. My objective is to add a service and discover RDS instances using an EC2 role. However, it seems to be listing only the RDS instances within the same account where the EC2 instance is hosted. I’m attempting to leverage the EC2 role to list all RDS instances in another AWS account without resorting to access keys.

To accomplish this, I’ve already configured a trust policy to assume a role in the target account. Despite these efforts, I haven’t been successful in achieving the desired cross-account RDS discovery using PMM.