Creating an AWS Engine AMI
To use the adapter with Amazon AWS, you must first create an Engine AMI and an auto scaling group based on that AMI.
Prerequisites
Before creating an Engine Image, ensure that the following requirements are met:
-
Disable the firewall on the machine or open all the appropriate ports for the Engine.
-
Install the Engine. You can install the Engine with the Director you plan to use for production or for a Director you use for a Development or QA grid. The adapter submits user data to AWS to reconfigure the Engine to use the Director for the grid.
-
Create an auto scaling group. For more information, see Creating an Auto scaling Group on AWS.
Related information
Creating an Engine AMI on Linux
Procedure
-
Shut down the Engine Daemon after the Engine starts running against the first Director.
-
Verify that the Engine Daemon does not start automatically at boot.
-
Save the AMI.
-
Create a launch template using the AMI created above and User Data as given in User Data for AWS.
-
Update
cloudprovider.propertieswith auto scaling group details.
Creating an Engine AMI on Windows
Procedure
-
Shut down the Engine Daemon after the Engine starts running against the first Director.
-
Verify that the Engine Daemon does not start automatically at boot. This is very important for Windows since it installs as a service by default. The service needs to be set for Manual start.

-
Access
gpedit.mscto enable PowerShell scripts. Go to Local Computer Policy > Computer configuration > Administrative Templates > Windows Components > Windows PowerShell > Turn on Script Execution. -
In the Turn on Script Execution window, select Enabled in the top left, then in the Options section, select Allow all scripts.

-
Go to Start > All Programs > EC2ConfigService > Settings. On the General tab, select the checkbox next to Enable in the User Data section. Also select Set the computer name of the instance... in the Set Computer Name section.

-
Save the AMI.
-
Create a launch template using the AMI created from the previous step and User Data as given in User Data for AWS.
-
Update
cloudprovider.propertieswith the auto scaling group details.
User Data for AWS
Linux
#!/bin/bash
//Stopping the engine
cd /opt/Datasynapse/engine
./engine.sh stop
//running the configure utility
./configure.sh -s DIRECTOR_HOST:DIRECTOR_MESSAGE_PORT
//Re-Starting the engine
./engine.sh start
If you are configuring the adapter over an SSL-enabled Manager, use the following configure command instead:
//running the configure utility
./configure.sh -s DIRECTOR_HOST:DIRECTOR_MESSAGE_PORT -l y
Windows
<powershell>
Stop-Service DataSynapse
$dsfolder="C:\Tibco\Datasynapse\Engine"
$director="ip-172-31-0-39"
$directorPort="8000"
Remove-Item -Recurse -Force "$($dsfolder)\profiles\"
$datfile="$($dsfolder)\intranet.dat"
$contents = [IO.File]::ReadAllText($datfile)
$httPrefixDelim="://"
$endpos=$contents.IndexOf
($httPrefixDelim)+$httPrefixDelim.Length
$newPrefix=$contents.Substring(0,$endpos)
"$($newPrefix)$($director):$($directorPort)/livecluster
/public_html/register/register.jsp".Trim() | Out-File -Encoding Ascii $datfile
Start-Service DataSynapse
</powershell>