| #!/bin/bash | |
| ############################################################################ | |
| # This script iterates over each child directory from where it runs | |
| # and deletes ALL contents of those child directories, while leaving | |
| # the directory itself intact. | |
| # | |
| # Copyright 2020 Eric A. Soto, [email protected] | |
| # | |
| # Permission is hereby granted, free of charge, to any person obtaining a |
Ansible is very helpful for automated deployments. However, it can also be used for server admin tasks against many servers by using both the Command, Shell and Script Modules.
Note: Although the process described here works with hosts that you can access via password or SSH keys, it is more convenient when working with hosts that you have SSH keys for (you don't have to enter passwords!)
This post explains how to create an AWS S3 Bucket and an IAM User with programmatic access to the bucket.
You will need access to the AWS S3 console for your account and have permissions to create new buckets and create new IAM users.
This is based on:
This post explains how to manually create a Snapshot of an Elastic Cloud instance to an AWS S3 Bucket using what Elasticsearch calls a custom repository.
This is based on the following:
| #!/bin/bash | |
| ############################################################################ | |
| # Random Sample - rsample.sh | |
| # | |
| # A utility to output a sample number of lines from | |
| # a text file based on a percentage passed in as an | |
| # argument. | |
| # | |
| # Dependencies: |
This is a sheet with some interesting GIT commands.
This content is shared under a Creative Commons Attribution-ShareAlike 4.0 International.
| #!/bin/bash | |
| ################################################################ | |
| # This is a script that pulls a list of IPs from AWS | |
| # published IP list, then parses it looking for a | |
| # specific region and service. | |
| # | |
| # Dependencies: | |
| # This script needs: | |
| # * Internet access |
| #!/bin/bash | |
| echo "Say something here to confirm some action." | |
| echo "" | |
| # Wait for the user to press any KEY to proceed or allow them to Ctrl+C | |
| read -n1 -rsp $'Press any key to continue or Ctrl+C to exit...\n' | |
| # Do your work after this... it won't execute if the user does Ctrl+C at the prompt! | |
| #!/bin/bash | |
| # Get the directory where the script lives. | |
| SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null && pwd )" | |
| # Setup a variable for easy reference to the pidfile | |
| pidfile=${SCRIPT_DIR}/tunnel.pid | |
| # Check for our pidfile, which we expect in order to be able to control the process | |
| if [ ! -f $pidfile ]; then | |
| echo "Tunnel pidfile does not exist. Tunnel might not up or not known! Exiting!" |
| #!/bin/bash | |
| # Get the directory where the script lives. | |
| SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null && pwd )" | |
| # Setup a variable for easy reference to the pidfile | |
| pidfile=${SCRIPT_DIR}/tunnel.pid | |
| # Check to see if there is a pidfile already... | |
| if [ -f $pidfile ]; then | |
| # There is, so the tunnel might be up! |