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
This is a pretty easy story to write. We should validate that S3 bucket exists after role assumption and before acquisition. If the bucket does not exist Raise() a custom exception.
Additionally good house keeping would also be to Raise() a custom exception based on the SSM RunCommand exit code for the script. ( Should in theory exit -1 for this kind of thing ) You can parse the response and raise.
I configured .threatreponse.ini with an S3 bucket that does not exist and ran
ssm_acquire --instance_id i-XXXXXXX --region us-west-2 --acquire
The command reports success.
Expected behavior would be an error.
The text was updated successfully, but these errors were encountered: