Abstract: An IoT service of a provider network may secure connections with IoT devices that are incapable of encrypted transport layer connections. The IoT service may expose a private endpoint of the IoT service into an isolated virtual network of a client. The provider network may provide a private pathway for traffic between the private endpoint and the isolated virtual network. The IoT service may receive, at the private endpoint from a remote edge device of the client, a request to connect to the IoT service. In response, the IoT network may determine that the request was received from the isolated virtual network of the client. In response to determining that he request was received from the isolated virtual network of the client, the IoT service may authenticate the private endpoint and establish a connection with the remote edge device.

Abstract: Systems and methods are provided for dynamically configuring an IoT communications system. The IoT communications system receives a client message from an IoT device. The client message includes an endpoint designation (such as by specifying an endpoint in the Server Name Indication (SNI) field of the TLS client hello message). The IoT communications system determines whether the endpoint is associated with a custom or default processing logic and/or settings. Either custom or default processing logic is executed or custom or default settings are applied.

Abstract: A technology is described for modifying a message frequency of a device. In one example, a network connection is identified between a device and a service provider environment. A message frequency is set for which to send reachability messages between the device and the service provider environment to maintain the network connection. The reachability messages may be sent between the device and the service provider environment at the message frequency. After testing whether the networking connection is maintained at the message frequency, the message frequency may be modified to a modified message frequency.

Abstract: Systems and methods are provided for dynamically configuring an IoT communications system. The IoT communications system receives a client message from an IoT device. The client message includes an endpoint designation (such as by specifying an endpoint in the Server Name Indication (SNI) field of the TLS client hello message). The IoT communications system determines whether the endpoint is associated with a custom or default processing logic and/or settings. Either custom or default processing logic is executed or custom or default settings are applied.

Abstract: A socket service may be used to link a peer socket to another peer socket. The peer socket is for communicating data to and from a client device and the other peer socket is for communicating data to and from another client device. If a socket opens and the corresponding peer socket is not yet open then the socket waits for the corresponding peer socket to open. When a client device requests a socket to be opened, the client device requests a particular client-defined function mapping to be associated with the socket. When the socket is opened, the endpoint specified in the client-defined function mapping is invoked. An identifier associated with the client device is sent to the endpoint. If the endpoint returns a socket identifier for another socket, then the socket service links the peer socket to the other peer socket, linking the client device to another client device.

Abstract: Compute hosts and a routing system may be used for connection and application state migration for uninterrupted service availability. In response to an indication to transfer a connection from a particular compute host to another compute host, the particular compute host obtains a connection state and an application state for the connection and sends the connection state and the application state to the other compute host. The connection state includes information for a connection-oriented protocol and the application state includes information for an application-layer protocol. The other compute host receives and applies the connection state and the application state in order to establish a termination point to terminate the connection at the other compute host instead of at the particular compute host. The data for the connection is routed to the other compute host, wherein the client is unaware of transfer of the connection to the other compute host.

Abstract: A socket service may be used to implement client-defined function mappings (e.g., custom protocols) for sockets hosted by the socket service so that when a particular socket is opened for a particular client device, the socket operates according to a particular client-defined function mapping requested by the particular client device. To establish a particular client-defined function mapping, a socket manager may receive request from a user that specifies a particular endpoint (e.g., a client-registered function). When a client device requests a socket to be opened, the client device requests the particular client-defined function mapping to be associated with the socket. When the socket is opened, the endpoint is invoked. The particular client-defined function mapping may also specify one or more receive criteria for data received at the socket. If the one or more receive criteria is met, the endpoint is invoked by sending the data to the endpoint.

Abstract: Techniques are described for providing a predictive data streaming service associated with a visual media file. For example, third type of frame data for a visual media file may be transmitted to a client device from a streaming service. In embodiments, a selection of the particular visual media file may be transmitted to the streaming service. A request may be made to an interface associated with the client device, via an application program interface call, for a first data stream of a first type of frame data and a second data stream of a second type of frame data for the particular visual media file. The request may be based at least in part on the selection of the particular visual media file and after receipt of the third type of frame data. The third type of frame data, the first data stream of the first type of frame data, and the second data stream of the second type of frame data may be interleaved based at least in part on instructions from the interface.

Abstract: Techniques are described for providing a predictive data streaming service associated with a visual media file. For example, third type of frame data for a visual media file may be transmitted to a client device from a streaming service. In embodiments, a selection of the particular visual media file may be transmitted to the streaming service. A request may be made to an interface associated with the client device, via an application program interface call, for a first data stream of a first type of frame data and a second data stream of a second type of frame data for the particular visual media file. The request may be based at least in part on the selection of the particular visual media file and after receipt of the third type of frame data. The third type of frame data, the first data stream of the first type of frame data, and the second data stream of the second type of frame data may be interleaved based at least in part on instructions from the interface.