Aviz ONE-Data Lake details S3 integration for ONES 2.1
Aviz's ONE-Data Lake in ONES 2.1 adds direct streaming of selected network telemetry to AWS S3, enabling centralized cloud storage and downstream analysis; this update is relevant for IT and security teams managing telemetry scale and retention.
Research Overview
ONE-Data Lake is presented as a cloud-based extension of ONES that moves on-premises (on-prem) network metrics into cloud object storage and retains the metric categories previously collected by ONES.
Technical breakdown
Integration requires creating an S3 instance in the ONES cloud configuration and supplying credentials and identifiers such as an ARN role, AWS region, bucket name, and an optional external ID for cross-account access.
The ONES interface supports management actions for the cloud instance including updating configuration details, pausing and resuming metric uploads, and deleting the integration when no longer needed.
Product update
Administrators can select which telemetry categories to stream to S3, with ONES 2.1 listing Traffic Statistics, Application-Specific Integrated Circuit (ASIC) capacity, device health, and inventory among supported metric types.
Data collection is vendor-agnostic and uses gNMI for SONiC devices and Simple Network Management Protocol (SNMP) for other network Operating System (OS) platforms, allowing multi-vendor telemetry to be consolidated in S3.
S3 analytical capabilities
Data in S3 can be queried and analyzed using AWS services: Athena for Structured Query Language (SQL) queries, Glue for Extract, Transform, Load (ETL) and data preparation, and SageMaker for model training and Machine Learning (ML) workflows.
Third-party analytics platforms and custom applications using AWS SDKs are also identified as options for processing and visualizing network telemetry stored in S3.
Operational impact
The blog notes S3 attributes relevant to cloud storage choices, including integration with AWS services, durability via replicated storage, encryption and access controls through Identity Access Management (IAM) and bucket policies, and multiple storage classes to manage costs.
It also highlights S3 features for lifecycle management, versioning, and cross-region replication that support Backup and Disaster Recovery (BDR) strategies for retained telemetry.
Enterprises can use ONES 2.1 to centralize selected network telemetry in AWS S3 while applying existing AWS analytics and data-management tooling; this “Blog Signals brief” is a fact-based summary of the vendor blog.