[scarface74]

Parameter Store is such a god awful experience via the UI. But everything about parameter store is awful.

- severe unchangeable, undocumented limits before you get throttled. Throttling is so bad that if you have too many parameter store resources in your CloudFormation template it will start causing errors because CF is trying to call the API too quickly - the only way around it is to use DependsOn and chain the creation.

- no way of creating an encrypted value with CF without a custom resource.

We ended up just using DynamoDB for config anda Custom CloudFormation resource to create values in it.

You should never depend on Parameter Store as a reliable key/value store for configuration.

[shepardrtc]

We've hit the throttling issue many, many times. Everything about Parameter Store is difficult. And its a shame. Its such a simple concept. They have enormous resources, so why not throw a couple of devs at it?

In any case, we do also use redis. It might be worthwhile to pitch an idea to move over to that. But we pull the parameters in bash scripts using a custom tool called aws-env, so we'd probably have to make or find something similar for redis.

[cthalupa]

https://docs.aws.amazon.com/systems-manager/latest/userguide...

I believe this is a new(ish?) feature, but someone from AWS Support recently pointed it out to me when dealing with throttling issues. Might be of interest to you.

[scarface74]

Yeah it’s relatively new. It just became available in April.

https://aws.amazon.com/about-aws/whats-new/2019/04/aws_syste...