These are my links for 26 Mar 2016 through 29 Mar 2016:
- Painless Immutable Infrastructure with Ansible and AWS | Radify Blog – […] In our blog posts Reducing Infrustration and Immutable Demo Nodes, we talk about our approach to immutable infrastructure and the benefits we have seen from employing this approach. In this article, we explore a practical project example so you can get up and running with immutable infrastructure in less than an hour! […]
- pearofducks/ansible-vim: A vim plugin for syntax highlighting Ansible’s common filetypes – A vim plugin for syntax highlighting Ansible’s common filetypes
- Provisioning EC2 Hosts with Ansible | Allan Denot – Looking to build EC2 hosts with more consistency? Using Ansible you can easily provision EC2 hosts and put some logic on it to adjust EC2 parameters based on the type of host you are building.
The easiest way to start is to create a playbook calling the ec2 module with the parameters you want to pass to AWS to create your host. In this post I will show a little more scalable way to do this, where the parameters are variables and you can easily have multiple types of hosts sharing the same playbook and role.
These are my links for 24 Mar 2016 through 25 Mar 2016:
- Coderwall | Dump all variables – For debugging purposes it can be useful to not just dump hostvars but also all other variables and group information. You can do this using a jinja template which you could include in a debug task
- Using Ansible to create AWS instances | Tivix – Ansible is a great tool for enhancing productivity. With a vast array of modules to choose from, it can save you a lot of time by automating away common tasks. At Tivix we use it for single-command deployment, with the most common destination being Amazon EC2 instances created beforehand. Since Ansible is capable of managing EC2 resources, we can improve this setup by making a playbook to create an instance for us.
- Home | OpenSCAP portal – The OpenSCAP ecosystem provides multiple tools to assist administrators and auditors with assessment, measurement and enforcement of security baselines. We maintain great flexibility and interoperability, reducing costs of performing security audits.
The OpenSCAP project provides a wide variety of hardening guides and configuration baselines developed by the open source community, ensuring that you can choose a security policy which best suits the needs of your organization, regardless of its size.
SCAP is U.S. standard maintained by National Institute of Standards and Technology (NIST). The OpenSCAP project is a collection of open source tools for implementing and enforcing this standard, and has been awarded the SCAP 1.2 certification by NIST in 2014.
- Wazuh | Augmenting OSSEC Host IDS – Wazuh contributes to Open Source Security developing and integrating new modules to extend OSSEC capabilities and functionality.
These are my links for 16 Mar 2016 through 24 Mar 2016:
- “Reverse Engineering for Beginners” free book –
- Resolve Hardware Status Alert SEL_FULLNESS | Brian Ragazzi – […] I noticed an alert on two UCS B250M2 hosts in the vSphere Client. The alert Name was “Status of other host hardware objects”. This isn’t helpful. To get more information, you have to navigate to the Hardware Status tab of the host properties. Here I saw more information about the alert. It’s cryptically named “System Board 0 SEL_FULLNESS”. […]
- Network Stack: Cisco ASA Packet Capture – […] The ASA platform has fantastic built-in packet capture capabilities which can come in very handy for troubleshooting issues. I will be demonstrating some of the capabilities using an ASA 5505 running version 9.0(1).Performing a packet capture is done using the capture command from privileged exec mode. […][ Fantastic… I won’t say that ]
- Multistage environments with Ansible – Ross Tuck – Ansible has excellent documentation but one thing I was confused about was the best way to store the configuration for multistage projects: say, different passwords for dev, staging, production. This isn’t really covered in the ansible-examples repo because it’s specific to your project and while the documentation has recommendations, it doesn’t spell it out completely (which I need since I’m an idiot).