# AWS SSM Parameters not picked up

**URL:** <https://community.seqera.io/t/aws-ssm-parameters-not-picked-up/998>\
**Category:** Ask for help\
**Tags:** aws, platform\
**Created:** [July 23, 2024, 2:42pm UTC](https://community.seqera.io/t/aws-ssm-parameters-not-picked-up/998 "2024-07-23T14:42:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcabraham](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/jcabraham/32/839_2.png) [@jcabraham](https://community.seqera.io/u/jcabraham)\
**Post date:** [July 23, 2024, 2:42pm UTC](https://community.seqera.io/t/aws-ssm-parameters-not-picked-up/998/1 "2024-07-23T14:42:59Z")

</div>

Upgrading my Tower on prem instance to 24.1, and I’m using AWS SSM parameters as mentioned in the docs. My parameter path is /config/tower/foo, etc, as described in the documentation, my tower.yml sets app name to tower:

micronaut:  
application:  
name: tower

But I get an error on startup that my role is not authorized to perform: ssm:GetParameters on resource: arn:aws:ssm:us-east-1:123456789:parameter/config/application

Notice the path: /config/application?

Why is Tower not using its own, documented path /config/tower or /config/tower-app?

---

<div class="post-metadata">

**Author:** ![jcabraham](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/jcabraham/32/839_2.png) [@jcabraham](https://community.seqera.io/u/jcabraham)\
**Post date:** [July 23, 2024, 2:43pm UTC](https://community.seqera.io/t/aws-ssm-parameters-not-picked-up/998/2 "2024-07-23T14:43:48Z")

</div>

Sorry about the formatting, which is not putting yaml spacing before the elements for micronaut.application.name