Let's make it happen
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.
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Step 1
Everything you need to launch this Guidance in your account is right here.
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 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.
This Guidance takes in a supplier location using GeoJSON, and processes geospatial imagery for that location to observe changes in vegetation which would be indicative of deforestation. This output is stored as both JSON and PNG files, so end users (Procurement and Sustainability teams) can interrogate the data to observe changes in vegetation with QuickSight.
This Guidance uses role-based access with AWS Identity and Access Management (IAM) and the Amazon S3 bucket has encryption enabled, is private, and blocks public access. The data catalog in AWS Glue has encryption enabled. All roles are defined with least-privilege, and all communications between services stay within the customer account. Administrators can control the notebook, and Athena and QuickSight data access through IAM roles.
AWS Glue, Amazon S3, and Athena are all serverless, and will scale data access performance as your data volume increases. Athena is serverless, so you can quickly query your data without having to set up and manage any servers or data warehouses.
By using serverless technologies, you provision only the exact resources you use. Athena automatically runs queries in parallel, so most results come back within seconds, which means Sustainability and Procurement team end users can quickly get information about supplier locations.
This Guidance uses serverless components such as AWS Glue, Amazon S3, and Athena, services that automatically scale up and down to meet demand, so you only pay for what you use.
With the exception of the SageMaker notebook (which will be set at a specific size), all other resources in this workload are serverless and scale with use, which reduces idle resources. Lifecyle configurations can be used to conclude the SageMaker notebook after inactivity.
This post demonstrates how to use SageMaker geospatial capabilities to easily baseline and monitor the vegetation type and density of areas where suppliers operate.