# Additional restrictions to ssh key to publish

**URL:** <https://discuss.circleci.com/t/additional-restrictions-to-ssh-key-to-publish/2336>\
**Category:** Deployments\
**Created:** [February 25, 2016, 3:23pm UTC](https://discuss.circleci.com/t/additional-restrictions-to-ssh-key-to-publish/2336 "2016-02-25T15:23:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![iovdin](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/iovdin/32/1770_2.png) [@iovdin](https://discuss.circleci.com/u/iovdin)\
**Post date:** [February 25, 2016, 3:23pm UTC](https://discuss.circleci.com/t/additional-restrictions-to-ssh-key-to-publish/2336/1 "2016-02-25T15:23:03Z")

</div>

Hi,  
We are using custom deployment configuration.  
In addition to ssh key based authentication we use ip based restrictions to our environment.  
But for CircleCI build machines every time ip is different,  
Is there any predefined ip range or additional security check we can apply?

Thanks

---

<div class="post-metadata">

**Author:** ![FelicianoTech](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/felicianotech/32/21348_2.png) [@FelicianoTech](https://discuss.circleci.com/u/FelicianoTech)\
**Post date:** [February 25, 2016, 5:56pm UTC](https://discuss.circleci.com/t/additional-restrictions-to-ssh-key-to-publish/2336/2 "2016-02-25T17:56:02Z")

</div>

There isn’t a great way to do this aside from whitelisting the two regions builds can run in on AWS: [CircleCi Source IP](https://discuss.circleci.com/t/circleci-source-ip/1202/2?u=felicianotech)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [June 18, 2018, 11:40am UTC](https://discuss.circleci.com/t/additional-restrictions-to-ssh-key-to-publish/2336/3 "2018-06-18T11:40:57Z")

</div>

Closed on June 18, 2018, 11:40am UTC