I am trying to build a architecture for custom anomaly ai on AWS for my startup. Please let me know if my way of thinking is correct or not 1. Data Ingestion: Ingesting the data into AWS S3 in JSON format 2. Data Preprocessing: Converting JSON format to Excel format using AWS Glue and storing it back into S3 3. ML : Using AWS Sagemaker to learn from the Excel format created 4. Quicksight to show the data for data visualization is my way of thinking correct here?

Architecture review for Custom Anomaly AI

I am trying to build a architecture for custom anomaly ai on AWS for my startup. Please let me know if my way of thinking is correct or not

Data Ingestion: Ingesting the data into AWS S3 in JSON format
Data Preprocessing: Converting JSON format to Excel format using AWS Glue and storing it back into S3
ML : Using AWS Sagemaker to learn from the Excel format created
Quicksight to show the data for data visualization

is my way of thinking correct here?

Antonio_Lagrotteria 전문가
일 년 전
May I ask why converting json to excel?
himanshustallongmailcom
일 년 전
it is just my way of thinking. I am open ears to learn in case you have any other idea. But I want to implement Custom Anomaly AI detection.

주제

스토리지 기계 학습 및 AI 분석

태그

아마존 심플 스토리지 서비스 ML 모델 구축 및 학습 아마존 QuickSight AWS Glue 아마존 세이지메이커 및 쿠버네티스를 사용한 ML Ops

언어

English

himanshustallongmailcom

질문됨 일 년 전265회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

이 답변이 도움이 되었나요?커뮤니티가 여러분의 지식을 활용할 수 있도록 정답을 찬성하세요.

I don't see the point of converting to Excel if you are not going to use a spreadsheet editor to open but instead using Quicksight. Any other format like CSV will allow you better support and parallelism.

전문가

Gonzalo Herreros

답변함 일 년 전

Architecture review for Custom Anomaly AI

관련 콘텐츠