# Hardcode the stack name in catalog **URL:** \ **Category:** Rancher 1.x\ **Created:** [June 4, 2017, 9:51am UTC](https://forums.suse.com/t/hardcode-the-stack-name-in-catalog/6552 "2017-06-04T09:51:36Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![vukor](https://avatars.discourse-cdn.com/v4/letter/v/f17d59/32.png) [@vukor](https://forums.suse.com/u/vukor)\ **Post date:** [June 4, 2017, 9:51am UTC](https://forums.suse.com/t/hardcode-the-stack-name-in-catalog/6552/1 "2017-06-04T09:51:36Z")
Good day, I created catalog with service, which using existing EBS volume. So I would like to add some restriction to have single copy stack to make sure that anyone else can’t create one more stack (second service won’t write to EBS volume). Probably, it’s could be stack name, i.e. one stack == one environment. Is it possible? Maybe anyone suggest another solutions. Thanks. ---
**Author:** ![StrongMonkey](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/strongmonkey/32/2476_2.png) [@StrongMonkey](https://forums.suse.com/u/StrongMonkey)\ **Post date:** [June 5, 2017, 11:48pm UTC](https://forums.suse.com/t/hardcode-the-stack-name-in-catalog/6552/2 "2017-06-05T23:48:00Z")
you can make a [stack-scoped](https://docs.rancher.com/rancher/v1.6/en/rancher-services/storage-service/#stack-scoped) volume so that all the services inside your stack can use that volume by name and other stacks can not access that volume. ---
**Author:** ![vukor](https://avatars.discourse-cdn.com/v4/letter/v/f17d59/32.png) [@vukor](https://forums.suse.com/u/vukor)\ **Post date:** [June 6, 2017, 4:15am UTC](https://forums.suse.com/t/hardcode-the-stack-name-in-catalog/6552/3 "2017-06-06T04:15:49Z")
Thnx for your reply. AFAIK, In this case if stack will be removed then ebs volumes will too. So my current workaround is use existing volume id in docker-compose and locate them in questions in rancher-compose. Probably, it’s might be a proof of accidental creation of stack.