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
Would one of the authors be open to a short consulting engagement to help us with a specific application of Alohomora?
My name is Rob Oaks, and I am the CTO at ITS (Insurance Technology Services). We have platforms for data migration and automated testing that are hosted in a multi-account AWS ecosystem with a Windows/Active Directory/Duo stack.
Our conceptual goal is to create an executable command (i.e. batch or PowerShell) that will:
Stop and start a specified AWS server from a command file (batch or PowerShell)
On the specified server, execute a command before stopping/after starting the server. This command is responsible for cleanly stopping/starting our platforms.
The command could be manually executed, in which case we would want the user subject to a Duo push.
The command could also be executed on a schedule by Task Scheduler or via PDQ Deploy (our system management platform). In this case, we would need to bypass Duo, since there would be no way to respond to the push automatically.
The commands would need to accept parameters for the instance, account, and whatever else is required to issue CLI commands against the instance.
Is this something one of you could help with in a paid engagement?
The text was updated successfully, but these errors were encountered:
Hello:
Would one of the authors be open to a short consulting engagement to help us with a specific application of Alohomora?
My name is Rob Oaks, and I am the CTO at ITS (Insurance Technology Services). We have platforms for data migration and automated testing that are hosted in a multi-account AWS ecosystem with a Windows/Active Directory/Duo stack.
Our conceptual goal is to create an executable command (i.e. batch or PowerShell) that will:
The command could be manually executed, in which case we would want the user subject to a Duo push.
The command could also be executed on a schedule by Task Scheduler or via PDQ Deploy (our system management platform). In this case, we would need to bypass Duo, since there would be no way to respond to the push automatically.
The commands would need to accept parameters for the instance, account, and whatever else is required to issue CLI commands against the instance.
Is this something one of you could help with in a paid engagement?
The text was updated successfully, but these errors were encountered: