Splunk license server and indexer cluster master, co-located.In the latter case, the search heads are distributed across the number of Availability Zones you specify. Splunk search heads, either stand-alone or in a cluster, based on your input during deployment.Splunk indexer cluster with the number of indexers you specify (3-10), distributed across the number of Availability Zones you specify.In the public subnets, EC2 instances for Splunk Enterprise, including the following:.Appropriate security groups for each instance or function to restrict access to only necessary protocols and ports.An AWS Identity and Access Management (IAM) user with fine-grained permissions for access to AWS services necessary for the deployment process.Two Elastic Load Balancing (ELB) load balancers: one to load-balance HTTP web traffic to the search head instances, and the other to load-balance HTTP event traffic destined for the Splunk HTTP Event Collector (HEC) across all indexer instances.An internet gateway to allow access from the internet to the public subnets.A virtual private cloud (VPC) configured across two Availability Zones, with a public subnet provisioned in each Availability Zone.Use this Quick Start to automatically set up the following Splunk Enterprise environment on AWS:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |