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. 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.
#Splunk limits.conf professional#
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 nf settings.Īs 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. Additionally, we've even spent time going back and enhancing existing APIs, such as adding DDAA and DDSS support for index creation. 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).īefore 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 nf settings management all via an intuitive, modern, REST API, and extremely handy CLI. 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.
0 kommentar(er)
