1
00:00:00,630 --> 00:00:06,310
By now we are familiar with the items tab on the dynamo D-B console.

2
00:00:06,360 --> 00:00:12,340
Let's have a quick look at some of the other tabs to find out what they do.

3
00:00:14,580 --> 00:00:16,620
First the overview tab.

4
00:00:17,840 --> 00:00:19,670
There are three sections here.

5
00:00:19,700 --> 00:00:24,560
Recent alcoves will show you if there are any letters.

6
00:00:24,890 --> 00:00:32,740
When we create our table dynamically we create some cloud watch alarms by default.

7
00:00:32,840 --> 00:00:40,580
So if any of these alarms get triggered let's say for example our requests are getting throttled due

8
00:00:40,580 --> 00:00:43,870
to under-privileged and capacity.

9
00:00:43,870 --> 00:00:54,010
You see a notification message here stream details applies to Dynamo IDB streams and we'll discuss the

10
00:00:54,010 --> 00:00:57,620
topic of streams a little later in this course.

11
00:00:58,630 --> 00:01:08,980
The table details as the name suggests lists all the meta data about our table the name primary key

12
00:01:08,980 --> 00:01:18,430
attribute capacity size and so on size data is not real time value but it's a day that a couple of times

13
00:01:18,430 --> 00:01:22,280
a day typically about every six hours.

14
00:01:25,010 --> 00:01:27,570
Let's go to the metrics tab.

15
00:01:27,770 --> 00:01:34,640
This will give us the runtime statistics about our tables performance.

16
00:01:34,770 --> 00:01:44,120
We'll be able to see the runtime graphs like the read write capacity consumption over time a number

17
00:01:44,120 --> 00:01:53,900
of throttled requests and so on the grass every element for the table index as well as the global secondary

18
00:01:53,900 --> 00:02:04,440
nexus we also have these stats for let him see which is actual response times then we house dads for

19
00:02:04,440 --> 00:02:14,760
streams t tills can and query operations performed as well as count of errors if there are any.

20
00:02:15,110 --> 00:02:20,050
You can click on any of these graphs to see a detail view.

21
00:02:21,230 --> 00:02:29,870
Or you could use the cloud watcher link at the top of which will take us to the cloud watch console

22
00:02:29,870 --> 00:02:34,900
where we can study these statistics in more detail.

23
00:02:35,910 --> 00:02:45,780
Set this tab will give us and holistic view of how our table is performing so we can assess if any adjustments

24
00:02:45,840 --> 00:02:47,820
are needed.

25
00:02:48,060 --> 00:02:57,090
Then we have the alarm Stabb And as I just discussed there are some predefined alarms and we can manage

26
00:02:57,090 --> 00:02:59,170
these alarms here.

27
00:02:59,700 --> 00:03:04,830
We can add remove or modify any of the alarms as needed.

28
00:03:04,890 --> 00:03:12,380
And if you click on any of these hyperlinks it will allow us to edit these alarms.

29
00:03:12,390 --> 00:03:18,540
You can also use this screen to set up e-mail notification if you like

30
00:03:21,300 --> 00:03:24,360
then we have the capacity tab.

31
00:03:24,720 --> 00:03:34,390
First section is recess killing act activities any capacity changes initiated through the auto scaling

32
00:03:34,410 --> 00:03:36,020
function will be logged.

33
00:03:36,030 --> 00:03:41,780
Here we'll go cover the topic of auto scaling later in this course.

34
00:03:43,800 --> 00:03:53,760
Then we have two more sections here provisioned our capacity and auto scaling which simply allows us

35
00:03:53,760 --> 00:03:56,190
to control the capacity.

36
00:03:56,340 --> 00:04:05,700
And these are the same settings that we saw when we created the table the next tab is in Texas.

37
00:04:05,740 --> 00:04:15,890
This simply lists all the secondary indexes on our table local as well as global secondary Nexxus where

38
00:04:15,990 --> 00:04:22,030
we can create more global submarine access up to a limit of 5 per day.

39
00:04:22,050 --> 00:04:29,740
Of course we can also delete any of the existing global secondary indexes if we need to.

40
00:04:32,030 --> 00:04:41,490
As we already know local secondary indexes however cannot be created now and we cannot delete any locals

41
00:04:41,490 --> 00:04:43,150
that are in the Nexus either.

42
00:04:43,980 --> 00:04:51,330
Only way to change or remote local secondary nexus is to create a new table.

43
00:04:52,230 --> 00:04:55,290
Then we have a path for global tables.

44
00:04:55,290 --> 00:05:02,600
This allows us to create multi-region tables and we'll dive deeper into this.

45
00:05:02,680 --> 00:05:14,520
In another lecture later in the score's the backup Stabb as the name suggests allows us to manage backups.

46
00:05:14,520 --> 00:05:23,370
We can create backups restore from existing backups and also delete any existing backups and we'll learn

47
00:05:23,370 --> 00:05:33,220
the specifics of backup and restore operations in one of the lectures I had in this course.

48
00:05:33,590 --> 00:05:44,030
Then we have triggers here we can define Landauer functions to execute based on some events like changes

49
00:05:44,030 --> 00:05:45,020
to our table.

50
00:05:45,080 --> 00:05:55,900
For example when new items are added we could trigger a function to do something we can use them in

51
00:05:55,900 --> 00:06:04,670
conjunction with Dynamo these dreams as we'll see later when we discussed the topic of the animality

52
00:06:04,770 --> 00:06:05,650
streams.

53
00:06:07,280 --> 00:06:09,710
Then we have access control tab.

54
00:06:09,710 --> 00:06:14,540
This allows us to control access to the table.

55
00:06:14,810 --> 00:06:22,010
And this is also one of the advanced topics that will cover a little later in this course.

56
00:06:25,190 --> 00:06:28,220
Finally we have tags.

57
00:06:28,370 --> 00:06:32,020
Tags are used to organize our tables.

58
00:06:32,050 --> 00:06:40,320
Our task is simply a key value pair and typically this is used to categorize resources.

59
00:06:40,490 --> 00:06:44,830
We can break down our AWOS bills by these tags.

60
00:06:45,020 --> 00:06:50,510
It's one of the ways to analyze our AWOS bills.

61
00:06:50,830 --> 00:06:58,430
That brings us to the end of this section in the next section we learn another way of working with phantom

62
00:06:58,450 --> 00:07:09,040
ALIMI And if you're a savvy developer who prefers the term we know our command prompt over the graphical

63
00:07:09,040 --> 00:07:10,300
interface.

64
00:07:10,450 --> 00:07:13,270
The next section is for you.

65
00:07:13,450 --> 00:07:23,140
We're learning how to use the NABC lighting to work with Dynamo D-B How ever if you like using the graphical

66
00:07:23,140 --> 00:07:32,120
interface instead then you can continue using this Web console that we just discussed.

67
00:07:32,130 --> 00:07:44,330
Either way I'd suggest that you watch the next section so you have a better idea of different possibilities.

68
00:07:44,820 --> 00:07:46,850
Thank you for joining me here.

69
00:07:47,160 --> 00:07:49,690
Let's meet in the next section.
