Skip to main content

Launch Configuration

This post is part of a bigger topic Autoscaling Publishers in AWS.

Each Auto Scaling Group in AWS is based on a Launch Configuration. The Launch Configuration cannot be modified once it's created, but it can however be copied and modified.

Once Auto Scaling is in place, the instances it creates will all be based on the specified Launch Configuration.

Creating a Launch Configuration implies specifying the AMI, the Instance Type, Security IAM role, EBS drive, security group and open incoming ports. All these are AWS settings and they don't make the object of this post.

What is particularly interesting is the section Configure details, subsection User data. This is where one can specify either a script of a file containing a script that will be executed inside the instance once it is created and it starts. Using this mechanism we created PowerShell scripts to configure each Publisher instance in part.

aws s3 cp s3://mybucket/scripts/publisher_userdata.ps1 D:\scripts\publisher_userdata.ps1
D:\scripts\publisher_userdata.ps1 2>&1 > D:\userdata.log

The implementation we used here is to copy a PowerShell script from an S3 bucket into the instance; then, execute the script inside the instance. This approach is flexible in the sense that one doesn't have to recreate the Launch Configuration in order to make modifications to the user data script.

The highlights of the script below show how the instance is configured. First the DNS is set on the server. Then a series of scripts are copied from S3 bucket to the local harddisk. The same mechanism is used to copy patches (jars, dlls, config files) when needed, without having to recreate the AMI.

The downloaded scripts are going to be executed on a subsequent reboot of the machine. During this initial execution, the machine is renamed to the name that has been extracted from the license server, but more about that in the following post.

$Logfile = "D:\tst.log"
Function LogWrite {
   Param ([string]$logstring)
   Add-content $Logfile -value $logstring
LogWrite("Start script...")

function setDNS($DNSServers) {
    try {
  $NICs = Get-WMIObject Win32_NetworkAdapterConfiguration |where{$_.IPEnabled -eq "TRUE"}
  Foreach($NIC in $NICs) {
   $message += $NIC.SetDNSServerSearchOrder(@($DNSServers)) | Out-String
 } catch {}
echo "DNS settings done"
LogWrite("DNS changed.")

LogWrite("downloading resume scripts")
Rename-Item "D:\SDL Web\lib\cd_transport.jar" cd_transport.jar_old
aws s3 cp s3://mybucket/jar/cd_transport-8.5.0-1050.jar "D:\SDL Web\lib\cd_transport-8.5.0-1050.jar"
aws s3 cp s3://mybucket/scripts/resume-workflows.ps1 d:\scripts\resume-workflows.ps1
aws s3 cp s3://mybucket/scripts/resume-workflows.cmd d:\scripts\resume-workflows.cmd
aws s3 cp s3://mybucket/scripts/resume_powershell_workflows.xml d:\scripts\resume_powershell_workflows.xml
aws s3 cp s3://mybucket/scripts/join_ad.ps1 d:\scripts\join_ad.ps1
aws s3 cp s3://mybucket/scripts/cleanup.ps1 d:\scripts\cleanup.ps1
aws s3 cp s3://mybucket/scripts/dns.ps1 d:\scripts\dns.ps1
aws s3 cp s3://mybucket/scripts/run-change-dns.cmd d:\scripts\run-change-dns.cmd
aws s3 cp s3://mybucket/config/cd_transport_conf.xml "D:\SDL Web\config\cd_transport_conf.xml"
aws s3 cp s3://mybucket/config/Tridion.ContentManager.config "D:\SDL Web\config\Tridion.ContentManager.config"

LogWrite("Creating scheduled task")
SchTasks /Create /SC ONSTART /RL HIGHEST /RU SYSTEM /TN "Resume Powershell Workflows" /TR "d:\scripts\resume-workflows.cmd"

LogWrite("Renaming & Rebooting...")
Rename-Computer -NewName $license_hostname -Force -Restart


Unknown said…
Casino - Bracket betting guide for your chance to win
The Casino is septcasino a unique casino that has been around for over a decade. It has managed to offer great games such 사설 토토 사이트 as Blackjack, ford fusion titanium Roulette and Video Poker,

Popular posts from this blog

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: I stumbled upon the following post from 2008 (!!!), , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Event System to Create Mapped Structure Groups for Binary Publish

As a continuation of last week's Publish Binaries to Mapped Structure Group , this week's TBB is in fact the Event System part of that solution. Make sure you do check out the previous post first, which explains why and what this Event System does. To reiterate, the Event System intercepts a Multimedia Component save, take its Folder path and create a 1-to-1 mapping of Structure Groups. The original code was written, again, by my colleague Eric Huiza : [ TcmExtension ( "MyEvents" )] public class EventsManager  : TcmExtension {     private Configuration configuration;     private readonly Regex SAFE_DIRNAME_REGEX = new Regex ( @"[\W_]+" );     public EventsManager() {         ExeConfigurationFileMap fileMap = new ExeConfigurationFileMap ();         fileMap.ExeConfigFilename = Path .GetDirectoryName( Assembly .GetExecutingAssembly().Location) + "\\EventSystem.config" ;         configuration = ConfigurationManager