Skip to content

Latest commit

 

History

History
125 lines (76 loc) · 4.2 KB

README.md

File metadata and controls

125 lines (76 loc) · 4.2 KB
Raw

AWS EC2 User Data script to launch a Splunk lab

This is a simple shell script to use as 'User Data' when launching an Amazon Linux AMI based EC2 instance serving as a Splunk quick Lab.

It will install Splunk and perform a few configuration steps so that Splunk is accessible straight away without any of the actions usually required with a fresh install.

It will also download Splunk Apps and Add-ons either from Splunkbase or from a provided S3 bucket and install them.

The goal is to set up a throwable Splunk instance for lab purposes without any dialog box to interfere.

Use the User Data script

Adjust the script to your needs

Define a password for Splunk admin account

Set password variable

# Provide the Splunk admin password you want to set
export password="<password>"

If you want to download Apps & Add-ons from Splunkbase

  1. Set download_splunkbase variable to true
# Set to true if you need to download Splunk Apps & Add-ons from Splunkbase
readonly download_splunkbase="false"
  1. Set Splunk.com credentials
# Provide Splunk.com credentials (could be a junk account)
readonly splunk_com_login="<login>"
readonly splunk_com_password="<password>"
  1. Provide the ID and version of each App or Add-on you want to download from Splunkbase
# Provide the id and version of each App or Add-on you want to download from Splunkbase
readonly splunkbase_apps=("<app_id> <app_version>" "<app_id> <app_version>")

Note: Get an App or Add-on's ID from its Splunkase URL: https://splunkbase.splunk.com/app/<app_id>/.

If you want to retrieve files from an S3 bucket

  1. Set retrieve_s3_data variable to true
# Set to true if you need to retrieve Splunk Apps & Add-ons for an S3 bucket?
readonly retrieve_s3_data="true"
  1. Set s3_bucket variable to the name of your S3 bucket
# Provide the name of the bucket you want to retrieve Splunk Apps and Add-ons from
readonly s3_bucket="<s3_bucket>"

Adjust the AWS side

Launch an Amazon Linux 2 AMI based EC2.

Make sure your EC2 instance is reachable

  1. Configure a security group to allow inbound HTTP and SSH traffic.

  2. Assign the security to your EC2 instance.

If you want to retrieve files from an S3 bucket

  1. Allow connection to your S3 bucket from your EC2 instance.

  2. Upload custom or downloaded Apps and Add-ons as tgz|tar.gz|spl|zip files to your S3 bucket.

Copy the script in the User data field

Copy the modified script in the User data field when launching an instance from the Launch Instance Wizard.

Quick steps summary

  1. Launch instance - Pick an 'Amazon Linux 2' AMI
  2. [Optional] Configure instance details - Specify IAM role if you are retrieving data from S3
  3. Configure instance details - Copy script in User data field
  4. [Optional] Add tags
  5. Configure Security Group - Assign the Security Group allowing HTTP & SSH
  6. Launch - Pick the right key pair

Access Splunk

When your EC2 instance is launched, access Splunk from your browser

http://<EC2 Public IP | Public DNS>

SSH Access

Connect to your EC2 via SSH.

Note that Splunk runs as ec2-user.

Browse cloud-init output

The script configures Splunk to monitor the output of the User Data script so it can be explored from Splunk if needed:

index="_internal" sourcetype="aws:cloud-init" | reverse

Access Splunk after a reboot

Splunk is configured to start at boot time. Hence, whenever you start your instance, Splunk starts.

Notes

Script uses Tyler James Frederic's splunkbase-download project