Managing check-in/check-out and power management of Instances
Bravura Security Fabric can manage Amazon virtual servers in addition to standard user management. In this case, Bravura Security Fabric can start and stop individual servers through Bravura Privilege check-out/check-in process.
Note
Virtual servers (instances) are listed as accounts in Bravura Privilege. In these cases, the account ID is prefixed with _instance.
Checking out an instance:
Ensures only a single person has access to it at any one given time.
Allows for authorization and approval of use of the instance via work-flow.
Powers on the instance, on demand, so that instances are not left running.
When the end user is finished with the instance they can check it in, which will:
Power off the instance, so that extra running costs are not incurred.
Allow access to the instance by other users.
Note
The instance is automatically checked in after the expiry time, in case the end user forgets to check it back in.
The following example shows how to check-out (or power on) an instance:
Add the AWS target.
Run
to list accounts (and instances).psupdate
Add an IDAPI user.
Manage the AWS accounts whose account ID is pre-fixed with
_instance
.Copy the sample file
pxnull-awsco.cfg
to the instance script folder.Update the credentials of the IDAPI user in
pxnull-awsco.cfg
.Configure the plugin points RES_CHECKOUT_SUCCESS and RES_CHECKIN_SUCCESS to execute
pxnull.exe -cfg pxnull-awsco.cfg
.As an end user, check-out the instance.
After the request is approved, verify the instance is powered on.
Check-in the instance, and verify the instance is powered off.