ACM.439 Deploy a 2SL task execution environment — Step 2 — Add a task configuration parameter to deploy a single resource
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ ~~~~~~
⚙️ Part of my series on Automation of cybersecurity measures. THE Coded.
🔒 Related Stories: AWS Security | Application security | Batch jobs
💻 Free content on Cybersecurity Jobs | ✉️ Register for Broadcast list
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ ~~~~~~
In the last article, I created a new batch job type for my job execution framework by adding a new repository, Dockerfile, and execution.sh file.
In this article, I want to define an SSM parameter with configuration for my batch job so that I can use the value of this parameter for the CloudFormation template parameters and the job execution environment arguments.
TLDR;
Add a job configuration parameter SSM that looks like this:Name:
/job/awsenvinit/root-admin/organizations-organizationalunit-dev
Value:
env=dev
region=us-east-2
cfparamParentid=:get_id:organization:organizationalunit:root
Add this command to execute.sh in your job:
deploy /job/awsenvinit/root-admin/organizations-organizationalunit-dev
Future: just pass that above job parameter name into the awsdeploy container
The 2nd Sight Lab Job Execution Framework does the rest.
SSM Settings for Task Configurations Revisited
I’ve already explained how to use SSM settings for task configuration here.