Skip to content

Instantly share code, notes, and snippets.

View mdasilva's full-sized avatar

Michael Da Silva mdasilva

View GitHub Profile
$ docker run -it --rm -p 24224:24224 -p 24224:24224/udp -p 8888:8888 -v $PWD/fluent.conf.test:/fluentd/etc/fluent.conf -e FLUENTD_CONF=fluent.conf igm-fluentd 112ms  Wed 23 May 2018 11:10:08 AM EDT
2018-05-23 15:10:35 +0000 [info]: reading config file path="/fluentd/etc/fluent.conf"
2018-05-23 15:10:35 +0000 [info]: starting fluentd-0.12.43
2018-05-23 15:10:35 +0000 [info]: gem 'fluent-plugin-splunk-http-eventcollector' version '0.3.0'
2018-05-23 15:10:35 +0000 [info]: gem 'fluentd' version '0.12.43'
2018-05-23 15:10:35 +0000 [info]: adding match pattern="**" type="copy"
2018-05-23 15:10:36 +0000 [info]: adding source type="http"
2018-05-23 15:10:36 +0000 [info]: using configuration file: <ROOT>
<source>
@type http

Vault Secret Management

Vault is a tool for securely accessing secrets. In this guide we'll be standing up development instances of Vault and Consul to illustrate features such as;

  • Dynamic secret generation
  • LDAP authentication
  • Policy based authorization

Before you get started

Vault Secret Management

Vault is a tool for securely accessing secrets. In this guide we'll be standing up development instances of Vault and Consul to illustrate features such as;

  • Dynamic secret generation
  • LDAP authentication
  • Policy based authorization

Before you get started

Vault Secret Management

Vault is a tool for securely accessing secrets. In this guide we'll be standing up development instances of Vault and Consul to illustrate features such as;

  • Dynamic secret generation
  • LDAP authentication
  • Policy based authorization

Before you get started

Vault Secret Management

Vault is a tool for securely accessing secrets. In this guide we'll be standing up development instances of Vault and Consul to illustrate features such as;

  • Dynamic secret generation
  • LDAP authentication
  • Policy based authorization

Before you get started

Setup Consul with ACL

This will setup a single node Consul cluster. Development mode is not used in order to allow data persistence. We'll be interacting with the Consul server from within the container for simplicity.

Create Consul configuration and persistent data directories

$ mkdir p consul/config consul/data

Setup Consul with ACL

This will setup a single node Consul cluster. Development mode is not used in order to allow data persistence. We'll be interacting with the Consul server from within the container for simplicity.

Create Consul configuration and persistent data directories

$ mkdir p consul/config consul/data

Setup Consul with ACL

This will setup a single node Consul cluster. Development mode is not used in order to allow data persistence. We'll be interacting with the Consul server from within the container for simplicity.

Create Consul configuration and persistent data directories

$ mkdir p consul/config consul/data
# Add an OU to hold user accounts
dn: ou=users,dc=example,dc=org
changeType: add
objectClass: organizationalUnit
description: Organization users
ou: users
# Add an OU to hold roles
dn: ou=roles,dc=example,dc=org
changeType: add

Business Capability teams

Typical Role Composition

  • Product owner
  • Designer
  • Tester(s)
  • Developers (1-3 pairs)