Hey All, Anyone used `aws paramstore` storing the config value and resolving at runtime at the appli...

# ktor

[Thiyagu]

Hey All, Anyone used aws paramstore storing the config value and resolving at runtime at the application start?

[Ben]

I’ve used it in a spring project before and it worked well.

[Alex]

yes, looks like this for me:

return MapApplicationConfig(
  ...
  Pair("db.password", ssmService.getSsmParameter("${stage}.db.password", true)),
  ...
)

and the ssmService utilize the AWS SsmClient
Straight forward.

[Thiyagu]

@Alex thanks.. It's really simple one..

[Thiyagu]

Actually I'm planning to migrate from DW to ktor.. in the current setup we have application.yml which has value like

db:
   name: test
   username: {{user_name}}

In these user name should be replaced by the ssmService at runtime. How do i go about this one?

[Alex]

When you use application.conf you still need to create your db-connection somehow at the start of the app .. so you can decide:
• are the keys for db.* in your config just ssm-keys? and you resolve them when you initialize your db
• or do you prefix your ssm keys with ssm: (or stuff like this) in your config, to just resolve specific values from ssm (when config._startsWith_(*"ssm:"*))
For me I found it personally easier to use embeddedServer and use MapApplicationConfig.

[Thiyagu]

Ah! It give me some idea to look into . Thanks

[Alex]

nice 👍