Sunil Kumar Wouldn't you need to update code anyways when there are new values? Not sure I see the distinction between the two; if its in code and you manually change in consul, you could just do the same with Param Store. But even if a config value results in a restart, its still a fully automated and auditable change. Yes, you can define the secret, but manually add in the value as a side process. If the secret needed (or would benefit) regular rotation then you can enable it.

Curious as to why you're not using Parameter Store for all the other config values? These can be implemented as infra-as-code and if they aren't secrety they can be committed alongside the application (similar to how you're currently doing it)