Add support for snowflake passwords stored in AWS SSM parameter store #20
Conversation
thomas-brx
force-pushed
the
support-for-parameter-store-passwords
branch
from
a37cd9f to
47c6cd2
Compare
jbeemster
left a comment
jbeemster
left a comment
There was a problem hiding this comment.
Thanks for the contribution here! Would be great if you can add a new variable for the parameter store ARN instead of overloading the existing password that would make it much clearer how to leverage this option.
I would also have assumed that the IAM Policy needs to be allowed Get access to the supplied parameter? Can you add the relevant change to the IAM Policy object in main.tf to manage that allowance conditionally?
README.md
Outdated
| | <a name="input_snowflake_database"></a> [snowflake\_database](#input\_snowflake\_database) | Snowflake database name | `string` | n/a | yes | | ||
| | <a name="input_snowflake_loader_user"></a> [snowflake\_loader\_user](#input\_snowflake\_loader\_user) | Snowflake username used by loader to perform loading | `string` | n/a | yes | | ||
| | <a name="input_snowflake_password"></a> [snowflake\_password](#input\_snowflake\_password) | Password for snowflake\_loader\_user used by loader to perform loading | `string` | n/a | yes | | ||
| | <a name="input_snowflake_password"></a> [snowflake\_password](#input\_snowflake\_password) | Snowflake password as a string or an object `{ ec2ParameterStore: { parameterName: "<parameter name>" }}`, for snowflake_loader_user used by loader to perform loading | `string\|map` | n/a | yes | |
There was a problem hiding this comment.
Rather than overloading this parameter can you instead just add a new variable of snowflake_password_from_parameter_store_arn - if this is populated it can favor using this as the option and the config can be updated conditionally?
There was a problem hiding this comment.
Thanks for the feedback. That's what I initially did before 47c6cd2, I will revert back.
It's not an ARN, so will use snowflake_password_from_parameter_store_name, if that's ok?
There was a problem hiding this comment.
Dropped that commit, and renamed the parameter to match the suggestion.
Ah, good catch. I had attached |
thomas-brx
force-pushed
the
support-for-parameter-store-passwords
branch
from
47c6cd2 to
d0edf95
Compare
Statement to allow Caveat - does not add statements to allow decryption of SecureString parameters - this would require knowing which KMS key was used. Let me know if I you think I should add support for that as well. |
3 participants
This PR fixes #18 by adding support for a new variable:
snowflake_password_from_parameter_store_name.The variable is validated according to the AWS documentation, but ignoring some rules like
A parameter name can't be prefixed with "aws" or "ssm".Caveat: Does add a policy statement to allow access to the parameter, but does not add any policy to decrypt the parameter if it's stored as SecureString.