Kinesis Video Streams without the internet: PrivateLink VPC endpoints are here
Hi, it's Shii-chan! Today's news is for everyone who wants to handle camera video on a closed network!
AWS What's NewWhat was announced?
AWS What's New announced that Amazon Kinesis Video Streams now supports interface VPC endpoints powered by AWS PrivateLink.
What changes
Traffic between your VPC and Kinesis Video Streams stays on the AWS network and is not exposed to the public internet. This covers the control plane and the video ingestion and playback data planes.
So even with strict security, compliance, or network-isolation requirements, you can ingest, store, and play back video without:
- Internet gateways
- NAT devices
- Public IP addresses
For example, connected-camera or IoT video workloads in a private subnet can send media to Kinesis Video Streams and retrieve it for playback and analytics entirely over private connectivity!
Dive Deep
- You create the endpoint from the Amazon VPC console, AWS CLI, or AWS SDKs
- You can attach a VPC endpoint policy to control access
- It's available in all AWS Regions where Kinesis Video Streams is available
- That includes the AWS GovCloud (US) Regions and the China (Beijing) Region operated by Sinnet
Wrap-up
- Kinesis Video Streams supports PrivateLink VPC endpoints
- Control plane and data planes both stay on the AWS network
- Ingest, store, and play back video without IGW, NAT, or public IPs
- Available in every supported Region, including GovCloud and China (Beijing)
This is a great fit for security-minded teams handling camera or IoT video in isolated networks!