From owner-freebsd-cloud@freebsd.org Wed Aug 30 14:14:25 2017 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9763E03122 for ; Wed, 30 Aug 2017 14:14:25 +0000 (UTC) (envelope-from raf@rafal.net) Received: from fallback-in2.mxes.net (fallback-out2.mxes.net [216.86.168.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 957326EDCF for ; Wed, 30 Aug 2017 14:14:24 +0000 (UTC) (envelope-from raf@rafal.net) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by fallback-in2.mxes.net (Postfix) with ESMTP id 2C3BA2FDC36 for ; Wed, 30 Aug 2017 10:08:08 -0400 (EDT) Received: from [192.168.40.37] (unknown [86.40.118.125]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 025D3509B8 for ; Wed, 30 Aug 2017 10:08:00 -0400 (EDT) From: Rafal Lukawiecki Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: AWS CloudWatch Logs Agent Message-Id: <4FFC6F3B-E8A1-49EE-A05A-C6B9B0A615FF@rafal.net> Date: Wed, 30 Aug 2017 15:07:59 +0100 To: freebsd-cloud@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 14:14:25 -0000 First of all: thank you Colin, and thank you all, for making FreeBSD = available in AWS and the other clouds. This is my first email here, so = let me briefly introduce myself and the context. I am evaluating FreeBSD = in AWS as a replacement for our existing (small) AWS fleet of CentOS 7 = and Amazon Linux machines that serve my company (Project Botticelli Ltd) = online training business, which focuses on analytics and what is now = called data science (my main profession) but used to be called data = mining and just plain-old statistics. Colin Percival has already been very helpful in giving me some guidance = with regards to his configinit scripts, which I am happy to say are = working well and making machine launch and teardown easy. While my three = devs have been working hard on the new web front and back ends, and our = app API, all of which we hope to ship in a month, it is down to me to = focus on the sysadmin part of moving the server infrastructure to = FreeBSD. So far, working with FreeBSD has been a pleasure and a = wonderful connection to my old Unix-days' roots. One nice AWS component is its CloudWatch Logs engine that collects = streams of syslog-generated data and centralises them, with a simple but = usable UI. AWS provides an automated set-up for the awslogs daemon = agent, but from a cursory look at the code, although parts of it are = plain Python, much of it is very Linux-focused shell script, with much = regard for runlevels, logrotate etc and not immediately usable as an = rc.d script. I was wondering if anyone has hacked that script yet to run on FreeBSD = or if you have any other suggestions how to help me get AWS CloudWatch = Logs integrated into FreeBSD running on AWS. Many thanks for your help and my best regards from Ireland PS. I have posted a request on the forum for opinions regarding FreeBSD = in the cloud, in case anyone is interested: = https://forums.freebsd.org/threads/62190/ -- Rafal Lukawiecki Data Scientist and Director=20 Project Botticelli Ltd=