{"id":101,"date":"2026-04-12T20:06:04","date_gmt":"2026-04-12T20:06:04","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/alibaba-cloud-link-visual-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-internet-of-things\/"},"modified":"2026-04-12T20:06:04","modified_gmt":"2026-04-12T20:06:04","slug":"alibaba-cloud-link-visual-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-internet-of-things","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/alibaba-cloud-link-visual-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-internet-of-things\/","title":{"rendered":"Alibaba Cloud Link Visual Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Internet of Things"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Internet of Things<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<p>Link Visual is an Alibaba Cloud Internet of Things (IoT) service designed for connecting, managing, and consuming <strong>video-capable IoT devices<\/strong>\u2014most commonly smart cameras, video doorbells, and industrial video sensors\u2014so applications can securely access <strong>live view<\/strong>, <strong>playback<\/strong>, and <strong>event-driven video<\/strong> experiences.<\/p>\n\n\n\n<p>In simple terms: <strong>Link Visual helps you build \u201ccamera features\u201d into your product<\/strong> (mobile app, web portal, or operations console) without having to design an entire video device access layer from scratch.<\/p>\n\n\n\n<p>Technically, Link Visual typically sits between <strong>video devices<\/strong> and <strong>applications<\/strong>. Devices authenticate to Alibaba Cloud, publish video streams and events, and applications request controlled access (for example, to view live video, retrieve recordings, or fetch snapshots). Link Visual is commonly used alongside <strong>Alibaba Cloud IoT Platform<\/strong> for device identity, provisioning, and fleet management, and it may rely on other Alibaba Cloud services for storage, logging, and auditability depending on your configuration.<\/p>\n\n\n\n<p><strong>What problem it solves:<\/strong> Building a reliable and secure IoT video solution is hard\u2014device connectivity, authentication, stream access control, cloud storage, event triggers, multi-tenant authorization, and operational tooling. Link Visual addresses this by providing a managed foundation for IoT video access patterns that teams can integrate into products and operations.<\/p>\n\n\n\n<blockquote>\n<p>Naming note: Alibaba Cloud product naming sometimes appears as <strong>\u201cLink Visual\u201d<\/strong> or <strong>\u201cLinkVisual\u201d<\/strong> across portals and SDKs. This tutorial uses <strong>Link Visual<\/strong> as the primary service name. <strong>Verify in official docs<\/strong> if your console uses a slightly different label.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Link Visual?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose (practical definition)<\/h3>\n\n\n\n<p>Link Visual is an Alibaba Cloud IoT video service that helps you connect <strong>video-enabled IoT devices<\/strong> to the cloud and enable <strong>application-side consumption<\/strong> of video-related capabilities (such as live preview and playback) in a controlled, scalable way.<\/p>\n\n\n\n<p>Because exact feature availability can vary by region and edition, treat the following scope as a <strong>capability model<\/strong> and <strong>verify in official docs<\/strong> for the precise list in your region:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities (typical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Device onboarding for video devices<\/strong> (often integrated with IoT Platform product\/device identities).<\/li>\n<li><strong>Secure application-side access<\/strong> to device video and media artifacts (for example, snapshots\/recordings).<\/li>\n<li><strong>Event-driven workflows<\/strong> for video devices (for example, motion\/alarm events that can trigger downstream processing).<\/li>\n<li><strong>Developer integration<\/strong> through console configuration, SDKs, and OpenAPI.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Major components (conceptual)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Component<\/th>\n<th>What it does<\/th>\n<th>Where it\u2019s used<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Link Visual console<\/td>\n<td>Service configuration, projects\/devices\/app credentials (varies)<\/td>\n<td>Operators, engineers<\/td>\n<\/tr>\n<tr>\n<td>Device-side integration (SDK\/protocol)<\/td>\n<td>Enables cameras\/gateways to authenticate and publish media\/events<\/td>\n<td>Firmware\/embedded teams<\/td>\n<\/tr>\n<tr>\n<td>Application-side integration (SDK\/OpenAPI)<\/td>\n<td>Lets your app request live preview\/playback and manage access<\/td>\n<td>Mobile\/web\/backend teams<\/td>\n<\/tr>\n<tr>\n<td>Storage integration (often OSS or service-managed storage)<\/td>\n<td>Stores recordings\/snapshots depending on your chosen mode<\/td>\n<td>Architects, cost owners<\/td>\n<\/tr>\n<tr>\n<td>Observability and auditing (CloudMonitor\/Log Service\/ActionTrail)<\/td>\n<td>Tracks usage, errors, and security actions<\/td>\n<td>SRE\/SecOps<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Service type<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Managed IoT video access service<\/strong> (device-to-cloud + app consumption control plane).<\/li>\n<li>Usually used together with <strong>Alibaba Cloud IoT Platform<\/strong> (device identity + fleet management).<br\/>\n  Exact coupling depends on how you onboard devices. <strong>Verify in official docs<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scope: regional\/global\/zonal and tenancy model<\/h3>\n\n\n\n<p>Alibaba Cloud IoT services are commonly <strong>region-scoped<\/strong>, and you typically must keep closely coupled resources (device identity, video access, storage) in the <strong>same region<\/strong> to minimize latency and avoid cross-region data transfer.<br\/>\n<strong>Verify in official docs\/console<\/strong>:\n&#8211; Which regions support Link Visual\n&#8211; Whether Link Visual resources are \u201cinstance\/project\u201d scoped\n&#8211; Any cross-region access constraints<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How it fits into the Alibaba Cloud ecosystem<\/h3>\n\n\n\n<p>A common production design is:\n&#8211; <strong>IoT Platform<\/strong> for device identities, topics, device shadows, OTA, and fleet operations\n&#8211; <strong>Link Visual<\/strong> for video device access patterns (live\/playback\/event media workflows)\n&#8211; <strong>Object Storage Service (OSS)<\/strong> for durable media storage (if your architecture stores recordings\/snapshots there)\n&#8211; <strong>Message Service \/ EventBridge<\/strong> (or IoT Platform rules) to route device events\n&#8211; <strong>Function Compute<\/strong> for event-driven processing (thumbnails, notifications, AI calls)\n&#8211; <strong>Log Service (SLS)<\/strong>, <strong>CloudMonitor<\/strong>, <strong>ActionTrail<\/strong> for observability and audit<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Link Visual?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Faster time to market<\/strong> for camera features in consumer or industrial products.<\/li>\n<li><strong>Reduced engineering effort<\/strong> compared to building a custom video device access layer.<\/li>\n<li><strong>More predictable operations<\/strong> with managed control-plane components (quotas, audit trails, console tooling).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Standardized device\/app access patterns<\/strong> (auth, authorization boundaries, token-based access patterns\u2014implementation varies; verify).<\/li>\n<li><strong>Integration with the Alibaba Cloud IoT stack<\/strong>, reducing glue code and simplifying device fleet management.<\/li>\n<li><strong>Scalable architecture patterns<\/strong> (multi-tenant device fleets, app-to-device access control).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Centralized management<\/strong> for video device access (projects, devices, credentials).<\/li>\n<li>Easier <strong>troubleshooting<\/strong> through Alibaba Cloud\u2019s logging and monitoring ecosystem (exact integration points vary).<\/li>\n<li>Helps avoid building and maintaining your own:<\/li>\n<li>video access gateways<\/li>\n<li>replay\/record indexing systems<\/li>\n<li>large-scale device stream authorization service<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Centralized <strong>identity and access controls<\/strong> via Alibaba Cloud account\/RAM and service-level credentials.<\/li>\n<li>Supportable security posture through:<\/li>\n<li>audit logging (ActionTrail)<\/li>\n<li>encryption and secrets hygiene (KMS\/Secrets Manager\u2014architecture choice)<\/li>\n<li>network exposure controls (public endpoints vs private connectivity\u2014verify)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability\/performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Designed for fleets of devices producing events and media metadata.<\/li>\n<li>Enables \u201cfan-out\u201d access patterns (many app viewers, many devices) while keeping authorization consistent.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose Link Visual<\/h3>\n\n\n\n<p>Choose Link Visual when:\n&#8211; You are building an IoT product where <strong>video is a primary capability<\/strong>\n&#8211; You need <strong>managed<\/strong> device-video access patterns and want to integrate with Alibaba Cloud IoT Platform\n&#8211; You want faster delivery and prefer using <strong>Alibaba Cloud-native controls<\/strong> for security\/audit\/operations<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<p>Avoid Link Visual (or validate carefully) when:\n&#8211; You need a <strong>general-purpose broadcast\/live streaming platform<\/strong> for human-generated content (consider Alibaba Cloud video streaming products instead)\n&#8211; Your devices are not video-capable and don\u2019t need any video\/media workflows\n&#8211; You require a <strong>fully air-gapped<\/strong> environment with no public cloud endpoints (possible only with special architectures\u2014verify)\n&#8211; You have strict requirements for a protocol\/codec\/RTSP\/ONVIF\/GB28181 workflow that Link Visual may not support in your region\/edition (verify)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Link Visual used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Smart home (doorbells, indoor\/outdoor cameras, baby monitors)<\/li>\n<li>Property management and smart buildings<\/li>\n<li>Retail (loss prevention, queue monitoring, store compliance)<\/li>\n<li>Manufacturing and industrial IoT (remote inspection, safety monitoring)<\/li>\n<li>Logistics and yards (gate cameras, perimeter monitoring)<\/li>\n<li>Agriculture (barn monitoring, crop area cameras)<\/li>\n<li>Healthcare (non-clinical monitoring\u2014must validate compliance and consent)<\/li>\n<li>Education\/campus operations (facility monitoring\u2014subject to policy)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Embedded\/firmware teams integrating camera modules or gateways<\/li>\n<li>Mobile\/web developers building the user experience (live preview, playback, alerts)<\/li>\n<li>Platform engineering teams managing multi-tenant identity, keys, and environments<\/li>\n<li>SRE\/operations teams handling incidents and monitoring<\/li>\n<li>Security engineers performing IAM review, audit validation, and threat modeling<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Live preview for end users (consumer apps)<\/li>\n<li>Playback of cloud recordings (support and incident review)<\/li>\n<li>Event-driven alerting (motion detection alarms -&gt; notifications)<\/li>\n<li>Video evidence workflows (export\/retain, compliance retention)<\/li>\n<li>Operational monitoring dashboards for a fleet of sites\/devices<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Edge camera \u2192 Link Visual \u2192 app viewers  <\/li>\n<li>Edge camera \u2192 Link Visual \u2192 event pipeline \u2192 downstream compute\/storage  <\/li>\n<li>Multi-tenant SaaS: many customers, each with isolated projects\/devices\/roles<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Production vs dev\/test usage<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dev\/test<\/strong>: usually focuses on onboarding flows, credential management, and app integration with a handful of devices.<\/li>\n<li><strong>Production<\/strong>: adds multi-region planning (if applicable), strict IAM boundaries, storage lifecycle policies, monitoring\/alerting, and cost controls for video retention and bandwidth.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic scenarios (verify exact support and APIs in your region\/edition).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Smart doorbell live view + event snapshots<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Users want immediate live view when a doorbell rings.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Provides a managed pattern for app-side secure access to device video and media artifacts.<\/li>\n<li><strong>Example:<\/strong> Doorbell sends a \u201cring\u201d event; the app requests live preview and shows a snapshot thumbnail in notifications.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Home camera cloud playback (7\/30-day retention)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Users want to review past recordings without local SD cards.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Integrates device recording workflows with cloud access control and playback retrieval.<\/li>\n<li><strong>Example:<\/strong> App provides a timeline UI; playback requests are authorized and served from cloud storage.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Industrial remote inspection for distributed assets<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Remote experts need to inspect equipment across many sites.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Centralized device video access with fleet identity management through Alibaba Cloud IoT.<\/li>\n<li><strong>Example:<\/strong> Operations portal shows device health plus live preview on-demand.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Retail incident review with event-driven bookmarks<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Reviewing long video is expensive and slow.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Event markers (motion\/alarm) can reduce search space and trigger retention workflows.<\/li>\n<li><strong>Example:<\/strong> Motion events create bookmarks; staff clicks an event to open corresponding playback window.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Construction site safety monitoring<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need quick checks of safety zones and incident evidence.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Enables controlled access for supervisors and auditors; integrates with logging\/audit trails.<\/li>\n<li><strong>Example:<\/strong> Supervisor accounts have read-only live view; audit exports are logged.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Fleet cameras for logistics yards<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Many cameras across gates and loading bays with frequent viewer access.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Built to handle large device fleets and viewer access patterns with centralized auth.<\/li>\n<li><strong>Example:<\/strong> Gate events trigger notifications and start short recordings for evidence.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Smart community property management<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Tenants and property staff need different access levels.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Supports multi-tenant access models (projects\/roles\/credentials\u2014verify).<\/li>\n<li><strong>Example:<\/strong> Tenants view their own building\u2019s cameras; property staff sees all common areas.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Remote caregiving (non-medical) monitoring with strict consent<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Families want controlled access and auditability.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Centralized access control and auditing support security posture (must ensure compliance).<\/li>\n<li><strong>Example:<\/strong> Access is time-bound and role-restricted; all access is logged.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) AI-assisted event triage pipeline<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Too many events; need auto-triage and classification.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Event stream can trigger downstream compute; media references can be processed.<\/li>\n<li><strong>Example:<\/strong> Alarm event triggers Function Compute which calls an AI model to classify \u201cperson vs pet\u201d.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Device manufacturing QA and soak testing<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need repeatable testing for camera onboarding, credentials, and streaming behavior.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Standardizes onboarding flows; integrates with IoT Platform test environments.<\/li>\n<li><strong>Example:<\/strong> QA scripts register test devices, verify stream access, and validate event generation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Customer support \u201cshare a live view\u201d (time-limited)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Support needs temporary access to troubleshoot device positioning\/connectivity.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> Controlled and auditable access patterns can be implemented (verify token\/role options).<\/li>\n<li><strong>Example:<\/strong> Support generates a 15-minute access grant; customer approves in-app.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Compliance-driven retention and deletion workflows<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Must retain evidence for N days, then delete.<\/li>\n<li><strong>Why Link Visual fits:<\/strong> If recordings land in OSS or managed storage, lifecycle policies can enforce retention.<\/li>\n<li><strong>Example:<\/strong> SLS\/ActionTrail provides audit logs; OSS lifecycle deletes after 30 days.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<p>Because the exact feature list can differ by region\/edition and product updates, treat this section as a structured checklist and <strong>verify each item in the official Link Visual documentation for your region<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6.1 Device video access enablement<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Enables video-capable devices to be represented and accessed through Link Visual.<\/li>\n<li><strong>Why it matters:<\/strong> You need a consistent cloud-side abstraction for live view\/playback access.<\/li>\n<li><strong>Practical benefit:<\/strong> Simplifies application development and operational tooling.<\/li>\n<li><strong>Caveats:<\/strong> Device compatibility, supported protocols, and SDK requirements vary\u2014<strong>verify supported device integration methods<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.2 Live preview (live view) for applications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Allows authorized applications\/users to request a live stream from a device.<\/li>\n<li><strong>Why it matters:<\/strong> Live view is the primary requirement for many IoT camera experiences.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster implementation of \u201cwatch now\u201d features with centralized authorization.<\/li>\n<li><strong>Caveats:<\/strong> Latency depends on region, device uplink, and chosen streaming mode; concurrency limits may apply\u2014verify quotas.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.3 Playback of recorded video (cloud recording)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Enables applications to play back historical recordings if you have recording enabled.<\/li>\n<li><strong>Why it matters:<\/strong> Playback is essential for security, operations, and incident review.<\/li>\n<li><strong>Practical benefit:<\/strong> Avoids implementing custom indexing\/storage\/retrieval pipelines.<\/li>\n<li><strong>Caveats:<\/strong> Storage billing and retention policies can dominate costs. Confirm storage location and lifecycle controls.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.4 Snapshots \/ image capture (if supported)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides snapshots for previews, notifications, and UI thumbnails.<\/li>\n<li><strong>Why it matters:<\/strong> Snapshots reduce bandwidth and improve user experience for event lists.<\/li>\n<li><strong>Practical benefit:<\/strong> \u201cEvent list with thumbnails\u201d becomes simpler to implement.<\/li>\n<li><strong>Caveats:<\/strong> Snapshot frequency and resolution may be limited; storage costs apply.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.5 Event integration (alarms\/motion\/doorbell press)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Handles device-originated events and makes them consumable by applications and downstream systems.<\/li>\n<li><strong>Why it matters:<\/strong> Most IoT camera solutions are event-driven, not continuous viewing.<\/li>\n<li><strong>Practical benefit:<\/strong> Enables alerts, workflows, and \u201cjump to playback at event time.\u201d<\/li>\n<li><strong>Caveats:<\/strong> Ensure event timestamping is robust (time sync); validate event ordering and deduplication design.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.6 Application-side credentials and authorization model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides a way to authorize apps\/users\/services to access device video features.<\/li>\n<li><strong>Why it matters:<\/strong> You need strict separation between:<\/li>\n<li>cloud operators (admins)<\/li>\n<li>applications (your product)<\/li>\n<li>end users (your customers)<\/li>\n<li><strong>Practical benefit:<\/strong> Supports multi-tenant architectures and least privilege.<\/li>\n<li><strong>Caveats:<\/strong> Exact token\/credential mechanisms vary\u2014<strong>verify official auth flow<\/strong> and avoid embedding long-lived secrets in mobile apps.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.7 OpenAPI \/ SDK integration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Allows programmatic management and data-plane requests.<\/li>\n<li><strong>Why it matters:<\/strong> Production systems need automation (provisioning, troubleshooting, analytics).<\/li>\n<li><strong>Practical benefit:<\/strong> CI\/CD and platform automation become feasible.<\/li>\n<li><strong>Caveats:<\/strong> API rate limits and request signing complexity\u2014use official SDKs where possible.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.8 Integration with Alibaba Cloud observability and governance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Enables operational visibility via Alibaba Cloud monitoring\/logging\/audit services.<\/li>\n<li><strong>Why it matters:<\/strong> Video services are high-traffic and incident-prone.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster incident response and accountability.<\/li>\n<li><strong>Caveats:<\/strong> Not all service events may be emitted automatically; you might need app-side logging.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">7.1 High-level architecture<\/h3>\n\n\n\n<p>A typical IoT video architecture using Alibaba Cloud looks like this:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Device provisioning<\/strong>\n   &#8211; A camera is manufactured with a device identity plan (per-device credentials).\n   &#8211; Device identity is commonly managed in <strong>Alibaba Cloud IoT Platform<\/strong> (product + device).<\/p>\n<\/li>\n<li>\n<p><strong>Device connectivity<\/strong>\n   &#8211; Device connects to the cloud and authenticates.\n   &#8211; Device sends telemetry\/events and participates in a video workflow (method depends on Link Visual integration model\u2014verify).<\/p>\n<\/li>\n<li>\n<p><strong>Control plane<\/strong>\n   &#8211; Operators configure projects, device associations, and application credentials in Link Visual.\n   &#8211; Applications request authorization for video actions (live preview, playback).<\/p>\n<\/li>\n<li>\n<p><strong>Data plane<\/strong>\n   &#8211; Live stream and\/or recordings are delivered to app clients (delivery model varies\u2014verify).\n   &#8211; Media may be stored in a managed store or OSS-backed storage, depending on your design and Link Visual features in your region.<\/p>\n<\/li>\n<li>\n<p><strong>Observability<\/strong>\n   &#8211; Logs and metrics are collected and monitored.\n   &#8211; Auditing tracks administrative actions and access patterns.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">7.2 Request\/data\/control flow (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Control flow:<\/strong> app\/backend \u2192 Link Visual (request access grant \/ session \/ token)<\/li>\n<li><strong>Data flow:<\/strong> device \u2192 Link Visual (video\/media\/events) and Link Visual \u2192 app (stream\/playback)<\/li>\n<li><strong>Event flow:<\/strong> device \u2192 IoT Platform topics\/rules (optional) \u2192 EventBridge\/MNS\/FC<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7.3 Integrations with related services (common patterns)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>IoT Platform<\/strong>: device registry, authentication, messaging, rules.<\/li>\n<li><strong>OSS<\/strong>: snapshots\/recordings storage, lifecycle policies, archival tiers.<\/li>\n<li><strong>Function Compute<\/strong>: event-driven processing (thumbnail generation, notifications, AI calls).<\/li>\n<li><strong>Message Service \/ EventBridge<\/strong>: routing events to your systems.<\/li>\n<li><strong>Log Service (SLS)<\/strong>: centralized logs for troubleshooting and access analytics.<\/li>\n<li><strong>ActionTrail<\/strong>: audit for console\/API actions.<\/li>\n<li><strong>RAM \/ KMS \/ Secrets Manager<\/strong>: identity and secrets controls.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7.4 Dependency services (design-time)<\/h3>\n\n\n\n<p>Your deployment may depend on:\n&#8211; IoT Platform instance\/product\/device setup\n&#8211; OSS buckets and lifecycle policies (if you store media there)\n&#8211; VPC endpoints\/private networking (if supported\/required)\n&#8211; RAM roles\/policies for CI\/CD automation<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7.5 Security\/authentication model (what to plan for)<\/h3>\n\n\n\n<p>You will usually have multiple identity planes:\n&#8211; <strong>Alibaba Cloud account\/RAM identities<\/strong> for admin and automation access\n&#8211; <strong>Device identities<\/strong> (per-device credentials) for device-to-cloud auth\n&#8211; <strong>Application identities<\/strong> (app credentials or RAM roles) for server-side access\n&#8211; <strong>End-user identities<\/strong> (your app\u2019s user accounts) mapped to device access in your backend<\/p>\n\n\n\n<p>A recommended pattern is:\n&#8211; Keep <strong>Link Visual administrative actions<\/strong> restricted to a small set of RAM roles.\n&#8211; Have your backend request time-bound access for end users.\n&#8211; Avoid putting privileged secrets in mobile apps.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7.6 Networking model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Devices generally connect to <strong>public cloud endpoints<\/strong> unless private connectivity options are supported and configured.<\/li>\n<li>For enterprises, consider:<\/li>\n<li>outbound-only device connectivity<\/li>\n<li>firewall egress allowlists<\/li>\n<li>region selection close to device geography<\/li>\n<li><strong>Verify in official docs<\/strong> if Link Visual supports private endpoints or VPC integration in your region.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7.7 Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Track:<\/li>\n<li>device online\/offline and stream success rate<\/li>\n<li>playback request latency<\/li>\n<li>error rate by region\/device model\/firmware version<\/li>\n<li>bandwidth and storage growth<\/li>\n<li>Governance:<\/li>\n<li>standard tagging for environments (dev\/test\/prod)<\/li>\n<li>per-tenant isolation strategy (projects\/accounts)<\/li>\n<li>audit review via ActionTrail<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7.8 Simple architecture diagram<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  D[IoT Camera \/ Video Device] --&gt;|auth + media\/events| LV[Alibaba Cloud Link Visual]\n  APP[Mobile\/Web App] --&gt;|request access| LV\n  LV --&gt;|live preview \/ playback| APP\n  LV &lt;--&gt;|device registry (optional)| IOTP[Alibaba Cloud IoT Platform]\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.9 Production-style architecture diagram<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Edge[\"Edge Sites (Homes \/ Stores \/ Factories)\"]\n    Cam1[Camera Devices]:::device\n    GW[Optional Gateway]:::device\n  end\n\n  subgraph AlibabaCloud[\"Alibaba Cloud (Region)\"]\n    IOTP[IoT Platform\\n(device identity, messaging)]:::svc\n    LV[Link Visual\\n(video access control plane)]:::svc\n    OSS[OSS\\n(media storage, lifecycle)]:::svc\n    FC[Function Compute\\n(event processing)]:::svc\n    EB[EventBridge \/ MNS\\n(event routing)]:::svc\n    SLS[Log Service (SLS)\\nlogs + dashboards]:::svc\n    AT[ActionTrail\\naudit]:::svc\n    RAM[RAM\\nroles\/policies]:::svc\n    KMS[KMS \/ Secrets Manager]:::svc\n  end\n\n  subgraph Apps[\"Applications\"]\n    BE[Backend API\\n(tenant + user auth)]:::app\n    Web[Web Console]:::app\n    Mobile[Mobile App]:::app\n  end\n\n  Cam1 --&gt;|connect\/auth| IOTP\n  Cam1 --&gt;|video\/events (verify path)| LV\n  GW --&gt;|video\/events| LV\n\n  BE --&gt;|OpenAPI\/SDK calls| LV\n  BE --&gt;|device mgmt| IOTP\n  Web --&gt;|user session| BE\n  Mobile --&gt;|user session| BE\n\n  LV --&gt;|recordings\/snapshots (if configured)| OSS\n  LV --&gt;|logs\/metrics (varies)| SLS\n  IOTP --&gt;|events| EB\n  EB --&gt; FC\n  FC --&gt; OSS\n  FC --&gt; SLS\n\n  AT --&gt; SLS\n  RAM --&gt; LV\n  KMS --&gt; BE\n\n  classDef svc fill:#eef,stroke:#335,stroke-width:1px;\n  classDef device fill:#efe,stroke:#353,stroke-width:1px;\n  classDef app fill:#ffe,stroke:#553,stroke-width:1px;\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Account and billing<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An <strong>Alibaba Cloud account<\/strong> with billing enabled.<\/li>\n<li>Ability to create\/attach <strong>RAM users\/roles<\/strong> and policies.<\/li>\n<li>A payment method or enterprise billing arrangement suitable for usage-based video services.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM (RAM)<\/h3>\n\n\n\n<p>You typically need:\n&#8211; Access to Link Visual console and APIs (service-specific permissions)\n&#8211; Access to IoT Platform resources if you use IoT Platform for device identity\n&#8211; Access to OSS, Log Service, ActionTrail if your architecture uses them<\/p>\n\n\n\n<p>Because managed policy names can differ and change, do this safely:\n&#8211; In RAM console, create a role for admins and one for automation.\n&#8211; Grant least privilege by selecting the Link Visual service and only required actions.\n&#8211; <strong>Verify in official docs<\/strong> for recommended RAM policies and actions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Tools<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Alibaba Cloud Console (web)<\/li>\n<li>Optional:<\/li>\n<li><a href=\"https:\/\/api.alibabacloud.com\/\">OpenAPI Explorer<\/a> for interactive API testing<\/li>\n<li>Official Alibaba Cloud SDK for your language (Java\/Python\/Go\/Node.js\u2014verify supported SDKs for Link Visual)<\/li>\n<li>Alibaba Cloud CLI (<code>aliyun<\/code>) <strong>if Link Visual is supported by CLI in your environment<\/strong> (verify)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Link Visual availability can be region-dependent.<\/li>\n<li>Choose the region closest to devices and end users.<\/li>\n<li><strong>Verify region support<\/strong> in the Alibaba Cloud console before provisioning.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas \/ limits<\/h3>\n\n\n\n<p>Expect quotas around:\n&#8211; number of devices\/projects\n&#8211; concurrent live viewers\n&#8211; API rate limits\n&#8211; recording retention and storage capacity (depending on plan)\n<strong>Verify quotas<\/strong> in the Link Visual documentation for your region\/edition.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services (common)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>IoT Platform<\/strong> (commonly used for device registry and connectivity)<\/li>\n<li><strong>OSS<\/strong> (if recordings\/snapshots are stored there)<\/li>\n<li><strong>ActionTrail<\/strong> for audit (recommended)<\/li>\n<li><strong>Log Service<\/strong> for centralized logs (recommended)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<blockquote>\n<p>Pricing changes by region, edition, and purchase model. Do not rely on unofficial numbers. Always confirm using official Alibaba Cloud pricing pages or your account\u2019s price sheet.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">9.1 Pricing dimensions (typical for IoT video)<\/h3>\n\n\n\n<p>Link Visual costs are usually driven by combinations of:\n&#8211; <strong>Number of devices<\/strong> (registered\/active) or enabled channels (depends on product model\u2014verify)\n&#8211; <strong>Live streaming bandwidth\/traffic<\/strong>\n&#8211; <strong>Cloud recording storage<\/strong> (GB-month), plus read\/write operations\n&#8211; <strong>Recording duration<\/strong> (retention days, continuous vs event-based)\n&#8211; <strong>API requests<\/strong> (control plane calls) and concurrency\n&#8211; <strong>Value-added features<\/strong> (for example, AI event processing\u2014if offered in your edition\/region; verify)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9.2 Free tier<\/h3>\n\n\n\n<p>Some Alibaba Cloud services offer trials or free quotas for new users. For Link Visual:\n&#8211; <strong>Verify in official pricing\/trial pages<\/strong> whether a free trial exists and what it includes (devices, storage, traffic, days).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9.3 Direct cost drivers<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Retention length: 7\/30\/90 days dramatically changes storage footprint.<\/li>\n<li>Continuous recording vs event-based recording.<\/li>\n<li>Camera resolution\/bitrate (1080p vs 4K) and frame rate.<\/li>\n<li>Viewer concurrency (many users watching live view).<\/li>\n<li>Exporting\/downloading recordings frequently.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9.4 Hidden or indirect costs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OSS storage<\/strong> and <strong>OSS retrieval\/requests<\/strong> if recordings\/snapshots are stored in OSS.<\/li>\n<li><strong>Cross-region data transfer<\/strong> if devices are in one region and apps consume in another (avoid if possible).<\/li>\n<li><strong>CDN\/acceleration<\/strong> if you use it for app delivery (architecture-dependent).<\/li>\n<li>Logging costs in SLS if you enable verbose logs.<\/li>\n<li>Compute costs in Function Compute if you process events\/media.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9.5 Network\/data transfer implications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Video is bandwidth-heavy. Consider:<\/li>\n<li>uplink capacity at device sites<\/li>\n<li>mobile user network variability<\/li>\n<li>peak hours and concurrency<\/li>\n<li>Keep device region close to user base when possible to reduce latency and egress complexity.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9.6 How to optimize cost (high impact)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prefer <strong>event-based recording<\/strong> if your scenario allows it.<\/li>\n<li>Use <strong>short retention<\/strong> in hot storage and lifecycle older data to cheaper tiers (if OSS is used).<\/li>\n<li>Reduce default bitrate\/resolution where acceptable.<\/li>\n<li>Implement <strong>role-based access<\/strong> and time-bound access to avoid accidental heavy playback usage.<\/li>\n<li>Monitor top devices by bandwidth and investigate anomalies (stuck streams, looping playback).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9.7 Example low-cost starter estimate (no fabricated numbers)<\/h3>\n\n\n\n<p>A low-cost evaluation typically includes:\n&#8211; 1\u20132 cameras\n&#8211; live view testing only (no continuous recording)\n&#8211; minimal snapshots\n&#8211; short test window (a few days)\nYour costs will primarily be:\n&#8211; Link Visual base enablement (if applicable)\n&#8211; small amount of traffic during testing\n&#8211; minimal storage (if any)<\/p>\n\n\n\n<p><strong>How to calculate:<\/strong>\n1. Estimate bitrate (Mbps) \u00d7 viewing hours \u00d7 number of viewers.\n2. Convert to GB and apply your region\u2019s traffic pricing.\n3. Add storage for recordings\/snapshots if enabled.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9.8 Example production cost considerations<\/h3>\n\n\n\n<p>In production, build a cost model per tenant\/site:\n&#8211; devices per site\n&#8211; average daily events\n&#8211; average recording minutes per event\n&#8211; average daily live view minutes per user\n&#8211; retention policy\nThen validate it against:\n&#8211; peak events (holidays, incidents)\n&#8211; firmware bugs causing excessive uploads\n&#8211; support workflows that increase playback usage<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9.9 Official pricing references<\/h3>\n\n\n\n<p>Use official Alibaba Cloud pages and tools:\n&#8211; Alibaba Cloud pricing landing: https:\/\/www.alibabacloud.com\/pricing<br\/>\n&#8211; Alibaba Cloud product search (to find Link Visual pricing page): https:\/\/www.alibabacloud.com\/product<br\/>\n&#8211; OpenAPI Explorer (for API discovery\/testing): https:\/\/api.alibabacloud.com\/  <\/p>\n\n\n\n<p>If you have a direct Link Visual pricing URL in your region\u2019s console, prefer that authoritative link.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab focuses on <strong>safe, low-cost setup<\/strong> and a realistic validation path <strong>without requiring a physical camera<\/strong>, while still preparing the exact building blocks you need for a real device integration.<\/p>\n\n\n\n<p>If you do have a Link Visual-compatible camera\/device SDK integration, you\u2019ll be able to extend the lab to live preview\/playback after Step 6.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Set up Alibaba Cloud IAM (RAM) guardrails for Link Visual administration.<\/li>\n<li>Create the minimum Link Visual + IoT Platform resources needed for a video device onboarding workflow.<\/li>\n<li>Validate access using console checks and OpenAPI Explorer discovery.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Choose a region and create an environment naming standard.\n2. Create RAM roles\/users for least-privilege admin and automation.\n3. Create (or identify) an IoT Platform instance and create a Product + Device placeholder for a camera.\n4. Open Link Visual and create the base project\/resources required for device association (names vary; verify).\n5. Bind\/associate the IoT device identity to Link Visual (method varies; verify).\n6. Validate by confirming the resource graph and discovering Link Visual APIs in OpenAPI Explorer.\n7. Clean up to avoid unwanted charges.<\/p>\n\n\n\n<blockquote>\n<p>Important: Console menu names and flows can change. Follow the intent of each step and <strong>verify in the latest official docs<\/strong> if you see different labels.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Pick a region and define environment naming<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Decide your environment: <code>dev<\/code> for this lab.<\/li>\n<li>Choose a region where:\n   &#8211; Link Visual is available\n   &#8211; IoT Platform is available\n   &#8211; Your target devices\/users are closest (for production)<\/li>\n<\/ol>\n\n\n\n<p><strong>Naming suggestion<\/strong>\n&#8211; Project: <code>lv-dev<\/code>\n&#8211; IoT Product: <code>cam-dev-product<\/code>\n&#8211; Device: <code>cam-dev-001<\/code><\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have a consistent naming scheme, which helps later with IAM scoping, tagging, and cost allocation.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Create RAM identities for least privilege<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to the <strong>RAM<\/strong> console in Alibaba Cloud.<\/li>\n<li>\n<p>Create:\n   &#8211; A RAM role\/user for <strong>Link Visual Admin<\/strong> (human operators)\n   &#8211; A RAM role for <strong>Automation<\/strong> (CI\/CD or backend)<\/p>\n<\/li>\n<li>\n<p>Attach only required permissions:\n   &#8211; Add Link Visual console\/API access\n   &#8211; Add IoT Platform access (create product\/device)\n   &#8211; Optional: OSS\/SLS\/ActionTrail read access for validation<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p>Because managed policy names and action sets can change:\n&#8211; Use the RAM policy editor UI to select services and actions.\n&#8211; Start with read-only where possible, then add specific write actions you need.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You can log in (or assume role) and access Link Visual and IoT Platform with controlled permissions.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Sign in as the admin role\/user and confirm you can open:\n  &#8211; IoT Platform console\n  &#8211; Link Visual console<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Create an IoT Platform Product and Device (camera placeholder)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open <strong>Alibaba Cloud IoT Platform<\/strong> console.<\/li>\n<li>Ensure you are in the same region chosen in Step 1.<\/li>\n<li>\n<p>Create a <strong>Product<\/strong>:\n   &#8211; Name: <code>cam-dev-product<\/code>\n   &#8211; Node type: choose the correct type for your device model (for a single camera, typically \u201cDevice\u201d; verify your design)<\/p>\n<\/li>\n<li>\n<p>Create a <strong>Device<\/strong> under that product:\n   &#8211; Device name: <code>cam-dev-001<\/code><\/p>\n<\/li>\n<li>\n<p>Record device identity parameters:\n   &#8211; DeviceName\n   &#8211; ProductKey \/ ProductId (as shown in console)\n   &#8211; DeviceSecret (if issued)\n   &#8211; Any required \u201cdevice triple\u201d values<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; A product and device entry exist in IoT Platform, ready to be associated with a Link Visual video workflow.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Device appears in IoT Platform device list.\n&#8211; You can view its credentials\/identity info.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Enable or open Link Visual in the same region<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open <strong>Link Visual<\/strong> from the Alibaba Cloud console.<\/li>\n<li>Confirm region alignment (same as IoT Platform product\/device).<\/li>\n<li>If Link Visual requires initial activation, complete the activation steps.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Link Visual is activated and you can access its main console pages.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; You can view the primary Link Visual management screen (projects\/devices\/apps\u2014exact sections vary).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Create Link Visual project\/app space (if required by your edition)<\/h3>\n\n\n\n<p>Many IoT video services use a \u201cproject\u201d or \u201capplication space\u201d concept to isolate environments\/tenants.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p>In Link Visual console, create a logical container:\n   &#8211; Name: <code>lv-dev<\/code>\n   &#8211; Description: \u201cLink Visual dev environment\u201d<\/p>\n<\/li>\n<li>\n<p>If the console asks for storage settings (for example, OSS bucket selection) or recording policy defaults:\n   &#8211; Choose the lowest-cost option\n   &#8211; Prefer \u201cno recording\u201d for this lab unless you explicitly need playback testing\n   &#8211; If OSS is required, ensure the bucket is in the same region<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; A dev project exists in Link Visual.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; The project appears in Link Visual console list and shows as \u201cactive\/created\u201d.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Associate the IoT device with Link Visual (binding\/registration)<\/h3>\n\n\n\n<p>The binding method depends on how Link Visual integrates with IoT Platform in your region\/edition.<\/p>\n\n\n\n<p>Common patterns (you may see one of these in console):\n&#8211; Select IoT Platform product\/device from a dropdown and \u201cenable video capability\u201d\n&#8211; Register a video device in Link Visual and map it to IoT Platform identifiers\n&#8211; Create a \u201cchannel\u201d or \u201cdevice entry\u201d in Link Visual and attach device credentials<\/p>\n\n\n\n<p>Proceed with the method supported by your console:\n1. Locate device association\/binding page in Link Visual.\n2. Associate <code>cam-dev-001<\/code> with <code>lv-dev<\/code>.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Link Visual shows the device (or a device placeholder) under the dev project.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Device list in Link Visual includes <code>cam-dev-001<\/code> (or mapped identifier).\n&#8211; Status may show \u201coffline\u201d because there is no physical camera connected; that is acceptable for this lab.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 7: (Optional but recommended) Prepare app-side access model<\/h3>\n\n\n\n<p>If Link Visual provides an \u201capplication\u201d concept (AppKey\/AppSecret or similar), create a dev app credential set <strong>for server-side use only<\/strong>.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Create an app credential in Link Visual for <code>lv-dev<\/code>.<\/li>\n<li>Store the credentials in a secure location:\n   &#8211; For labs: local password manager\n   &#8211; For production: Secrets Manager \/ KMS-encrypted secrets<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have app credentials ready for backend integration.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Credential exists in Link Visual console.\n&#8211; You can rotate\/revoke it (confirm lifecycle controls exist).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 8: Validate using OpenAPI Explorer (API discovery + permissions)<\/h3>\n\n\n\n<p>This step validates that your RAM identity can reach Link Visual APIs without you needing to guess the API names.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to <strong>OpenAPI Explorer<\/strong>: https:\/\/api.alibabacloud.com\/<\/li>\n<li>Sign in with the RAM identity from Step 2.<\/li>\n<li>Search for the product: <strong>Link Visual<\/strong> (may appear as \u201cLinkVisual\u201d; verify).<\/li>\n<li>\n<p>Pick a <strong>read-only<\/strong> API operation (for example, \u201cList\/Describe\u201d style operations) that:\n   &#8211; Lists projects, devices, or configuration\n   &#8211; Does not create billable resources<\/p>\n<\/li>\n<li>\n<p>Click <strong>Try Now<\/strong> and run the request.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The API call succeeds and returns a response (possibly an empty list if your resource type differs).<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; No \u201cAccessDenied\u201d errors.\n&#8211; If \u201cAccessDenied\u201d occurs, update RAM policy to include the missing actions and retry.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>By the end, you should be able to confirm:\n&#8211; IoT Platform has a product and device (<code>cam-dev-product<\/code>, <code>cam-dev-001<\/code>)\n&#8211; Link Visual has a project\/container (<code>lv-dev<\/code>)\n&#8211; Link Visual has an entry mapped to your device identity (even if offline)\n&#8211; OpenAPI Explorer can successfully call at least one Link Visual read-only API using your RAM identity<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<p><strong>Problem: Can\u2019t find Link Visual in console<\/strong>\n&#8211; Confirm you are in a supported region.\n&#8211; Search \u201cLink Visual\u201d and \u201cLinkVisual\u201d in the product list.\n&#8211; Verify service availability in your account type (some services require enterprise verification in some regions\u2014verify).<\/p>\n\n\n\n<p><strong>Problem: AccessDenied in OpenAPI Explorer<\/strong>\n&#8211; Your RAM policy is missing Link Visual permissions.\n&#8211; Add read-only actions first; avoid wildcard permissions.\n&#8211; Confirm you are using the correct RAM role\/user and region.<\/p>\n\n\n\n<p><strong>Problem: Device doesn\u2019t appear in Link Visual<\/strong>\n&#8211; Confirm region alignment with IoT Platform.\n&#8211; Verify whether Link Visual expects devices to be created directly in Link Visual vs imported from IoT Platform.\n&#8211; Check whether a \u201cvideo capability\u201d toggle is required on the IoT product.<\/p>\n\n\n\n<p><strong>Problem: Unexpected charges<\/strong>\n&#8211; Disable recording and snapshots by default for the lab.\n&#8211; Delete unused OSS buckets or lifecycle policies.\n&#8211; Confirm you did not enable continuous recording or high retention plans.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing costs:\n1. In Link Visual:\n   &#8211; Delete <code>lv-dev<\/code> project\/container (and any associated app credentials).\n   &#8211; Remove any device\/channel associations created for the lab.<\/p>\n\n\n\n<ol class=\"wp-block-list\" start=\"2\">\n<li>\n<p>In IoT Platform:\n   &#8211; Delete device <code>cam-dev-001<\/code>\n   &#8211; Delete product <code>cam-dev-product<\/code> (only if not used elsewhere)<\/p>\n<\/li>\n<li>\n<p>In OSS (if created\/used):\n   &#8211; Empty and delete any lab buckets (ensure no compliance retention policies block deletion)<\/p>\n<\/li>\n<li>\n<p>In RAM:\n   &#8211; Remove temporary lab permissions or delete lab RAM users\/roles if not needed<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Keep device identity, Link Visual resources, and storage <strong>in the same region<\/strong> unless you have a validated cross-region design.<\/li>\n<li>Separate concerns:<\/li>\n<li>IoT Platform for device identity\/messaging<\/li>\n<li>Link Visual for video access<\/li>\n<li>OSS for storage lifecycle and retention (if used)<\/li>\n<li>Prefer event-driven designs:<\/li>\n<li>Use events to trigger recording or processing rather than continuous streaming for every device.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>RAM roles<\/strong> with least privilege.<\/li>\n<li>Separate roles:<\/li>\n<li><strong>Admin<\/strong> (console + provisioning)<\/li>\n<li><strong>Automation<\/strong> (CI\/CD)<\/li>\n<li><strong>App backend runtime<\/strong> (only required data-plane calls)<\/li>\n<li>Never embed long-lived secrets in mobile apps. Use a backend to mint time-bound access.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat video retention as a product feature with a budget:<\/li>\n<li>set default retention conservatively<\/li>\n<li>offer tiers (7\/30\/90 days) if you are a SaaS<\/li>\n<li>Reduce bandwidth:<\/li>\n<li>lower default stream bitrate\/resolution where acceptable<\/li>\n<li>limit live view concurrency per user\/account (quota or business rules)<\/li>\n<li>Use OSS lifecycle policies (if OSS is used) for aging recordings.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Choose region close to device deployment.<\/li>\n<li>Validate stream startup time and playback seek latency with realistic networks (4G\/5G, congested Wi-Fi).<\/li>\n<li>Implement retries and circuit breakers in your backend when calling Link Visual APIs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build \u201cdegraded mode\u201d UX:<\/li>\n<li>show last snapshot if live view fails<\/li>\n<li>provide device offline status and troubleshooting tips<\/li>\n<li>Maintain device firmware update plans (often managed via IoT Platform OTA) to fix streaming bugs quickly.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Centralize logs:<\/li>\n<li>app backend request logs (including correlation IDs)<\/li>\n<li>device-side connectivity logs<\/li>\n<li>Monitor:<\/li>\n<li>error rates by API<\/li>\n<li>top devices by traffic<\/li>\n<li>device online\/offline trends<\/li>\n<li>Run regular access reviews and rotate app credentials.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Naming:<\/li>\n<li>include env (<code>dev\/test\/prod<\/code>) and region in names<\/li>\n<li>Tagging (where supported):<\/li>\n<li><code>env=dev<\/code><\/li>\n<li><code>cost-center=iot-video<\/code><\/li>\n<li><code>owner=team-name<\/code><\/li>\n<li>Maintain a runbook:<\/li>\n<li>device onboarding checklist<\/li>\n<li>incident response playbooks (stream outage, storage growth, auth failures)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<p>Plan for four distinct identities:\n1. <strong>Alibaba Cloud admins<\/strong> (RAM users\/roles)\n2. <strong>Automation<\/strong> (CI\/CD)\n3. <strong>Devices<\/strong> (per-device credentials)\n4. <strong>End users<\/strong> (your product\u2019s users)<\/p>\n\n\n\n<p>Recommended control:\n&#8211; Admins manage configuration; apps should not have admin permission.\n&#8211; Backend services should use RAM roles (or secure credentials) and only the minimum API actions required.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>In transit:<\/strong> ensure TLS is used for API calls and device connectivity (verify Link Visual device transport requirements).<\/li>\n<li><strong>At rest:<\/strong> ensure recordings\/snapshots are stored with encryption at rest:<\/li>\n<li>OSS server-side encryption if OSS is used<\/li>\n<li>KMS-managed keys where required by policy<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Assume devices connect over the internet unless private connectivity is supported and enabled.<\/li>\n<li>Use outbound-only firewall rules from device networks when possible.<\/li>\n<li>Consider IP allowlists for administrative consoles where feasible (enterprise networks).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Store app credentials in:<\/li>\n<li>Alibaba Cloud Secrets Manager (preferred) or KMS-encrypted secrets<\/li>\n<li>Rotate keys on a schedule and on incident.<\/li>\n<li>Do not log secrets or signed URLs\/tokens in plaintext logs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enable <strong>ActionTrail<\/strong> for account activity and configuration changes.<\/li>\n<li>Centralize logs (SLS) and keep retention aligned with incident investigation needs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<p>IoT video often involves personal data. Before production:\n&#8211; Confirm data residency requirements (region selection).\n&#8211; Implement consent and access policies.\n&#8211; Document retention, deletion, and user data export workflows.\n&#8211; Ensure least privilege and auditability for staff access.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Putting master credentials in mobile apps<\/li>\n<li>Overly broad RAM policies (wildcards)<\/li>\n<li>No audit trail for who accessed which camera and when<\/li>\n<li>Long retention by default without policy review<\/li>\n<li>Using one shared credential for all tenants\/customers<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use a backend to mediate access and issue time-bound grants.<\/li>\n<li>Enforce per-tenant isolation (projects\/accounts) based on risk profile.<\/li>\n<li>Regularly run IAM access advisor reviews and security posture checks.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<p>Because service limits can change, <strong>verify in official docs<\/strong>. Common \u201cgotchas\u201d for IoT video designs include:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Known limitations (typical categories)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Region availability<\/strong>: not all regions support Link Visual.<\/li>\n<li><strong>Protocol\/device compatibility<\/strong>: only specific device integration methods are supported.<\/li>\n<li><strong>Concurrency quotas<\/strong>: concurrent live view sessions can be limited.<\/li>\n<li><strong>API throttling<\/strong>: control-plane calls may be rate limited.<\/li>\n<li><strong>Retention constraints<\/strong>: some recording features may require specific plans or storage configuration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing surprises<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>High egress\/traffic costs due to:<\/li>\n<li>continuous live view usage<\/li>\n<li>high-resolution streams<\/li>\n<li>repeated playback downloads<\/li>\n<li>Storage growth due to:<\/li>\n<li>long retention policies<\/li>\n<li>continuous recording<\/li>\n<li>frequent snapshots<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compatibility issues<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Firmware time drift can break event-to-playback alignment.<\/li>\n<li>NAT\/firewall behavior at edge sites can impact stream stability.<\/li>\n<li>Mobile network changes cause frequent reconnects; design robust session handling.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational gotchas<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cOffline device\u201d may be caused by:<\/li>\n<li>expired credentials<\/li>\n<li>wrong region endpoints<\/li>\n<li>clock skew<\/li>\n<li>firewall blocks<\/li>\n<li>Access failures often trace back to:<\/li>\n<li>RAM permission gaps<\/li>\n<li>app credential rotation not applied everywhere<\/li>\n<li>incorrect tenant-to-device authorization logic in your backend<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Migration challenges<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migrating from SD-card-only devices to cloud recording changes:<\/li>\n<li>privacy policy requirements<\/li>\n<li>storage cost model<\/li>\n<li>customer expectations for playback reliability<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Vendor-specific nuances<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Alibaba Cloud console flows can be region\/edition dependent.<\/li>\n<li>Some settings may exist in IoT Platform vs Link Visual depending on integration model. Validate your chosen authoritative source for each configuration.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Within Alibaba Cloud<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>IoT Platform (without Link Visual):<\/strong> great for telemetry, device messaging, and fleet management, but not sufficient alone for full video workflows.<\/li>\n<li><strong>Alibaba Cloud video streaming services (ApsaraVideo Live \/ VOD, etc.):<\/strong> often better for media broadcasting and content workflows, but may not provide IoT-device-centric access controls and device binding models.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Other clouds<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>AWS Kinesis Video Streams:<\/strong> managed ingestion, storage, and playback for video streams; strong SDK ecosystem; different IoT integration model.<\/li>\n<li><strong>Azure IoT + media components:<\/strong> can be built using IoT Hub and media services patterns; more \u201cassemble the pieces\u201d approach.<\/li>\n<li><strong>Google Cloud:<\/strong> typically more DIY (Pub\/Sub + storage + player pipelines), unless using partner solutions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Open-source \/ self-managed<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>RTSP\/ONVIF + self-hosted NVR<\/strong> (e.g., Shinobi, ZoneMinder): high control, but operational burden, scaling, and security become your responsibility.<\/li>\n<li><strong>WebRTC gateways<\/strong>: low-latency live view, but complex and requires significant ops\/security work.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Comparison table<\/h4>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Alibaba Cloud Link Visual<\/strong><\/td>\n<td>IoT products with camera devices on Alibaba Cloud<\/td>\n<td>IoT-oriented video access patterns; integrates with Alibaba Cloud IoT ecosystem<\/td>\n<td>Region\/edition constraints; device compatibility requirements<\/td>\n<td>You want Alibaba Cloud-native IoT + video workflow with managed control plane<\/td>\n<\/tr>\n<tr>\n<td>Alibaba Cloud IoT Platform only<\/td>\n<td>Non-video IoT or minimal media needs<\/td>\n<td>Mature device identity\/messaging<\/td>\n<td>No full video access layer<\/td>\n<td>You only need telemetry\/events, not video streaming\/playback<\/td>\n<\/tr>\n<tr>\n<td>Alibaba Cloud video streaming services<\/td>\n<td>Content\/live broadcasting workflows<\/td>\n<td>Media-focused features, distribution patterns<\/td>\n<td>Not device-centric; IoT device binding may be DIY<\/td>\n<td>You are building a streaming platform rather than an IoT camera product<\/td>\n<\/tr>\n<tr>\n<td>AWS Kinesis Video Streams<\/td>\n<td>IoT video on AWS<\/td>\n<td>Strong APIs and tooling for video streams<\/td>\n<td>Different ecosystem; may require more custom IoT glue<\/td>\n<td>Your stack is standardized on AWS<\/td>\n<\/tr>\n<tr>\n<td>Self-managed NVR\/RTSP<\/td>\n<td>Small deployments, high control<\/td>\n<td>Full control, no vendor lock-in<\/td>\n<td>Ops burden, scaling, security hard<\/td>\n<td>Single site\/small scale or strict on-prem requirements<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example: Multi-site retail operations with centralized incident review<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A retailer has 1,000+ stores and wants centralized visibility for incidents and audits. They need controlled staff access and retention policies.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>Cameras onboarded through IoT Platform identities<\/li>\n<li>Link Visual for live view + playback access patterns<\/li>\n<li>OSS for recordings with lifecycle rules (hot \u2192 colder tiers if supported)<\/li>\n<li>Event pipeline: device events \u2192 EventBridge\/MNS \u2192 Function Compute<\/li>\n<li>SLS dashboards for stream errors and event volume<\/li>\n<li>ActionTrail for audit of admin actions<\/li>\n<li><strong>Why Link Visual was chosen:<\/strong><\/li>\n<li>Fits an IoT camera fleet model<\/li>\n<li>Centralizes authorization and reduces custom backend complexity<\/li>\n<li>Integrates cleanly with Alibaba Cloud governance stack<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Reduced incident response time<\/li>\n<li>Lower engineering effort compared to building a custom video access layer<\/li>\n<li>Better auditability for compliance and internal controls<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: Smart doorbell MVP<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A startup needs an MVP for doorbell live view, event notifications, and short playback clips, with minimal platform engineering.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>IoT Platform for device onboarding (\u201cdevice triple\u201d identity)<\/li>\n<li>Link Visual for live view and event-driven recording references<\/li>\n<li>Serverless backend (Function Compute) for notification workflow<\/li>\n<li>OSS for storing short event clips and thumbnails (if required)<\/li>\n<li><strong>Why Link Visual was chosen:<\/strong><\/li>\n<li>Accelerates delivery of core doorbell video features<\/li>\n<li>Avoids building custom streaming session authorization<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>MVP in weeks rather than months<\/li>\n<li>Clear cost model tied to events, retention, and usage<\/li>\n<li>Ability to scale devices without rewriting core access logic<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Is Link Visual the same as a general live streaming service?<\/strong><br\/>\n   No. Link Visual is typically designed around <strong>IoT video devices<\/strong> and controlled access patterns. For creator\/content live streaming, consider Alibaba Cloud\u2019s media streaming products instead.<\/p>\n<\/li>\n<li>\n<p><strong>Do I need IoT Platform to use Link Visual?<\/strong><br\/>\n   Many architectures use IoT Platform for device identity and fleet management, but the exact dependency can vary by edition\/region. <strong>Verify in official docs<\/strong> for your integration path.<\/p>\n<\/li>\n<li>\n<p><strong>Can I use Link Visual without a physical camera?<\/strong><br\/>\n   You can set up projects, IAM, and API access without a camera. Live view\/playback validation requires a compatible device or emulator that supports the Link Visual device integration method.<\/p>\n<\/li>\n<li>\n<p><strong>How do end users securely access live view?<\/strong><br\/>\n   A best practice is to have your backend authorize the user and then request time-bound access to live view from Link Visual (token\/session approach). The exact API flow depends on Link Visual\u2019s auth model\u2014<strong>verify in docs<\/strong>.<\/p>\n<\/li>\n<li>\n<p><strong>Where are recordings stored?<\/strong><br\/>\n   This depends on your configuration and the Link Visual offering in your region. It may use service-managed storage or integrate with OSS. <strong>Verify storage options<\/strong> and lifecycle support.<\/p>\n<\/li>\n<li>\n<p><strong>What are the biggest cost drivers?<\/strong><br\/>\n   Bandwidth\/traffic, recording storage and retention duration, and high concurrency are the usual top drivers.<\/p>\n<\/li>\n<li>\n<p><strong>How do I control retention (7\/30\/90 days)?<\/strong><br\/>\n   Use Link Visual recording policy settings and\/or OSS lifecycle rules if recordings are stored in OSS. Validate what controls are available in your region.<\/p>\n<\/li>\n<li>\n<p><strong>Can I isolate customers\/tenants?<\/strong><br\/>\n   Common approaches include per-tenant projects, per-tenant credentials, or even separate Alibaba Cloud accounts for strict isolation. Choose based on threat model and compliance needs.<\/p>\n<\/li>\n<li>\n<p><strong>Does Link Visual support private networking (VPC endpoints)?<\/strong><br\/>\n   Possibly region\/edition dependent. <strong>Verify in official docs<\/strong> and plan for public endpoint connectivity by default.<\/p>\n<\/li>\n<li>\n<p><strong>How do I audit who accessed which camera?<\/strong><br\/>\n   Use a combination of:\n   &#8211; application logs (user identity mapped to access request)\n   &#8211; ActionTrail (admin\/API activity)\n   &#8211; Link Visual access logs if provided (verify)<\/p>\n<\/li>\n<li>\n<p><strong>What happens when a device is offline?<\/strong><br\/>\n   Live view won\u2019t work; playback may still work if recordings exist. Your app should show last known status and provide troubleshooting steps.<\/p>\n<\/li>\n<li>\n<p><strong>Can I use my own AI models on events?<\/strong><br\/>\n   Yes, commonly via event routing to Function Compute and calling external model endpoints. Link Visual\u2019s built-in AI (if any) is offering-dependent\u2014verify.<\/p>\n<\/li>\n<li>\n<p><strong>How do I prevent sharing of streams outside my app?<\/strong><br\/>\n   Use short-lived access, watermarking (if supported), strict user authorization, and backend mediation. Avoid long-lived public URLs.<\/p>\n<\/li>\n<li>\n<p><strong>Is Link Visual suitable for 24\/7 continuous recording for all devices?<\/strong><br\/>\n   It can be, but cost and storage can be substantial. Many teams prefer event-based recording. Validate quotas and pricing.<\/p>\n<\/li>\n<li>\n<p><strong>What\u2019s the first thing to test in a PoC?<\/strong><br\/>\n   Test:\n   &#8211; device onboarding success rate\n   &#8211; stream startup time and stability\n   &#8211; event-to-playback alignment\n   &#8211; cost model under realistic usage<\/p>\n<\/li>\n<li>\n<p><strong>Can I migrate from another cloud\/provider?<\/strong><br\/>\n   Yes, but you must address device firmware\/protocol integration differences and storage\/export formats. Plan for a phased migration.<\/p>\n<\/li>\n<li>\n<p><strong>How do I rotate app credentials safely?<\/strong><br\/>\n   Store credentials in Secrets Manager, deploy rotation with dual-key overlap, then revoke old keys. Validate Link Visual supports key rotation without downtime.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Link Visual<\/h2>\n\n\n\n<p>Because Alibaba Cloud URLs and doc structures can vary by locale and change over time, the safest approach is to start from official landing pages and search for \u201cLink Visual \/ LinkVisual\u201d.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official documentation (entry)<\/td>\n<td>Alibaba Cloud Help Center: https:\/\/www.alibabacloud.com\/help<\/td>\n<td>Starting point to find the latest Link Visual docs and region notes<\/td>\n<\/tr>\n<tr>\n<td>Official API reference<\/td>\n<td>OpenAPI Explorer: https:\/\/api.alibabacloud.com\/<\/td>\n<td>Discover and test Link Visual APIs without guessing operation names<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>Alibaba Cloud Pricing: https:\/\/www.alibabacloud.com\/pricing<\/td>\n<td>Find authoritative pricing entry points and calculators (if available)<\/td>\n<\/tr>\n<tr>\n<td>Product catalog<\/td>\n<td>Alibaba Cloud Products: https:\/\/www.alibabacloud.com\/product<\/td>\n<td>Locate the Link Visual product page, feature list, and purchase options<\/td>\n<\/tr>\n<tr>\n<td>IoT Platform docs<\/td>\n<td>Alibaba Cloud Help Center (search \u201cIoT Platform\u201d) https:\/\/www.alibabacloud.com\/help<\/td>\n<td>Link Visual is commonly used with IoT Platform; device identity concepts live there<\/td>\n<\/tr>\n<tr>\n<td>Security\/audit<\/td>\n<td>ActionTrail docs (via Help Center search) https:\/\/www.alibabacloud.com\/help<\/td>\n<td>How to audit console\/API activity for governance<\/td>\n<\/tr>\n<tr>\n<td>Storage\/lifecycle<\/td>\n<td>OSS docs (via Help Center search) https:\/\/www.alibabacloud.com\/help<\/td>\n<td>If recordings\/snapshots land in OSS, lifecycle and encryption guidance lives here<\/td>\n<\/tr>\n<tr>\n<td>Serverless event processing<\/td>\n<td>Function Compute docs (via Help Center search) https:\/\/www.alibabacloud.com\/help<\/td>\n<td>Common for event-driven processing pipelines<\/td>\n<\/tr>\n<tr>\n<td>Community learning<\/td>\n<td>Alibaba Cloud community portal: https:\/\/www.alibabacloud.com\/blog<\/td>\n<td>Use for examples and patterns; validate against official docs<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<p>The following institutes are listed as external training resources. Availability, syllabus depth, and certification alignment may change\u2014check each website.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Institute<\/th>\n<th>Suitable Audience<\/th>\n<th>Likely Learning Focus<\/th>\n<th>Mode<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps engineers, cloud engineers, architects<\/td>\n<td>Cloud + DevOps practices, automation, operations<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>Beginners to intermediate<\/td>\n<td>DevOps\/SCM fundamentals and tooling<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Cloud operations teams<\/td>\n<td>CloudOps, monitoring, operations practices<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.cloudopsnow.in\/<\/td>\n<\/tr>\n<tr>\n<td>SreSchool.com<\/td>\n<td>SREs, platform teams<\/td>\n<td>Reliability engineering, SLOs\/SLIs, incident response<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.sreschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>AiOpsSchool.com<\/td>\n<td>Ops and platform teams<\/td>\n<td>AIOps concepts, automation, observability<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<p>Listed as external trainer platforms\/sites. Verify offerings and credentials directly on the websites.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Platform\/Site<\/th>\n<th>Likely Specialization<\/th>\n<th>Suitable Audience<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>Cloud\/DevOps training (verify specific courses)<\/td>\n<td>Beginners to intermediate<\/td>\n<td>https:\/\/rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps tools and practices<\/td>\n<td>DevOps engineers<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>DevOps consulting\/training marketplace style (verify)<\/td>\n<td>Teams seeking hands-on help<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>DevOps support and training (verify)<\/td>\n<td>Ops\/DevOps practitioners<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<p>Neutral listing of consulting providers. Validate scope, references, and security posture directly with each company.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Company<\/th>\n<th>Likely Service Area<\/th>\n<th>Where They May Help<\/th>\n<th>Consulting Use Case Examples<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting (verify)<\/td>\n<td>Architecture reviews, implementation support<\/td>\n<td>IoT platform ops setup, CI\/CD hardening, monitoring rollout<\/td>\n<td>https:\/\/cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps consulting and training<\/td>\n<td>DevOps process, automation, SRE practices<\/td>\n<td>Build deployment pipelines, implement logging\/monitoring strategy<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting (verify)<\/td>\n<td>Operations maturity, security reviews<\/td>\n<td>IAM least privilege, incident response playbooks, cost governance<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before Link Visual<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>IoT fundamentals:<\/li>\n<li>device identity, provisioning, authentication<\/li>\n<li>MQTT concepts (topics, QoS) if using IoT Platform messaging<\/li>\n<li>Networking basics:<\/li>\n<li>NAT, firewall egress rules<\/li>\n<li>latency and bandwidth planning<\/li>\n<li>Security basics:<\/li>\n<li>IAM\/RAM concepts<\/li>\n<li>key management and secret storage<\/li>\n<li>Media basics (helpful):<\/li>\n<li>bitrate, resolution, GOP, latency tradeoffs<\/li>\n<li>storage retention planning<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Link Visual<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Scalable event processing:<\/li>\n<li>EventBridge\/MNS patterns<\/li>\n<li>Function Compute and idempotent handlers<\/li>\n<li>Observability:<\/li>\n<li>SLS queries, dashboards, alerting<\/li>\n<li>SLOs for stream availability and startup latency<\/li>\n<li>Data lifecycle and compliance:<\/li>\n<li>OSS lifecycle<\/li>\n<li>encryption and access logging<\/li>\n<li>privacy-by-design for video products<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>IoT Solutions Architect<\/li>\n<li>IoT\/Platform Engineer<\/li>\n<li>Backend Engineer (IoT product)<\/li>\n<li>Mobile Engineer (IoT video app integration)<\/li>\n<li>SRE \/ Operations Engineer (IoT platform)<\/li>\n<li>Security Engineer (cloud governance for IoT video)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Alibaba Cloud certification programs evolve. For Link Visual specifically, a dedicated certification may or may not exist.\n&#8211; Start with Alibaba Cloud fundamentals and IoT-related learning paths if available.\n&#8211; <strong>Verify in official Alibaba Cloud certification pages<\/strong> for current tracks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Build a \u201ccamera fleet dashboard\u201d:\n   &#8211; device list + status + last event time<\/li>\n<li>Event-driven notification pipeline:\n   &#8211; event \u2192 Function Compute \u2192 notification service<\/li>\n<li>Cost guardrails:\n   &#8211; daily traffic\/storage metrics + budget alerts<\/li>\n<li>Multi-tenant authorization model:\n   &#8211; map users \u2192 devices \u2192 access grants<\/li>\n<li>Retention compliance demo:\n   &#8211; implement lifecycle + deletion verification workflow<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>IoT (Internet of Things):<\/strong> Network of physical devices that connect to cloud services for telemetry, control, and automation.<\/li>\n<li><strong>IoT Platform:<\/strong> Alibaba Cloud service for device identity, connectivity, and messaging (often used alongside Link Visual).<\/li>\n<li><strong>Link Visual:<\/strong> Alibaba Cloud service focused on video-capable IoT device access patterns (live view\/playback\/events\u2014verify exact features).<\/li>\n<li><strong>RAM (Resource Access Management):<\/strong> Alibaba Cloud IAM service for users, roles, and permissions.<\/li>\n<li><strong>ActionTrail:<\/strong> Alibaba Cloud audit logging for API\/console actions.<\/li>\n<li><strong>OSS (Object Storage Service):<\/strong> Alibaba Cloud object storage used for durable storage and lifecycle policies.<\/li>\n<li><strong>SLS (Log Service):<\/strong> Alibaba Cloud log collection, search, dashboards, and alerting service.<\/li>\n<li><strong>Retention policy:<\/strong> How long recordings\/snapshots are stored before deletion\/archival.<\/li>\n<li><strong>Event-driven architecture:<\/strong> A design where events (motion, doorbell press) trigger processing rather than constant polling.<\/li>\n<li><strong>Least privilege:<\/strong> Security principle of granting only the minimal permissions required.<\/li>\n<li><strong>Bitrate:<\/strong> Data rate of a video stream; strong driver of bandwidth costs.<\/li>\n<li><strong>Concurrency:<\/strong> Number of simultaneous viewers\/streams; impacts quotas and cost.<\/li>\n<li><strong>Data residency:<\/strong> Legal requirement to keep data stored\/processed in specific regions\/countries.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Link Visual is an Alibaba Cloud <strong>Internet of Things<\/strong> service aimed at enabling <strong>secure, scalable video workflows for IoT devices<\/strong>, most commonly smart cameras and video sensors. It typically complements <strong>Alibaba Cloud IoT Platform<\/strong> by adding video-focused access patterns like live preview, playback, and event-driven media experiences (exact capabilities depend on region\/edition\u2014verify).<\/p>\n\n\n\n<p>For architects and operators, the most important considerations are:\n&#8211; <strong>Cost:<\/strong> bandwidth + retention\/storage dominate; optimize with event-based recording and lifecycle policies.\n&#8211; <strong>Security:<\/strong> separate admin\/app\/device\/end-user identities; use RAM least privilege; avoid long-lived secrets in clients; enable audit logging.\n&#8211; <strong>Operations:<\/strong> monitor stream success rate, device availability, and API errors; plan for offline devices and degraded UX.<\/p>\n\n\n\n<p>Use Link Visual when you need an Alibaba Cloud-native approach to IoT camera features and want managed building blocks instead of a fully custom video access platform. Next, validate your region\u2019s official documentation via the Alibaba Cloud Help Center and prototype with a small device set while measuring real bandwidth and retention costs.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Internet of Things<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,16],"tags":[],"class_list":["post-101","post","type-post","status-publish","format-standard","hentry","category-alibaba-cloud","category-internet-of-things"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/101","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=101"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/101\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=101"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=101"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=101"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}