This Guidance demonstrates how to use spatial computing to make 3D product images. A retailer or third-party can upload images to AWS, store the image, validate the image, and use AWS services to maintain metadata about that image. The services scale automatically, so retailers can quickly adapt to changes in demand.
A Lambda function validates images to meet quality standards.
To notify of process failure, Amazon Simple Notification Service (Amazon SNS) sends a short message service (SMS) and email.
Once the images are rendered, they are stored in Amazon S3.
Images are presented through Amplify.
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
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.
DynamoDB is a serverless, flexible database service designed to run high-performance applications at any scale. By deploying DynamoDB in this Guidance, you can capture image metadata and use it to select the most useful information for your business over time.
When you upload images using Transfer Family, your data is encrypted in transit through SFTP, FTPS, FTP, and Applicability Statement 2 (AS2) protocols.
We recommend using AWS Identity and Access Management (IAM) to securely manage identities and access to the AWS services. This helps you apply least privilege access so that only the permissions required to perform the task are granted.
When you have a workload with multiple redundant subsystems, you can achieve more availability than by using a single subsystem. Amazon S3, Lambda, and DynamoDB all have redundancy built in and are designed to handle concurrent device failures, providing a highly durable infrastructure.
Lambda is an event-driven serverless service that scales to match your data volume automatically. This decreases latency and improves performance, enhancing your customer's experience.
Lambda Functions are initiated as events occur, thereby saving on cost by not paying for idle compute resources. Fargate is also a serverless service to reduce on cost and operational overhead.
Serverless technologies automatically scale from zero to peak demands, so you can adapt to customer needs faster than ever while ensuring that only the minimum resources are required.
A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.
The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.
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.