Linqpad connection password NO after imaging the instance on server

I was trying to use linqpad on our windows server for basic DB queries, but the connection string doesn't work after we create an Image(AMI) on AWS > And relaunch the instance using that AMI.

I think that Linqpad store the connection/password decryption key somewhere in local system cache, which is not migrated to AMI and then to new machines while imaging. This causes all the connection lost and automation scripts not to work.

Any workaround?

Comments

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!