Releases: chef-boneyard/aws_native_chef_server
Releases · chef-boneyard/aws_native_chef_server
3.2.0
This versions adds not one but TWO centralized log capture mechanisms!
- Cloudwatch Logs for all system and chef server logs. Storing data in AWS which is useful for audit and troubleshooting cluster launch issues without sshing all over the place
- Filebeat for shipping all system and chef server logs into the built-in Elasticsearch instance, useful for visualizing traffic in Kibana.
Using it (command-line)
Cloudwatch logs
get the awslogs utility and then you can do things like this:
$ awslogs groups
mychefstack-VarLogAwsSigningProxyLog-1QVRV8DF5NBCW
mychefstack-VarLogCfnInitCmdLog-1N95V3M26B95V
mychefstack-VarLogCfnInitLog-1W4PHEJA5VOYW
...
$ awslogs get mychefstack-VarLogOpscodeOpscodeErchefRequestsLog-1G8GNRNLG01QU ALL --watch
irving-backendless-chef2-VarLogOpscodeOpscodeErchefRequestsLog-1G8GNRNLG01QU i-07147cb1ec58da84f 2018-01-24T00:35:25Z [email protected] method=GET; path=/_status; status=200;
irving-backendless-chef2-VarLogOpscodeOpscodeErchefRequestsLog-1G8GNRNLG01QU i-0ae3d3c56ec9b1071 2018-01-24T00:35:25Z [email protected] method=GET; path=/_status; status=200;
irving-backendless-chef2-VarLogOpscodeOpscodeErchefRequestsLog-1G8GNRNLG01QU i-0ae3d3c56ec9b1071 2018-01-24T00:35:25Z [email protected] method=GET; path=/_status; status=200;
irving-backendless-chef2-VarLogOpscodeOpscodeErchefRequestsLog-1G8GNRNLG01QU i-07147cb1ec58da84f 2018-01-24T00:36:01Z [email protected] method=GET; path=/_status; status=200;
irving-backendless-chef2-VarLogOpscodeOpscodeErchefRequestsLog-1G8GNRNLG01QU i-0ae3d3c56ec9b1071 2018-01-24T00:36:01Z [email protected] method=GET; path=/_status; status=200;
Filebeat/Kibana
To access the VPC-integrated Kibana instance that's built-in to your AWS ES service, ssh to the instance with port forwarding like so:
ssh -L 9200:localhost:9200 -l ec2-user my-ec2-instance
Then open a web browser and navigate to http://localhost:9200/_plugin/kibana/
What it looks like:
Filebeat/Kibana
Cloudwatch logs:
3.1.3
3.1.1
3.1.0
What's changed
- Remove never-used parameters
DBSubnetGroupArnandLoadBalancerSubnets - Reorganize parameters for easier consumption
- Enable users to provide custom before and after scripts. Also switch to explicit S3 files locations for those scripts.
- Add configurables for a Chef Automate data collector
- Enable users to provide their own security group IDs for the frontends and load balancers
- Route53 integration
- Enable and recommend newer instance types like C5, M5 and I3 where available
- Move Elasticsearch into the VPC! woohoo!
- Make Elasticsearch instance type configurable, and default to i3.large which is a way better bang-for-buck than the old m3 options.
- the template is now officially too big to be run from disk (via
template-body), so now it must be run from S3 (viatemplate-url) so updating the workflow to match that.
Because these changes break backwards compatibility, I'm bumping the major release version and including a fun image to make it easier:
