PMM-15389 Assume IAM role for RDS monitoring (full stack) - #4548
Conversation
|
Server docker: perconalab/pmm-server-fb:PR-4548-1000670 |
|
API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/7180/ |
pmm: PMM-15389-rds-assume-iam-role (main + #5804 adopted + 4 defect fixes + instance_id inventory/CLI wiring). grafana: PMM-15389-rds-role-arn-ui (role ARN field on the Add Instance / Discovery credentials form). Replaces the earlier pin on the contributor fork; #5804 itself is untouched. Signed-off-by: Ante Gulin <ante.gulin@percona.com>
|
Server docker: perconalab/pmm-server-fb:PR-4548-bd21a28 |
1 similar comment
|
Server docker: perconalab/pmm-server-fb:PR-4548-bd21a28 |
|
API tests have failed: https://pmm.cd.percona.com/job/pmm3-api-tests/7343/ |
|
API tests have failed: https://pmm.cd.percona.com/job/pmm3-api-tests/7344/ |
Retrigger only. pmm PMM-15389-rds-assume-iam-role now at 1ebc19b4, which fixes the api-test TestRDSExporter/WithRoleARN failure (role ARN was rejected for a pmm-agent that had not reported a version). Signed-off-by: Ante Gulin <ante.gulin@percona.com>
|
Server docker: perconalab/pmm-server-fb:PR-4548-8862af2 |
|
API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/7346/ |
Feature build for assumed-IAM-role RDS monitoring: PMM assumes an AWS IAM role instead of using static access keys to monitor RDS.
Full stack, pinned on branches we own (the contributor PR percona/pmm#5804 is left untouched):
pmm:
PMM-15389-rds-assume-iam-roleinstance_idthrough the inventory node API andpmm-admin, so the rds_exporter actually has a DB instance to scrape. This delivery-surface gap predates #5804 and blocks it.grafana:
PMM-15389-rds-role-arn-uiDocs companion: percona/pmm#5838.
Draft: built for end-to-end testing on AWS, not for merge.