# Data Retention of PMM running under AWS

**URL:** <https://forums.percona.com/t/data-retention-of-pmm-running-under-aws/7862>\
**Category:** PMM 1.x\
**Tags:** pmm\
**Created:** [August 7, 2020, 12:22am UTC](https://forums.percona.com/t/data-retention-of-pmm-running-under-aws/7862 "2020-08-07T00:22:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nkhakharia](https://avatars.discourse-cdn.com/v4/letter/n/a587f6/32.png) [@nkhakharia](https://forums.percona.com/u/nkhakharia)\
**Post date:** [August 7, 2020, 12:22am UTC](https://forums.percona.com/t/data-retention-of-pmm-running-under-aws/7862/1 "2020-08-07T00:22:22Z")

</div>

How do I change data retention of PMM server (METRICS\_RETENTION &&nbsp;QUERIES\_RETENTION) configured using AWS AMI. I see option to change for docker but unable to do for PMM configured with AWS AMI

---

<div class="post-metadata">

**Author:** ![Agustin\_G](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/agustin_g/32/14111_2.png) [@Agustin\_G](https://forums.percona.com/u/Agustin_G)\
**Post date:** [August 12, 2020, 7:10pm UTC](https://forums.percona.com/t/data-retention-of-pmm-running-under-aws/7862/2 "2020-08-12T19:10:28Z")

</div>

First, let me note that there is a simple way of doing this in v2:&nbsp;[https://www.percona.com/doc/percona-monitoring-and-management/2.x/faq.html#how-to-control-data-retention-for-pmm](https://www.percona.com/doc/percona-monitoring-and-management/2.x/faq.html#how-to-control-data-retention-for-pmm)  
  
However, there is a workaround for v1 deployed on AMI. Login to the EC2, and edit two files:  
/etc/sysconfig/prometheus1&nbsp;to modify&nbsp;–storage.local.retention&nbsp;under&nbsp;OPTIONS:&nbsp;

```auto
OPTIONS="--storage.local.retention=720h --storage.local.chunk-encoding-version=2 --web.external-url=http://localhost:9094/prometheus1/"

```

/etc/sysconfig/prometheus&nbsp;to modify&nbsp;–storage.tsdb.retention&nbsp;under&nbsp;OPTIONS:

```auto
OPTIONS="--storage.tsdb.retention=720h --web.enable-lifecycle --web.enable-admin-api --web.external-url=http://localhost:9090/prometheus/"

```

and restart the services:

```auto
$ systemctl restart prometheus.service
$ systemctl restart prometheus1.service

```

These changes may not survive an upgrade, so be on the lookout in case you upgrade!