Can we run command as background process through AWS SSM?

Question

I am trying to sync a S3 bucket which takes close to 3 hours to completely sync.

sync-bucket.sh:

nohup aws s3 sync "$source_bucket/$folder/" "s3://$destination_bucket/" \
        --profile abc --acl bucket-owner-full-control --sse "aws:kms" \
        --sse-kms-key-id "$KEY_ARN" > /var/log/$folder.log 2>&1 &

echo "Successfully triggered the sync job"

I was hoping to trigger the sync job using AWS SSM send command something like below:

trigger.sh:

COMMAND=$(aws ssm send-command --document-name "AWS-RunShellScript" \
            --targets "Key=instanceids,Values=${RECOVERY}"  \
            --parameters '{"executionTimeout":["10800"],"commands":["/opt/scripts/sync-bucket.sh"]}' \
            --output-s3-bucket-name "some-bucket" \
            --timeout-seconds 10800 \
            | jq -r '.Command.CommandId')

My observation is that SSM waits for this background job to finish before marking the execution as 'Success'. Is there a way we could perhaps just trigger the background job and make SSM finish the execution without having to wait for background job to finish?

Or is there a better way of doing this? I am basically trying to automate the process here and happy to let the job running in background on demand without having to login to instance and run command manually.

Thanks for your time.

**Side-note:** The `aws` command includes a `--query` parameter that will normally remove the need to use `jq`. — John Rotenstein, Sep 18 '20 at 06:46
Have you tried running the script through [nohup](https://www.maketecheasier.com/nohup-and-uses/)? — Marcin, Sep 18 '20 at 07:12

MyUsername112358 · Answer 1 · 2021-03-23T13:02:05.377

3

The issue isn't that SSM is waiting for your background command to finish, it's that your command isn't actually put into background because your nohup command waits for input. To fix, replace nohup whatever_your_command_is & by nohup whatever_your_command_is < /dev/null 2> /dev/null > /dev/null &

edited Mar 23 '21 at 13:02

answered Mar 23 '21 at 12:04

MyUsername112358

1,320
14
39

1

`nohup whatever_command >/dev/null 2>&1 &` worked for me. There's a conversation about the Go libraries involved here: https://github.com/go-cmd/cmd/issues/20#issuecomment-407701181 – russau Sep 04 '21 at 06:34

Can we run command as background process through AWS SSM?

1 Answers1