Summertime ACS Updates

Platform Splunk

We've had quite the stellar run with Admin Config Service (ACS), and the month of July is no exception! For those of you new to ACS, it is a cloud-native API that provides self-service administration capabilities for Splunk Cloud Platform. As of July 28th, 2022, ACS has now introduced some new capabilities both to the ACS API itself, as well as the ACS Command Line Interface (CLI).

Before we dig into the major updates this month, a little history: over the last year ACS has introduced support for things like app installation (private & Splunkbase), index creation, HEC token creation, IP Allow List, and Limits.conf settings management; all via an intuitive, modern, REST API, and extremely handy CLI. Additionally, we've even spent time going back and enhancing existing APIs, such as adding DDAA and DDSS support for index creation.

We've seen the Splunk Admin community come up with amazing and innovative ways to leverage these APIs, like integrating CI/CD processes with their Splunk Cloud Stack(s), to our amazing partners "terraforming" new stacks for their customers with standard app and limits.conf settings.

As we've looked at new areas of need, we spent some time internally asking other Splunkers, like our Professional Services group, what value ACS could bring to their daily lives. It turns out that migrating to Splunk Cloud has seen incredible interest over the last 12 months, and a big part of those migrations involve app installs (public and private), index creation, HEC token creation, and a myriad of other tasks. After reviewing some prior migrations with our PS compatriots, we realized there was a lot of opportunity to introduce "bulk" operations for a number of repetitive tasks that occur during a Splunk Enterprise to Splunk Cloud migration.

While we can't cover all the details in a single blog post, I do want to point you to the excellent documentation for the ACS CLI.

Effectively, the team has built out some client-side logic in the CLI that allows you to pass a sort of "manifest" — in the form of a JSON file — to the CLI, and let it serially perform each operation on your Splunk Cloud stack.

The CLI also creates a client-side log file of each operation, allowing you to grab your coffee, come back and see how far things have progressed. I liken it to an astromech droid (you know which one) that helps get your Splunk Cloud stack in tip-top shape.

Now, before you run out and start testing these awesome new capabilities, there are some important details for the new APIs:

There's plenty more to unpack in a future blog post, and we'll be sure to highlight your stories as we continue to see you innovate with these new features!

Additional References:

----------------------------------------------------
Thanks!
Kyle Champlin

Related Articles

Dashboard Studio: Token Eval and Conditional Panel Visibility
Platform
4 Minute Read

Dashboard Studio: Token Eval and Conditional Panel Visibility

Dashboard Studio in Splunk Cloud Platform can address more complex use cases with conditional panel visibility, token eval, and custom visualizations support.
Introducing Automatic UI Updates
Platform
3 Minute Read

Introducing Automatic UI Updates

Learn more about Automatic UI Updates (AUIU), a new cloud service that allows admins to get the most up-to-date UI experience between Splunk Cloud upgrades.
Stream Your AWS Services Metrics to Splunk
Platform
2 Minute Read

Stream Your AWS Services Metrics to Splunk

Amazon Web Services (AWS) recently announced the launch of CloudWatch Metric Streams. Cloudwatch Streams can stream metrics from a number of different AWS resources using Amazon Kinesis Data Firehose to target destinations. What this means for current Splunk customers is they now have the option of either using the Splunk add-on of AWS to poll metrics or to make use of this new service and let Amazon Kinesis Data Firehose push metrics to a Splunk HEC endpoint, and reduce their latency by anywhere between 5 to 10 minutes.