Update the SSM secret manager implementation to do basic validation of given secret paths, in the style of the Azure Key Vault version.
The Azure Key Vault checks were added because feeding SSM-style paths directly into the Key Vault were causing some off-script 404s that I think was either twigging resilience retry or just misleading. What I'm trying to say is that validation was in response to a problem rather than a matter of planning.
SSM is a bit more explicit with its exceptions in my experience, but it does strike me as general good practice to validate low-hanging fruit before spending time on the back and forth of it all by communicating with an external service.
Update the SSM secret manager implementation to do basic validation of given secret paths, in the style of the Azure Key Vault version.
The Azure Key Vault checks were added because feeding SSM-style paths directly into the Key Vault were causing some off-script 404s that I think was either twigging resilience retry or just misleading. What I'm trying to say is that validation was in response to a problem rather than a matter of planning.
SSM is a bit more explicit with its exceptions in my experience, but it does strike me as general good practice to validate low-hanging fruit before spending time on the back and forth of it all by communicating with an external service.