# Trying to auto-deploy but token is changing regularly

**URL:** <https://community.netdata.cloud/t/trying-to-auto-deploy-but-token-is-changing-regularly/999>\
**Category:** Help\
**Tags:** cloud\
**Created:** [February 26, 2021, 2:53pm UTC](https://community.netdata.cloud/t/trying-to-auto-deploy-but-token-is-changing-regularly/999 "2021-02-26T14:53:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hazar](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/hazar/32/547_2.png) [@hazar](https://community.netdata.cloud/u/hazar)\
**Post date:** [February 26, 2021, 2:53pm UTC](https://community.netdata.cloud/t/trying-to-auto-deploy-but-token-is-changing-regularly/999/1 "2021-02-26T14:53:41Z")

</div>

Hi, I have an auto-scaling setup at AWS and trying to monitor my nodes with Netdata Cloud.

I grabbed the `token` and `room` parameters from the claiming command and added to my launch configuration template as an environment variable. With a init script, I can run `netdata-claim.sh` with token and room parameters at the first boot.

In my testing setup, the new machines showed up in my account effortlessly (kudos to developers) but after a while I noticed that new machines are no longer auto-claimed. Looking more closely I noticed the `token` is changed at the Cloud UI after a while.

The `token` probably has time limited for security reasons. Is there a way to support auto deployment scenarios? (Same applies for auto-unclaiming but I think this feature is not ready yet as there is a note about that in claming command UI)

Thanks!