Current AWS elastic load balancer instances

Data required

AWS: Description data

Procedure

1. Configure the Splunk Add-on for Amazon Web Services.
2. Ensure that your deployment is ingesting AWS data through one of the following methods:
   • Pulling the data from Splunk via AWS APIs. At small scale, pull via the AWS APIs will work.
   • Pushing the data from AWS into Splunk via Lambda/Firehose to Splunk HTTP event collector. As the size and scale of either your AWS accounts or the amount of data to be collected grows, pushing data from AWS into the Splunk platform is the easier and more scalable method.
3. Run the following search. You can optimize it by specifying an index and adjusting the time range.

   source="*_load_balancers" sourcetype="aws:description" 
   |eval name=if(isnull(name),LoadBalancerName,name), vpc_id=if(isnull(vpc_id),VpcId,vpc_id), dns_name=if(isnull(dns_name),DNSName,dns_name), id=((((name . "#") . account_id) . "#") . region) 
   |dedup id sortby - created_time
   |table account_id created_time region name dns_name vpc_id

Search explanation

The table provides an explanation of what each part of this search achieves. You can adjust this query based on the specifics of your environment.

Next steps

Sample results for this search are shown in the table below. Created_time is an interesting field to sort on because you could determine how long the ELB has been in service. The table also shows information on network dns, virtual private cloud id, location, and account owner. Other fields that are available but not shown below include subnets, ports, protocols, listener, and instance state and ssl_certificate_id. Depending on the information you are trying to track, these might be of interest to add to the table or track separately.

Finally, you might be interested in other processes associated with the Managing an Amazon Web Services environment use case.