{"id":177,"date":"2020-09-02T18:25:59","date_gmt":"2020-09-02T18:25:59","guid":{"rendered":"https:\/\/machine-learning.webcloning.com\/2020\/09\/02\/getting-a-batch-job-completion-message-from-amazon-translate\/"},"modified":"2020-09-02T18:25:59","modified_gmt":"2020-09-02T18:25:59","slug":"getting-a-batch-job-completion-message-from-amazon-translate","status":"publish","type":"post","link":"https:\/\/salarydistribution.com\/machine-learning\/2020\/09\/02\/getting-a-batch-job-completion-message-from-amazon-translate\/","title":{"rendered":"Getting a batch job completion message from Amazon Translate"},"content":{"rendered":"
\n

Amazon Translate<\/a> is a neural machine translation service that delivers fast, high-quality, and affordable language translation. Neural machine translation is a form of language translation automation that uses deep learning models to deliver more accurate and natural-sounding translation than traditional statistical and rule-based translation algorithms. The translation service is trained on a wide variety of content across different use cases and domains to perform well on many kinds of content.<\/p>\n

The Amazon Translate asynchronous <\/a>batch processing<\/a> capability enables organizations to translate a large collection of text or HTML documents. They can translate the collection of documents from one language to another with just a single API call. The ability to process data at scale is becoming important to organizations across all industries. In this blog post, we are going to demonstrate how you can build a notification mechanism to message you when a batch translation job is complete. This can enable end-end automation by triggering other Lambda functions or integrate with SQS for any post processing steps.<\/p>\n

Solution overview<\/h2>\n

The following diagram illustrates the high-level architecture of the solution.<\/p>\n

\"Architecture<\/p>\n

The solution contains the following steps:<\/p>\n

    \n
  1. A user starts a batch translation job.<\/li>\n
  2. An Amazon CloudWatch Events<\/a> rule picks up the event and triggers the AWS Step Functions<\/a>\n<\/li>\n
  3. The Job Poller AWS Lambda<\/a> function polls the job status every 5 minutes.<\/li>\n
  4. When the Amazon Translate batch job is complete, an email notification is sent via an Amazon Simple Notification Service<\/a> (Amazon SNS) topic.<\/li>\n<\/ol>\n

    To implement this solution, you must create the following:<\/p>\n

      \n
    1. An SNS topic<\/li>\n
    2. An AWS Identity and Access Management<\/a> (IAM) role<\/li>\n
    3. A Lambda function<\/li>\n
    4. A Step Functions state machine<\/li>\n
    5. A CloudWatch Events rule<\/li>\n<\/ol>\n

      Creating an SNS topic<\/h2>\n

      To create an SNS topic, complete the following steps:<\/p>\n

        \n
      1. On the Amazon SNS console<\/a>, create a new topic.<\/li>\n
      2. For Topic name<\/strong>, enter a name (for example, TranslateJobNotificationTopic<\/code>).<\/li>\n
      3. Choose Create topic<\/strong>.<\/li>\n<\/ol>\n

        You can now see the TranslateJobNotificationTopic page. The Details<\/strong> section displays the topic\u2019s name, ARN, display name (optional), and the AWS account ID of the Topic owner.<\/p>\n

          \n
        1. In the Details<\/strong> section, copy the topic ARN to the clipboard (arn:aws:sns:us-east-1:123456789012<\/em>:TranslateJobNotificationTopic<\/code>).<\/li>\n
        2. On the left navigation pane, choose Subscriptions<\/strong>.<\/li>\n
        3. Choose Create subscription<\/strong>.<\/li>\n
        4. On the Create subscription<\/strong> page, enter the topic ARN of the topic you created earlier (arn:aws:sns:us-east-1:123456789012<\/em>:TranslateJobNotificationTopic<\/code>).<\/li>\n
        5. For Protocol<\/strong>, select Email<\/strong>.<\/li>\n
        6. For Endpoint<\/strong>, enter an email address that can receive notifications.<\/li>\n
        7. Choose Create subscription<\/strong>.<\/li>\n<\/ol>\n

          For email subscriptions, you have to first confirm the subscription by choosing the confirm subscription<\/strong> link in the email you received.<\/p>\n

          Creating an IAM role for the Lambda function<\/h3>\n

          To create an IAM role, complete the following steps. For more information, see Creating an IAM Role<\/a>.<\/p>\n

            \n
          1. On the IAM console<\/a>, choose Policies<\/strong>.<\/li>\n
          2. Choose Create Policy<\/strong>.<\/li>\n
          3. On the JSON<\/strong> tab, enter the following IAM policy:<\/li>\n<\/ol>\n
            {    \"Version\": \"2012-10-17\",\r\n    \"Statement\": [\r\n        {\r\n            \"Sid\": \"VisualEditor0\",\r\n            \"Effect\": \"Allow\",\r\n            \"Action\": \"translate:DescribeTextTranslationJob\",\r\n            \"Resource\": \"*\"\r\n        },\r\n        {\r\n            \"Effect\": \"Allow\",\r\n            \"Action\": [\r\n                \"logs:CreateLogGroup\",\r\n                \"logs:CreateLogStream\",\r\n                \"logs:PutLogEvents\"\r\n            ],\r\n            \"Resource\": \"arn:aws:logs:us-east-1:123456789012:log-group:\/aws\/lambda\/TranslateJobStatusPoller:*\"\r\n        }\r\n    ]\r\n}<\/code><\/pre>\n
            Update the resource property for CloudWatch Logs permission to reflect your configuration for Region, AWS account ID, and the Lambda function name.<\/p>\n
              \n
            1. Choose Review policy<\/strong>.<\/li>\n
            2. Enter a name (MyLambdaPolicy) for this policy and choose Create policy<\/strong>.<\/li>\n
            3. Record the name of this policy for later steps.<\/li>\n
            4. On the left navigation pane, choose Roles<\/strong>.<\/li>\n
            5. Choose Create role<\/strong>.<\/li>\n
            6. On the Select role type<\/strong> page, choose Lambda<\/strong> and the Lambda<\/strong> use case.<\/li>\n
            7. Choose Next: Permissions<\/strong>.<\/li>\n
            8. Filter policies by the policy name that you just created, and select the check-box.<\/li>\n
            9. Choose Next: Tags<\/strong>.<\/li>\n
            10. Add an appropriate tag.<\/li>\n
            11. Choose Next: Review<\/strong>.<\/li>\n
            12. Give this IAM role an appropriate name, and note it for future use.<\/li>\n
            13. Choose Create role<\/strong>.<\/li>\n<\/ol>\n
              Creating a Lambda function<\/h3>\n
              To create a Lambda function, complete the following steps. For more information, see Create a Lambda Function with the Console<\/a>.<\/p>\n
                \n
              1. On the Lambda console<\/a>, choose Author from scratch<\/strong>.<\/li>\n
              2. For Function Name<\/strong>, enter the name of your function (for example, TranslateJobStatusPoller<\/strong>).<\/li>\n
              3. For Runtime<\/strong>, choose Python 3.8<\/strong>.<\/li>\n
              4. For Execution role<\/strong>, select Use an existing role<\/strong>.<\/li>\n
              5. Choose the IAM role you created in the previous step.<\/li>\n
              6. Choose Create Function<\/strong>.<\/li>\n
              7. Remove the default function and enter the following code into the Function Code<\/strong> window:<\/li>\n<\/ol>\n
                # Copyright 2020 Amazon.com, Inc. or its affiliates. All Rights Reserved.\r\n# Licensed under the Apache License, Version 2.0 (the \"License\").\r\n# You may not use this file except in compliance with the License.\r\n# A copy of the License is located at## http:\/\/aws.amazon.com\/apache2.0\/\r\n# or in the \"license\" file accompanying this file.\r\n# This file is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,\r\n# either express or implied. See the License for the specific language governing permissions\r\n# and limitations under the License.\r\n# Description: This Lambda function is part of the a step function that checks the status of Amazon translate batch job. \r\n# Author: Sudhanshu Malhotra\r\nimport boto3\r\nimport logging\r\nimport os\r\n\r\nfrom botocore.exceptions import ClientError\r\n\r\nlogging.basicConfig(level=logging.DEBUG)\r\nlogger = logging.getLogger(__name__)\r\n\r\ndef msgpublish(jobid):\r\n    client = boto3.client('translate')\r\n    try:\r\n        response = client.describe_text_translation_job(JobId=jobid)\r\n        logger.debug('Job Status is: {}' .format(response['TextTranslationJobProperties']['JobStatus']))\r\n        return(response['TextTranslationJobProperties']['JobStatus'])\r\n    \r\n    except ClientError as e:\r\n        logger.error(\"An error occured: %s\" % e)\r\n    \r\ndef lambda_handler(event, context):\r\n    logger.setLevel(logging.DEBUG)\r\n    logger.debug('Job ID is: {}' .format(event))\r\n    return(msgpublish(event))\r\n<\/code><\/pre>\n
                  \n
                1. Choose Save<\/strong>.<\/li>\n<\/ol>\n
                  Creating a state machine<\/h3>\n
                  To create a state machine, complete the following steps. For more information, see Create a State Machine<\/a>.<\/p>\n
                    \n
                  1. On the Step Functions console<\/a>, on the Define state machine<\/strong> page, choose Start with a template<\/strong>.<\/li>\n
                  2. Choose Hello world<\/strong>.<\/li>\n
                  3. Under Type<\/strong>, choose Standard.<\/strong>\n<\/li>\n
                  4. Under Definition, <\/strong>enter the following Amazon States Language<\/a>. Make sure to replace the Lambda function and SNS topic ARN.<\/li>\n<\/ol>\n
                    {\r\n\"Comment\": \"Polling step function for translate job complete\",\r\n\"StartAt\": \"LambdaPoll\",\r\n\"States\": {\r\n\"LambdaPoll\": {\r\n\"Type\": \"Task\",\r\n\"Resource\": \"<ARN of the Lambda Function created in step 3>\",\r\n\"InputPath\": \"$.detail.responseElements.jobId\",\r\n\"ResultPath\": \"$.detail.responseElements.jobStatus\",\r\n\"Next\": \"Job Complete?\",\r\n\"Retry\": [\r\n{\r\n\"ErrorEquals\": [\r\n\"States.ALL\"\r\n],\r\n\"IntervalSeconds\": 1,\r\n\"MaxAttempts\": 3,\r\n\"BackoffRate\": 2\r\n}\r\n]\r\n},\r\n\"Job Complete?\": {\r\n\"Type\": \"Choice\",\r\n\"Choices\": [\r\n{\r\n\"Variable\": \"$.detail.responseElements.jobStatus\",\r\n\"StringEquals\": \"IN_PROGRESS\",\r\n\"Next\": \"Wait X Seconds\"\r\n},\r\n{\r\n\"Variable\": \"$.detail.responseElements.jobStatus\",\r\n\"StringEquals\": \"SUBMITTED\",\r\n\"Next\": \"Wait X Seconds\"\r\n},\r\n{\r\n\"Variable\": \"$.detail.responseElements.jobStatus\",\r\n\"StringEquals\": \"COMPLETED\",\r\n\"Next\": \"Notify\"\r\n},\r\n{\r\n\"Variable\": \"$.detail.responseElements.jobStatus\",\r\n\"StringEquals\": \"FAILED\",\r\n\"Next\": \"Notify\"\r\n},\r\n{\r\n\"Variable\": \"$.detail.responseElements.jobStatus\",\r\n\"StringEquals\": \"STOPPED\",\r\n\"Next\": \"Notify\"\r\n}\r\n],\r\n\"Default\": \"Wait X Seconds\"\r\n},\r\n\"Wait X Seconds\": {\r\n\"Type\": \"Wait\",\r\n\"Seconds\": 60,\r\n\"Next\": \"LambdaPoll\"\r\n},\r\n\"Notify\": {\r\n\"Type\": \"Task\",\r\n\"Resource\": \"arn:aws:states:::sns:publish\",\r\n\"Parameters\": {\r\n\"Subject\": \"Translate Batch Job Notification\",\r\n\"Message\": {\r\n\"JobId.$\": \"$.detail.responseElements.jobId\",\r\n\"S3OutputLocation.$\": \"$.detail.requestParameters.outputDataConfig.s3Uri\",\r\n\"JobStatus.$\": \"$.detail.responseElements.jobStatus\"\r\n},\r\n\"MessageAttributes\": {\r\n\"JobId\": {\r\n\"DataType\": \"String\",\r\n\"StringValue.$\": \"$.detail.responseElements.jobId\"\r\n},\r\n\"S3OutputLocation\": {\r\n\"DataType\": \"String\",\r\n\"StringValue.$\": \"$.detail.requestParameters.outputDataConfig.s3Uri\"\r\n}\r\n},\r\n\"TopicArn\": \"<ARN of the SNS topic created in step 1>\"\r\n},\r\n\"End\": true\r\n}\r\n}\r\n}\r\n<\/code><\/pre>\n
                      \n
                    1. Use the graph in the Visual Workflow<\/strong> pane to check that your Amazon States Language code describes your state machine correctly. You should see something like the following screenshot.
                      \"Amazon\n<\/li>\n<\/ol>\n
                        \n
                      1. Choose Next<\/strong>.<\/li>\n
                      2. For Name<\/strong>, enter a name for the state machine.<\/li>\n
                      3. Under Permissions<\/strong>, select Create new role<\/strong>.<\/li>\n<\/ol>\n
                        You now see an info block with the details of the role and the associated permissions.<\/p>\n
                        \"IAM<\/p>\n
                          \n
                        1. Choose Create state machine.<\/strong>\n<\/li>\n<\/ol>\n
                          Creating a CloudWatch Events rule<\/h3>\n
                          To create a CloudWatch Events rule, complete the following steps. This rule catches when a user performs a StartTextTranslationJob API event and triggers the step function (set as a target).<\/p>\n
                            \n
                          1. On the CloudWatch console<\/a>, choose Rules<\/strong>.<\/li>\n
                          2. Choose Create rule<\/strong>.<\/li>\n
                          3. On the Step 1: Create rule <\/strong>page, under Event Source<\/strong>, select Event Pattern<\/strong>.<\/li>\n
                          4. Choose Build custom event pattern<\/strong> from the drop-down menu.<\/li>\n
                          5. Enter the following code into the preview pane:<\/li>\n<\/ol>\n
                            { \r\n    \"source\": [ \"aws.translate\" ], \r\n    \"detail-type\": [ \"AWS API Call via CloudTrail\" ], \r\n    \"detail\": { \r\n            \"eventSource\": [ \"translate.amazonaws.com\" ], \r\n            \"eventName\": [ \"StartTextTranslationJob\" ] \r\n            } \r\n }<\/code><\/pre>\n
                              \n
                            1. For Targets<\/strong>, select Step Functions state machine<\/strong>.<\/li>\n
                            2. Select the state machine you created earlier.<\/li>\n
                            3. For permission to send events to Step Functions, select Create a new role for this specific resource<\/strong>.<\/li>\n
                            4. Choose Configure details<\/strong>.<\/li>\n
                            5. On the Step 2: Configure rule details<\/strong> page, enter a name and description for the rule.<\/li>\n
                            6. For State<\/strong>, select Enabled<\/strong>.<\/li>\n
                            7. Choose Create rule<\/strong>.<\/li>\n<\/ol>\n
                              Validating the solution<\/h2>\n
                              To test this solution, I first create an Amazon Translate batch job and provide the input text Amazon Simple Storage Service<\/a> (Amazon S3) location, output Amazon S3 location, target language, and the data access service role ARN. For instructions on creating a batch translate job, see Asynchronous Batch Processing<\/a> or Translating documents with Amazon Translate, AWS Lambda, and the new Batch Translate API<\/a>.<\/p>\n
                              The following screenshot shows my batch job on the Translation jobs<\/strong> page.<\/p>\n
                              \"Amazon<\/p>\n
                              The CloudWatch Events rule picks up the StartTextTranslationJob API and triggers the state machine. When the job is complete, I get an email notification via Amazon SNS.<\/p>\n
                              \"Translate<\/p>\n
                              Conclusion<\/h2>\n
                              In this post, we demonstrated how you can use Step Functions to poll for an Amazon Translate batch job. For this use case, we configured an email notification to send when a job is complete; however, you can use this framework to trigger other Lambda functions or integrate with Amazon Simple Queue Service<\/a> (Amazon SQS) for any postprocessing automated steps, enabling you to build an end-to-end automated workflow. For further reading, see the following:<\/p>\n
                              About the Authors<\/h2>\n
                              \n
                              \"\"<\/em>Sudhanshu Malhotra is a Boston-based Enterprise Solutions Architect for AWS. He is a technology enthusiast who enjoys helping customers find innovative solutions to complex business challenges. His core areas of focus are DevOps, Machine Learning, and Security. When he\u2019s not working with customers on their journey to the cloud, he enjoys reading, hiking, and exploring new cuisines.<\/p>\n
                              \u00a0<\/p>\n
                              \u00a0<\/p>\n
                              \u00a0<\/p>\n
                              \"\"<\/em><\/span>Siva Rajamani is a Boston-based Enterprise Solutions Architect for AWS. He enjoys working closely with customers, supporting their digital transformation and AWS adoption journey. His core areas of focus are Serverless, Application Integration, and Security. Outside of work, he enjoys outdoor activities and watching documentaries.<\/p>\n
                              \u00a0<\/p>\n
                              \u00a0<\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"
                              https:\/\/aws.amazon.com\/blogs\/machine-learning\/getting-a-batch-job-completion-message-from-amazon-translate\/<\/p>\n","protected":false},"author":0,"featured_media":178,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/posts\/177"}],"collection":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/comments?post=177"}],"version-history":[{"count":0,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/posts\/177\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/media\/178"}],"wp:attachment":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/media?parent=177"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/categories?post=177"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/tags?post=177"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}