# Managing Link devices
This section provides reference information for operations you can perform on the Link device. For complete procedures to use Link in a MediaLive channel or a MediaConnect flow, see [Using Link with a MediaLive input](device-use-input.md) and [Using Link with a MediaConnect flow](device-use-flow.md).
**Topics**
+ [Setting up users with IAM permissions](device-iam-for-user.md)
+ [Setting up MediaLive as a trusted entity](device-iam-for-medialive.md)
+ [Claiming a Link device](device-claim.md)
+ [Creating a Link input device](device-create.md)
+ [Viewing your Link devices](device-view.md)
+ [Transferring a Link device to another account](device-transfers.md)
+ [Transferring a Link device to another Region](device-transfer-region.md)
+ [Configuring a Link device](device-edit.md)
+ [Attaching and detaching a Link device](device-attach.md)
+ [Starting and stopping a Link device](device-start-stop.md)
+ [Rebooting a Link device](device-reboot.md)
+ [Updating software on a Link device](device-update.md)
+ [Deleting a Link input device](device-delete.md)
# Setting up users with IAM permissions
This section describes the permissions that an IAM administrator must assign to users and other AWS identities so that they can configure a Link device to work with a MediaLive input or an MediaConnect flow.
This information supplements the information about setting up a user to work with all MediaLive features. Read this information as follows:
+ Read this section if your organization has users who will only work with MediaLive to deploy devices and configure them for use as sources, and you want to follow a *least permissions* rule.
+ If your organization has users who will deploy devices, use those devices, and use all MediaLive features, see [Requirements for AWS Elemental Link](requirements-for-link.md). You should revise their existing policies to include the device permissions.
This section assumes that you have already performed these tasks:
+ You have performed the initial setup described in [Preliminary steps for setting up to use MediaLive](setting-up.md) in order to sign up for MediaLive and to create an administrator.
+ You have read the recommendations in [Identity and Access Management for AWS Elemental MediaLive](security-iam.md)about how to create administrators, users, and other AWS identities.
**Topics**
+ [Required permissions](#device-iam-permissions)
+ [Creating the policy](#device-iam-policy)
## Required permissions
You must assign permissions for actions in several services, as described in the following table.
| Permissions | Service name in IAM | Actions |
| --- | --- | --- |
| View, configure, and manage a Link device | medialive | `DescribeInputDevice` `DescribeInputDeviceThumbnail` `ListInputDevices` `RebootInputDevice` `StartInputDeviceMaintenanceWindow` `StartInputDevice` `StopInputDevice` `UpdateInputDevice` |
| Handle transfers of Link devices | medialive | `AcceptInputDeviceTransfer` `CancelInputDeviceTransfer` `ClaimDevice` `ListInputDeviceTransfers` `RejectInputDeviceTransfer` `TransferInputDevice` |
| On the MediaLive console, view MediaConnect flows in the dropdown list. This dropdown list appears in the **Flow ARN** field in the **Attachments** tab on the **Device details** page. | mediaconnect | ListFlows |
| On the MediaLive console, view Secrets Manager secrets in the dropdown list. This dropdown list appears in the **Secret ARN** field in the **Attachments** tab on the **Device details** page. | secretsmanager | ListSecrets |
| On the MediaLive console, view IAM roles in the dropdown list. This dropdown list appears in the **Role ARN** field in the **Attachments** tab on the **Device details** page. | iam | ListRoles |
## Creating the policy
1. Sign in to the AWS Management Console and open the IAM console at [https://console.aws.amazon.com/iam/](https://console.aws.amazon.com/iam/).
1. In the navigation pane on the left, choose **Policies**. Choose **Create Policy**, then choose the **JSON** tab.
1. In the **Policy editor**, clear the sample content and paste the policy that appears after this procedure.
1. Give the policy a name that makes it clear that this policy is for using Link. For example, `ElementalLinkAccess`.
1. Choose **Create policy**.
Sample policy:
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"medialive:DescribeInputDevice",
"medialive:DescribeInputDeviceThumbnail",
"medialive:ListInputDevices",
"medialive:RebootInputDevice",
"medialive:StartInputDeviceMaintenanceWindow",
"medialive:StartInputDevice",
"medialive:StopInputDevice",
"medialive:UpdateInputDevice"
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"medialive:AcceptInputDeviceTransfer",
"medialive:CancelInputDeviceTransfer",
"medialive:ClaimDevice",
"medialive:ListInputDeviceTransfers",
"medialive:RejectInputDeviceTransfer",
"medialive:TransferInputDevice"
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"mediaconnect:ListFlows"
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"secretsmanager:ListSecrets"
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"iam:ListRoles"
],
"Resource": [
"*"
]
}
]
}
```
------
# Setting up MediaLive as a trusted entity
An IAM administrator must consider the special permissions that MediaLive requires if your organization will use a Link device as the source for a MediaConnect flow.
You must set up MediaLive as a *trusted entity*. In a trusted entity relationship, a role identifies MediaLive as a trusted entity. One or more policies are attached to the role. Each policy contains statements about allowed operations and resources. The chain between the trusted entity, role, and policies makes this statement:
"MediaLive is allowed to assume this role in order to perform the operations on the resources that are specified in the policies."
**Important**
You might be familiar with the trusted entity role that MediaLive needs [to work with channels at runtime](setting-up-trusted-entity.md). We recommend that you create a separate trusted entity role for MediaLive to use with Link devices. The permissions for channels are very complicated. The permissions for devices are very simple. Keep them separate.
**Permissions that MediaLive requires**
For you to use a Link device, MediaLive must have permissions on operations and resources in MediaConnect and in Secrets Manager:
+ For MediaConnect: MediaLive must be able to read details about a flow.
+ For Secrets Manager: The device always encrypts the content it sends to MediaConnect. It encrypts using an encryption key that MediaLiveprovides. MediaLive in turn obtains the encryption key from a secret that the MediaConnect user has stored in Secrets Manager. Therefore, MediaLive needs permission to read the encryption key that is stored in a secret.
This table specifies the required operations and resources.
| Permissions | Service name in IAM | Actions | Resources |
| --- | --- | --- | --- |
| View the details of a flow | mediaconnect | `DescribeFlow` | All resources |
| Obtain the encryption key from the secret. See the explanation after this table. | secretsmanager | `GetSecretValue` | The ARN of each secret that holds an encryption key that MediaLive needs to access |
**Topics**
+ [Step 1: Create the IAM policy](#device-iam-medialive-policy)
+ [Step 2: Set up the trusted entity role](#device-iam-medialive-role)
## Step 1: Create the IAM policy
In this step, you create a policy that makes the statement "Let a principal have access to the specified Secrets Manager actions on the specified resource". Note that the policy doesn't specify a principal. You specify the principal in the next step, when you set up the trusted entity role.
1. Sign in to the AWS Management Console and open the IAM console at [https://console.aws.amazon.com/iam/](https://console.aws.amazon.com/iam/).
1. In the navigation pane on the left, choose **Policies**. Choose **Create Policy**, then choose the **JSON** tab.
1. In the **Policy editor**, clear the sample content and paste the following:
1. In the **Resource** section for **secretsmanager**, replace the Region, account, and secret name with real values.
1. Add more lines in the **Resources** section or `secretsmanager`, one for each secret. Make sure you include a comma at the end of all lines except the last line. For example:
```
"Resource": [
"arn:aws:secretsmanager:us-west-2:111122223333:secret:emx_special_skating-KM19jL",
"arn:aws:secretsmanager:us-west-2:111122223333:secret:aes-":secret:emx_weekly_live_poetry-3ASA30",
"arn:aws:secretsmanager:us-west-2:111122223333:secret:aes-":secret:emx_tuesday_night_curling-AMcb01"
]
```
1. Give the policy a name that makes it clear that this policy is for Link and a flow. For example, `medialiveForLinkFlowAccess`.
1. Choose **Create policy**.
## Step 2: Set up the trusted entity role
In this step, you create a role that consists of a trust policy ("let MediaLive call the `AssumeRole` action") and a policy (the policy that you just created). In this way, MediaLive has permission to assume the role. When it assumes the role, it acquires the permissions specified in the policy.
1. On the IAM console, in the navigation pane on the left, choose **Roles**, then **Create Role**. The **Create role** wizard appears. This wizard walks you through the steps of setting up a trusted entity, and adding permissions (by adding a policy).
1. On the **Select trusted entity** page, choose the **Custom trust policy** card. The **Custom trust policy **section appears, with a sample policy.
1. Erase the sample, copy the following text, and paste the text in the **Custom trust policy **section. The **Custom trust policy **section now looks like this:
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Service": "medialive.amazonaws.com"
},
"Action": "sts:AssumeRole"
}
]
}
```
------
1. Choose **Next**.
1. On the **Add Permissions** page, find the policy that you created (for example, `medialiveForLinkFlowAccess`), and select the checkbox. Then choose **Next**.
1. On the review page, enter a name for the role. For example, `medialiveRoleForLinkFlowAccess`.
1. Choose **Create role**.
# Claiming a Link device
If you purchase a device from an AWS reseller, you must claim the device.
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the MediaLive console, look for the Region menu in the navigation bar at the top of the page. Switch to the us-west-2 Region.
1. In the navigation pane, choose **Input devices**. The **Claim a device** button appears. (This button only appears in this Region.)
1. Choose **Claim a device** and enter the ID of the device. For example, **hd-0000aaaa1111bbbb2222cccc** or **uhd-9999aaaa8888bbbb7777cccc**.
The device now appears in the list of devices.
1. Find the card for the Link input device. If there are many Link input devices, enter part of the name to filter the list.
# Creating a Link input device
Within MediaLive, the Link device is represented a resource that is called theLink input device. You don't need to create this resource. Instead, when an user connects a Link device to the internet and powers it on, the device automatically connects to MediaLive in your AWS account, and specifically to MediaLive in the AWS Region that it is configured for.
# Viewing your Link devices
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Input devices**. The devices that you have access to appear in the **Device list** page.
1. If you don't see **Link input device** listed in the navigation pane, or if you don't see a card for the device that you want, you are probably in the wrong Region, follow the troubleshooting tips after this procedure.
1. Find the card for the Link input device that you want. If there are many Link input devices, enter part of the name to filter the list.
1. Choose the hyperlink. The **Device details** page appears. The page consists of an **Aggregate status** panel, and a panel with three tabs.
**Troubleshooting tips**
If you can't find an expected device in the list, try the following:
+ Another user in your organization might have moved the device to another Region.
Determine the Region that the device is in. In the MediaLive console, look for the Region menu in the navigation bar at the top of the page. Switch to the appropriate Region.
+ This might be a new device that you purchased from AWS. In this case, the device initially appears in the Region you specified when you purchased the device.
In the MediaLive console, look for the Region menu in the navigation bar at the top of the page. Switch to the appropriate Region.
+ This might be a new device that you purchased from an AWS reseller. In this case, the device is in the us-west-2 Region.
In the MediaLive console, look for the Region menu in the navigation bar at the top of the page. Switch to the us-west-2 Region. If the device still doesn't appear, you probably need to [claim the device.](device-claim.md)
**Topics**
+ [Aggregate status panel](#device-view-aggregate-status)
+ [Details tab](#device-view-details-tab)
+ [Attachments tab](#device-view-attachments-tab)
+ [Tags tab](#device-view-tags-tab)
## Aggregate status panel
The panel includes the sections and fields specified in this table.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/device-view.html)
## Details tab
This tab includes the sections and fields specified in this table.
| Section | Fields | Details |
| --- | --- | --- |
| Network settings | The current network settings | Shows information only if the device is connected to AWS. To connect, see [Deploying the Link hardware](elink-setup-device.md). |
| Device settings | The current configuration of the device. | The streaming fields (such as the framerate) show information only if the device is sending content to AWS.You can set some fields. Choose the **Modify** then **Configure device**. For information about the dialog, see [Configuring a Link device](device-edit.md). |
| Device metadata | The Device ARN (which includes the unique device ID), serial number, device ID, type, name of device | |
## Attachments tab
This tab displays information about how the device is currently being used — whether the device is connected to a MediaLive input, a MediaConnect flow, or isn't being used.
You can change the flow that the device is attached to. You can detach the flow, so that the device isn't in use. For more information about both these tasks, see [Attaching and detaching a Link device](device-attach.md).
**Device is not configured for any use**
A message indicates that the device is not being used. To set up the device as the source for an input, see [Using Link with a MediaLive input](device-use-input.md). To set up the device as the source for a MediaConnect flow (UHD devices only), see [Using Link with a MediaConnect flow](device-use-flow.md).
**Device is configured as the source for one or more inputs**
The tab displays the ARN of the MediaLive input that the device is attached to. You can set up the device as the source for up to four inputs. You can detach the input so that the device isn't in use. For more information about both these tasks, see [Attaching and detaching a Link device](device-attach.md).
**Device is configured as the source for an MediaConnect flow**
Applies only to UHD devices. The tab displays information about the attachment to the flow:
+ The ARN of the flow
+ The source name of the flow. Keep in mind that flows can have more than one source.
+ The ARN of the secret used for encryption.
+ The ARN of the role that MediaLive uses to work with the flow.
## Tags tab
This table displays tags that you have set up for the device. You can choose **Add tag** and **Remove tag** to change tags. For more information about tags, see [Tagging AWS Elemental MediaLive
resources.](tagging.md)
# Transferring a Link device to another account
You can transfer a device to a different AWS account, to transfer ownership of the device to that account. The recipient of a transfer must accept or reject the incoming transfer in order for the transfer to be finalized. After the transfer is finalized, all charges for use of the device are applied to the new account.
**Topics**
+ [Initiating a device transfer](#device-transfer-send)
+ [Cancelling an outgoing device transfer](#device-transfer-cancel)
+ [Accepting a device transfer](#device-transfer-receive)
## Initiating a device transfer
**To transfer a Link to another AWS account**
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Input devices**. Find the card for the Link that you want to transfer and choose the hyperlink.
1. On the **Device details** page for the device, choose **Other device actions** then **Transfer device**.
1. On the **Transfer input device** dialog, choose **Transfer to another AWS account**, enter the AWS account to transfer to, and type an optional message. Then choose **Transfer**.
1. In the navigation pane, choose **Input devices**, then choose **Device transfers**. The transfer request appears in the **Outgoing transfers** tab.
The transfer is pending until the recipient accepts the device. While the transfer is pending, you can cancel the request, as described in the following section.
If the recipient accepts the transfer, the device no longer appears in any of your device lists.
If the recipient rejects the transfer, the device appears again on your **Input devices** page.
## Cancelling an outgoing device transfer
You can cancel a device transfer while the request is pending.
**To cancel an outgoing device transfer**
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Input Devices**. Choose **Device transfers**, then choose the **Outgoing transfers** tab.
1. In the list of transfers, choose the transfer you want to cancel, then choose **Cancel**.
## Accepting a device transfer
The owner of a device can transfer a device to your AWS account. For example, someone in your organization might transfer the device from one AWS account in your organization to another AWS account.
If you are expecting to receive a device transfer, you should regularly check the **Incoming transfers** tab on the **Device transfers** page. You must accept the transfer. You can't use the device until you have accepted the transfer.
**To accept a device transfer**
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Input devices**. Choose **Device transfers**, then choose the **Incoming transfers** tab.
1. In the list of transfers, choose the device that you want to accept, then choose **Accept** or **Reject**.
1. In the navigation pane, choose **Input devices** again. The device now appears in the list of devices on the **Input devices** page.
# Transferring a Link device to another Region
You can transfer a device to a different AWS Region. (If instead you want to transfer the device to a different Availability Zone in the existing Region, see [Configuring a Link device](device-edit.md).)
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Input devices**. Find the card for the Link that you want to transfer, and choose the hyperlink.
1. On the **Device details** page for the device, choose **Other device actions** then **Transfer device**.
1. On the **Transfer input device** dialog, choose **Transfer to another AWS Region**, and enter the Region. Then choose **Transfer**. The transfer occurs immediately. There is no need to confirm the transfer.
1. To locate the moved device, switch to the target Region. Choose **Input devices** in the left navigation pane. The devices that you have access to appear.
You should [review the configuration](device-edit.md) because any customizations (such as the Availability Zone) are deleted during the transfer.
# Configuring a Link device
The Link device has properties that control how it behaves when it is streaming. You should set these properties every time you get ready for a new video event.
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Link input devices**. Find the Link that you want. If there are many devices listed, enter part of the name to filter the list.
1. Choose the hyperlink for the device. The **Device details** page for this device appears.
1. Choose **Modify** then **Configure device**. Change fields. For details about each field, see the sections after this procedure. Then choose **Update**.
MediaLive sends the new values (except for the name) to the devices, so that the device can update itself.
1. Display the **Device details** page and take the appropriate action:
+ If the device is not attached to a MediaLive input or a MediaConnect flow, watch for the state of the device to return to **Idle**. You can now start the channel (which automatically starts the device), or you can start the device and the flow.
+ If the device is currently attached to a MediaLive input or a MediaConnect flow that is active, watch for the state of the device to return to **In use**. Note that there is no need for you to restart the input or flow.
| Field | Description |
| --- | --- |
| Name | Enter a descriptive nickname for the device, for use only in MediaLive. |
| Input source | Configures the source that Link sends to MediaLive: SDI or HDMI.[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/device-edit.html) |
| Maximum bitrate | Set a value if you want to throttle the delivery bitrate to MediaLive. Leave this field blank to let the device determine the bitrate that is best for the network conditions between the device and MediaLive. |
| Latency | Set the device buffer size (latency). [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/device-edit.html)If you leave this field blank, the service uses the default value. Default: 1000 ms (HD devices) or 2000 ms (UHD devices). Minimum: 0 ms. Maximum: 6000 ms. |
| Availability Zone | The Availability Zone (AZ) for the device. This field has an effect only when the device is attached to a MediaLive input. It is ignored when the device is attached to a flow.You should change the Availability Zone for the device whenever the device needs to belong to a different Availability Zone. Key use cases for changing the Availability Zone are the following:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/device-edit.html)You can change the Availability Zone only when the device is attached to a MediaLive input. Typically you change the Availability Zone only when you're deploying it to use it with a new channel. Even if you stop the channel (which automatically stops the device), you can't simply change the Availability Zone. Doing so would probably make the channel inoperable. |
| Codec | This field applies only when the device is connected to a MediaConnect flows. Set this field to the codec you want to use for the event that you are getting ready for. The default is HEVC.Note the following:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/device-edit.html) |
| Input resolution | This field applies only if the device is a UHD device and only when the device is the source for a MediaLive input.Choose the resolution to match the resolution that the device is sending, either HD or UHD. MediaLive uses the value you specify here to calculate the input charges that you will incur — either the charge for HD or the charge for UHD.Note the following:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/device-edit.html) |
# Attaching and detaching a Link device
If you are using a Link device as the source for a MediaConnect flow, you must attach the flow to the device. You can also detach the flow to stop using the device as the source for that flow.
**To attach a device to a flow**
1. Obtain the information about the flow from the person who created the flow.
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Input devices**. Find the card for the appropriate Link , and choose the hyperlink.
1. Choose **Attach MediaConnect flow**. Complete the fields:
+ Flow ARN: The ARN of the flow that you obtained from the MediaConnect user. Either choose **List of ARNs** and select the ARN, or choose **Manual input** and type the ARN.
+ Source name: Type the name that you obtained from the MediaConnect user. Keep in mind that the flow might an have more than one source, so make sure that you obtain the correct name.
+ Secret ARN: The ARN of the secret that holds the encryption key to use with this flow. You obtained this value from the MediaConnect user.
+ Role ARN: The ARN of the role that MediaLive must assume. Obtain this value from your IAM administrator.
1. Choose **Save**.
The device is attached to the specified flow. When you later start the device, MediaLive uses the role ARN to obtain the encryption key that is stored in the secret. MediaLive delivers the key to the device, and the device encrypts the content that it streams. The MediaConnect flow uses the same key to decrypt the content as it receives it.
**To detach a flow from device**
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Input devices**. Find the card for the appropriate Link , and choose the hyperlink.
If the **Device details** page displays information about a MediaConnect flow, then you know that the device is currently attached to a flow.
1. Choose **Remove MediaConnect flow**. Then choose **Save**.
**To detach a device from an input**
To remove the connection between a device an Elemental Link input, you can do either of these changes:
+ You can [Editing an input](edit-input.md) so that it is connected to a different device.
+ You can [delete the input](delete-input.md). Note that you can't modify an Elemental Link input so that it doesn't have a device connected to it.
# Starting and stopping a Link device
You must start or stop a Link only if it is configured as the source for a MediaConnect flow. (You don't need to start or stop the device when it is configured as the source for a MediaLive input. In this case, MediaLive automatically starts and stops the device when you start and stop the related channel.)
You must start a device to instruct it to start streaming video content to send to MediaConnect. After you start a device, it will always try to stream content. It will only stop trying when you explicitly stop it. This means, for example, that if you reboot a device, streaming will automatically resume after the reboot.
You must stop a device before you can perform the following actions:
+ [Update some settings](device-edit.md)
+ [Attach ](device-attach.md)the flow to a different device or detach the flow from the device.
**To start or stop a device**
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Input devices**. Find the card for the appropriate Link , and choose the hyperlink.
1. On the **Device details** page for the device, choose **Start** or **Stop**.
# Rebooting a Link device
You can remotely reboot a Link device from the AWS console. You don't need physical access to the device.
Typically, you reboot the device only as a last resort, to resolve a problem with the device response or with the content that is streaming.
You don't have to stop either the device or the channels before rebooting. MediaLive handles the reboot smoothly.
**To reboot a device**
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Input devices**. Find the card for the Link that you want to reboot, and choose the hyperlink.
1. On the **Device details** page for the device, choose **Other device actions** then **Reboot device**, then confirm the request.
Any MediaLive channels or MediaConnect flows that are using the device will lose input briefly, but the channels or flows won't stop or fail.
When the reboot is complete, the device connection status changes to **Connected**. If the device was streaming prior to the reboot, it automatically resumes streaming.
# Updating software on a Link device
Link devices automatically install updates when they are powered on, assuming that the MediaLive channels that use the device have stopped.
However, if you don't stop your channels frequently, you should start a maintenance window at a convenient time. The device will install software updates some time in the next two hours.
You don't have to stop either the device or the channels before starting a maintenance window. MediaLive handles the update smoothly.
**To start a maintenance window for a device**
1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).
1. In the navigation pane, choose **Input devices**. Find the card for the Link that you want to update, and choose the hyperlink.
1. On the **Device details** page for the device, choose **Other device actions** then **Start maintenance**, then confirm the request.
The maintenance window starts. The update will start some time during the next two hours. When the update starts, any channels that are using the device will lose input briefly, but the channels won't stop or fail.
When the reboot is complete, the device connection status changes to **Connected**. If the device was streaming prior to the reboot, it automatically resumes streaming output.
# Deleting a Link input device
You don't delete Link input devices. Instead, if someone deregisters the Link device, the Link input device (which is the interface for the device in the console) no longer appears in the **Devices** section. Note that this is the only way that the Link input device is ever removed.
+ If someone powers down the device, the Link input device still appears in the list.
+ If the device is disconnected from the internet, or if the connection from MediaLive to the Link device is down, the Link input device still appears in the list.