Name	Name	Last commit message	Last commit date
parent directory ..
images	images
src	src
test-images	test-images
README.md	README.md

Module: Coordinate a serverless image processing workflow with AWS Step Functions

In this module you'll use AWS Step Functions to build an image processing workflow by orchestrating multiple AWS Lambda functions.

The Wild Rydes team wants to add a new feature to the app by requiring riders to upload a selfie after signing up. This accomplishes a few things:

Allows the unicorns to easily identify the rider during pickup to provide a good customer experience. This also enhances security so bad guys can't spoof to be riders and get on the unicorns.
Prevents the same user from signing up for multiple accounts to abuse new-user promotions.

When users upload the photo of themselves, a few steps of verification and processing need to take place:

Verify the photo shows a clear face the app/unicorns can use to identify the rider.
Match against the collection of previously indexed faces to make sure the user hasn't already signed up.
Resize the photo to thumbnails to display on the app.
Index the user's face into the collection so it can be used for matching in the future.
Store the photo metadata with the user's profile.

In the serverless world, each of steps above can be easily implemented with a AWS Lambda function. But how can we manage the flow of invoking one Lambda function after the previous step has finished and keep track of what happened with each image? What if one of the Lambda function times out and needs to be retried? Some of the Lambda functions can be run in parallel to reduce end-to-end processing latency, how can we coordinate running Lambda functions in parallel and wait for them to finish? AWS Step Functions makes it very easy to solve these problems and provides an audit trail and visualization to track what happened with each flow.

Architecture Overview

The architecture for this module is composed of several AWS Lambda functions that leverage the facial detection capabilities of Amazon Rekognition, resize the uploaded image stored in Amazon S3, and save the image metadata with the user profile using Amazon DynamoDB. The orchestration of these Lambda functions is managed by an AWS Step Functions state machine.

Below is the flow diagram of the workflow we will build as visualized by AWS Step Functions:

In this module, we will manually kick-off processing workflows from the AWS Step Functions management console. In a real world application, you can configure an Amazon API Gateway that your application invokes to trigger the Step Functions state machine, or have it triggered by an Amazon S3 upload event through Amazon CloudWatch Events or S3 event notifications.

Implementation Instructions

Each of the following sections provide an implementation overview and detailed, step-by-step instructions. The overview should provide enough context for you to complete the implementation if you're already familiar with the AWS Management Console or you want to explore the services yourself without following a walkthrough.

If you're using the latest version of the Chrome, Firefox, or Safari web browsers the step-by-step instructions won't be visible until you expand the section.

1. Create a collection in Amazon Rekognition

A Face Collection is a container in Amazon Rekognition to store indexed face images as searchable vectors.

Using the AWS Command Line Interface, create a collection in the Amazon Rekognition called rider-photos

Step-by-step instructions (expand for details)

In a terminal window, run the following command and replace the REPLACE_WITH_YOUR_CHOSEN_AWS_REGION portion with the region string of your chosen region. (see Rekognition regions)

 aws rekognition create-collection --region REPLACE_WITH_YOUR_CHOSEN_AWS_REGION --collection-id rider-photos

For example:

 aws rekognition create-collection --region us-east-1 --collection-id rider-photos
 aws rekognition create-collection --region us-west-2 --collection-id rider-photos
 aws rekognition create-collection --region eu-west-1 --collection-id rider-photos

If successful, you should get an acknowledgment from the service that looks like:

{
	"CollectionArn": "aws:rekognition:us-west-2:012345678912:collection/rider-photos",
	"StatusCode": 200
}

2. Deploy Amazon S3, AWS Lambda and Amazon DynamoDB resources using AWS CloudFormation

The following AWS CloudFormation template will create these resources:

Two Amazon S3 buckets:
- RiderPhotoS3Bucket stores the photos uploaded by the riders
- A few test images will be copied into the RiderPhotoS3Bucket bucket
- ThumbnailS3Bucket stores the resized thumbnails of the rider photos
One Amazon DynamoDB table RiderPhotoDDBTable that stores the metadata of the rider's photo with rider's profile
AWS Lambda functions that performs the processing steps
IAM role StateMachineRole that gives the Step Functions state machine to invoke lambda functions

Click on the link for the region you have chosen:

Region	Code	Launch
US East (Ohio)	us-east-2
US East (N. Virginia)	us-east-1
US West (Oregon)	us-west-2
EU (Ireland)	eu-west-1
Asia Pacific (Mumbai)	ap-south-1
Asia Pacific (Seoul)	ap-northeast-2
Asia Pacific (Tokyo)	ap-northeast-1
Asia Pacific (Sydney)	ap-southeast-2

AWS CloudFormation Launch Instructions (expand for details)

Click the Launch Stack link above for the region of your choice.
Click Next on the Select Template page.
On the Specify Details page, leave all the defaults and click Next.
On the Options page, leave all the defaults and click Next.
On the Review page, Click the checkboxes to give AWS CloudFormation permission to "create IAM resources" and "create IAM resources with custom names"
Click "Create Change Set" in the Transforms section
Click "Execute"
Wait for the wildrydes-step-module-resources stack to reach a status of CREATE_COMPLETE.
With the wildrydes-step-module-resources stack selected, click on the Outputs tab. These resources will be referenced in the later steps.

You may copy & paste the contents of the Outputs tab of the CloudFormation stack to a separate text editor for ease of access later.

3. Create an initial AWS Step Functions state machine

After the riders upload their photo, the first thing we need do in our processing pipeline is to run a face detection algorithm on it to verify that it has a recognizable face in the photo (zero or multiple faces in the photo doesn't help unicorns recognize the rider) and the face is not wearing sunglasses (makes it harder to identify the rider). If these validations fail, notify the user and end the workflow.

The AWS Lambda function that implements this check by leveraging the Amazon Rekognition deep-learning based image analysis API is already deployed by AWS CloudFormation in the previous step. Look in the Outputs section for FaceDetectionFunctionArn for the ARN of the Lambda function.

The AWS Lambda function to be called when the validations fail is the NotificationPlaceholderFunction deployed by AWS CloudFormation. The intent behind this step is to notify the user the photo validation failed and the error reason, so they can try upload a different photo. It's currently a stub implementation that just prepares the message instead of actually sending the message.

Now you can create an AWS Step Functions state machine with the initial face detection step.

Step-by-step instructions (expand for details)

AWS Step Functions state machine flows are defined by a JSON document. In your favorite text editor, create a file called rider-photo-state-machine.json.
Copy and paste the following into your JSON file:
```
{
  "Comment": "Rider photo processing workflow",
  "StartAt": "FaceDetection",
  "States": {
    "FaceDetection": {
      "Type": "Task",
      "Resource": "REPLACE_WITH_FaceDetectionFunctionArn",
      "ResultPath": "$.detectedFaceDetails",
      "End": true,
      "Catch": [
        {
          "ErrorEquals": [
            "PhotoDoesNotMeetRequirementError"
          ],
          "ResultPath": "$.errorInfo",
          "Next": "PhotoDoesNotMeetRequirement"
        }
      ]
    },
    "PhotoDoesNotMeetRequirement": {
      "Type": "Task",
      "Resource": "REPLACE_WITH_NotificationPlaceholderFunctionArn",
      "End": true
    }
  }
}
```
The above JSON defines a state machine using the Amazon States Language. Take a moment to understand its structure.

When this state machine is launched, the AWS Step Functions interpreter begins execution by identifying the Start State. It executes that state, and then checks to see if the state is marked as an End State. If it is, the machine terminates and returns a result. If the state is not an End State, the interpreter looks for a “Next” field to determine what state to run next; it repeats this process until it reaches a Terminal State (Succeed, Fail, or an End State) or a runtime error occurs.

The ResultPath parameter in the FaceDetection state causes the output of the state to be the union of the original input passed to the state and an additional detectedFaceDetails field that holds the output from the AWS Lambda function.

The Catch parameter in the FaceDetection state can match custom error types thrown by the AWS Lambda function and change the flow of the execution based on the error type caught.
Replace the REPLACE_WITH_FaceDetectionFunctionArn in the JSON with the ARN of the face detection AWS Lambda function.

To find the ARN of the face detection AWS Lambda function, in the AWS CloudFormation Console, go to the wildrydes-step-module-resources stack, look in the Outputs section for FaceDetectionFunctionArn)
Replace the REPLACE_WITH_NotificationPlaceholderFunctionArn in the JSON with the ARN of the AWS Lambda function that mocks sending user notifications.

To find the ARN of the mock notification AWS Lambda function, in the AWS CloudFormation Console, go to the wildrydes-step-module-resources stack, look in the Outputs section for NotificationPlaceholderFunctionArn)
From the AWS Management Console, choose Services then select Step Functions.
You might see the Get Started page if you have not used AWS Step Functions before. If that's the case, click Get Started, it should lead you to the page to create a new state machine. Otherwise, click the Create a State Machine button.
Type RiderPhotoProcessing for the state machine name.
For IAM role for your state machine executions, pick I will use an existing role, and select the IAM role created by the CloudFormation in the previous step.

The name of the IAM role should have the prefix wildrydes-step-modules-resources (the name of the CloudFormation stack) To verify the IAM role's full name, you can open a new tab for the CloudFormation console and check the Output section of the stack you just created, and look for StateMachineRole.
Paste in the JSON from your rider-photo-state-machine.json file into the Code editor portion.
You can click on the ↺ sign next to Preview to visualize the workflow:
Click Create State Machine to create the state machine.
Click the New execution button to start a new execution.
Here you specify the input data passed into the AWS Step Functions state machine to process.

Each execution of a Step Functions state machine has an unique ID. You can either specify one when starting the execution, or have the service generate one for you. In the text field that says "enter your execution id here", you can specify an execution ID, or leave it blank.

For the input data, type in the follow JSON. Make sure to substitute the s3Bucket field with your own values.

For s3Bucket field, look in the Outputs section of the wildrydes-step-module-resources stack for RiderPhotoS3Bucket.

The userId field is needed because in later processing steps, the userId is used to record which user the profile picture is associated with.
```
{
  "userId": "user_a", 
  "s3Bucket": "REPLACE_WITH_YOUR_BUCKET_NAME",
  "s3Key": "1_happy_face.jpg"
} 
```
this tells the image processing workflow the userId that uploaded the picture and the Amazon S3 bucket and keys the photo is at.
You can now see the state machine execution in action. Explore the different tabs in the Console to see what information is available to you for this execution:

Create another execution by passing in the s3 key of a photo that wears sunglasses, see how the execution differs:

{
  "userId": "user_b",
  "s3Bucket": "REPLACE_WITH_YOUR_BUCKET_NAME",
  "s3Key": "2_sunglass_face.jpg"
}

4. Add steps to prevent duplication and add face to index

If the uploaded photo has passed the basic face detection checks, the next step is to ensure the face has not been stored in our collection already to prevent the same user from signing up multiple times. In this section, you will add a CheckFaceDuplicate step to your state machine by leveraging the FaceSearchFunction AWS Lambda function.

Step-by-step instructions (expand for details)

Edit your rider-photo-state-machine.json file to add a new step to the workflow.

First, add a new state CheckFaceDuplicate following the PhotoDoesNotMeetRequirement state. Then, replace the REPLACE_WITH_FaceSearchFunctionArn with the FaceSearchFunctionArn from the AWS CloudFormation output:

,
"CheckFaceDuplicate": {
  "Type": "Task",
  "Resource": "REPLACE_WITH_FaceSearchFunctionArn",
  "ResultPath": null,
  "End": true,
  "Catch": [
    {
      "ErrorEquals": [
        "FaceAlreadyExistsError"
      ],
      "ResultPath": "$.errorInfo",
      "Next": "PhotoDoesNotMeetRequirement"
    }
  ]
}

Find the line in the FaceDetection state that marks it as the End state of the state machine
```
     	 "End": true,
```
and replace it with
```
  		"Next": "CheckFaceDuplicate",
```
This tells AWS Step Functions if the FaceDetection state runs successfully, go on to run the CheckFaceDuplicate state as the next step in the process.

At this point, your rider-photo-state-machine.json file should look like this (the AWS Lambda ARNs are examples):

(expand to see)

{
  "Comment": "Rider photo processing workflow",
  "StartAt": "FaceDetection",
  "States": {
    "FaceDetection": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-FaceDetectionFunction-4AYSKX2EGPV0",
      "ResultPath": "$.detectedFaceDetails",
      "Next": "CheckFaceDuplicate",
      "Catch": [
        {
          "ErrorEquals": [
            "PhotoDoesNotMeetRequirementError"
          ],
          "ResultPath": "$.errorInfo",
          "Next": "PhotoDoesNotMeetRequirement"
        }
      ]
    },
    "PhotoDoesNotMeetRequirement": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-NotificationPlaceholderFunct-CDRLZC8BRFWP",
      "End": true
    },
    "CheckFaceDuplicate": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-FaceSearchFunction-1IT67V4J214DC",
      "ResultPath": null,
      "End": true,
      "Catch": [
        {
          "ErrorEquals": [
            "FaceAlreadyExistsError"
          ],
          "ResultPath": "$.errorInfo",
          "Next": "PhotoDoesNotMeetRequirement"
        }
      ]
    }
  }
}

Go back the AWS Step Functions Console, select the RiderPhotoProcessing state machine and click the Edit state machine button
Copy-paste the updated JSON definition into the editor, then click Update and start execution
Test the new state machine with the test input you've used before:
```
{
  "userId": "user_a",
  "s3Bucket": "REPLACE_WITH_YOUR_BUCKET_NAME",
  "s3Key": "1_happy_face.jpg"
} 
```
Because we haven't added the step yet to index the face in the photo into the Rekognition collection, the CheckFaceDuplicate step will always succeed at this point.

5. Add parallel processing step

If the uploaded photo passes both the FaceDetection and CheckFaceDuplicate stage, we can now proceed to index the rider's face and resize the photo for displaying in the app. Since these two steps don't depend on one another, they can be run in parallel. We will add a Parallel state in AWS Step Functions to run these steps.

The ARNs of the two AWS Lambda functions that performs face index and generate thumbnails can be found in the AWS CloudFormation output IndexFaceFunctionArn and ThumbnailFunctionArn respectively.

Step-by-step instructions (expand for details)

Edit your rider-photo-state-machine.json file to add a parallel step (with two sub-steps) to the workflow.

First, add a new state ParallelProcessing following the CheckFaceDuplicate state. Also make sure:

Replace the REPLACE_WITH_IndexFaceFunctionArn with the IndexFaceFunctionArn from the AWS CloudFormation output.
Replace the REPLACE_WITH_ThumbnailFunctionArn with the ThumbnailFunctionArn from the AWS CloudFormation output.

,
"ParallelProcessing": {
  "Type": "Parallel",
  "Branches": [
    {
      "StartAt": "AddFaceToIndex",
      "States": {
        "AddFaceToIndex": {
          "Type": "Task",
          "Resource": "REPLACE_WITH_IndexFaceFunctionArn",
          "End": true
        }
      }
    },
    {
      "StartAt": "Thumbnail",
      "States": {
        "Thumbnail": {
          "Type": "Task",
          "Resource": "REPLACE_WITH_ThumbnailFunctionArn",
          "End": true
        }
      }
    }
  ],
   "ResultPath": "$.parallelResult",
  "End": true
}

Find the line in the CheckFaceDuplicate state that marks it as the End state of the state machine.
```
     	 "End": true,
```
and replace it with
```
  		"Next": "ParallelProcessing",
```
This tells AWS Step Functions if the CheckFaceDuplicate state runs successfully, go on to run the ParallelProcessing state as the next step in the process.

At this point, your rider-photo-state-machine.json file should look like this (the AWS Lambda ARNs are examples):

(expand to see)

{
  "Comment": "Rider photo processing workflow",
  "StartAt": "FaceDetection",
  "States": {
    "FaceDetection": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-FaceDetectionFunction-4AYSKX2EGPV0",
      "ResultPath": "$.detectedFaceDetails",
      "Next": "CheckFaceDuplicate",
      "Catch": [
        {
          "ErrorEquals": [
            "PhotoDoesNotMeetRequirementError"
          ],
          "ResultPath": "$.errorInfo",
          "Next": "PhotoDoesNotMeetRequirement"
        }
      ]
    },
    "PhotoDoesNotMeetRequirement": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-NotificationPlaceholderFunct-CDRLZC8BRFWP",
      "End": true
    },
    "CheckFaceDuplicate": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-FaceSearchFunction-1IT67V4J214DC",
      "ResultPath": null,
      "Next": "ParallelProcessing",
      "Catch": [
        {
          "ErrorEquals": [
            "FaceAlreadyExistsError"
          ],
          "ResultPath": "$.errorInfo",
          "Next": "PhotoDoesNotMeetRequirement"
        }
      ]
    },
    "ParallelProcessing": {
      "Type": "Parallel",
      "Branches": [
        {
          "StartAt": "AddFaceToIndex",
          "States": {
            "AddFaceToIndex": {
              "Type": "Task",
              "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-IndexFaceFunction-15658V8WUI67V",
              "End": true
            }
          }
        },
        {
          "StartAt": "Thumbnail",
          "States": {
            "Thumbnail": {
              "Type": "Task",
              "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-ThumbnailFunction-A30TCJMIG0U8",
              "End": true
            }
          }
        }
      ],
      "ResultPath": "$.parallelResult",
      "End": true
    }
  }
}

Go back the AWS Step Functions Console, update the RiderPhotoProcessing statemachine by copy-pasting the updated JSON definition:

Test the new state machine with the test input you've used before:

{
  "userId": "user_a",
  "s3Bucket": "REPLACE_WITH_YOUR_BUCKET_NAME",
  "s3Key": "1_happy_face.jpg"
}

If last step succeeds, you can use the AWS CLI to check the list of faces indexed in your Rekognition collection (replace the REPLACE_WITH_YOUR_CHOSEN_AWS_REGION portion with the region string of your chosen region):
```
aws rekognition list-faces --collection-id rider-photos --region REPLACE_WITH_YOUR_CHOSEN_AWS_REGION
```
You might find the delete-faces command useful when testing:
```
aws rekognition delete-faces --collection-id rider-photos --face-ids REPLACE_WITH_ID_OF_FACE_TO_DELETE --region REPLACE_WITH_YOUR_CHOSEN_AWS_REGION
```
You can also use the Amazon S3 Console to check the Amazon S3 bucket created by AWS CloudFormation to store the resized thumbnail images. You should find resized thumbnail images in the bucket.

The name of the S3 bucket can be found in the in AWS CloudFormation output ThumbnailS3Bucket. You can also simply search for it in the S3 Console for wildrydes-step-module-resources-thumbnails3bucket
What happens if you start a new workflow with a different userId but the same s3key and s3bucket parameters?

6. Add metadata persistence step

The last step of our image processing workflow is to persist the metadata of the profile photo with the user's profile.

The ARN of the AWS Lambda function that persists the metadata can be found in the in AWS CloudFormation output PersistMetadataFunctionArn.

Step-by-step instructions (expand for details)

Edit your rider-photo-state-machine.json file to add the final persistence step.

First, add a new state PersistMetadata following the ParallelProcessing state. Also make sure:
- Replace the REPLACE_WITH_PersistMetadataFunctionArn with the PersistMetadataFunctionArn from the AWS CloudFormation output
```
    ,
    "PersistMetadata": {
      "Type": "Task",
      "Resource": "REPLACE_WITH_PersistMetadataFunctionArn",
      "ResultPath": null,
      "End": true
    }
```
Find the line in the ParallelProcessing state that marks it as the End state of the state machine.
```
     	 "End": true
```
and replace it with
```
  		"Next": "PersistMetadata"
```
Note: be careful to edit the "End" line at the ParallelProcessing level, not the individual branch level within the parallel state.

This tells AWS Step Functions if the ParallelProcessing state runs successfully, go on to run the PersistMetadata state as the next step in the process.

At this point, your rider-photo-state-machine.json file should look like this (the AWS Lambda ARNs are examples):

(expand to see)

{
  "Comment": "Rider photo processing workflow",
  "StartAt": "FaceDetection",
  "States": {
    "FaceDetection": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-FaceDetectionFunction-4AYSKX2EGPV0",
      "ResultPath": "$.detectedFaceDetails",
      "Next": "CheckFaceDuplicate",
      "Catch": [
        {
          "ErrorEquals": [
            "PhotoDoesNotMeetRequirementError"
          ],
          "ResultPath": "$.errorInfo",
          "Next": "PhotoDoesNotMeetRequirement"
        }
      ]
    },
    "PhotoDoesNotMeetRequirement": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-NotificationPlaceholderFunct-CDRLZC8BRFWP",
      "End": true
    },
    "CheckFaceDuplicate": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-FaceSearchFunction-1IT67V4J214DC",
      "ResultPath": null,
      "Next": "ParallelProcessing",
      "Catch": [
        {
          "ErrorEquals": [
            "FaceAlreadyExistsError"
          ],
          "ResultPath": "$.errorInfo",
          "Next": "PhotoDoesNotMeetRequirement"
        }
      ]
    },
    "ParallelProcessing": {
      "Type": "Parallel",
      "Branches": [
        {
          "StartAt": "AddFaceToIndex",
          "States": {
            "AddFaceToIndex": {
              "Type": "Task",
              "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-IndexFaceFunction-15658V8WUI67V",
              "End": true
            }
          }
        },
        {
          "StartAt": "Thumbnail",
          "States": {
            "Thumbnail": {
              "Type": "Task",
              "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-ThumbnailFunction-A30TCJMIG0U8",
              "End": true
            }
          }
        }
      ],
      "ResultPath": "$.parallelResult",
      "Next": "PersistMetadata"
    },
    "PersistMetadata": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:us-west-2:012345678912:function:wild-ryde-step-module-PersistMetadataFunction-9PDCT2DT7K70",
      "ResultPath": null,
      "End": true
    }
  }
}

Go back the AWS Step Functions Console, update the state machine by copy-pasting the updated JSON definition:
Test the new state machine with test input:
```
{
  "userId": "user_a",
  "s3Bucket": "REPLACE_WITH_YOUR_BUCKET_NAME",
  "s3Key": "1_happy_face.jpg"
} 
```
If you reference an image that's already indexed when you were testing the previous state machine, the execution would fail the CheckFaceDuplicate step like this:

You can use the aws rekognition list-faces and aws rekognition delete-faces commands to clean up the previous indexed faces during testing. Or you can upload a different picture to the RiderPhotoS3Bucket and use the s3 key of the new picture to test.

Implementation Validation

Test the final state machine (RiderPhotoProcessing-4) with different test images provided

Photo with sunglasses:

{
  "userId": "user_b",
  "s3Bucket": "REPLACE_WITH_YOUR_BUCKET_NAME",
  "s3Key": "2_sunglass_face.jpg"
}

Photo with multiple faces in it:

{
  "userId": "user_c",
  "s3Bucket": "REPLACE_WITH_YOUR_BUCKET_NAME",
  "s3Key": "3_multiple_faces.jpg"
}

Photo with no faces in it:

{
  "userId": "user_d",
  "s3Bucket": "REPLACE_WITH_YOUR_BUCKET_NAME",
  "s3Key": "4_no_face.jpg"
}

Upload some pictures you have to S3, test some executions. If you have more than one picture of the same person, upload them both and run the workflow on each picture (make sure to use different userId fields in the test input). Verify the CheckFaceDuplicate step will prevent the same face from being indexed more than once.
Go to the Amazon DynamoDB console, look for a table with name starting with "wildrydes-step-module-resources-RiderPhotoDDBTable" (you can also find the table name in the CloudFormation stack output). Check out the items of the table.
Go to the Amazon S3 console, verify the thumbnail images of the photos you processed are in the thumbnail S3 Bucket.

Now you have built a multi-step image processing workflow using AWS Step Functions! The workflow can be integrated to your app by fronting it with AWS API Gateway or triggered from an Amazon S3 upload event.

Extra credit

The intent of the PhotoDoesNotMeetRequirement step is to send notification to the user that the verification of their profile photo failed so they might try uploading a different picture. It currently uses the AWS Lambda function NotificationPlaceholderFunction which simply returns the message instead of actually sending the notification. Implement sending email notifications in the Lambda function using Amazon Simple Email Service (SES).

Clean-up

Delete the RiderPhotoProcessing state machine from the AWS Step Functions console.
Delete the wildrydes-step-module-resources AWS CloudFormation stack that launched the AWS Lambda functions, Amazon S3 buckets and Amazon DynamoDB table.
Step-by-step instructions (expand for details)
1. In the AWS CloudFormation Management Console, select the wildrydes-step-module-resources stack.
2. Select Delete Stack under Actions.
3. Click Yes, Delete

Delete the Amazon Rekognition collection.

Step-by-step instructions (expand for details)

In a terminal window, run the following command and replace the REPLACE_WITH_YOUR_CHOSEN_AWS_REGION portion with the AWS region you have used.

 aws rekognition delete-collection --region REPLACE_WITH_YOUR_CHOSEN_AWS_REGION --collection-id rider-photos

For example:

 aws rekognition delete-collection --region us-east-1 --collection-id rider-photos
 aws rekognition delete-collection --region us-west-2 --collection-id rider-photos
 aws rekognition delete-collection --region eu-west-1 --collection-id rider-photos

If successful, you should get an acknowledgment from the service that looks like:
```
{
	"StatusCode": 200
}
```

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ImageProcessing

ImageProcessing

README.md

Module: Coordinate a serverless image processing workflow with AWS Step Functions

Architecture Overview

Implementation Instructions

1. Create a collection in Amazon Rekognition

2. Deploy Amazon S3, AWS Lambda and Amazon DynamoDB resources using AWS CloudFormation

3. Create an initial AWS Step Functions state machine

4. Add steps to prevent duplication and add face to index

5. Add parallel processing step

6. Add metadata persistence step

Implementation Validation

Extra credit

Clean-up

Files

ImageProcessing

Directory actions

More options

Directory actions

More options

Latest commit

History

ImageProcessing

Folders and files

parent directory

README.md

Module: Coordinate a serverless image processing workflow with AWS Step Functions

Architecture Overview

Implementation Instructions

1. Create a collection in Amazon Rekognition

2. Deploy Amazon S3, AWS Lambda and Amazon DynamoDB resources using AWS CloudFormation

3. Create an initial AWS Step Functions state machine

4. Add steps to prevent duplication and add face to index

5. Add parallel processing step

6. Add metadata persistence step

Implementation Validation

Extra credit

Clean-up