Admin Configuration Service

The ACS API now supports egress private connectivity for Splunk Cloud Platform deployments on AWS. Use this feature to establish secure, private outbound connections from Splunk Cloud Platform to endpoints in your AWS Virtual Private Cloud (VPC) without routing traffic over the public internet. Use cases include DB Connect and Federated Search.

For more information, see About egress private connectivity. To get started, see Set up egress private connectivity.

ACS now supports private connectivity for Splunk Cloud stacks on Google Cloud Platform, letting admins route traffic over private VPC endpoints instead of the public internet.

ACS now supports Maintenance Window service integration for IL2 GovCloud environments, with ACS endpoints to list and view maintenance window schedules.

For more information, see Manage maintenance windows for Splunk Cloud Platform.

Index creation now supports an mdlIndex flag, and internal/system-managed indexes are no longer surfaced in list indexes responses.

Admins can now set preferred maintenance window schedules for their Splunk Cloud stack by choosing a preferred day and time slot, and ACS provides APIs to view and update those preferences.

A new ACS Allowlist API lets admins control which IP addresses can reach the ACS API service itself, with create, delete, and describe support backed by Istio authorization policy.

HTTP Event Collector tokens now support a _meta field so admins can attach default metadata to events ingested through a token.

ACS now supports centralized RBAC integration with Splunk Observability Cloud, including an --o11y-realm parameter for multi-region deployments.

Splunk Cloud admins can manage IPv6 IP allowlists and outbound port rules via the ACS API, including add, remove, and describe operations for IPv6 subnets and egress ranges.