The Image Recognition and Processing Backend demonstrates how to use AWS Step Functions to orchestrate a serverless processing workflow using AWS Lambda, Amazon S3, Amazon DynamoDB and Amazon Rekognition. This workflow processes photos uploaded to Amazon S3 and extracts metadata from the image such as geolocation, size/format, time, etc. It then uses image recognition to tag objects in the photo. In parallel, it also produces a thumbnail of the photo.
This repository contains sample code for all the Lambda functions depicted in the diagram below as well as an AWS CloudFormation template for creating the functions and related resources. There is also a test web app that you can run to interact with the backend.
- An image is uploaded to the
PhotoRepo
S3 bucket under theprivate/{userid}/uploads
prefix - The S3 upload event triggers the
S3Trigger
Lambda function, which kicks off an execution of theImageProcStateMachine
in AWS Step Functions, passing in the S3 bucket and object key as input parameters. - The
ImageProcStateMachine
has the following sub-steps:
- Read the file from S3 and extract image metadata (format, EXIF data, size, etc.)
- Based on output from previous step, validate if the file uploaded is a supported file format (png or jpg). If not, throw
NotSupportedImageType
error and end execution. - Store the extracted metadata in the
ImageMetadata
DynamoDB table - In parallel, kick off two processes simultaneously:
- Call Amazon Rekognition to detect objects in the image file. If detected, store the tags in the
ImageMetadata
DynamoDB table - Generate a thumbnail and store it under the
private/{userid}/resized
prefix in thePhotoRepo
S3 bucket
- Call Amazon Rekognition to detect objects in the image file. If detected, store the tags in the
Follow these instructions to deploy the application (both backend and frontend):
- Use 1-click deployment button above. Amplify Console will fork this repository in your GitHub account, and deploy the backend and frontend application.
- Note: If you forked and changed the repository first, you can use the Amplify console and select "Connect App" to connect to your forked repo.
- For IAM Service Role, create one if you don't have one or select an existing role. (This is required because the Amplify Console needs permissions to deploy backend resources on your behalf. More info)
- Within your new app in Amplify Console, wait for deployment to complete (this may take a while)
- Once the deployment is complete, you can test out the application!
If you want to make changes to the code locally:
- Clone the repo in your Github account that Amplify created
- In the Amplify console, choose Backend environments, and toggle "Edit backend" on the environment with categories added
- Under Edit backend, copy the
amplify pull --appId <your app id> --envName <your env name>
command displayed- If you don't see this command and instead see
amplify init --appId
, try refreshing the backend environment tab after waiting a few minutes (cloudformation could still be provisioning resources)
- If you don't see this command and instead see
- Within your forked repository locally, run the command you copied and follow the instructions
- This command synchronizes what's deployed to your local Amplify environment
- Do you want to use an AWS profile: Yes
- default
- Choose your default editor: Visutal Studio Code
- Choose the type of app that you're building: javascript
- What javascript framework are you using: react
- Source Directory Path: src/react-frontend/src
- Distribution Directory Path: src/react-frontend/build
- Build Command: npm.cmd run-script build
- Start Command: npm.cmd run-script start
- Do you plan on modifying this backend? (Yes)
If at anytime you want to change these options. Look into amplify/.config/project-config.json
and make your changes there.
You can use the test web app to upload images and explore the image recognition and processing workflow.
-
Go to the URL of the Amplify app that was deployed
-
In the login page, click on "Create account"
-
Register an account by following the sign up instructions
-
After confirming the account, sign in
-
Click into an album you created
-
You can follow the Step Functions execution link to review the details of the workflow execution Below is the diagram of the state machine being executed every time a new image is uploaded (you can explore this in the Step Functions Console):
-
When the processing finishes, the photo and extracted information is added to the display
To remove all resources created by this example, do the following:
- Go to AWS CloudFormation console, delete the 2 stacks with name "amplify-photoshare-"
- Go to the AWS Amplify console and delete the app.
This reference architecture sample is licensed under Apache 2.0.