From 7f5b37f736c24117b4b371210cbd9be081bbfd96 Mon Sep 17 00:00:00 2001
From: Josh Bean <1139540+joshbean@users.noreply.github.com>
Date: Mon, 3 Jul 2023 14:21:59 -0700
Subject: [PATCH] Delete documentation content
---
doc_source/api_reference.md | 3 -
doc_source/async-monitor.md | 74 ---
doc_source/async-prereqs.md | 188 --------
doc_source/async-results.md | 57 ---
doc_source/async-start.md | 167 -------
doc_source/async.md | 28 --
doc_source/compliance.md | 12 -
doc_source/creating-custom-terminology.md | 69 ---
doc_source/ct-best-practices.md | 7 -
.../customizing-translations-formality.md | 45 --
...izing-translations-parallel-data-adding.md | 88 ----
...-translations-parallel-data-input-files.md | 176 -------
...ing-translations-parallel-data-managing.md | 143 ------
.../customizing-translations-parallel-data.md | 57 ---
.../customizing-translations-profanity.md | 42 --
doc_source/customizing-translations-tags.md | 52 --
doc_source/customizing-translations.md | 15 -
doc_source/data-protection.md | 18 -
doc_source/disaster-recovery-resiliency.md | 5 -
doc_source/doc-history.md | 45 --
doc_source/encryption-at-rest.md | 29 --
doc_source/encryption-in-transit.md | 3 -
doc_source/examples-ddb.md | 184 -------
doc_source/examples-java.md | 38 --
doc_source/examples-polly.md | 251 ----------
doc_source/examples-python.md | 104 ----
doc_source/examples-sigv4.md | 169 -------
doc_source/examples-split.md | 104 ----
doc_source/examples-twitch.md | 448 ------------------
doc_source/examples-web.md | 155 ------
doc_source/examples.md | 11 -
doc_source/get-started-cli.md | 80 ----
doc_source/get-started-console.md | 19 -
doc_source/get-started-sdk.md | 11 -
doc_source/getting-started-android.md | 85 ----
doc_source/getting-started-ios.md | 81 ----
doc_source/getting-started.md | 10 -
doc_source/glossary.md | 3 -
doc_source/how-custom-terminology.md | 20 -
doc_source/how-it-works.md | 29 --
doc_source/identity-and-access-management.md | 141 ------
doc_source/index.md | 81 ----
doc_source/infrastructure-security.md | 7 -
doc_source/logging-using-cloudtrail.md | 68 ---
doc_source/monitoring-translate.md | 60 ---
doc_source/monitoring-with-eventbridge.md | 99 ----
doc_source/permissible-language-pairs.md | 26 -
doc_source/processing.md | 5 -
doc_source/protect-terminology.md | 8 -
doc_source/security.md | 18 -
.../security_iam_id-based-policy-examples.md | 138 ------
doc_source/security_iam_service-with-iam.md | 85 ----
doc_source/security_iam_troubleshoot.md | 66 ---
doc_source/setting-up.md | 47 --
doc_source/setup-awscli.md | 32 --
doc_source/sync.md | 5 -
doc_source/tagging-existingtags.md | 22 -
doc_source/tagging-newtags.md | 30 --
doc_source/tagging.md | 23 -
doc_source/translate-api-permissions-ref.md | 9 -
doc_source/translate-cloudwatch.md | 25 -
doc_source/using-ct.md | 41 --
doc_source/vpc-interface-endpoints.md | 70 ---
doc_source/what-is-languages.md | 93 ----
doc_source/what-is-limits.md | 90 ----
doc_source/what-is.md | 53 ---
66 files changed, 4467 deletions(-)
delete mode 100644 doc_source/api_reference.md
delete mode 100644 doc_source/async-monitor.md
delete mode 100644 doc_source/async-prereqs.md
delete mode 100644 doc_source/async-results.md
delete mode 100644 doc_source/async-start.md
delete mode 100644 doc_source/async.md
delete mode 100644 doc_source/compliance.md
delete mode 100644 doc_source/creating-custom-terminology.md
delete mode 100644 doc_source/ct-best-practices.md
delete mode 100644 doc_source/customizing-translations-formality.md
delete mode 100644 doc_source/customizing-translations-parallel-data-adding.md
delete mode 100644 doc_source/customizing-translations-parallel-data-input-files.md
delete mode 100644 doc_source/customizing-translations-parallel-data-managing.md
delete mode 100644 doc_source/customizing-translations-parallel-data.md
delete mode 100644 doc_source/customizing-translations-profanity.md
delete mode 100644 doc_source/customizing-translations-tags.md
delete mode 100644 doc_source/customizing-translations.md
delete mode 100644 doc_source/data-protection.md
delete mode 100644 doc_source/disaster-recovery-resiliency.md
delete mode 100644 doc_source/doc-history.md
delete mode 100644 doc_source/encryption-at-rest.md
delete mode 100644 doc_source/encryption-in-transit.md
delete mode 100644 doc_source/examples-ddb.md
delete mode 100644 doc_source/examples-java.md
delete mode 100644 doc_source/examples-polly.md
delete mode 100644 doc_source/examples-python.md
delete mode 100644 doc_source/examples-sigv4.md
delete mode 100644 doc_source/examples-split.md
delete mode 100644 doc_source/examples-twitch.md
delete mode 100644 doc_source/examples-web.md
delete mode 100644 doc_source/examples.md
delete mode 100644 doc_source/get-started-cli.md
delete mode 100644 doc_source/get-started-console.md
delete mode 100644 doc_source/get-started-sdk.md
delete mode 100644 doc_source/getting-started-android.md
delete mode 100644 doc_source/getting-started-ios.md
delete mode 100644 doc_source/getting-started.md
delete mode 100644 doc_source/glossary.md
delete mode 100644 doc_source/how-custom-terminology.md
delete mode 100644 doc_source/how-it-works.md
delete mode 100644 doc_source/identity-and-access-management.md
delete mode 100644 doc_source/index.md
delete mode 100644 doc_source/infrastructure-security.md
delete mode 100644 doc_source/logging-using-cloudtrail.md
delete mode 100644 doc_source/monitoring-translate.md
delete mode 100644 doc_source/monitoring-with-eventbridge.md
delete mode 100644 doc_source/permissible-language-pairs.md
delete mode 100644 doc_source/processing.md
delete mode 100644 doc_source/protect-terminology.md
delete mode 100644 doc_source/security.md
delete mode 100644 doc_source/security_iam_id-based-policy-examples.md
delete mode 100644 doc_source/security_iam_service-with-iam.md
delete mode 100644 doc_source/security_iam_troubleshoot.md
delete mode 100644 doc_source/setting-up.md
delete mode 100644 doc_source/setup-awscli.md
delete mode 100644 doc_source/sync.md
delete mode 100644 doc_source/tagging-existingtags.md
delete mode 100644 doc_source/tagging-newtags.md
delete mode 100644 doc_source/tagging.md
delete mode 100644 doc_source/translate-api-permissions-ref.md
delete mode 100644 doc_source/translate-cloudwatch.md
delete mode 100644 doc_source/using-ct.md
delete mode 100644 doc_source/vpc-interface-endpoints.md
delete mode 100644 doc_source/what-is-languages.md
delete mode 100644 doc_source/what-is-limits.md
delete mode 100644 doc_source/what-is.md
diff --git a/doc_source/api_reference.md b/doc_source/api_reference.md
deleted file mode 100644
index b77c000..0000000
--- a/doc_source/api_reference.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# API reference
-
-The Amazon Translate API Reference is now a separate document\. For more information, see [Amazon Translate API Reference](https://docs.aws.amazon.com/translate/latest/APIReference/Welcome.html)\.
\ No newline at end of file
diff --git a/doc_source/async-monitor.md b/doc_source/async-monitor.md
deleted file mode 100644
index 74719cd..0000000
--- a/doc_source/async-monitor.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Monitoring and analyzing batch translation jobs
-
-You can use a job's ID to monitor its progress and get the Amazon S3 location of its output documents\. To monitor a specific job, use the [DescribeTextTranslationJob](https://docs.aws.amazon.com/translate/latest/APIReference/API_DescribeTextTranslationJob.html) operation\. You can also use the [ListTextTranslationJobs](https://docs.aws.amazon.com/translate/latest/APIReference/API_ListTextTranslationJobs.html) operation to retrieve information on all of the translation jobs in your account\. To restrict results to jobs that match a certain criteria, use the [ListTextTranslationJobs](https://docs.aws.amazon.com/translate/latest/APIReference/API_ListTextTranslationJobs.html) operation's `filter` parameter\. You can filter results by job name, job status, or the date and time that the job was submitted\.
-
-**Example describe\-text\-translation\-job command**
-The following example check's a job's status by using the AWS CLI to run the [DescribeTextTranslationJob](https://docs.aws.amazon.com/translate/latest/APIReference/API_DescribeTextTranslationJob.html) command:
-
-```
-$ aws translate describe-text-translation-job --job-id 1c1838f470806ab9c3e0057f14717bed
-```
-This command returns the following output:
-
-```
-{
- "TextTranslationJobProperties": {
- "InputDataConfig": {
- "ContentType": "text/plain",
- "S3Uri": "s3://input-bucket-name/folder"
- },
- "EndTime": 1576551359.483,
- "SourceLanguageCode": "en",
- "DataAccessRoleArn": "arn:aws:iam::012345678901:role/service-role/AmazonTranslateInputOutputAccess",
- "JobId": "1c1838f470806ab9c3e0057f14717bed",
- "TargetLanguageCodes": [
- "fr"
- ],
- "JobName": "batch-test",
- "SubmittedTime": 1576544017.357,
- "JobStatus": "COMPLETED",
- "Message": "Your job has completed successfully.",
- "JobDetails": {
- "InputDocumentsCount": 77,
- "DocumentsWithErrorsCount": 0,
- "TranslatedDocumentsCount": 77
- },
- "OutputDataConfig": {
- "S3Uri": "s3://bucket-name/output/012345678901-TranslateText-1c1838f470806ab9c3e0057f14717bed/"
- }
- }
-}
-```
-
-You can stop a batch translation job while its status is `IN_PROGRESS` by using the [StopTextTranslationJob](https://docs.aws.amazon.com/translate/latest/APIReference/API_StopTextTranslationJob.html) operation\.
-
-**Example stop\-text\-translation\-job command**
-The following example stops a batch translation with by using the AWS CLI to run the [StopTextTranslationJob](https://docs.aws.amazon.com/translate/latest/APIReference/API_StopTextTranslationJob.html) command:
-
-```
-$ aws translate stop-text-translation-job --job-id 5236d36ce5192abdb3e2519f3ab8b065
-```
-This command returns the following output:
-
-```
-{
- "TextTranslationJobProperties": {
- "InputDataConfig": {
- "ContentType": "text/plain",
- "S3Uri": "s3://input-bucket-name/folder"
- },
- "SourceLanguageCode": "en",
- "DataAccessRoleArn": "arn:aws:iam::012345678901:role/service-role/AmazonTranslateInputOutputAccess",
- "TargetLanguageCodes": [
- "fr"
- ],
- "JobName": "canceled-test",
- "SubmittedTime": 1576558958.167,
- "JobStatus": "STOP_REQUESTED",
- "JobId": "5236d36ce5192abdb3e2519f3ab8b065",
- "OutputDataConfig": {
- "S3Uri": "s3://output-bucket-name/012345678901-TranslateText-5236d36ce5192abdb3e2519f3ab8b065/"
- }
- }
-}
-```
\ No newline at end of file
diff --git a/doc_source/async-prereqs.md b/doc_source/async-prereqs.md
deleted file mode 100644
index e69fcbe..0000000
--- a/doc_source/async-prereqs.md
+++ /dev/null
@@ -1,188 +0,0 @@
-# Prerequisites for batch translation jobs
-
-The following prerequisites must be met in order for Amazon Translate to perform a successful batch translation job:
-+ The Amazon S3 buckets that contain your input and output documents must be in the same AWS Region as the API endpoint you are calling\.
-+ The collection of batch input documents must be 5 GB or less in size\.
-+ There can be a maximum of one million documents submitted in a batch translation job\.
-+ Each input document must be 20 MB or less and must contain fewer than 1 million characters\.
-+ Your input files must be in a folder in an Amazon S3 bucket\. If you add your input files to the top level of a bucket, Amazon Translate throws an error when you attempt to run a batch translation job\. This requirement applies to the input files\. No folder is necessary for the output files, and Amazon Translate can place them at the top level of an Amazon S3 bucket\.
-+ Your input file folder can contain nested folders\. Make sure none of the nested folders are named details, otherwise Amazon Translate throws an error when you attempt to run the batch translation job\.
-
-## Supported file formats
-
-Amazon Translate supports the following types of files for batch translation jobs:
-+ Plain text\.
-+ HTML\.
-+ Word documents \(\.docx\)\.
-+ PowerPoint Presentation files \(\.pptx\)\.
-+ Excel Workbook files \(\.xlsx\)\.
-+ XML Localization Interchange File Format \(XLIFF\) files \(\.xlf\)\. Amazon Translate supports only XLIFF version 1\.2\.
-
-Amazon Translate requires files to be UTF\-8 encoded\.
-
-## Prerequisite permissions
-
-Before you can run a batch translation job, your AWS account must have a service role in IAM\. This role must have a permissions policy that grants Amazon Translate:
-+ Read access to your input folder and all its sub\-folders in Amazon S3\.
-+ Read and write access to your output bucket\.
-
-It must also include a trust policy that allows Amazon Translate to assume the role and gain its permissions\. This trust policy must allow the `translate.amazonaws.com` service principal to perform the `sts:AssumeRole` action\.
-
-When you create a batch translation job by using the Amazon Translate console, you have the option to allow Amazon Translate to automatically create this role for you\. When you run a batch translation job by using the AWS CLI or the Amazon Translate API, you provide the Amazon Resource Name \(ARN\) of the role in your request\.
-
-For more information, see [Creating a Role to Delegate Permissions to an AWS Service](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*\.
-
-**Example Permissions policy**
-The following example permissions policy grants read access to an input folder in an Amazon S3 bucket\. It grants read and write access to an output bucket\.
-
-```
-{
- "Version": "2012-10-17",
- "Statement": [
- {
- "Effect": "Allow",
- "Action": "s3:GetObject",
- "Resource": [
- "arn:aws:s3:::input-bucket-name/*",
- "arn:aws:s3:::output-bucket-name/*"
- ]
- },
- {
- "Effect": "Allow",
- "Action": "s3:ListBucket",
- "Resource": [
- "arn:aws:s3:::input-bucket-name",
- "arn:aws:s3:::output-bucket-name"
- ]
- },
- {
- "Effect": "Allow",
- "Action": [
- "s3:PutObject"
- ],
- "Resource": "arn:aws:s3:::output-bucket-name/*"
- }
- ]
-}
-```
-
-**Example Trust policy**
-The following trust policy allows Amazon Translate to assume the IAM role that the policy belongs to\.
-We recommend that you verify the AWS account that is using the trust policy, to mitigate the [ Confused deputy](https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html) problem\. This example uses the aws:SourceArn and aws:SourceAccount condition keys to verify the source account\. Enter the AWS account that submits the batch translation job\.
-
-```
-{
- "Version": "2012-10-17",
- "Statement": [
- {
- "Effect": "Allow",
- "Principal": {
- "Service": "translate.amazonaws.com"
- },
- "Action": "sts:AssumeRole",
- "Condition": {
- "ArnLike": {
- "aws:SourceArn": "arn:aws:translate:*:111122223333:*"
- },
- "StringEquals": {
- "aws:SourceAccount": "111122223333"
- }
- }
- }
- ]
-}
-```
-
-## Prerequisite permissions to customize encryption
-
-You can customize your encryption settings in Amazon Translate, but first you must add permissions to the service role in IAM\.
-
-Amazon Translate encrypts the translation output that you produce when you run a batch translation job\. By default, it does this encryption with an *AWS managed key*\. This type of key is created by AWS and stored in AWS Key Management Service \(AWS KMS\) in your account\. However, you cannot manage this KMS key yourself\. It is managed and used on your behalf only by AWS\.
-
-Optionally, you can choose to encrypt your output with a *customer managed key*, which is a KMS key that you create, own, and manage in your AWS account\.
-
-Your key must have a key policy that enables Amazon Translate to use it\. The key policy does this by granting its permissions to the service role that allows Amazon Translate to access your Amazon S3 bucket\.
-
-The key policy allows the service role to perform the AWS KMS operations that are required to encrypt your output, as shown by the following example policy statement\.
-
-**Example KMS key policy statement**
-
-```
-{
- "Effect": "Allow",
- "Principal":
- {
- "AWS":
- [
- "arn:aws:iam::111122223333:role/AmazonTranslateServiceRoleS3FullAccess"
- ]
- },
- "Action":
- [
- "kms:Decrypt",
- "kms:GenerateDataKey",
- "kms:CreateGrant",
- "kms:RetireGrant",
- "kms:DescribeKey"
- ],
- "Resource": "*"
-}
-```
-
-For more information, see [Key policies in AWS KMS](https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html) in the *AWS Key Management Service Developer Guide*
-
-### Permissions to use an AWS KMS key from another AWS account
-
-If you want to use a KMS key that's in a different AWS account from the one where you use Amazon Translate, then you must:
-
-1. Update the service role for Amazon Translate in IAM\.
-
-1. Update the key policy in AWS KMS\.
-
-To update your service role, attach a policy that allows it to perform the necessary AWS KMS operations with the KMS key that's in the other AWS account, as shown by the following example\.
-
-**Example IAM policy to grant access to a KMS key in a different account**
-
-```
-{
- "Effect": "Allow",
- "Action":
- [
- "kms:Decrypt",
- "kms:GenerateDataKey",
- "kms:CreateGrant",
- "kms:RetireGrant",
- "kms:DescribeKey"
- ],
- "Resource": "arn:aws:kms:us-west-2:111122223333:key/key-id"
-}
-```
-
-To update your KMS key policy, add the service role and root user as principals that are allowed to use the key, as shown by the following example policy statement\.
-
-**Example KMS key policy statement to allow an IAM role to use the key**
-
-```
-{
- "Effect": "Allow",
- "Principal":
- {
- "AWS":
- [
- "arn:aws:iam::444455556666:role/AmazonTranslateServiceRoleS3FullAccess",
- "arn:aws:iam::444455556666:root"
- ]
- },
- "Action":
- [
- "kms:Decrypt",
- "kms:CreateGrant",
- "kms:GenerateDataKey",
- "kms:RetireGrant",
- "kms:DescribeKey"
- ],
- "Resource": "*"
-}
-```
-
-For more information, see [Allowing users in other accounts to use a AWS KMS key](https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-modifying-external-accounts.html) in the *AWS Key Management Service Developer Guide*
\ No newline at end of file
diff --git a/doc_source/async-results.md b/doc_source/async-results.md
deleted file mode 100644
index ebcc7db..0000000
--- a/doc_source/async-results.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# Getting batch translation results
-
-Once the job's status is `COMPLETED` or `COMPLETED_WITH_ERROR`, your output documents are available in the Amazon S3 folder you specified\. The output document names match the input document names, with the addition of the target language code as a prefix\. For instance, if you translated a document called `mySourceText.txt` into French, the output document will be called `fr.mySourceText.txt`\.
-
-If the status of a batch translation job is `FAILED`, the [DescribeTextTranslationJob](https://docs.aws.amazon.com/translate/latest/APIReference/API_DescribeTextTranslationJob.html) operation response includes a `Message` field that describes the reason why the job didn't complete successfully\.
-
-Each batch translation job also generates an auxiliary file that contains information on the translations performed, such as the total number of characters translated and the number of errors encountered\. This file, called `target-language-code.auxiliary-translation-details.json`, is generated in the `details` subfolder of your output folder\.
-
-The following is an example of a batch translation auxiliary file\.
-
-```
-{
- "sourceLanguageCode": "en",
- "targetLanguageCode": "fr",
- "charactersTranslated": "105",
- "documentCountWithCustomerError": "0",
- "documentCountWithServerError": "0",
- "inputDataPrefix": "s3://input-bucket-name/folder",
- "outputDataPrefix": "s3://output-bucket-name/012345678901-TranslateText-1c1838f470806ab9c3e0057f14717bed/",
- "details": [
- {
- "sourceFile": "mySourceText.txt",
- "targetFile": "fr.mySourceText.txt",
- "auxiliaryData": {
- "appliedTerminologies": [
- {
- "name": "TestTerminology",
- "terms": [
- {
- "sourceText": "Amazon",
- "targetText": "Amazon"
- }
- ]
- }
- ]
- }
- },
- {
- "sourceFile": "batchText.txt",
- "targetFile": "fr.batchText.txt",
- "auxiliaryData": {
- "appliedTerminologies": [
- {
- "name": "TestTerminology",
- "terms": [
- {
- "sourceText": "Amazon",
- "targetText": "Amazon"
- }
- ]
- }
- ]
- }
- }
- ]
-}
-```
\ No newline at end of file
diff --git a/doc_source/async-start.md b/doc_source/async-start.md
deleted file mode 100644
index 7a3d88e..0000000
--- a/doc_source/async-start.md
+++ /dev/null
@@ -1,167 +0,0 @@
-# Running a batch translation job
-
-You can run a batch translation job by using the Amazon Translate console, the AWS CLI, or the Amazon Translate API\.
-
-**Note**
-Batch translation jobs are long\-running operations and can take significant time to complete\. For example, batch translation on a small dataset might take a few minutes, while very large datasets may take up to 2 days or more\. Completion time is also dependent on the availability of resources\.
-
-## Amazon Translate console
-
-To run a translation job by using the Amazon Translate console, use the **Batch translation** page to create the job:
-
-1. Open the [Amazon Translate console](https://console.aws.amazon.com/translate/home)\.
-
-1. In the navigation menu on the left, choose **Batch translation**\.
-
-1. On the **Translation jobs** page, choose **Create job**\. The console shows the **Create translation job** page\.
-
-1. Under **Job settings**, do the following:
-
- 1. For **Name**, enter a custom name for the batch translation job\.
-
- 1. For **Source language**, select the language of the source files\. If you don't know the language of the source files, or your input documents contains different source languages, select `auto`\. Amazon Translate auto detects the source language for each file\.
-
- 1. For **Target languages**, select up to 10 languages\. Amazon Translate translates each source file into each target language\.
-
-1. Under **Input data**, do the following:
-
- 1. For **Input S3 location**, specify the input folder that contains the translation source files in Amazon S3\. To provide the folder by navigating to it in Amazon S3, choose **Select folder**\.
-
- 1. For **File format**, select format of the translation source files\.
-
-1. Under **Output data**, do the following:
-
- 1. For **Output S3 location**, specify the output folder in Amazon S3 where Amazon Translate puts the translation output\. To provide the folder by navigating to it in Amazon S3, choose **Select folder**\.
-
- 1. Optionally, choose **Customize encryption settings \(advanced\)** if you want to encrypt your output with a customer managed key that you manage in the AWS Key Management Service \(AWS KMS\)\.
-
- By default, Amazon Translate encrypts your translation output using a KMS key that is created, managed, and used on your behalf by AWS\. Choose this option if you want to encrypt your output with your own KMS key instead\.
-
- If you want to use a KMS key from the current AWS account, select it under **Choose an AWS Key Management Service key**\. Or, if you want to use a KMS key from a different AWS account, enter the Amazon Resource Name \(ARN\) for that key\.
-**Note**
-Before you can use your own KMS key, you must add permissions to the service role for Amazon Translate in IAM\. If you want to use a KMS key from a different account, you must also update the key policy in AWS KMS\. For more information, see [Prerequisite permissions to customize encryption](async-prereqs.md#async-prereqs-permissions-custom-encryption)\.
-
-1. Under **Customizations \- optional**, you can choose to customize the output of your translation job with the following settings:
-**Profanity**
-Masks profane words and phrases in your translation output\. If you specify multiple target languages for the job, all the target languages must support profanity masking\. If any of the target languages don't support profanity masking, the translation job won't mask profanity for any target language\.
-For more information, see [Masking profane words and phrases in Amazon Translate](customizing-translations-profanity.md)\.
-**Formality**
-For some target languages, you can set **Formality** to formal or informal\. If you specify multiple target languages for the job, translate ignores the formality setting for any unsupported target language\.
- For more information, see [Setting formality in Amazon Translate](customizing-translations-formality.md)\.
-**Custom terminology**
-Consists of example source terms and the desired translation for each term\. If you specify multiple target languages for the job, translate uses the designated terminology for each requested target language that has an entry for the source term in the terminology file\.
-For more information, see [Customizing your translations with custom terminology](how-custom-terminology.md)\.
-**Parallel data**
-Consists of examples that show how you want segments of text to be translated\. If you specify multiple target languages for the job, the parallel data file must include translations for all the target languages\.
-When you add parallel data to a batch translation job, you create an *Active Custom Translation* job\.
-Active Custom Translation jobs are priced at a higher rate than other jobs that don't use parallel data\. For more information, see [Amazon Translate pricing](http://aws.amazon.com/translate/pricing/)\.
-For more information, see [Customizing your translations with parallel data \(Active Custom Translation\)](customizing-translations-parallel-data.md)\.
-
-1. Under **Access permissions**, provide Amazon Translate with an IAM role that grants the required permissions to your input and output files in Amazon S3:
- + If you already have this IAM role in your account, choose **Use an existing IAM role**, and select it under **IAM role**\.
- + If you don't already have this IAM role in your account, choose **Create an IAM role**\. For **IAM role**, choose **Input and output S3 buckets**\. For **Role name**, provide a custom name\. When you create the translation job, Amazon Translate creates the role automatically\. The role name in IAM is prefixed with *AmazonTranslateServiceRole\-*\.
-**Note**
-If you chose to encrypt your translation output with your own KMS key, then you cannot choose **Create an IAM role**\. In this case, you must use a preexisting IAM role, and your KMS key must have a key policy that allows the role to use the key\.
-For more information, see [Prerequisite permissions to customize encryption](async-prereqs.md#async-prereqs-permissions-custom-encryption)
-
-1. Choose **Create job**\.
-
- The console returns to the **Translation jobs** page, where the job creation status is shown in a banner at the top of the page\. After a few minutes, your job is shown in the table\.
-
-1. Choose the job name in the **Name** column to open the job details page\.
-
- While your translation job runs, the **Status** field shows **In progress**\.
-
-1. When the status becomes **Completed**, go to your translation output by choosing the link under **Output file location**\. The console goes to your output bucket in Amazon S3\.
-
-1. To download your output files, select the check box for each, and choose **Download**\.
-
-## AWS CLI
-
-To run a translation job by using the AWS CLI, use the [https://docs.aws.amazon.com/cli/latest/reference/translate/start-text-translation-job.html](https://docs.aws.amazon.com/cli/latest/reference/translate/start-text-translation-job.html) command, and specify the name of your parallel data resource for the `parallel-data-names` parameter\.
-
-**Example Start\-text\-translation\-job command**
-The following example runs a translation job by submitting an Excel file that is stored in an input bucket in Amazon S3\. This job is customized by the parallel data that is included in the request\.
-
-```
-$ aws translate start-text-translation-job \
-> --input-data-config ContentType=application/vnd.openxmlformats-officedocument.spreadsheetml.sheet,S3Uri=s3://my-s3-bucket/input/ \
-> --output-data-config S3Uri=s3://my-s3-bucket/output/ \
-> --data-access-role-arn arn:aws:iam::111122223333:role/my-iam-role \
-> --source-language-code en \
-> --target-language-codes es it \
-> --job-name my-translation-job
-```
-If the command succeeds, Amazon Translate responds with the job ID and status:
-
-```
-{
- "JobId": "4446f95f20c88a4b347449d3671fbe3d",
- "JobStatus": "SUBMITTED"
-}
-```
-If you want to customize the output of your translation job, you can use the following parameters:
-`--settings`
-Settings to configure your translation output, including the following options:
-Enable profanity to mask profane words and phrases\. To enable, set the profanity parameter to `Profanity=MASK`\. For more information, see [Masking profane words and phrases in Amazon Translate](customizing-translations-profanity.md)\. If any of the target languages don't support profanity masking, the translation job won't mask profanity for any target language\.
-Set the level of formality in the translation output\. Set the `Formality` parameter to `FORMAL` or `INFORMAL`\. If you specify multiple target languages for the job, translate ignores the formality setting for any unsupported target language\. For more information, see [Setting formality in Amazon Translate](customizing-translations-formality.md)\.
-`--terminology-names`
-The name of a custom terminology resource to add to the translation job\. This resource lists example source terms and the desired translation for each term\. If you specify multiple target languages for the job, translate uses the designated terminology for each requested target language that has an entry for the source term in the terminology file\.
-This parameter accepts only one custom terminology resource\.
-For a list of available custom terminology resources, use the [https://docs.aws.amazon.com/cli/latest/reference/translate/list-terminologies.html](https://docs.aws.amazon.com/cli/latest/reference/translate/list-terminologies.html) command\.
-For more information, see [Customizing your translations with custom terminology](how-custom-terminology.md)\.
-`--parallel-data-names`
-The name of a parallel data resource to add to the translation job\. This resource consists of examples that show how you want segments of text to be translated\. If you specify multiple target languages for the job, the parallel data file must include translations for all the target languages\.
-When you add parallel data to a translation job, you create an *Active Custom Translation* job\.
-This parameter accepts only one parallel data resource\.
-Active Custom Translation jobs are priced at a higher rate than other jobs that don't use parallel data\. For more information, see [Amazon Translate pricing](http://aws.amazon.com/translate/pricing/)\.
-For a list of available parallel data resources, use the [https://docs.aws.amazon.com/cli/latest/reference/translate/list-parallel-data.html](https://docs.aws.amazon.com/cli/latest/reference/translate/list-parallel-data.html) command\.
-For more information, see [Customizing your translations with parallel data \(Active Custom Translation\)](customizing-translations-parallel-data.md)\.
-
-To check the status of your translation job, use the [https://docs.aws.amazon.com/cli/latest/reference/translate/describe-text-translation-job.html](https://docs.aws.amazon.com/cli/latest/reference/translate/describe-text-translation-job.html) command\.
-
-**Example Describe\-text\-translation\-job command**
-
-The following example checks the job status by providing the job ID\. This ID was provided by Amazon Translate when the job was initiated by the `start-text-translation-job` command\.
-
-```
-$ aws translate describe-text-translation-job \
-> --job-id 4446f95f20c88a4b347449d3671fbe3d
-```
-
-Amazon Translate responds with the job properties, which include its status:
-
-```
-{
- "TextTranslationJobProperties": {
- "JobId": "4446f95f20c88a4b347449d3671fbe3d",
- "JobName": "my-translation-job",
- "JobStatus": "COMPLETED",
- "JobDetails": {
- "TranslatedDocumentsCount": 0,
- "DocumentsWithErrorsCount": 0,
- "InputDocumentsCount": 1
- },
- "SourceLanguageCode": "en",
- "TargetLanguageCodes": [
- "es",
- "it"
- ],
- "SubmittedTime": 1598661012.468,
- "InputDataConfig": {
- "S3Uri": "s3://my-s3-bucket/input/",
- "ContentType": "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet"
- },
- "OutputDataConfig": {
- "S3Uri": "s3://my-s3-bucket/output/111122223333-TranslateText-4446f95f20c88a4b347449d3671fbe3d/"
- },
- "DataAccessRoleArn": "arn:aws:iam::111122223333:role/my-iam-role"
- }
-}
-```
-
-If the `JobStatus` value is `IN_PROGRESS`, allow a few minutes to pass, and run [https://docs.aws.amazon.com/cli/latest/reference/translate/describe-text-translation-job.html](https://docs.aws.amazon.com/cli/latest/reference/translate/describe-text-translation-job.html) again until the status is `COMPLETED`\. When the job completes, you can download the translation results at the location provided by the `S3Uri` field under `OutputDataConfig`\.
-
-## Amazon Translate API
-
-To submit a batch translation job by using the Amazon Translate API, use the [StartTextTranslationJob](https://docs.aws.amazon.com/translate/latest/APIReference/API_StartTextTranslationJob.html) operation\.
\ No newline at end of file
diff --git a/doc_source/async.md b/doc_source/async.md
deleted file mode 100644
index c7b8eaf..0000000
--- a/doc_source/async.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# Asynchronous batch processing with Amazon Translate
-
-To translate large collections of documents \(up to 5 GB in size\), use the Amazon Translate asynchronous batch processing operation, [StartTextTranslationJob](https://docs.aws.amazon.com/translate/latest/APIReference/API_StartTextTranslationJob.html)\. This is best for collections of short documents, such as social media postings or user reviews, or any situation in which instantaneous translation is not required\.
-
-To perform an asynchronous batch translation, you typically perform the following steps:
-
-1. Store a set of documents in an input folder inside of an Amazon S3 bucket\.
-
-1. Start a batch translation job\.
-
-1. As part of your request, provide Amazon Translate with an IAM role that has read access to the input Amazon S3 folder and all its sub\-folders\. The role must also have read and write access to an output Amazon S3 bucket\.
-
-1. Monitor the progress of the batch translation job\.
-
-1. Retrieve the results of the batch translation job from the specified output bucket\.
-
-## Region availability
-
-Batch translation is supported in the following AWS Regions:
-+ US East \(N\. Virginia\)
-+ US East \(Ohio\)
-+ US West \(Oregon\)
-+ Asia Pacific \(Seoul\)
-+ Europe \(Frankfurt\)
-+ Europe \(Ireland\)
-+ Europe \(London\)
-
-**Topics**
\ No newline at end of file
diff --git a/doc_source/compliance.md b/doc_source/compliance.md
deleted file mode 100644
index b99172d..0000000
--- a/doc_source/compliance.md
+++ /dev/null
@@ -1,12 +0,0 @@
-# Compliance validation for Amazon Translate
-
-Third\-party auditors assess the security and compliance of Amazon Translate as part of multiple AWS compliance programs\. These include PCI, FedRAMP, HIPAA, and others\. You can download third\-party audit reports using AWS Artifact\. For more information, see [Downloading reports in AWS Artifact](https://docs.aws.amazon.com/artifact/latest/ug/downloading-documents.html)\.
-
-Your compliance responsibility when using Amazon Translate is determined by the sensitivity of your data, your company's compliance objectives, and applicable laws and regulations\. AWS provides the following resources to help with compliance:
-+ [Security and Compliance Quick Start Guides](http://aws.amazon.com/quickstart/?awsf.quickstart-homepage-filter=categories%23security-identity-compliance) – These deployment guides discuss architectural considerations and provide steps for deploying security\- and compliance\-focused baseline environments on AWS\.
-+ [Architecting for HIPAA Security and Compliance Whitepaper ](https://d0.awsstatic.com/whitepapers/compliance/AWS_HIPAA_Compliance_Whitepaper.pdf) – This whitepaper describes how companies can use AWS to create HIPAA\-compliant applications\.
-+ [AWS Compliance Resources](http://aws.amazon.com/compliance/resources/) – This collection of workbooks and guides might apply to your industry and location\.
-+ [AWS Config](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html) – This AWS service assesses how well your resource configurations comply with internal practices, industry guidelines, and regulations\.
-+ [AWS Security Hub](https://docs.aws.amazon.com/securityhub/latest/userguide/what-is-securityhub.html) – This AWS service provides a comprehensive view of your security state within AWS that helps you check your compliance with security industry standards and best practices\.
-
-For a list of AWS services in scope of specific compliance programs, see [AWS Services in Scope by Compliance Program](http://aws.amazon.com/compliance/services-in-scope/)\. For general information, see [AWS Compliance Programs](http://aws.amazon.com/compliance/programs/)\.
\ No newline at end of file
diff --git a/doc_source/creating-custom-terminology.md b/doc_source/creating-custom-terminology.md
deleted file mode 100644
index 9ec4e90..0000000
--- a/doc_source/creating-custom-terminology.md
+++ /dev/null
@@ -1,69 +0,0 @@
-# Creating a custom terminology
-
-You can use a CSV, TSV, or TMX file with the source text and the target \(translated\) term for the terminology file\. A single source text is used for each term, but there can be multiple target terms, one for each language, as long as the target and source language can be used\.
-
-**Important**
-The source word within a custom terminology is *case\-sensitive* and will not work for words that are not an exact match\.
-
-## Directionality
-
-When you create custom terminology in Amazon Translate, you can choose the following types for *directionality*, which indicates whether your terminology has one or multiple source languages\.
-
-**Uni\-directional**
-The file contains one source language\. All other languages are target languages\. For example, if your terminology file is a CSV file, then the first column contains text in the source language, and all other columns contain text in the target languages\.
-
-**Multi\-directional**
-Any language in the file can be a source language or a target language\. For example, if your terminology file contains text in English, Chinese, and Spanish, then you could use the same file for jobs that translate the following language pairs:
-+ English to Chinese
-+ English to Spanish
-+ Chinese to English
-+ Chinese to Spanish
-+ Spanish to English
-+ Spanish to Chinese
-
-In contrast, if you used uni\-directional terminology for those translation jobs, then you would need to create three terminology files\. Each file would have the same content, but each would use English, Chinese, or Spanish as the source language respectively\.
-
-## Example terminology files
-
-See [Supported languages and language codes](what-is-languages.md) for the supported language codes\.
-
-**CSV \(comma separated values\)**
-
-
-| | | | |
-| --- |--- |--- |--- |
-| en | fr | de | es |
-| Amazon | Amazon | Amazon | Amazon |
-
-**TMX \(Translation Memory eXchange\) **
-
-A TMX file is an XML\-type file commonly used by translation software\. Although the form is different than the CSV, the content is similar:
-
-```
-
-
-
-
-
-
- Amazon
-
-
- Amazon
-
-
- Amazon
-
-
- Amazon
-
-
-
-
-```
-
-These files are then attached to your Amazon Translate account\. When a translation job is run and you choose to use the custom terminology, Amazon Translate then uses the designated word whenever it encounters the source word\.
\ No newline at end of file
diff --git a/doc_source/ct-best-practices.md b/doc_source/ct-best-practices.md
deleted file mode 100644
index 2c79520..0000000
--- a/doc_source/ct-best-practices.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Best practices
-
-The following are suggested best practices when using custom terminologies
-+ Keep your custom terminology minimal\. Only include words which you want to control and which are completely unambiguous\. Only use words that you know you will never want to use an alternate meaning of, and you want it to only ever be translated in a single way\. Ideally, limit the list to proper names, like brand names and product names\.
-+ Custom terminologies are case\-sensitive\. If you need both capitalized and non\-capitalized versions of a word to be included, you must include an entry for each version\.
-+ Do not include different translations for the same source phrase \(for example, entry \#1\-EN: Amazon, FR: Amazon; entry \#2\-EN: Amazon FR: Amazone\)\.
-+ Some languages do not change the shape of a word based on sentence context\. With these languages, applying a custom terminology is most likely to improve overall translation quality\. However, some languages do have extensive word shape changes\. We do not recommend applying the feature to those languages, but we do not restrict you from doing so\. For more information, see [Compatible languages](permissible-language-pairs.md)\.
\ No newline at end of file
diff --git a/doc_source/customizing-translations-formality.md b/doc_source/customizing-translations-formality.md
deleted file mode 100644
index 88985b6..0000000
--- a/doc_source/customizing-translations-formality.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# Setting formality in Amazon Translate
-
-You can optionally specify the desired level of *formality* for translations to supported target languages\. The formality setting controls the level of formal language usage \(also known as [honorifics](https://en.wikipedia.org/wiki/Honorifics_(linguistics)) or [register](https://en.wikipedia.org/wiki/Register_(sociolinguistics)#Register_as_formality_scale)\) in the translation output\. The formality setting is available for real\-time translation and asynchronous batch processing\.
-
-Formality supports the following values:
-+ **Informal** – All sentences in the translated text use language constructs associated with informal communication\. For example, translated text uses the familiar form of second person pronouns and their verb agreement \(or Kudaketa form for Japanese\)\.
-+ **Formal** – All sentences in the translated text use language constructs associated with formal, polite communication\. For example, translated text uses the formal form of second person pronouns and their verb agreement \(or Teineigo form for Japanese\)\.
-
-For example, the sentence ‘Are you sure?’ can have two correct translations in German: ‘Sind Sie sicher?’ for the formal register and ‘Bist du sicher?’ for the informal one\.
-
-If Amazon Translate doesn’t support formality level for the target language, or you don't specify the formality parameter, the translation job ignores the formality setting\.
-
-**Topics**
-+ [Using the formality setting](#customizing-translations-formality-using)
-+ [Supported languages](#customizing-translations-formality-languages)
-
-## Using the formality setting
-
-To set formality in a real\-time translation request, do one of the following:
-+ On the **Real\-time translation** page in the Amazon Translate console, under **Additional settings**, enable the **Formality** setting and select one of the values\.
-+ Use the Settings parameter in the [TranslateText](https://docs.aws.amazon.com/translate/latest/APIReference/API_TranslateText.html) operation in the Amazon Translate API\.
-+ For the `translate-text` command in the AWS CLI, set the `--settings` parameter to `Formality=FORMAL` or `Formality=INFORMAL`\. For more information, see [translate\-text](https://docs.aws.amazon.com/cli/latest/reference/translate/translate-text.html) in the *AWS CLI Command Reference*\.
-
-To set formality in a batch translation request, set the **Formality** parameter when you start the translation job\. For details and examples, see [Running a batch translation job](async-start.md)\.
-
-For CLI or API requests, the `AppliedSettings` field in the response includes the formality setting \(if any\) from the request\. If the target language doesn't support formality, the `AppliedSettings` value in the response is NULL\.
-
-## Supported languages
-
-Amazon Translate supports the formality setting for translation from any source language to the following target languages\.
-
-
-| Language | Language code |
-| --- | --- |
-| Dutch | nl |
-| French | fr |
-| German | de |
-| Hindi | hi |
-| Italian | it |
-| Japanese | ja |
-| Korean | ko |
-| Spanish | es |
-| Spanish \(Mexico\) | es\-MX |
-
-For all the languages that Amazon Translate supports, see [Supported languages and language codes](what-is-languages.md)\.
\ No newline at end of file
diff --git a/doc_source/customizing-translations-parallel-data-adding.md b/doc_source/customizing-translations-parallel-data-adding.md
deleted file mode 100644
index aac6660..0000000
--- a/doc_source/customizing-translations-parallel-data-adding.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# Adding your parallel data to Amazon Translate
-
-To add parallel data to Amazon Translate, you import a parallel data input file from Amazon S3\. Afterwards, you can use the parallel data to customize the output produced by a batch translation job\.
-
-**Prerequisites**
-Before you can add parallel data to Amazon Translate, you must:
-Have a parallel data input file\. To create one, see [Parallel data input files for Amazon Translate](customizing-translations-parallel-data-input-files.md)\.
-Have an Amazon S3 bucket in your AWS account\. To create one, see [How do I create an S3 Bucket?](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/create-bucket.html) in the *Amazon Simple Storage Service User Guide*\.
-Upload your input file to an Amazon S3 bucket\. For more information, see [How do I upload files and folders to an S3 bucket?](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/upload-objects.html) in the *Amazon Simple Storage Service User Guide*\.
-
-## Adding parallel data \(Amazon Translate console\)
-
-To add parallel data by using the Amazon Translate console, use the **Parallel data** page:
-
-1. Open the [Amazon Translate console](https://console.aws.amazon.com/translate/home)\.
-
-1. In the navigation menu on the left, choose **Customization**, and choose **Parallel data**\.
-
-1. On the **Parallel data** page, choose **Create parallel data**\. The console shows the **Create parallel data** page\.
-
-1. Provide the following:
-**Name**
-A custom name for the parallel data resource\. You must assign a name that is unique in the account and region\.
-**Description \- *optional***
-A custom description\.
-**Parallel data location on S3**
-The location of the parallel data input file in Amazon S3\. To provide the location by navigating to the file in Amazon S3, choose **Select file**\.
-**File format**
-The format of the parallel data input file\. Supported formats are Translation Memory eXchange \(TMX\), comma\-separated values \(CSV\), and tab\-separated values \(TSV\)\.
-
-1. Under **Encryption key**, choose an AWS KMS key to secure your parallel data\. These KMS keys are managed by AWS Key Management Service \(AWS KMS\)\. For more information about AWS KMS, see the [AWS Key Management Service Developer Guide](https://docs.aws.amazon.com/kms/latest/developerguide/)\.
-**Use AWS owned key**
-Use a KMS key that is owned and managed by Amazon Translate\. This is the default option and is used to encrypt your information if you don't choose another method\. For more information, see [AWS owned keys](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-owned-cmk) in the *AWS Key Management Service Developer Guide*\.
-**Use key from current account**
-Use one of the KMS keys that you manage in AWS KMS in your AWS account\. If you choose this option, a menu provides a list of your KMS keys to choose from\. For more information, see [Customer managed keys](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk) in the *AWS Key Management Service Developer Guide*\.
-**Use key from different account**
-Use a KMS key that is managed in AWS KMS in a different AWS account\. If you choose this option, the console provides a field for you to enter the Amazon Resource Name \(ARN\) of the KMS key\.
-
- For more information about encryption keys, see the *[AWS Key Management Service Developer Guide](https://docs.aws.amazon.com/kms/latest/developerguide/)*\.
-
-1. Choose **Create parallel data**\.
-
- The console returns to the **Parallel data** page, where the import status is shown in a banner at the top of the page\. After a few minutes, your parallel data resource is shown in the table\. When the value in the **Status** column is **Active**, the parallel data is ready for you to use in a batch translation job\.
-
-### Error file for troubleshooting
-
-If Amazon Translate generates any errors or warnings while processing your input file, the console provides an error file that you can download to review the error messages\. The contents of this file resemble the following example:
-
-```
-{
- "summary": {
- "record_error_count": 1,
- "record_skipped_count": 0
- },
- "messages": [
- {
- "content": "Number 1 TU element",
- "message": "Invalid TMX format. One tu element should contain exactly one tuv element with the source language code: en"
- }
- ]
-}
-```
-
-## Adding parallel data \(AWS CLI\)
-
-To add parallel data by using the AWS CLI, use the `create-parallel-data` command\.
-
-**Example create\-parallel\-data command**
-The following example creates a parallel data object by importing a TSV file from Amazon S3:
-
-```
-$ aws translate create-parallel-data \
-> --name my-parallel-data \
-> --parallel-data-config S3Uri=s3://input-bucket/parallel-data-file.tsv,Format=TSV
-```
-If the command succeeds, Amazon Translate responds with the status of the new parallel data object:
-
-```
-{
- "Name": "my-parallel-data",
- "Status": "CREATING"
-}
-```
-You can monitor the ongoing status of the parallel data by using the `get-parallel-data` command\. When the status is `ACTIVE`, the parallel data is ready for you to use in a batch translation job\. For an example of the `get-parallel-data` command, see [To view the details for a parallel data object](customizing-translations-parallel-data-managing.md#customizing-translations-parallel-data-managing-cli-get)\.
-
-## Using your parallel data
-
-Now that you have created a parallel data resource, you can apply it to a batch translation job to customize the output\. To run a batch job, see [Running a batch translation job](async-start.md)\.
\ No newline at end of file
diff --git a/doc_source/customizing-translations-parallel-data-input-files.md b/doc_source/customizing-translations-parallel-data-input-files.md
deleted file mode 100644
index ce2c66a..0000000
--- a/doc_source/customizing-translations-parallel-data-input-files.md
+++ /dev/null
@@ -1,176 +0,0 @@
-# Parallel data input files for Amazon Translate
-
-Before you can create a parallel data resource in Amazon Translate, you must create an input file that contains your translation examples\. Your parallel data input file must use languages that Amazon Translate supports\. For a list of these languages, see [Supported languages and language codes](what-is-languages.md)\.
-
-## Example parallel data
-
-The text in the following table provides examples of translation segments that can be formatted into a parallel data input file:
-
-
-| en | es | zh |
-| --- | --- | --- |
-| Amazon Translate is a neural machine translation service\. | Amazon Translate es un servicio de traducción automática basado en redes neuronales\. | Amazon Translate 是一项神经机器翻译服务。 |
-| Neural machine translation is a form of language translation automation that uses deep learning models\. | La traducción automática neuronal es una forma de automatizar la traducción de lenguajes utilizando modelos de aprendizaje profundo\. | 神经机器翻译使用深度学习模型，是一种语言翻译自动化的形式。 |
-| Amazon Translate allows you to localize content for international users\. | Amazon Translate le permite localizar contenido para usuarios internacionales\. | Amazon Translate 允许您为国际用户本地化内容。 |
-
-The first row of the table provides the language codes\. The first language, English \(en\), is the source language\. Spanish \(es\) and Chinese \(zh\) are the target languages\. The first column provides examples of source text\. The other columns contain examples of translations\. When this parallel data customizes a batch job, Amazon Translate adapts the translation to reflect the examples\.
-
-## Input file formats
-
-Amazon Translate supports the following formats for parallel data input files:
-+ Translation Memory eXchange \(TMX\)
-+ Comma\-separated values \(CSV\)
-+ Tab\-separated values \(TSV\)
-
-------
-#### [ TMX ]
-
-
-
-**Example TMX input file**
-The following example TMX file defines parallel data in a format that Amazon Translate accepts\. In this file, English \(`en`\) is the source language\. Spanish \(`es`\) and Chinese \(`zh`\) are the target languages\. As an input file for parallel data, it provides several examples that Amazon Translate can use to tailor the output of a batch job\.
-
-```
-
-
-
-
-
-
- Amazon Translate is a neural machine translation service.
-
-
- Amazon Translate es un servicio de traducción automática basado en redes neuronales.
-
-
- Amazon Translate 是一项神经机器翻译服务。
-
-
-
-
- Neural machine translation is a form of language translation automation that uses deep learning models.
-
-
- La traducción automática neuronal es una forma de automatizar la traducción de lenguajes utilizando modelos de aprendizaje profundo.
-
-
- 神经机器翻译使用深度学习模型，是一种语言翻译自动化的形式。
-
-
-
-
- Amazon Translate allows you to localize content for international users.
-
-
- Amazon Translate le permite localizar contenido para usuarios internacionales.
-
-
- Amazon Translate 允许您为国际用户本地化内容。
-
-
-
-
-```
-
-**TMX requirements**
-
-Remember the following requirements from Amazon Translate when you define your parallel data in a TMX file:
-+ Amazon Translate supports TMX 1\.4b\. For more information, see the [TMX 1\.4b specification](https://www.gala-global.org/tmx-14b#SectionReferences) on the Globalization and Localization Association website\.
-+ The `header` element must include the `srclang` attribute\. The value of this attribute determines the source language of the parallel data\.
-+ The `body` element must contain at least one translation unit \(`tu`\) element\.
-+ Each `tu` element must contain at least two translation unit variant \(`tuv`\) elements\. One of these `tuv` elements must have an `xml:lang` attribute that has the same value as the one assigned to the `srclang` attribute in the `header` element\.
-+ All `tuv` elements must have the `xml:lang` attribute\.
-+ All `tuv` elements must have a segment \(`seg`\) element\.
-+ While processing your input file, Amazon Translate skips certain `tu` or `tuv` elements if it encounters `seg` elements that are empty or contain only white space:
- + If the `seg` element corresponds to the source language, Amazon Translate skips the `tu` element that the `seg` element occupies\.
- + If the `seg` element corresponds to a target language, Amazon Translate skips only the `tuv` element that the `seg` element occupies\.
-+ While processing your input file, Amazon Translate skips certain `tu` or `tuv` elements if it encounters `seg` elements that exceed 1000 bytes:
- + If the `seg` element corresponds to the source language, Amazon Translate skips the `tu` element that the `seg` element occupies\.
- + If the `seg` element corresponds to a target language, Amazon Translate skips only the `tuv` element that the `seg` element occupies\.
-+ If the input file contains multiple `tu` elements with the same source text, Amazon Translate does one of the following:
- + If the `tu` elements have the `changedate` attribute, it uses the element with the most recent date\.
- + Otherwise, it uses the element that occurs closest to the end of the file\.
-
-------
-#### [ CSV ]
-
-The following example CSV file defines parallel data in a format that Amazon Translate accepts\. In this file, English \(`en`\) is the source language\. Spanish \(`es`\) and Chinese \(`zh`\) are the target languages\. As an input file for parallel data, it provides several examples that Amazon Translate can use to tailor the output of a batch job\.
-
-**Example CSV input file**
-
-```
-en,es,zh
-Amazon Translate is a neural machine translation service.,Amazon Translate es un servicio de traducción automática basado en redes neuronales.,Amazon Translate 是一项神经机器翻译服务。
-Neural machine translation is a form of language translation automation that uses deep learning models.,La traducción automática neuronal es una forma de automatizar la traducción de lenguajes utilizando modelos de aprendizaje profundo.,神经机器翻译使用深度学习模型，是一种语言翻译自动化的形式。
-Amazon Translate allows you to localize content for international users.,Amazon Translate le permite localizar contenido para usuarios internacionales.,Amazon Translate 允许您为国际用户本地化内容。
-```
-
-**CSV requirements**
-
-Remember the following requirements from Amazon Translate when you define your parallel data in a CSV file:
-+ The first row consists of the language codes\. The first code is the source language, and each subsequent code is a target language\.
-+ Each field in the first column contains source text\. Each field in a subsequent column contains a target translation\.
-+ If the text in any field contains a comma, the text must be enclosed in double quote \("\) characters\.
-+ A text field cannot span multiple lines\.
-+ Fields cannot start with the following characters: \+, \-, =, @\. This requirement applies whether or not the field is enclosed in double quotes \("\)\.
-+ If the text in a field contains a double quote \("\), it must be escaped with a double quote\. For example, text such as:
-
- ```
- 34" monitor
- ```
-
- Must be written as:
-
- ```
- 34"" monitor
- ```
-+ While processing your input file, Amazon Translate will skip certain lines or fields if it encounters fields that are empty or contain only white space:
- + If a source text field is empty, Amazon Translate skips the line that it occupies\.
- + If a target translation field is empty, Amazon Translate skips only that field\.
-+ While processing your input file, Amazon Translate skips certain lines or fields if it encounters fields that exceed 1000 bytes:
- + If a source text field exceeds the byte limit, Amazon Translate skips the line that it occupies\.
- + If a target translation field exceeds the byte limit, Amazon Translate skips only that field\.
-+ If the input file contains multiple records with the same source text, Amazon Translate uses the record that occurs closest to the end of the file\.
-
-------
-#### [ TSV ]
-
-The following example TSV file defines parallel data in a format that Amazon Translate accepts\. In this file, English \(`en`\) is the source language\. Spanish \(`es`\) and Chinese \(`zh`\) are the target languages\. As an input file for parallel data, it provides several examples that Amazon Translate can use to tailor the output of a batch job\.
-
-**Example TSV input file**
-
-```
-en es zh
-Amazon Translate is a neural machine translation service. Amazon Translate es un servicio de traducción automática basado en redes neuronales. Amazon Translate 是一项神经机器翻译服务。
-Neural machine translation is a form of language translation automation that uses deep learning models. La traducción automática neuronal es una forma de automatizar la traducción de lenguajes utilizando modelos de aprendizaje profundo. 神经机器翻译使用深度学习模型，是一种语言翻译自动化的形式。
-Amazon Translate allows you to localize content for international users. Amazon Translate le permite localizar contenido para usuarios internacionales. Amazon Translate 允许您为国际用户本地化内容。
-```
-
-**TSV requirements**
-
-Remember the following requirements from Amazon Translate when you define your parallel data in a TSV file:
-+ The first row consists of the language codes\. The first code is the source language, and each subsequent code is a target language\.
-+ Each field in the first column contains source text\. Each field in a subsequent column contains a target translation\.
-+ If the text in any field contains a tab character, the text must be enclosed in double quote \("\) characters\.
-+ A text field cannot span multiple lines\.
-+ Fields cannot start with the following characters: \+, \-, =, @\. This requirement applies whether or not the field is enclosed in double quotes \("\)\.
-+ If the text in a field contains a double quote \("\), it must be escaped with a double quote\. For example, text such as:
-
- ```
- 34" monitor
- ```
-
- Must be written as:
-
- ```
- 34"" monitor
- ```
-+ While processing your input file, Amazon Translate skips certain lines or fields if it encounters fields that are empty or contain only white space:
- + If a source text field is empty, Amazon Translate skips the line that it occupies\.
- + If a target translation field is empty, Amazon Translate skips only that field\.
-+ While processing your input file, Amazon Translate skips certain lines or fields if it encounters fields that exceed 1000 bytes:
- + If a source text field exceeds the byte limit, Amazon Translate skips the line that it occupies\.
- + If a target translation field exceeds the byte limit, Amazon Translate skips only that field\.
-+ If the input file contains multiple records with the same source text, Amazon Translate uses the record that occurs closest to the end of the file\.
-
-------
\ No newline at end of file
diff --git a/doc_source/customizing-translations-parallel-data-managing.md b/doc_source/customizing-translations-parallel-data-managing.md
deleted file mode 100644
index 3e16419..0000000
--- a/doc_source/customizing-translations-parallel-data-managing.md
+++ /dev/null
@@ -1,143 +0,0 @@
-# Viewing and managing your parallel data in Amazon Translate
-
-You can view all of the parallel data resources that you have added to Amazon Translate, and you can access detailed summaries for each one\. As your translation requirements change, you can refine your translation output by updating your parallel data\.
-
-## Viewing and managing parallel data \(Amazon Translate console\)
-
-To view and manage your parallel data in the Amazon Translate console, use the **Parallel data** page:
-
-**To view a list of your of parallel data resources**
-
-1. Open the [Amazon Translate console](https://console.aws.amazon.com/translate/home)\.
-
-1. In the navigation menu on the left, choose **Customization**, and choose **Parallel data**\. The table on this page lists the parallel data resources that you have added to Amazon Translate\.
-
-**To view the details for a parallel data resource**
-+ On the **Parallel data** page, choose the name of the parallel data resource in the **Name** column\. The console opens the details page, which includes information such as the status, last updated date, source language, and target languages\.
-
-**To update a parallel data resource**
-
-1. Upload the updated version of your parallel data as a new input file in an Amazon S3 bucket\.
-
-1. In the Amazon Translate console, go to the **Parallel data** page\.
-
-1. Select the parallel data that you want to update, and choose **Update**\. The console shows the **Update parallel data** page\.
-
-1. Provide the following:
-**Description \- optional**
-An updated description\.
-**Parallel data location on S3**
-The location of the updated parallel data input file in Amazon S3\. To provide the location by navigating to the file in Amazon S3, choose **Select file**\.
-**Select parallel data file format**
-The format of the parallel data input file\. Supported formats are Translation Memory eXchange \(TMX\), comma\-separated values \(CSV\), and tab\-separated values \(TSV\)\.
-
-1. Choose **Save**\. Amazon Translate replaces the old parallel data with the new input file\.
-
-## Viewing and managing parallel data \(AWS CLI\)
-
-You can use the AWS CLI to view and update your parallel data resources\.
-
-### To view a list of your parallel data resources
-
-To view a list of the parallel data resources that you have added to Amazon Translate, use the `list-parallel-data` command\.
-
-**Example list\-parallel\-data command**
-The following example returns a list of parallel data resources and their properties\.
-
-```
-$ aws translate list-parallel-data
-```
-If the command succeeds, Amazon Translate returns an array like the following:
-
-```
-{
- "ParallelDataPropertiesList": [
- {
- "Name": "my-parallel-data",
- "Arn": "arn:aws:translate:us-west-2:111122223333:parallel-data/my-parallel-data",
- "Status": "ACTIVE",
- "SourceLanguageCode": "en",
- "TargetLanguageCodes": [
- "es",
- "ja",
- "zh"
- ],
- "ParallelDataConfig": {
- "S3Uri": "s3://input-bucket/parallel-data-file.tsv",
- "Format": "TSV"
- },
- "ImportedDataSize": 2283,
- "ImportedRecordCount": 3,
- "FailedRecordCount": 0,
- "CreatedAt": 1598597751.406,
- "LastUpdatedAt": 1598597911.675
- }
- ]
-}
-```
-
-### To view the details for a parallel data object
-
-To look up the details for a single parallel data resource, use the `get-parallel-data` command\. This command returns the properties of the parallel data as well as a pre\-signed S3 URL where you can download the input file that was used to create it\.
-
-**Example get\-parallel\-data command**
-The following example gets the properties and download location for the `my-parallel-data` object:
-
-```
-$ aws translate get-parallel-data \
-> --name my-parallel-data
-```
-If the command succeeds, Amazon Translate returns the properties and download location:
-
-```
-{
- "ParallelDataProperties": {
- "Name": "my-parallel-data",
- "Arn": "arn:aws:translate:us-west-2:111122223333:parallel-data/my-parallel-data",
- "Status": "ACTIVE",
- "SourceLanguageCode": "en",
- "TargetLanguageCodes": [
- "es",
- "ja",
- "zh"
- ],
- "ParallelDataConfig": {
- "S3Uri": "s3://input-bucket/parallel-data-file.tsv",
- "Format": "TSV"
- },
- "ImportedDataSize": 2283,
- "ImportedRecordCount": 3,
- "FailedRecordCount": 0,
- "CreatedAt": 1598597751.406,
- "LastUpdatedAt": 1598597911.675
- },
- "DataLocation": {
- "RepositoryType": "S3",
- "Location": "pre-signed S3 URL"
- }
-}
-```
-
-### To update a parallel data resource
-
-To update a parallel data resource, first, upload a new input file to an Amazon S3 input bucket\. Then, use the `update-parallel-data` command and specify the parallel data resource that you want to update\. Amazon Translate replaces the old parallel data with the information that's in the new input file\.
-
-**Example update\-parallel\-data command**
-The following command updates `my-parallel-data` with a new input file from Amazon S3:
-
-```
-$ aws translate update-parallel-data \
-> --name my-parallel-data \
-> --parallel-data-config S3Uri=s3://input-bucket/parallel-data-file.tsv,Format=TSV
-```
-If the command succeeds, Amazon Translate provides a response like the following:
-
-```
-{
- "Name": "my-parallel-data",
- "Status": "ACTIVE",
- "LatestUpdateAttemptStatus": "UPDATING",
- "LatestUpdateAttemptAt": 1598601455.844
-}
-```
-In this response, the `Status` field provides the status of the preexisting parallel data object, and the `LatestUpdateAttemptStatus` field provides the status of the current update attempt\.
\ No newline at end of file
diff --git a/doc_source/customizing-translations-parallel-data.md b/doc_source/customizing-translations-parallel-data.md
deleted file mode 100644
index 64a7796..0000000
--- a/doc_source/customizing-translations-parallel-data.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# Customizing your translations with parallel data \(Active Custom Translation\)
-
-Add *parallel data* to Amazon Translate to customize the output of your batch translations jobs\. Parallel data consists of examples that show how you want segments of text to be translated\. It includes a collection of textual examples in a source language, and for each example, it contains the desired translation output in one or more target languages\.
-
-When you add parallel data to a batch translation job, you create an *Active Custom Translation* job\. When you run these jobs, Amazon Translate uses your parallel data at runtime to produce customized machine translation output\. It adapts the translation to reflect the style, tone, and word choices that it finds in your parallel data\. With parallel data, you can tailor your translations for terms or phrases that are unique to a specific domain, such as life sciences, law or finance\.
-
-**Note**
-Active Custom Translation jobs are priced at a higher rate than other jobs that don't use parallel data\. For more information, see [Amazon Translate pricing](http://aws.amazon.com/translate/pricing/)\.
-
-For example, the following parallel data is defined in a CSV file:
-
-```
-"en","fr"
-"How are you?","Comment ça va ?"
-```
-
-In this example, English \(`en`\) is the source language, and French \(`fr`\) is the target language\. The example shows how the source phrase "How are you?" should be translated into French\. After this example input file is imported into Amazon Translate, it can be applied to translation jobs to influence their output\. During such jobs, Amazon Translate translates "How are you?" into the informal “Comment ça va ?” as opposed to the formal “Comment allez\-vous ?” For example, the job might receive the following source text:
-
-```
-Hello, how are you?
-How are you?
-Hi, how are you?
-How are you doing?
-```
-
-From this text, the job produces the following translation:
-
-```
-Bonjour, comment ça va ?
-Comment ça va ?
-Salut, comment ça va ?
-Comment ça va ?
-```
-
-In contrast, if the job runs without the parallel data, the output might include the more formal "comment allez\-vous":
-
-```
-Bonjour, comment allez-vous ?
-Comment allez-vous ?
-Salut, comment allez-vous ?
-Comment allez-vous ?
-```
-
-By customizing your batch translation jobs with parallel data, you influence the output in a way that's similar to using a custom translation model that you train with your translation examples\. With Active Custom Translation, training a custom model is unnecessary, and you avoid the time and expense that such training requires\. As your translation requirements change over time, you can refine your output by updating your parallel data, which is easier than retraining a custom model\.
-
-## Region availability
-
-Active Custom Translation is available in the following regions:
-+ US East \(N\. Virginia\)
-+ US West \(Oregon\)
-+ Europe \(Ireland\)
-
-**Topics**
-+ [Region availability](#customizing-translations-parallel-data-regions)
-+ [Parallel data input files for Amazon Translate](customizing-translations-parallel-data-input-files.md)
-+ [Adding your parallel data to Amazon Translate](customizing-translations-parallel-data-adding.md)
-+ [Viewing and managing your parallel data in Amazon Translate](customizing-translations-parallel-data-managing.md)
\ No newline at end of file
diff --git a/doc_source/customizing-translations-profanity.md b/doc_source/customizing-translations-profanity.md
deleted file mode 100644
index 87f79f9..0000000
--- a/doc_source/customizing-translations-profanity.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Masking profane words and phrases in Amazon Translate
-
-When you run translations with Amazon Translate, you can enable the *profanity* setting to mask profane words and phrases in your translation output\.
-
-To mask profane words and phrases, Amazon Translate replaces them with the grawlix string “?$\#@$“\. This 5\-character sequence is used for each profane word or phrase, regardless of the length or number of words\.
-
-Amazon Translate does not mask profanity in translation requests where the source language and target language are the same\.
-
-In some cases, a profane word in the source input might naturally become inoffensive in the translated output\. In such cases, no masking is applied\.
-
-Amazon Translate detects each profane word or phrase literally, not contextually\. This means that it might mask a profane word even if it’s inoffensive in context\. For example, if Amazon Translate detected “jerk” as a profane word, then it would write the phrase “jerk chicken” as “?$\#@$ chicken”, even though “jerk chicken” is inoffensive\. \(Here, “jerk” is used as an example only\. Amazon Translate does not detect that word as profanity\.\)
-
-**Topics**
-+ [Using the profanity setting](#customizing-translations-profanity-using)
-+ [Unsupported languages](#customizing-translations-profanity-languages)
-
-## Using the profanity setting
-
-You can use the profanity setting with both types of translation operations in Amazon Translate: real\-time translation and asynchronous batch processing\.
-
-To mask profanity in a real\-time translation request, do any of the following:
-+ On the **Real\-time translation** page in the Amazon Translate console, under **Additional settings**, enable the **Profanity** setting\.
-+ For `translate-text` command in the AWS CLI, set the `--settings` parameter to `Profanity=MASK`\. For more information, see [TranslateText](https://docs.aws.amazon.com/translate/latest/APIReference/API_TranslateText.html) in the *AWS CLI Command Reference*\.
-+ Use the Settings parameter in the [TranslateText](http://amazonaws.com/translate/latest/dg/API_TranslateText.html) action in the Amazon Translate API\.
-
-To mask profanity in an asynchronous batch operation, see [Running a batch translation job](async-start.md)\.
-
-## Unsupported languages
-
-You can mask profanity when you translate to any of the target languages that Amazon Translate supports, with the following exceptions:
-
-
-| Language | Language code |
-| --- | --- |
-| Bengali | bn |
-| Hindi | hi |
-| Malayalam | ml |
-| Punjabi | pa |
-| Sinhala | si |
-| Vietnamese | vi |
-
-For all of the languages that Amazon Translate supports, see [Supported languages and language codes](what-is-languages.md)\.
\ No newline at end of file
diff --git a/doc_source/customizing-translations-tags.md b/doc_source/customizing-translations-tags.md
deleted file mode 100644
index 4294fd3..0000000
--- a/doc_source/customizing-translations-tags.md
+++ /dev/null
@@ -1,52 +0,0 @@
-# Using do\-not\-translate tags in Amazon Translate
-
-You can add tags in your input content to specify text that you do not want to translate\. This feature is available for the console and for API operations\.
-
-**Topics**
-+ [Using do\-not\-translate with the console](#console-tags)
-+ [Using do\-not\-translate with the API](#api-tags)
-
-## Using do\-not\-translate with the console
-
-In the source text, use span tags to surround any text that you do not want to translate\. For example, to translate the following text from English to Italian:
-
-```
-Musée du Louvre, that's how you say Louvre Museum in French.
-```
-
-The text “Musée du Louvre” needs to remain in French, so we use a span tag around this content to skip translation:
-
-```
-Musée du Louvre, that's how you say Louvre Museum in French.
-```
-
-This sentence has the resulting Italian translation:
-
-```
-Musée du Louvre, così si dice Museo del Louvre in francese.
-```
-
-## Using do\-not\-translate with the API
-
-You can use do\-not\-translate with the real\-time `TranslateText` and the asynchronous `TextTranslation` API operations\. In the source text that you provide for the API request, you can use any type of HTML element to specify content that needs to skip translation\.
-
-In the following example, we translate some text from English to Spanish, but leave some text in English:
-
-```
-aws translate translate-text \
- --source-language-code "en" \
- --target-language-code "es" \
- --region us-west-2 \
- --text "This can be translated to any language.
But do not translate this!
"
-```
-
-This API request returns the following Spanish translation:
-
-```
-{
- "TranslatedText": "Esto se puede traducir a cualquier idioma.
-
But do not translate this!
",
- "SourceLanguageCode": "en",
- "TargetLanguageCode": "es"
-}
-```
\ No newline at end of file
diff --git a/doc_source/customizing-translations.md b/doc_source/customizing-translations.md
deleted file mode 100644
index 32f1278..0000000
--- a/doc_source/customizing-translations.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Customizing your translations with Amazon Translate
-
-You can use the following settings to customize the translations that you produce with Amazon Translate:
-+ **Do\-not\-translate tags** – Use start and end tags to specify content that you do not want to translate\.
-+ **Custom terminology** – Defines how you want Amazon Translate to translate specific terms, such as brand names\.
-+ **Profanity** – Enable this option to mask profane words and phrases in your translation output\.
-+ **Formality** – Enable this option to set the level of language formality in your translation output\.
-+ **Parallel data** – Consists of segments of example source text and their translations\. When you customize a job with parallel data, Amazon Translate adapts the translation output to reflect the style, tone, and word choices that it finds in the example translations\.
-
-**Topics**
-+ [Using do\-not\-translate tags in Amazon Translate](customizing-translations-tags.md)
-+ [Customizing your translations with custom terminology](how-custom-terminology.md)
-+ [Masking profane words and phrases in Amazon Translate](customizing-translations-profanity.md)
-+ [Setting formality in Amazon Translate](customizing-translations-formality.md)
-+ [Customizing your translations with parallel data \(Active Custom Translation\)](customizing-translations-parallel-data.md)
\ No newline at end of file
diff --git a/doc_source/data-protection.md b/doc_source/data-protection.md
deleted file mode 100644
index 497dca5..0000000
--- a/doc_source/data-protection.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Data protection in Amazon Translate
-
-Amazon Translate conforms to the AWS [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/), which includes regulations and guidelines for data protection\. AWS is responsible for protecting the global infrastructure that runs all of the AWS services\. AWS maintains control over data hosted on this infrastructure, including the security configuration controls for handling customer content and personal data\. AWS customers and APN partners, acting either as data controllers or data processors, are responsible for any personal data that they put in the AWS Cloud\.
-
-For data protection purposes, we recommend that you protect AWS account credentials and set up individual user accounts with AWS Identity and Access Management \(IAM\), so that each user is given only the permissions necessary to fulfill their job duties\. We also recommend that you secure your data in the following ways:
-+ Use multi\-factor authentication \(MFA\) with each account\.
-+ Use SSL/TLS to communicate with AWS resources\.
-+ Set up API and user activity logging with AWS CloudTrail\.
-+ Use AWS encryption solutions, along with all default security controls within AWS services\.
-+ Use advanced managed security services such as Amazon Macie, which assists in discovering and securing personal data that is stored in Amazon Simple Storage Service \(Amazon S3\)\.
-
-We strongly recommend that you never put sensitive identifying information, such as your customers' account numbers, into free\-form fields such as a **Name** field\. This includes when you work with Amazon Translate or other AWS services using the console, API, AWS CLI, or AWS SDKs\. Any data that you enter into Amazon Translate or other services might get picked up for inclusion in diagnostic logs\. When you provide a URL to an external server, don't include credentials information in the URL to validate your request to that server\.
-
-For more information about data protection, see the [AWS Shared Responsibility Model and GDPR](https://aws.amazon.com/blogs/security/the-aws-shared-responsibility-model-and-gdpr/) blog post on the *AWS Security Blog*\.
-
-**Topics**
-+ [Encryption at rest](encryption-at-rest.md)
-+ [Encryption in transit](encryption-in-transit.md)
\ No newline at end of file
diff --git a/doc_source/disaster-recovery-resiliency.md b/doc_source/disaster-recovery-resiliency.md
deleted file mode 100644
index 3eb6d32..0000000
--- a/doc_source/disaster-recovery-resiliency.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Resilience in Amazon Translate
-
-The AWS global infrastructure is built around AWS Regions and Availability Zones\. AWS Regions provide multiple physically separated and isolated Availability Zones, which are connected with low\-latency, high\-throughput, and highly redundant networking\. With Availability Zones, you can design and operate applications and databases that automatically fail over between Availability Zones without interruption\. Availability Zones are more highly available, fault tolerant, and scalable than traditional single or multiple data center infrastructures\.
-
-For more information about AWS Regions and Availability Zones, see [AWS Global Infrastructure](http://aws.amazon.com/about-aws/global-infrastructure/)\.
\ No newline at end of file
diff --git a/doc_source/doc-history.md b/doc_source/doc-history.md
deleted file mode 100644
index f63c3bc..0000000
--- a/doc_source/doc-history.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# Document history for Amazon Translate
-
-The following table describes the documentation for this release of Amazon Translate\.
-
-| Change | Description | Date |
-| --- |--- |--- |
-| [Support for nested input folders for batch mode](https://docs.aws.amazon.com/translate/latest/dg/async-start.html) | You can now provide nested input folders to batch translation jobs\. For more information, see [Running a batch translation job](https://docs.aws.amazon.com/translate/latest/dg/async-start.html) in Amazon Translate\. | November 18, 2022 |
-| [Support for auto\-language detection for batch mode](https://docs.aws.amazon.com/translate/latest/dg/async-start.html) | You can now auto\-detect the source language in batch translation jobs\. As a result, you can now input documents with different source languages in batch translation jobs\. For more information, see [Running a batch translation job](https://docs.aws.amazon.com/translate/latest/dg/async-start.html) in Amazon Translate\. | November 18, 2022 |
-| [Support for multiple target languages](https://docs.aws.amazon.com/translate/latest/dg/async-start.html) | You can now specify multiple target languages in batch translation jobs\. For more information, see [Running a batch translation job](https://docs.aws.amazon.com/translate/latest/dg/async-start.html) in Amazon Translate\. | October 10, 2022 |
-| [Support for tags](https://docs.aws.amazon.com/translate/latest/dg/tagging.html) | You can now tag **ParallelData** and **Custom Terminology** resources in Amazon Translate\. For more information, see [Tagging your resources in Amazon Translate](https://docs.aws.amazon.com/translate/latest/dg/tagging.html)\. | October 6, 2022 |
-| [Formality support for additional languages](https://docs.aws.amazon.com/translate/latest/dg/customizing-translations-formality.html) | You can now set the translation formality level for Dutch, Korean, and Mexican Spanish in Amazon Translate\. For more information, see [Setting formality in Amazon Translate](https://docs.aws.amazon.com/translate/latest/dg/customizing-translations-formality.html)\. | October 5, 2022 |
-| [Separate API Reference](https://docs.aws.amazon.com/translate/latest/APIReference/Welcome.html) | The Amazon Translate API Reference is now a separate document from the Developer Guide\. For more information, see [Amazon Translate API Reference](https://docs.aws.amazon.com/translate/latest/APIReference/Welcome.html)\. | August 25, 2022 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/customizing-translations-formality.html) | You can now set the formality level for your translation output\. For more information, see [Setting formality in Amazon Translate](https://docs.aws.amazon.com/translate/latest/dg/customizing-translations-formality.html)\. | February 22, 2022 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/customizing-translations-profanity.html) | You can now mask profane words and phrases in your translation output\. For more information, see [Masking profane words and phrases in Amazon Translate](https://docs.aws.amazon.com/translate/latest/dg/customizing-translations-profanity.html)\. | November 24, 2021 |
-| [AWS PrivateLink support](https://docs.aws.amazon.com/translate/latest/dg/vpc-interface-endpoints.html) | You can now establish a private connection between your VPC and Amazon Translate by using AWS PrivateLink\. For more information, see [Amazon Translate and interface VPC endpoints \(AWS PrivateLink\)](https://docs.aws.amazon.com/translate/latest/dg/vpc-interface-endpoints.html)\. | November 24, 2021 |
-| [Parallel data update](https://docs.aws.amazon.com/translate/latest/dg/customizing-translations-parallel-data.html) | You can now create parallel data resources that use any of the languages that are supported by Amazon Translate\. You no longer need to use English as one of the languages\. For more information about parallel data, see [Customizing your translations with parallel data \(Active Custom Translation\)](https://docs.aws.amazon.com/translate/latest/dg/customizing-translations-parallel-data.html)\. | November 15, 2021 |
-| [Custom terminology directionality](https://docs.aws.amazon.com/translate/latest/dg/creating-custom-terminology.html) | You can now create multi\-directional terminology, in which any language can be the source language or a target language\. For more information, see [Creating a custom terminology](https://docs.aws.amazon.com/translate/latest/dg/creating-custom-terminology.html)\. | November 11, 2021 |
-| [New languages](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate now supports the following languages: Irish, Marathi, Portuguese \(Portugal\), and Punjabi\. For all of the languages that Amazon Translate supports, see [Supported languages and language codes](https://docs.aws.amazon.com/translate/latest/dg/what-is.html)\. | November 10, 2021 |
-| [New custom encryption settings](https://docs.aws.amazon.com/translate/latest/dg/async-start.html) | You can now encrypt your translation output by using your own customer managed key that you manage in AWS Key Management Service\. For more information, see [Running a batch translation job](https://docs.aws.amazon.com/translate/latest/dg/async-start.html) | November 5, 2021 |
-| [New file format support](https://docs.aws.amazon.com/translate/latest/dg/async-prereqs.html#async-prereqs-formats) | Amazon Translate now supports XML Localization Interchange File Format \(XLIFF\) files for asynchronous batch processing\. For all supported formats, see [Supported file formats](https://docs.aws.amazon.com/translate/latest/dg/async-prereqs.html#async-prereqs-formats)\. | June 9, 2021 |
-| [EventBridge integration](https://docs.aws.amazon.com/translate/latest/dg/monitoring-with-eventbridge.html) | Amazon Translate now sends events to Amazon EventBridge to notify you about changes that affect your translation jobs and parallel data resources\. For more information, see [Monitoring Amazon Translate events with Amazon EventBridge](https://docs.aws.amazon.com/translate/latest/dg/monitoring-with-eventbridge.html)\. | June 4, 2021 |
-| [New quota](https://docs.aws.amazon.com/translate/latest/dg/what-is-limits.html) | Amazon Translate now supports up to 1000 queued batch translation jobs\. For all Amazon Translate quotas, see [Guidelines and limits](https://docs.aws.amazon.com/translate/latest/dg/what-is-limits.html)\. | April 23, 2021 |
-| [Quota increase](https://docs.aws.amazon.com/translate/latest/dg/what-is-limits.html) | The maximum size for a parallel data input file has increased from 1 MB to 5 MB\. For all Amazon Translate quotas, see [Guidelines and limits](https://docs.aws.amazon.com/translate/latest/dg/what-is-limits.html)\. | March 31, 2021 |
-| [New languages](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate now supports the following languages: Armenian, Catalan, Farsi \(Persian\), Filipino Tagalog, Gujarati, Haitian Creole, Icelandic, Kannada, Kazakh, Lithuanian, Macedonian, Malayalam, Maltese, Mongolian, Sinhala, Telugu, Uzbek, and Welsh\. For all of the languages that Amazon Translate supports, see [Supported languages and language codes](https://docs.aws.amazon.com/translate/latest/dg/what-is.html)\. | November 23, 2020 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/customizing-translations-parallel-data.html) | You can now customize batch translation jobs by using *parallel data*, which consists of examples of source text and their translations\. Jobs that use parallel data are called *Active Custom Translation* jobs\. During these jobs, Amazon Translate adapts the translation output to reflect the examples in the parallel data\. For more information, see [Customizing your translations with parallel data \(Active Custom Translation\)](https://docs.aws.amazon.com/translate/latest/dg/customizing-translations-parallel-data.html)\. | November 23, 2020 |
-| [New file format support](https://docs.aws.amazon.com/translate/latest/dg/async.html#async-start) | Amazon Translate now supports the following Office Open XML file formats as input for asynchronous batch processing: Word document \(\.docx\), PowerPoint presentation \(\.pptx\), Excel workbook \(\.xlsx\)\. For more information, see [Starting a batch translation job](https://docs.aws.amazon.com/translate/latest/dg/async.html#async-start)\. | July 29, 2020 |
-| [New language](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate now supports the Spanish \(Mexico\) language for translation\. For all supported languages, see [Supported languages and language codes](https://docs.aws.amazon.com/translate/latest/dg/what-is.html)\. | April 30, 2020 |
-| [New region](https://docs.aws.amazon.com/translate/latest/dg/async.html#async-regions) | Amazon Translate supports asynchronous batch processing in the Europe \(London\) Region\. For all of the AWS regions where asynchronous batch processing is available, see [Region availability](https://docs.aws.amazon.com/translate/latest/dg/async.html#async-regions)\. | April 20, 2020 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/async.html) | Amazon Translate adds asynchronous batch translation functionality\. For more information, see [Asynchronous batch processing](https://docs.aws.amazon.com/translate/latest/dg/async.html)\. | December 23, 2019 |
-| [New regions](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds support for the Asia Pacific \(Hong Kong\), Asia Pacific \(Sydney\), EU \(London\), EU \(Paris\), EU \(Stockholm\), and US West \(N\. California\) Regions\. For a complete list of the AWS Regions supported by Amazon Translate, see the [AWS Region Table](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/) or [AWS Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html#translate_region) in the *Amazon Web Services General Reference*\. | November 25, 2019 |
-| [New languages](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds new language for translation: Afrikaans, Albanian, Amharic, Azerbaijani, Bengali, Bosnian, Bulgarian, Canadian\-French, Croatian, Dari, Estonian, Georgian, Hausa, Latvian, Pashto, Serbian, Slovak, Slovenian, Somali, Swahili, Tagalog, and Tamil\. For a list of the language combinations that Amazon Translate can translate directly, see [Supported languages](https://docs.aws.amazon.com/translate/latest/dg/what-is.html)\. | November 25, 2019 |
-| [New languages](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds new languages for translation: Greek, Hungarian, Romanian, Thai, Ukrainian, Urdu, and Vietnamese\. For a list of the language combinations that Amazon Translate can translate directly, see [Supported languages](https://docs.aws.amazon.com/translate/latest/dg/what-is.html)\. | October 3, 2019 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds [FedRAMP compliance](https://www.fedramp.gov/)\. For more information, see [Compliance](https://docs.aws.amazon.com/translate/latest/dg/what-is-limits.html#what-is-compliance)\. | July 31, 2019 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds [SOC compliance](https://docs.aws.amazon.com/translate/latest/dg/what-is-limits.html#what-is-compliance)\. For more information, see [Compliance](https://docs.aws.amazon.com/translate/latest/dg/what-is-compliance.html)\. | May 30, 2019 |
-| [New regions](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds support for the Asia Pacific \(Mumbai\), Asia Pacific \(Singapore\), Asia Pacific \(Tokyo\), and Canada \(Central\) Regions\. For a complete list of the AWS Regions supported by Amazon Translate, see the [AWS Region Table](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/) or [AWS Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html#translate_region) in the *Amazon Web Services General Reference*\. | May 8, 2019 |
-| [New languages](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds new languages for translation: Hindi, Malay, Norwegian, and Persian\. For a list of the language combinations that Amazon Translate can translate directly, see [Supported languages](https://docs.aws.amazon.com/translate/latest/dg/what-is.html)\. | May 6, 2019 |
-| [New region](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds support for the EU \(Frankfurt\) and Asia Pacific \(Seoul\) Regions\. For a complete list of the AWS Regions supported by Amazon Translate, see the [AWS Region Table](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/) or [AWS Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html#translate_region) in the *Amazon Web Services General Reference*\. | February 28, 2019 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds [PCI compliance](https://www.pcisecuritystandards.org/)\. For more information, see [Compliance](https://docs.aws.amazon.com/translate/latest/dg/what-is-limits.html#what-is-compliance)\. | December 12, 2018 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/how-custom-terminology.html) | Amazon Translate adds four new APIs and the custom terminology feature to give you more control over your translation\. By using a custom terminology with your translation requests, you can make sure that your brand names, character names, model names, and other unique content is translated exactly the way you want it, every time, regardless of the standard translation or context\. For more information, see [Custom terminology](https://docs.aws.amazon.com/translate/latest/dg/how-custom-terminology.html)\. | November 27, 2018 |
-| [New languages](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate now translates documents in the following languages: Danish, Dutch, Finnish, Hebrew, Indonesian, Korean, Polish, and Swedish\. Amazon Translate continues to improve direct translation by significantly reducing the number of unsupported language pairs\. For the language combinations that Amazon Translate can translate directly, see [Supported languages](https://docs.aws.amazon.com/translate/latest/dg/what-is.html)\. | November 20, 2018 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds direct translation between supported languages other than English\. For the language combinations that Amazon Translate can translate directly, see [Supported languages](https://docs.aws.amazon.com/translate/latest/dg/what-is-languages.html)\. | October 29, 2018 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds [HIPAA](https://www.hhs.gov/hipaa/for-professionals/privacy/index.html) compliance\. For more information, see [Compliance](https://docs.aws.amazon.com/translate/latest/dg/what-is-limits.html#what-is-compliance)\. | October 25, 2018 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/what-is.html) | Amazon Translate adds multiple new languages for translation: Chinese \(Tradition\), Czech, Italian, Japanese, Russian, and Turkish\. For a list of languages that Amazon Translate supports, see [Supported languages](https://docs.aws.amazon.com/translate/latest/dg/what-is-languages.html)\. | July 17, 2018 |
-| [New feature](https://docs.aws.amazon.com/translate/latest/dg/how-it-works.html) | Amazon Translate adds support for automatic source language detection\. For more information, see [ How Amazon Translate works](https://docs.aws.amazon.com/translate/latest/dg/how-it-works.html)\. | April 4, 2018 |
-| [New guide](#doc-history) | This is the first release of the *Amazon Translate Developer Guide*\. | November 29, 2017 |
\ No newline at end of file
diff --git a/doc_source/encryption-at-rest.md b/doc_source/encryption-at-rest.md
deleted file mode 100644
index 071e279..0000000
--- a/doc_source/encryption-at-rest.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# Encryption at rest
-
-For the batch translation jobs that you run with Amazon Translate, your translation input and output are both encrypted at rest\. However, the encryption method is different for each\.
-
-Amazon Translate also uses an Amazon Elastic Block Store \(Amazon EBS\) volume encrypted with the default key\.
-
-## Translation input
-
-When you use Amazon Translate to translate documents in batch, you store a set of input documents in an Amazon S3 bucket\. To encrypt these documents at rest, you can use the SSE\-S3 server\-side encryption option that is provided by Amazon S3\. With this option, each object is encrypted with a unique key that is managed by Amazon S3\.
-
-For more information, see [Protecting data using server\-side encryption with Amazon S3\-managed encryption keys \(SSE\-S3\)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingServerSideEncryption.html) in the *Amazon Simple Storage Service User Guide*\.
-
-## Translation output
-
-When Amazon Translate completes a batch translation job, it puts the output in an Amazon S3 bucket in your AWS account\. To encrypt the output at rest, Amazon Translate uses the SSE\-KMS encryption option that is provided by Amazon S3\. With this option, your output is encrypted with a key that is stored in AWS Key Management Service \(AWS KMS\)\.
-
-For more information about SSE\-KMS, see [Protecting Data using server\-side encryption with AWS Key Management Service \(SSE\-KMS\)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html) in the *Amazon Simple Storage Service User Guide*\.
-
-For more information about KMS keys, see [AWS KMS keys](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms_keys) in the *AWS Key Management Service Developer Guide*\.
-
-For this encryption, Amazon Translate can use either of the following types of keys:
-
-**AWS managed key**
-By default, Amazon Translate uses an *AWS managed key*\. This type of KMS key is created by AWS and stored in your account\. However, you cannot manage this KMS key yourself\. It is managed and used on your behalf only by AWS\.
-
-**Customer managed key**
-Optionally, you can choose to encrypt your output with a *customer managed key*, which is a KMS key that you create, own, and manage in your AWS account\.
-Before you can use your own KMS key, you must add permissions to the IAM service role that Amazon Translate uses to access your output bucket in Amazon S3\. If you want to use a KMS key that's in a different AWS account, you must also update the key policy in AWS KMS\. For more information, see [Prerequisite permissions to customize encryption](async-prereqs.md#async-prereqs-permissions-custom-encryption)\.
-You can choose to use your customer managed key when you run a batch translation job\. For more information, see [Running a batch translation job](async-start.md)\.
\ No newline at end of file
diff --git a/doc_source/encryption-in-transit.md b/doc_source/encryption-in-transit.md
deleted file mode 100644
index f48698c..0000000
--- a/doc_source/encryption-in-transit.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# Encryption in transit
-
-To encrypt data in transit, Amazon Translate uses TLS 1\.2 with AWS certificates\.
\ No newline at end of file
diff --git a/doc_source/examples-ddb.md b/doc_source/examples-ddb.md
deleted file mode 100644
index b390364..0000000
--- a/doc_source/examples-ddb.md
+++ /dev/null
@@ -1,184 +0,0 @@
-# Using Amazon Translate with Amazon DynamoDB
-
-This example shows you how to translate a product review and store it in Amazon DynamoDB\. If you request the same review later, DynamoDB returns it without Amazon Translate needing to translate it again\.
-
-In this example, you:
-+ Use AWS CloudFormation to create DynamoDB tables to store the translation and a Lambda function that calls the [TranslateText](https://docs.aws.amazon.com/translate/latest/APIReference/API_TranslateText.html) operation\.
-+ Test the function using the AWS Lambda console\.
-
-**To run the example**
-
-1. Copy the contents of `example.py`, which you can find in [Python Lambda function](#examples-ddb-code-lambda), to a file named `example.py`\. `example.py` is a Lambda function that calls the [TranslateText](https://docs.aws.amazon.com/translate/latest/APIReference/API_TranslateText.html) operation\. Compress the file to a zip archive named `example.zip`\. Store it in an S3 bucket in the same AWS Region where you want to run the function\.
-
-1. Create a new file named `template.yaml`\. Copy the AWS CloudFormation template code, which you can find in [AWS CloudFormation template](#examples-ddb-code-yaml), into the file\. AWS CloudFormation uses the template to create resources for the sample application\. Change `BUCKET_NAME` to the name of the S3 bucket that contains `example.zip`\. Save the file in a local directory\.
-
-1. Sign in to the AWS Management Console and open the AWS CloudFormation console at [https://console\.aws\.amazon\.com/cloudformation](https://console.aws.amazon.com/cloudformation/)\.
-
-1. Choose **Create new stack**\.
-
-1. Choose **Upload a template to Amazon S3**, and then choose **Choose file**\. Choose `template.yaml`, that you created in Step 2, then **Next**\.
-
-1. Type a name for the stack, then choose **Next**\.
-
-1. On the **Options** page, choose **Next**\.
-
-1. Choose **I acknowledge that AWS CloudFormation might create IAM resources** and **I acknowledge that AWS CloudFormation might create IAM resources with custom names**\. For more information, see [Controlling Access with AWS Identity and Access Management](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-template.html) in the *AWS CloudFormation User Guide*\.
-
-1. Choose **Create Change Set**\.
-
-1. After AWS CloudFormation creates the change set, choose **Execute**\. Wait until AWS CloudFormation creates the stack\.
-
-1. Sign in to the AWS Management Console and open the AWS Lambda console at [https://console\.aws\.amazon\.com/lambda/](https://console.aws.amazon.com/lambda/)\.
-
-1. Choose the new function\. Its name starts with `TestTranslate-ReviewTranslate`\.
-
-1. On the function detail page, choose **Test**\.
-
-1. For **Event name**, type **TestTranslate**\. For **Configure test event**, replace the JSON with the following:
-
- ```
- {
- "review": "hello world",
- "target_language": "es",
- "source_language": "en",
- "review_id": "1"
- }
- ```
-
- Choose **Create**\.
-
-1. Make sure that **TestTranslate** is selected, then choose **Test**\. When the test finishes, you receive the following message:
-![\[A panel showing the results of the operation, "Hello world" in Spanish.\]](http://docs.aws.amazon.com/translate/latest/dg/images/example-3-results.png)
-
-## Example code
-
-Use the following code to create the example\.
-
-### Python Lambda function
-
-The following is the contents of the Python Lambda function\. The Lambda function call the `TranslateText` operation and passes the review, the source language, and the target language to get the translated review\. Save this file as `example.py` and them compress it in a \.zip archive called `example.zip`\. Save the file in an S3 bucket in the same region that you are running the example\.\.
-
-```
-import logging
-import json
-import boto3
-import os
-
-translate = boto3.client('translate')
-dynamodb = boto3.client('dynamodb')
-firehose = boto3.client('firehose')
-
-TABLE_NAME = os.getenv('TABLE_NAME')
-
-logger = logging.getLogger()
-logger.setLevel(logging.INFO)
-
-def lambda_handler(event, context):
-
- logger.info(event)
-
- if 'source_language' in event and 'target_language' in event and 'review' in event and 'review_id' in event:
- review_id = event['review_id']
- source_language = event['source_language']
- target_language = event['target_language']
- review = event['review']
-
- try:
- # The Lambda function queries the Amazon DynamoDB table to check whether
- # the review has already been translated. If the translated review
- # is already stored in Amazon DynamoDB, the function returns it.
- response = dynamodb.get_item(
- TableName=TABLE_NAME,
- Key={
- 'review_id': {
- 'N': review_id,
- },
- 'language': {
- 'S': target_language,
- },
- }
- )
- logger.info(response)
- if 'Item' in response:
- return response['Item']['review']['S']
- except Exception as e:
- logger.error(response)
- raise Exception("[ErrorMessage]: " + str(e))
-
- try:
- # The Lambda function calls the TranslateText operation and passes the
- # review, the source language, and the target language to get the
- # translated review.
- result = translate.translate_text(Text=review, SourceLanguageCode=source_language, TargetLanguageCode=target_language)
- logging.info("Translation output: " + str(result))
- except Exception as e:
- logger.error(response)
- raise Exception("[ErrorMessage]: " + str(e))
-
- try:
- # After the review is translated, the function stores it using
- # the Amazon DynamoDB putItem operation. Subsequent requests
- # for this translated review are returned from Amazon DynamoDB.
- response = dynamodb.put_item(
- TableName=TABLE_NAME,
- Item={
- 'review_id': {
- 'N': review_id,
- },
- 'language': {
- 'S': target_language,
- },
- 'review': {
- 'S': result.get('TranslatedText')
- }
- }
- )
- logger.info(response)
- except Exception as e:
- logger.error(e)
- raise Exception("[ErrorMessage]: " + str(e))
- return result.get('TranslatedText')
- else:
- logger.error(e)
- raise Exception("[ErrorMessage]: Invalid input ")
-```
-
-### AWS CloudFormation template
-
-The following is the template file that you use with AWS CloudFormation to create and configure the Lambda function and the DynamoDB tables\. Use this file when you create the AWS CloudFormation stack for the example\. Update `BUCKET_NAME` to the name of the S3 bucket that contains the `example.zip` file and then save it to a local directory as `template.yaml`\.
-
-```
-AWSTemplateFormatVersion: '2010-09-09'
-Transform: 'AWS::Serverless-2016-10-31'
-Resources: ReviewTranslate:
- Type: 'AWS::Serverless::Function'
- Properties:
- Handler: example.lambda_handler
- Runtime: python2.7
- CodeUri:
- Bucket: BUCKET_NAME
- Key: example.zip
- Policies:
- - AWSLambdaFullAccess
- - TranslateReadOnly
- Environment:
- Variables:
- TABLE_NAME: !Ref ReviewTable
- Tracing: "Active"
- ReviewTable:
- Type: 'AWS::DynamoDB::Table'
- Properties:
- AttributeDefinitions:
- - AttributeName: "review_id"
- AttributeType: "N"
- - AttributeName: "language"
- AttributeType: "S"
- KeySchema:
- - AttributeName: "review_id"
- KeyType: "HASH"
- - AttributeName: "language"
- KeyType: "RANGE"
- ProvisionedThroughput:
- ReadCapacityUnits: 5
- WriteCapacityUnits: 5
-```
\ No newline at end of file
diff --git a/doc_source/examples-java.md b/doc_source/examples-java.md
deleted file mode 100644
index aea3fb3..0000000
--- a/doc_source/examples-java.md
+++ /dev/null
@@ -1,38 +0,0 @@
-# Translating text using the AWS SDK for Java
-
-The following example demonstrates using the [TranslateText](https://docs.aws.amazon.com/translate/latest/APIReference/API_TranslateText.html) operation in Java\. To run this example, you need the AWS SDK for Java\. For instructions for installing the SDK for Java, see [ Set up the AWS SDK for Java](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/setup-install.html)\.
-
-```
-import com.amazonaws.auth.AWSStaticCredentialsProvider;
-import com.amazonaws.auth.BasicAWSCredentials;
-import com.amazonaws.client.builder.AwsClientBuilder;
-import com.amazonaws.services.translate.AmazonTranslate;
-import com.amazonaws.services.translate.AmazonTranslateClient;
-import com.amazonaws.services.translate.model.TranslateTextRequest;
-import com.amazonaws.services.translate.model.TranslateTextResult;
-
-public class App {
- private static final String REGION = "region";
-
- public static void main( String[] args ) {
-
- // Create credentials using a provider chain. For more information, see
- // https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html
- AWSCredentialsProvider awsCreds = DefaultAWSCredentialsProviderChain.getInstance();
-
- AmazonTranslate translate = AmazonTranslateClient.builder()
- .withCredentials(new AWSStaticCredentialsProvider(awsCreds.getCredentials()))
- .withRegion(REGION)
- .build();
-
- TranslateTextRequest request = new TranslateTextRequest()
- .withText("Hello, world")
- .withSourceLanguageCode("en")
- .withTargetLanguageCode("es");
- TranslateTextResult result = translate.translateText(request);
- System.out.println(result.getTranslatedText());
- }
-}
-```
-
-For a list of supported languages and language codes, see [Supported languages and language codes](what-is-languages.md)
\ No newline at end of file
diff --git a/doc_source/examples-polly.md b/doc_source/examples-polly.md
deleted file mode 100644
index 5f6eb5e..0000000
--- a/doc_source/examples-polly.md
+++ /dev/null
@@ -1,251 +0,0 @@
-# Using Amazon Polly with Amazon Translate
-
-To speak translated text, you can use Amazon Polly with Amazon Translate\. In this example you'll create a Web page where you can translate text using Amazon Translate and then speak that text using Amazon Polly\. The code can be summarized into the following:
-+ CSS and HTML to create the Web page\.
-+ Initialization code that creates controllers for Amazon Translate and Amazon Polly\.
-+ A function that reads data from the Web page and calls Amazon Translate\.
-+ A function that reads data from the Web page and calls Amazon Polly\.
-+ Utility functions for managing the Web page\.
-
-**To configure the example**
-
-1. Install and Configure the AWS SDK for JavaScript\. For instructions for installing the SDK for JavaScript, see [Installing the SDK for JavaScript](https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/installing-jssdk.html)\.
-
-1. Copy the code for the example to an HTML file on your Web server\.
-
-1. Update the `
-
-
-
-