You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
After reviewing the documentation referenced here, it appears like AWS SSM is not currently supported. It would be amazing to support this AWS service so that we can get some drift detection on these resources.
Example
Ideal scenario, I can setup a .driftignore file that looks like this:
*
!aws_ssm_parameter*
Then when I run driftctl, I can either query my statefiles in S3 or pull them down locally to compare and see the diff.
Thanks again in advance for considering this. Systems manager within itself has a lot of different features. I know SSM could be handling sensitive information since it could be dealing with secrets/properties.
The text was updated successfully, but these errors were encountered:
Description
After reviewing the documentation referenced here, it appears like AWS SSM is not currently supported. It would be amazing to support this AWS service so that we can get some drift detection on these resources.
Example
Ideal scenario, I can setup a
.driftignore
file that looks like this:Then when I run
driftctl
, I can either query my statefiles in S3 or pull them down locally to compare and see the diff.Thanks again in advance for considering this. Systems manager within itself has a lot of different features. I know SSM could be handling sensitive information since it could be dealing with secrets/properties.
The text was updated successfully, but these errors were encountered: