When working with a particularly large json file to be put into parameter store, throttling can be encountered due to the way parameters are being put.
I suspect that resolution of this problem lies in getting this updated with some exponential back off implemented, but I don't know to detect this throttling error (ThrottlingException: Rate exceeded), as these seem to be the errors that can be returned by the PutParameter: https://docs.aws.amazon.com/sdk-for-go/api/service/ssm/#SSM.PutParameter
Some investigation will be necessary.
As a workaround, AWS accounts can be adjusted to increase throttling limits, but it costs money and it might benefit free tier users to have the retry when throttled.
When working with a particularly large json file to be put into parameter store, throttling can be encountered due to the way parameters are being put.
I suspect that resolution of this problem lies in getting this updated with some exponential back off implemented, but I don't know to detect this throttling error (ThrottlingException: Rate exceeded), as these seem to be the errors that can be returned by the PutParameter: https://docs.aws.amazon.com/sdk-for-go/api/service/ssm/#SSM.PutParameter
Some investigation will be necessary.
As a workaround, AWS accounts can be adjusted to increase throttling limits, but it costs money and it might benefit free tier users to have the retry when throttled.