Compliant and Testable Environments Through Infrastructure-as-Code

1. Compliant and Testable Environments
Through Infrastructure-As-Code
Denis - Florin Rendler
September 20th, 2018
1

2. DEFINING THE PROBLEM
2

3. $ ssh
3

4. 4
EVERYONE’S FAVORITE AUTOMATION TOOL

5. 5
$ ssh

6. INFRASTRUCTURE-AS-CODE TOOLS
6

7. 7
2005 2009 2011 2012 2014

8. 8

9. 9

10. INFRASTRUCTURE-AS-CODE ADVANTAGES
10

11. 11
TESTABLE INFRASTRUCTURE DEPLOYMENTS
VERSION CONTROL SELF DOCUMENTING
REUSABLE SCRIPTS ACROSS ENVIRONMENTS
CROSS-ENVIRONMENT DEPLOYMENTS
PREDICTABLE INFRASTRUCTURE
SCALABLE INFRASTRUCTURE
AUTOMATED INFRASTRUCTURE DEPLOYMENTS

12. TESTING THE INFRASTRUCTURE
12

13. 13

14. 14

15. 15

16. INSPEC.IO WORKFLOWS
16

17. 17
DEVOPS ENGINEER WRITES
INFRASTRUCTURE-AS-CODE SCRIPTS $ sudo
WORKFLOW #1
DEVOPS DEVELOPMENT

18. 18
STEP 1: PREPARE ENVIRONMENT
STEP 2: DEPLOY I-A-C SCRIPTS
STEP 3: TEST INFRASTRUCTURE
ENVIRONMENT
WORKFLOW #1
DEVOPS DEVELOPMENT

19. WORKFLOW #2
TESTING & MONITORING PRODUCTION INFRASTRUCTURE
19
PRODUCTION INFRASTRUCTURE
$ sudo

20. Presentation name 20
CS
WORKFLOW #3
APPLICATION SUPPORT
CS

21. 21

22. REFERENCES
22
• https://learn.chef.io/modules/create-profile-from-doc#
• https://supermarket.chef.io/users/dev-sec/tools
• https://dev-sec.io