# 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:** 1\
**Showing post:** 2

<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)

---

_[View the full topic](https://discuss.circleci.com/t/additional-restrictions-to-ssh-key-to-publish/2336)._