1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
--cli-input-json
is a generic way of passing parameters to the AWS CLI from a file,as described here - https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-skeleton.html.
You mentioned you want to specify a config file to start-pii-entities-detection-job
- maybe you want to use --input-data-config
?
start-pii-entities-detection-job
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Description
***********
Starts an asynchronous PII entity detection job for a collection of
documents.
See also: AWS API Documentation
See 'aws help' for descriptions of global parameters.
Synopsis
********
start-pii-entities-detection-job
--input-data-config <value>
--output-data-config <value>
--mode <value>
[--redaction-config <value>]
--data-access-role-arn <value>
[--job-name <value>]
--language-code <value>
[--client-request-token <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
From what I see here: https://docs.aws.amazon.com/cli/latest/reference/comprehend/start-pii-entities-detection-job.html, input-data-config is a specific set of input values, specifically the S3Uri to the text to be redacted, etc. I am trying to capture all the required parameters, including the input-data-config information, in a json file stored in S3 rather than specifying each on the command line. I can craft CLI commands with all the information in parameters but it isn't pretty due to the large list of PII entity types that I need to specify.
This page shows syntax with a "file://" prefix to the input json but I want to have the file in s3, not locally as I am using CloudShell. Was hoping someone knew the secret for using a file stored in S3. https://docs.aws.amazon.com/comprehend/latest/dg/redact-api-pii.html
Unfortunately as in https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-parameters-file.html the file to load parameters from has to be specified as
file://complete/path/to/file
.