WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.450 --> 00:00:10.830
In this video, I'll share some best practices for running Lennox in the cloud.

1
00:00:12.610 --> 00:00:13.740
Just like any os,

2
00:00:13.740 --> 00:00:16.780
there are some steps you could take to make sure your experience and your

3
00:00:17.020 --> 00:00:18.180
customers experience are good ones.

4
00:00:18.690 --> 00:00:23.020
I've chosen 12 tips I and others have learned while running a cloud-based

5
00:00:23.460 --> 00:00:27.910
workload on Lennox. The first one, keep it simple.

6
00:00:28.700 --> 00:00:33.670
Do not overcomplicate your setup software is complicated enough. Two,

7
00:00:34.490 --> 00:00:35.920
avoid unnecessary toil.

8
00:00:36.220 --> 00:00:39.520
You should automate all you can so you have more time to work on things to bring

9
00:00:39.520 --> 00:00:43.770
revenue or support your customers. Three A B u.

10
00:00:44.310 --> 00:00:45.490
Always be updating.

11
00:00:45.760 --> 00:00:48.450
Most of the security breaches happen because of outdated software.

12
00:00:48.640 --> 00:00:51.620
Just patch your host regularly. Number four,

13
00:00:52.290 --> 00:00:56.340
slim down your Lennox host as much as possible. Get rid of anything not needed.

14
00:00:56.400 --> 00:00:59.900
For example, like X Windows or any other unused applications,

15
00:01:00.290 --> 00:01:03.460
this will lower your security footprint. Five,

16
00:01:03.950 --> 00:01:07.260
treat your Lennox host like a disposable commodity and not a pet.

17
00:01:07.740 --> 00:01:11.060
A Lennox host should be able to be torn down and thrown away at any given time.

18
00:01:12.000 --> 00:01:12.833
Six,

19
00:01:12.840 --> 00:01:16.900
try to avoid giving production route level remote access to your Lennox host.

20
00:01:17.130 --> 00:01:20.650
This one is self-explanatory. Number seven,

21
00:01:21.150 --> 00:01:23.410
if you must access your Lennox host remotely,

22
00:01:23.790 --> 00:01:26.010
use two FA to provide another layer of security.

23
00:01:26.180 --> 00:01:29.360
There are PAM modules that can do this. Number eight,

24
00:01:29.740 --> 00:01:32.440
add observability to your Lennox host from day one.

25
00:01:32.790 --> 00:01:35.720
This should not be an afterthought and bolted on later when things are broken.

26
00:01:36.700 --> 00:01:37.420
Nine,

27
00:01:37.420 --> 00:01:42.150
perform regular backups to a cloud object store or an elastic storage

28
00:01:42.170 --> 00:01:45.290
device. You'll thank yourself later. 10.

29
00:01:45.710 --> 00:01:48.450
Use configuration management software like Ansible or Chef,

30
00:01:48.870 --> 00:01:52.010
or you can use the cloud provider's built-in version of these tools as well.

31
00:01:52.580 --> 00:01:56.290
Regardless of which you choose, keep your host consistent. 11,

32
00:01:56.950 --> 00:02:00.730
use infrastructure's code like Terraform or whatever the cloud provider's

33
00:02:00.730 --> 00:02:01.563
equivalent is.

34
00:02:01.820 --> 00:02:05.050
Never create infrastructure by hand or use some throwaway bash scripts.

35
00:02:05.390 --> 00:02:10.180
And finally, 12. Use Autoscaling functionality for your application workloads.

36
00:02:10.480 --> 00:02:13.260
You should never have to get paid the middle of the night to scale up a

37
00:02:13.420 --> 00:02:17.970
workload. Let the cloud provider do that for you. Okay,

38
00:02:18.390 --> 00:02:19.890
so let's talk about what we did. In this video.

39
00:02:20.430 --> 00:02:23.490
We discussed some best practices when operating Lennox in the cloud.

40
00:02:24.030 --> 00:02:28.210
You learned about good habits like security backups, limiting access,

41
00:02:28.670 --> 00:02:32.430
and day one observability. In the next video,

42
00:02:32.740 --> 00:02:36.110
I'll share with you a Lennox command cheat sheet you can download and keep.
