# Monitoring postgres y sql server on AWS with an elastic on premises

**URL:** <https://discuss.elastic.co/t/monitoring-postgres-y-sql-server-on-aws-with-an-elastic-on-premises/325660>\
**Category:** Elasticsearch\
**Created:** [February 15, 2023, 8:27pm UTC](https://discuss.elastic.co/t/monitoring-postgres-y-sql-server-on-aws-with-an-elastic-on-premises/325660 "2023-02-15T20:27:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ElasticLiver](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elasticliver/32/64869_2.png) [@ElasticLiver](https://discuss.elastic.co/u/ElasticLiver)\
**Post date:** [February 15, 2023, 8:27pm UTC](https://discuss.elastic.co/t/monitoring-postgres-y-sql-server-on-aws-with-an-elastic-on-premises/325660/1 "2023-02-15T20:27:50Z")

</div>

It is posible to monitor postgres y sql server on aws? if it is, with wich tool?

our elastic is on premises.

thanks.

---

<div class="post-metadata">

**Author:** ![ingri.mahecha](https://avatars.discourse-cdn.com/v4/letter/i/51bf81/32.png) [@ingri.mahecha](https://discuss.elastic.co/u/ingri.mahecha)\
**Post date:** [February 27, 2023, 2:57am UTC](https://discuss.elastic.co/t/monitoring-postgres-y-sql-server-on-aws-with-an-elastic-on-premises/325660/2 "2023-02-27T02:57:53Z")

</div>

Hello,

You can bring in postgresql logs from AWS, but they must generate certain permissions in the AWS IAM and through AWS Elastic integrations can be done.

**Configuration in AWS**

[cloudwatch logs](https://docs.aws.amazon.com/en_us/AmazonRDS/latest/UserGuide/USER_LogAccess.Concepts.PostgreSQL.html#USER_LogAccess.PostgreSQL.PublishtoCloudWatchLogs)

**CloudWatch**  
[configuration ELK](https://docs.elastic.co/en/integrations/aws/cloudwatch)

**AWS permissions for ELK**  
[AWS-Permissions](https://docs.elastic.co/integrations/aws)

### AWS Permissions

Specific AWS permissions are required for the IAM user to make specific AWS API calls. To enable the AWS integration to collect metrics and logs from all supported services, make sure these permissions are given:

- `ec2:DescribeInstances`
- `ec2:DescribeRegions`
- `cloudwatch:GetMetricData`
- `cloudwatch:ListMetrics`
- `iam:ListAccountAliases`
- `rds:DescribeDBInstances`
- `rds:ListTagsForResource`
- `s3:GetObject`
- `sns:ListTopics`
- `sqs:ChangeMessageVisibility`
- `sqs:DeleteMessage`
- `sqs:ListQueues`
- `sqs:ReceiveMessage`
- `sts:AssumeRole`
- `sts:GetCallerIdentity`
- `tag:GetResources`

---

<div class="post-metadata">

**Author:** ![ingri.mahecha](https://avatars.discourse-cdn.com/v4/letter/i/51bf81/32.png) [@ingri.mahecha](https://discuss.elastic.co/u/ingri.mahecha)\
**Post date:** [February 27, 2023, 3:00am UTC](https://discuss.elastic.co/t/monitoring-postgres-y-sql-server-on-aws-with-an-elastic-on-premises/325660/3 "2023-02-27T03:00:33Z")

</div>

or else you can integrate the metrics part of postgresql only.  
[RDS postgresql in ELK](https://docs.elastic.co/en/integrations/aws/rds)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 27, 2023, 3:01am UTC](https://discuss.elastic.co/t/monitoring-postgres-y-sql-server-on-aws-with-an-elastic-on-premises/325660/4 "2023-03-27T03:01:24Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.