Skip to main content

AWS Solutions Library

Guidance for Visual Asset Management System on AWS

Overview

This Guidance helps you centralize and automate the process of storing, converting, optimizing, and distributing 3D and 2D assets using serverless technologies. Visual Asset Management System (VAMS) with Amazon stores and manages visual assets in the cloud, which empowers any user with a web browser to upload, manage, visualize, transform, and retrieve visual assets. Organizations that previously had to visualize, transform, interface with, and deliver these assets on local systems can now do so from a web-based cloud dashboard. The VAMS API helps you build custom applications and automation.

How it works

This architecture diagram shows the standard system architecture for a VAMS deployment. AWS Cloud Development Kit (AWS CDK) is used to deploy a React-based web app for asset management and a serverless backend for storing and processing spatial data.

Download the architecture diagram

Well-Architected Pillars

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

Amazon CloudWatch logs enable you to monitor Step Functions and Lambda as they travel through the API Gateway APIs to the underlying services. Visualizing and analyzing these components using CloudWatch helps you identify performance bottlenecks and troubleshoot requests.

Read the Operational Excellence whitepaper

Amazon Cognito user pools authenticate and authorize users in VAMS. By using Amazon Cognito user pools, admins have greater control and security over who can access which parts of VAMS.

Read the Security whitepaper

Amazon S3 and API Gateway are both fully managed services that allow VAMS to scale up or down as needed. Using loosely-coupled and microservices allow VAMS to remain working even when one component may be unavailable.

Read the Reliability whitepaper

AWS Cloud Development Kit  (AWS CDK) allows users to provision the cloud infrastructure needed to create a custom content management system (CMS). VAMS is open source and easily deployable through AWS CDK , allowing for rapid deployment, iteration, and experimentation within any new or existing AWS account.

Read the Performance Efficiency whitepaper

Amazon S3 allows youto select a retention policy for your data. Lambda is used to run code only when that code is needed, and DynamoDB is used to store asset metadata and other necessary information. Using these managed and serverless services will help ensure that users are only charged for the resources that they actually use.

Read the Cost Optimization whitepaper

SageMaker is used to create pipelines through Jupyter notebooks. When the pipeline is not in use, you are not charged for SageMaker , meaning these resources are not unnecessarily running. VAMS shuts down any notebook after 1 hour of idle time, which reduces the number of resources being used. This reduction in the number of resources minimizes the workload’s environmental impact.

Read the Sustainability whitepaper

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

Did you find what you were looking for today?

Let us know so we can improve the quality of the content on our pages