Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

How to write bash or shell script in SSM run command and execute in linux ec2 instance?

B
baileigh last edited by

I want to run the bash or shell script in Linux using the SSM run command. But I don't want to write it on the Linux server and execute it remotely using the SSM command. I want to write a script in the run command itself.

Is there any way to run a script from the AWS console? Apart from the run command is there any other way to run the whole script?

I am referring to the multiline script not only one command.
Reply Quote 0
1 Reply Last reply
Demir last edited by

First option using aws "CloudShell" service (available only in specific region).

Alternately, you can execute shell script using AWS Systems Manager > Run Command > Run a command, Select the type of command that you want to run & Search by keyword " AWS-RunShellScript " (Linux platform only).

In Command Parameters, specify a shell script or a command to run.

PS : For both Windows & Linux platform, search by keyword " AWS-RunPowerShellScript "
Reply Quote 0
1 Reply Last reply

2
Posts

0
Views

Suggested Topics

E

How to export data from AWS RDS MySQL database and import to an other AWS RDS MySQL database instance
SQL, Database Testing • mysql amazon rds amazon web services etl • • elysha

2

0
Votes

2
Posts

1
Views

T

A simple way of copy an entire database is to create a read replica of the original and promote this read replica into a separate database.
K

"Route.post() requires a callback function but got a Object" using multer
Software Programming • javascript node.js amazon web services route multer • • Kadyn

2

0
Votes

2
Posts

0
Views

Exports uploadDon't call him. multerYou've already got it.module.exports = upload
J

Assertions for CLI Commands in CI/CD environment
Continuous Integration and Delivery (CI, CD) • cypress • • jonetta

2

0
Votes

2
Posts

1
Views

If you want to roll your own bash script you can model it on mine at https://durrantm.wordpress.com/2015/04/02/tdd-for-sh/ See below. So you could do something like: # Define the function $ check_git () { git grep '>>>>> HEAD' && return 1; return 0; } # Call the function $ check_git # do something based on return code - $? # "To check the exit code we can simply print the $? special variable in bash. # This variable will print the exit code of the last run command" The code below is the full detail of my code which essentially lets you use do_test some_bash_function expected_result other_param1 other_param2 ... Code: #!/usr/bin/env bash . colors_for_text.sh 2> /dev/null do_test () { if [[ $# -eq 0 ]]; then printf "$fail_color Error - do_test: No parameters provided - Usage is do_test [function_name] \$LINENO [expected result] [optional params]\n" exit 1 elif [[ $# -eq 1 ]]; then printf "$fail_color Error - do_test: Two parameters missing - \$LINENO and expected result (other params as needed)\n" exit 1 fi declare -ig test_runs test_passes test_fails local -r function="$1";shift local -r line_number="$1";shift local failfast="False" local debug="False" local verbose="False" local test_description= local test_matcher= local expected= local pass_on_params= local command_not_found=False type "setup" &> /dev/null && setup # TODO Replace with for loop (initial attempts failed) [[ "$1" == "failfast" ]] && failfast="True" && shift [[ "$1" == "debug" ]] && debug="True" && shift [[ "$1" == "verbose" ]] && verbose="True" && shift [[ "$1" == "failfast" ]] && failfast="True" && shift [[ "$1" == "debug" ]] && debug="True" && shift [[ "$1" == "failfast" ]] && failfast="True" && shift if [[ "$1" =~ ^description= ]]; then [[ `echo $1 | grep =` ]] && test_description=`echo $1 | sed 's/.*=//'`' ' && shift fi if [[ "$1" =~ ^matcher= ]]; then [[ `echo "$1" | grep =` ]] && test_matcher="`echo "$1" | sed 's/matcher=//'`" && shift fi if [[ $# -eq 0 ]]; then printf "$fail_color Error - Function: $function, Line: $line_number \n do_test: Third parameter missing - expected result\n" exit 1 fi expected="$1";shift pass_on_params="$@" $function ${pass_on_params[@]} 2> $TMPDIR"/output$$-"$test_runs".txt" cat $TMPDIR"/output$$-"$test_runs".txt" | grep -i "command not found" && command_not_found=True debug_printf "(debug)" if [[ $command_not_found == "True" ]]; then record_script_failure "$function" elif [[ "$test_matcher" == "==" ]]; then [[ "$result" == $expected ]] && record_test_success "$function" || record_test_failure "$function"; elif [[ "$expected" =~ ^-?[0-9]+$ ]]; then [[ "$result" -eq $expected ]] && record_test_success "$function" || record_test_failure "$function"; else [[ "$result" == $expected ]] && record_test_success "$function" || record_test_failure "$function"; fi test_runs+=1 } record_test_success () { [[ $# -eq 0 ]] && no_param_quit $FUNCNAME local -r function="$1" printf "$pass_color"."$color_end" [[ "$verbose" == "True" ]] && printf "$function" test_passes+=1 } record_test_failure () { [[ $# -eq 0 ]] && no_param_quit $FUNCNAME local -r function="$1" test_fails+=1 printf "$fail_color"F"$color_end" function_exists? "$function" && error_messages=$error_messages"$fail_color""$test_description""Line: $line_number - \ '$function ${pass_on_params[@]}' failed:\n\ Expected: $expected\n\ Received: $result $color_end\n\n" || error_messages=$error_messages"$fail_color""Line: $line_number: \ Function '$function' is undefined\n" [[ "$failfast" == "True" ]] && failfast "Test" $error_messages } record_script_failure () { [[ $# -eq 0 ]] && no_param_quit $FUNCNAME local -r function="$1" test_fails+=1 err=`cat $TMPDIR"/output$$-"$test_runs".txt"` printf $err error_messages=$error_messages"$fail_color""Line: $line_number: \ Error within function '$function', getting \"command not found\" in $err \n" [[ "$failfast" == "True" ]] && failfast "Script" $error_messages } failfast () { printf "\n$1 error & failfast set to exit immediately.\n$2\n" && exit 1 } no_param_quit () { printf "\nError - 1 parameter required for: $1 - exiting\n" && exit 1 } function_exists?() { declare -f -F $1 > /dev/null return $? } debug_echo () { [[ "$debug" == "True" ]] && echo "$1" } debug_printf () { [[ "$debug" == "True" ]] && printf "$1" }
K

CodeBuild - multiple input artifacts in AWS Pipeline
Continuous Integration and Delivery (CI, CD) • amazon web services build pipeline • • Kadir

2

0
Votes

2
Posts

1
Views

C

We've had exactly the same problem - our build stage needs to use information from two separate locations. To solve this in a generic manner, I've created two general purpose Lambdas - one that will merge artifacts, and one that will extract specific files from an artifact. In both cases a new artifact is created that can be passed on to a subsequent CodePipeline stage. See https://github.com/tooltwist/codepipeline-artifact-munge If it does not meet your exact requirement, it should be easy enough to tweak to do what you need.
N

SaltStack: Use Temporary Scripts And Not Cause State Changes To Reported
Continuous Integration and Delivery (CI, CD) • salt • • nishika

2

0
Votes

2
Posts

1
Views

You might want to consider adding an unless or onlyif requisite in the first directive - especially if script.sh is particularly complicated or expensive. With unless or onlyif, you will use the reults of several BASH commands to determine if you need to push down and execute your script. If your system is out of plumb only then is the state enforced. If everything checks out OK, then the script will never be pushed and executed preventing changed=2 in the final status report. You will want to use a require requisite for the second and third directives to prevent them from running if the script is not pushed by file.managed otherwise you will get to errors instead of two changes.
Value of succeeded() in Azure DevOps pipeline before first stage is run
Continuous Integration and Delivery (CI, CD) • azure devops azure pipelines • • Mystic

2

0
Votes

2
Posts

0
Views

M

Five minutes later I found this dealt with at https://github.com/MicrosoftDocs/azure-devops-docs/issues/7738 . Indeed, it appears that the Succeed outcome is not set until a stage has actually been executed. One respondent in the discussion indicates that this has worked for them: As a work-around, our team has had success (no pun intended) using: condition: not(or(failed(), canceled()) This works because the previous stage being skipped does not set a failed status.
R

Jenkins Pipeline - conditional execution with branch and 1 other parameter (manual)
Continuous Integration and Delivery (CI, CD) • jenkins jenkins pipeline • • rosemadder

2

0
Votes

2
Posts

1
Views

If I got it right, you could try to tag by using environment variables. Maybe something defined in the environment {} directive within the stage. E. g. $PROD = xyz_prod Then, when { branch 'master' tag: $PROD } Not sure why your approach failed, but building tags on a script using variables could do the trick.
J

Is there a way through which I can control type of load balancer like round robin , least-connections
Continuous Integration and Delivery (CI, CD) • kubernetes amazon web services helm load balance • • jonetta

2

0
Votes

2
Posts

1
Views

Well there are 2 possibble options. One is to create a LoadBalancer type for each service you want to be exposed. In case you have just one service that's great. That's rarely the case of course If you build your k8s cluster properly ( having Prometheus-Operator doing the monitoring for example ) most likely besides the business logic service/s, you would want to expose internal cluster valuable services like Grafana. That's why even if you have just 1 service, for future extension of such type of need the best would be to use an Ingress resource. It providees a way to expose multiple services through a single IP address — HTTP level (network layer 7). You could play with HTTP headers essentially and do some path/host routing. You express the definition for your object and helm would do the installation. Another option is to use a tool like ArgoCD, basically sticking to GitOps policy. A fundamnetal knowledge is to be aware that the Load Balancer/Ingress would forward the traffic to the service, not the pods. Services are abstracted entities by kube-proxy, by default kube-proxy uses a round-robin algorithm. https://kubernetes.io/docs/concepts/services-networking/service/ Regarding the definition, it follows the standart K8s scheme [ apiVersion, kind, metadata, spec fields]. Example would be an Ingress created from AWS-Ingress-Controller. apiVersion: extensions/v1beta1 kind: Ingress metadata: name: ingress namespace: management annotations: kubernetes.io/ingress.class: alb alb.ingress.kubernetes.io/scheme: internet-facing spec: rules: - host: grafana.com http: paths: - backend: serviceName: grafana servicePort: 80 path: /* ```
G

Bad practice having a single SSH gateway with access to all environments?
Continuous Integration and Delivery (CI, CD) • security amazon web services • • guilherme

2

0
Votes

2
Posts

1
Views

J

I assume your users connect to the gateway with ssh (possibly with additional credentials like a hardware-generated one-time-password), and then jump to the actual servers with a second ssh connection. In itself, this is fine (and the usual thing that's done regularly by companies I've worked with). The secondary ssh connection (still) takes care of only letting those people in who are authorized. The job of the gateway is primarily to avoid the need for the ssh port of the servers to be open to the internet on the network level. Obviously, you want to avoid people opening ssh tunnels, using proper settings in your global ssh/sshd configuration, and you will want to tighten down the gateway itself (for example, by having read-only home directories for your incoming users; and having no tools installed that can help in somehow bypassing any of your rules - i.e., no telnet, netcat and so on; ideally a chroot environment in which nothing except the ssh executable is available).
Why my docker container is running on swarm manager node instead of worker?
Continuous Integration and Delivery (CI, CD) • docker docker swarm • • Mystic

2

0
Votes

2
Posts

0
Views

K

A manager is able to run containers just as workers do. To prevent workloads from running on the manager, you need to include a constraint. This is different from the kubernetes model where the managers are tainted and you include a toleration to run on managers. version: "3.4" services: redis: image: redis:alpine ports: - "6379" networks: - frontend deploy: replicas: 1 update_config: parallelism: 2 delay: 10s restart_policy: condition: on-failure # add the below constraint placement: constraints: - "node.role==worker" networks: frontend: volumes: db-data: For more on the placement policies and constraints, see: https://docs.docker.com/compose/compose-file/compose-file-v3/#placement https://docs.docker.com/engine/reference/commandline/service_create/#specify-service-constraints---constraint
O

How to allow a non-root user to write to a mounted EFS in EKS
Continuous Integration and Delivery (CI, CD) • kubernetes kubernetes helm • • Oba22

2

0
Votes

2
Posts

1
Views

If anyone comes across this later I resolved my issue by using an initContainer for any Pod that needed to write to the file system. For example: apiVersion: v1 kind: Pod metadata: name: app3 spec: containers: - name: app3 image: busybox command: ["/bin/sh"] args: ["-c", "while true; do echo $(date -u) >> /data/out3.txt; sleep 5; done"] volumeMounts: - name: persistent-storage mountPath: /data securityContext: runAsGroup: 1337 initContainers: - name: fs-owner-change image: busybox command: - chown - "root:1337" - "/efs-fs" volumeMounts - mountPath: /efs-fs name: cog-data securityContext: fsGroup: 1337 volumes: - name: persistent-storage persistentVolumeClaim: claimName: efs-claim ``` The rest of the definitions match what was in my question. Working sort of off what @JerryChen suggested ("use access points") I discovered that things were simpler if I just used a dynamically provisioned EFS which does utilize EFS access points to allow shared access to an EFS instance. Below is the StorageClass, PersistentVolumeClaim, and an example Pod. kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: efs-sc provisioner: efs.csi.aws.com parameters: provisioningMode: efs-ap fileSystemId: {{ .Values.efsVolumeHandle }} directoryPerms: "775" reclaimPolicy: Retain --- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: efs-claim spec: accessModes: - ReadWriteMany storageClassName: efs-sc resources: requests: storage: 5Gi # Not actually used - see https://aws.amazon.com/blogs/containers/introducing-efs-csi-dynamic-provisioning/ --- apiVersion: v1 kind: Pod metadata: name: app3 spec: containers: - name: app3 image: busybox command: ["/bin/sh"] args: ["-c", "while true; do echo $(date -u) >> /data/out3.txt; sleep 5; done"] volumeMounts: - name: persistent-storage mountPath: /data securityContext: runAsUser: 1000 runAsGroup: 1337 fsGroup: 1337 volumes: - name: persistent-storage persistentVolumeClaim: claimName: efs-claim ``` Note the directoryPerms (775) specified in the StorageClass, as well as the runAsGroup and fsGroup specified in the Pod. When utilizing this PVC in a Pod that runs as a non-root user shared a user group number is the key. runAsUser was only used to ensure the busybox command was executed by a non-root user. This is likely leagues better than brute-forcing the file system permissions using an initContainer
M

How to programmatically enable and disable SQS triggering AWS Lambda?
Continuous Integration and Delivery (CI, CD) • amazon web services aws lambda aws iam serverless amazon sqs • • meriah

2

0
Votes

2
Posts

1
Views

P

Call Lambda's UpdateEventSourceMapping API with the {"Enabled":true/false} request body. If, for some reason, you want your own API for this, you can create one in API Gateway as described below. Before you begin, you need the UUID of the event source mapping you wish to enable/disable. Use the AWS CLI to get this (it isn’t shown on the UI): aws lambda list-event-source-mappings --function-name my-func { "EventSourceMappings": [ { "UUID": "b962dcee-173c-47r1-9600-5c6d81catf85", "BatchSize": 1, "EventSourceArn": "arn:aws:sqs:us-east-1:123456789012:my-queue", "FunctionArn": "arn:aws:lambda:us-east-1:123456789012:function:my-func", "LastModified": 1595058588.141, "State": "Enabled", "StateTransitionReason": "USER_INITIATED" } ] } Next, either create a new API in API Gateway or add a resource & a GET method to your existing API. Configure it as shown below. The UUID you got above is highlighted below: The execution role shown above must allow API Gateway to invoke Lambda APIs. Scroll further down & provide this mapping template: Content-Type: application/json { "Enabled" : $input.params("Enabled") } Save & deploy to a stage. Now you can hit this API with the query param Enabled=true / Enabled=false to enable/disable your Lambda's SQS trigger. Here's a test done from the API Gateway console: For a detailed screenshot-guided walkthrough of this entire process, see my blog post.
S

how to set automatic git pull from bitbucket and complie project on ec2 instance create event
Continuous Integration and Delivery (CI, CD) • deployment amazon ec2 autoscaling • • simrah

2

0
Votes

2
Posts

1
Views

M

You want to make use of user_data scripts. It's basically a bootstrap shell script that gets executed on an instance during launch. You can embed your app configuration script in there (either directly via bash, or have it call your configuration management software like Ansible or Chef). Then, if you attach this script to a Launch Template or a Launch Configuration (which is an instance template required as part of an AWS ASG), it will be applied to the whole autoscaling group. Then, when you have a scaling event, any new instances that come up in the ASG will run the script and deploy your code. However, I would recommend you look into immutable infrastructure instead. I.e. set up automation (i.e. via Packer) that builds your application code into your AMI, with user_data only used for actually starting the app. Then, when you have a new build, have the same automation build a new AMI and replace your ASG (note you'll need to have your ASG created/deployed in a programmatic fashion.. I personally recommend Terraform).
A

docker command substitution fails on gitlab
Continuous Integration and Delivery (CI, CD) • bash gitlab docker swarm • • Avante

2

0
Votes

2
Posts

0
Views

I think this is a problem with https://wiki.bash-hackers.org/syntax/expansion/cmdsubst . $(`printf "docker-compose.%s.unimark.yaml" "$SRV_DEPLOY_ENV"`) or DOCKER_COMPOSE_DEPLOY_FILE=`printf "docker-compose.%s.unimark.yaml" "$SRV_DEPLOY_ENV"` $($DOCKER_COMPOSE_DEPLOY_FILE) To bash is interpreted the same: please execute the command that is the result of this nested command. Removing the backtick in the first instance or removing the parenthesis in the second one should do the trick.
Issue in running docker container on ecs
Continuous Integration and Delivery (CI, CD) • amazon web services amazon ec2 amazon ecs • • emmalee

2

0
Votes

2
Posts

0
Views

E

Did you choose/select ecsTaskExecutionRole? When creating a new task definition. Cause it's a must. OR create a role manually for tasks that gives API requests permission to AWS services. Also, give task execution role IAM (you may use the same one created before) Update: I deployed your image with ECS EC2 and it's working fine... I'm not sure but I think you have issues using/defining roles...

How to write bash or shell script in SSM run command and execute in linux ec2 instance?

Suggested Topics

How to export data from AWS RDS MySQL database and import to an other AWS RDS MySQL database instance SQL, Database Testing • mysql amazon rds amazon web services etl • • elysha

"Route.post() requires a callback function but got a Object" using multer Software Programming • javascript node.js amazon web services route multer • • Kadyn

Assertions for CLI Commands in CI/CD environment Continuous Integration and Delivery (CI, CD) • cypress • • jonetta

CodeBuild - multiple input artifacts in AWS Pipeline Continuous Integration and Delivery (CI, CD) • amazon web services build pipeline • • Kadir

SaltStack: Use Temporary Scripts And Not Cause State Changes To Reported Continuous Integration and Delivery (CI, CD) • salt • • nishika

Value of succeeded() in Azure DevOps pipeline before first stage is run Continuous Integration and Delivery (CI, CD) • azure devops azure pipelines • • Mystic

Jenkins Pipeline - conditional execution with branch and 1 other parameter (manual) Continuous Integration and Delivery (CI, CD) • jenkins jenkins pipeline • • rosemadder

Is there a way through which I can control type of load balancer like round robin , least-connections Continuous Integration and Delivery (CI, CD) • kubernetes amazon web services helm load balance • • jonetta

Bad practice having a single SSH gateway with access to all environments? Continuous Integration and Delivery (CI, CD) • security amazon web services • • guilherme

Why my docker container is running on swarm manager node instead of worker? Continuous Integration and Delivery (CI, CD) • docker docker swarm • • Mystic

How to allow a non-root user to write to a mounted EFS in EKS Continuous Integration and Delivery (CI, CD) • kubernetes kubernetes helm • • Oba22

How to programmatically enable and disable SQS triggering AWS Lambda? Continuous Integration and Delivery (CI, CD) • amazon web services aws lambda aws iam serverless amazon sqs • • meriah

how to set automatic git pull from bitbucket and complie project on ec2 instance create event Continuous Integration and Delivery (CI, CD) • deployment amazon ec2 autoscaling • • simrah

docker command substitution fails on gitlab Continuous Integration and Delivery (CI, CD) • bash gitlab docker swarm • • Avante

Issue in running docker container on ecs Continuous Integration and Delivery (CI, CD) • amazon web services amazon ec2 amazon ecs • • emmalee

How to export data from AWS RDS MySQL database and import to an other AWS RDS MySQL database instance
SQL, Database Testing • mysql amazon rds amazon web services etl • • elysha

"Route.post() requires a callback function but got a Object" using multer
Software Programming • javascript node.js amazon web services route multer • • Kadyn

Assertions for CLI Commands in CI/CD environment
Continuous Integration and Delivery (CI, CD) • cypress • • jonetta

CodeBuild - multiple input artifacts in AWS Pipeline
Continuous Integration and Delivery (CI, CD) • amazon web services build pipeline • • Kadir

SaltStack: Use Temporary Scripts And Not Cause State Changes To Reported
Continuous Integration and Delivery (CI, CD) • salt • • nishika

Value of succeeded() in Azure DevOps pipeline before first stage is run
Continuous Integration and Delivery (CI, CD) • azure devops azure pipelines • • Mystic

Jenkins Pipeline - conditional execution with branch and 1 other parameter (manual)
Continuous Integration and Delivery (CI, CD) • jenkins jenkins pipeline • • rosemadder

Is there a way through which I can control type of load balancer like round robin , least-connections
Continuous Integration and Delivery (CI, CD) • kubernetes amazon web services helm load balance • • jonetta

Bad practice having a single SSH gateway with access to all environments?
Continuous Integration and Delivery (CI, CD) • security amazon web services • • guilherme

Why my docker container is running on swarm manager node instead of worker?
Continuous Integration and Delivery (CI, CD) • docker docker swarm • • Mystic

How to allow a non-root user to write to a mounted EFS in EKS
Continuous Integration and Delivery (CI, CD) • kubernetes kubernetes helm • • Oba22

How to programmatically enable and disable SQS triggering AWS Lambda?
Continuous Integration and Delivery (CI, CD) • amazon web services aws lambda aws iam serverless amazon sqs • • meriah

how to set automatic git pull from bitbucket and complie project on ec2 instance create event
Continuous Integration and Delivery (CI, CD) • deployment amazon ec2 autoscaling • • simrah

docker command substitution fails on gitlab
Continuous Integration and Delivery (CI, CD) • bash gitlab docker swarm • • Avante

Issue in running docker container on ecs
Continuous Integration and Delivery (CI, CD) • amazon web services amazon ec2 amazon ecs • • emmalee