This gives the site engineer a degree of flexibility in managing the underlying infrastructure but with the added cost of complexity. We built a cluster with a single VM running as our container instance which hosts the container and all of its dependencies. In part 2 of this series we built an Elastic Container Service (ECS) cluster to host and manage our application containers. What is Fargate, And How Is It Different from ECS? Splunk HEC Token: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.Splunk HEC Index: scratch (the name of the index you configured in your HEC).Splunk HEC server: ( Splunk Enterprise) or ( Splunk Cloud).AWS Task Execution Role: ecsTaskExecutionRole (the name of the role to run ECS tasks).AWS ECS Instance Role: ecsInstanceRole (the name of the role to run container instances).AWS CloudWatch Log Group: SplunkECS (the name of the log group).AWS Region: US-East-1 (the region you're working in).In order to follow the remainder of this post in the series, you will need the following information that we defined in the last part: However if you did follow along in part 2, you'll notice there are a number of similarities in the principals we'll be discussing in this segment.Īs a quick recap, in part 1 we configured a CloudWatch log group and two IAM roles that will be required for this walkthrough along with an HTTP Event Collector and index within Splunk. Configuring Fargate is an alternative to ECS which we'll discuss later and can be performed independently of the work we completed in part 2. This blog segment picks up directly after part 1 in the series, and is not dependent on part 2. In this next segment in the series we will be focusing on building a Fargate profile, defining tasks and deploying a simple container that routes its application logs to Splunk with Firelens. In part 2, Splunking AWS ECS Part 2: Sending ECS Logs To Splunk, we focused on how to configure an ECS cluster, create tasks and workloads and send their outputs to Splunk for indexing. In part 1, Splunking AWS ECS Part 1: Setting Up AWS And Splunk, we focused on understanding what ECS and Fargate are, along with how to get AWS and Splunk ready for log routing to Splunk's Data-to-Everything Platform. Welcome to part 3 of the blog series where we go through how to forward container logs from Amazon ECS and Fargate to Splunk.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |