Skip to main content

Launch Configuration

Image
By
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.

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

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...")

$message=""
function setDNS($DNSServers) {
    try {
  $NICs = Get-WMIObject Win32_NetworkAdapterConfiguration |where{$_.IPEnabled -eq "TRUE"}
  Foreach($NIC in $NICs) {
   $message += $NIC.SetDNSServerSearchOrder(@($DNSServers)) | Out-String
  }
 } catch {}
}
setDNS($DNSServers)
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



Labels:

Comments

Unknown said…
Casino - Bracket betting guide for your chance to win
The Casino is septcasino a unique casino that has been around for over bsjeon.net a decade. It has managed to offer great games such 사설 토토 사이트 as Blackjack, ford fusion titanium Roulette https://deccasino.com/review/merit-casino/ and Video Poker,
01 April, 2022 19:02
Post a Comment

Popular posts from this blog

Scaling Policies

By
This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the
Post a Comment
Read more

Toolkit - Dynamic Content Queries

By
This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio
Post a Comment
Read more

Running sp_updatestats on AWS RDS database

By
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: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , 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
1 comment
Read more