The usage above should suffice for the efficient provisioning of many instance of the images you're already using. If you'd like to use the prototype to start annexes, the procedure is somewhat involved. The basic idea is as follows: when HTCondor starts up (this may be replaced by "when the OS finishes booting" in future releases), it runs a script which looks at the permissions which have been granted to the instance. (Obviously, this fails if the instance hasn't been granted permission to look at its own permissions.) If one of those permisssions is read access to a specific file in a specific S3 bucket, the script downloads the file into the HTCondor =config.d= directory, or, if the file is a tarball, untars it there. Because this mechanism is entirely independent of the usual userdata-dependent contextualization methods, it can be used to dynamically configure HTCondor regardless of an how an instance otherwise might configure itself. We expect this ability to generally be used to configure HTCondor to join one specific pool or another. -We have provided a second CloudWatch template to help construct this mechanism. Actually, because we hope it's easier than editing the template, we have provided a script which -- given the S3 bucket name and file -- outputs a CloudFormation template which creates the corresponding IAM role and instance profile. Download and run the attached file =generate-role=: =generate-role bucketName fileName > role.json= and follow the instructions above (under "Lambda function") to create the corresponding stack (you'll have to name it something else). The _bucketName_ must be a bucket you can write to, and the _fileName_ should probably be something like =config.tar.gz=. Note -- you don't need to, nor do you probably want to, give the configuration file read permission in S3; the role provides the necessary authorization. This keeps _fileName_ private. For this stack, the output will be called "InstanceConfigurationProfile". +We have provided a second CloudWatch template to help construct this mechanism. Actually, because we hope it's easier than editing the template, we have provided a script, attached as =generate-role= which -- given the S3 bucket name and file -- outputs a CloudFormation template which creates the corresponding IAM role and instance profile. Run the script as follows: =generate-role bucketName fileName > role.json= and follow the instructions above (under "Lambda function") to create the corresponding stack (you'll have to name it something else). The _bucketName_ must be a bucket you can write to, and the _fileName_ should probably be something like =config.tar.gz=. Note -- you don't need to, nor do you probably want to, give the configuration file read permission in S3; the role provides the necessary authorization. This keeps _fileName_ private. For this stack, the output will be called "InstanceConfigurationProfile". You'll need to create some configuration to upload. For testing purposes, any valid configuration will do; you just want to be able to check that HTCondor is using the configuration. (For example, you could create a file name =17custom=, with the following contents:
