cdk-lambda-subminute 2.0.272 → 2.0.274
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.jsii +3 -3
- package/lib/cdk-lambda-subminute.js +3 -3
- package/node_modules/aws-sdk/CHANGELOG.md +18 -1
- package/node_modules/aws-sdk/README.md +1 -1
- package/node_modules/aws-sdk/apis/appintegrations-2020-07-29.min.json +1 -2
- package/node_modules/aws-sdk/apis/connect-2017-08-08.min.json +28 -6
- package/node_modules/aws-sdk/apis/discovery-2015-11-01.min.json +167 -35
- package/node_modules/aws-sdk/apis/discovery-2015-11-01.paginators.json +34 -2
- package/node_modules/aws-sdk/apis/metadata.json +0 -3
- package/node_modules/aws-sdk/apis/omics-2022-11-28.min.json +30 -21
- package/node_modules/aws-sdk/apis/opensearch-2021-01-01.min.json +134 -9
- package/node_modules/aws-sdk/apis/opensearch-2021-01-01.paginators.json +5 -0
- package/node_modules/aws-sdk/apis/quicksight-2018-04-01.min.json +776 -698
- package/node_modules/aws-sdk/apis/ssm-2014-11-06.min.json +188 -173
- package/node_modules/aws-sdk/clients/all.d.ts +0 -1
- package/node_modules/aws-sdk/clients/all.js +0 -1
- package/node_modules/aws-sdk/clients/appintegrations.d.ts +1 -1
- package/node_modules/aws-sdk/clients/connect.d.ts +53 -31
- package/node_modules/aws-sdk/clients/discovery.d.ts +170 -0
- package/node_modules/aws-sdk/clients/ec2.d.ts +1 -1
- package/node_modules/aws-sdk/clients/managedblockchainquery.d.ts +1 -1
- package/node_modules/aws-sdk/clients/medicalimaging.d.ts +10 -10
- package/node_modules/aws-sdk/clients/neptunedata.d.ts +81 -81
- package/node_modules/aws-sdk/clients/omics.d.ts +27 -1
- package/node_modules/aws-sdk/clients/opensearch.d.ts +152 -1
- package/node_modules/aws-sdk/clients/quicksight.d.ts +111 -7
- package/node_modules/aws-sdk/clients/secretsmanager.d.ts +7 -7
- package/node_modules/aws-sdk/clients/servicecatalog.d.ts +9 -9
- package/node_modules/aws-sdk/clients/ssm.d.ts +19 -3
- package/node_modules/aws-sdk/clients/verifiedpermissions.d.ts +2 -2
- package/node_modules/aws-sdk/clients/workspaces.d.ts +2 -2
- package/node_modules/aws-sdk/dist/aws-sdk-core-react-native.js +246 -86
- package/node_modules/aws-sdk/dist/aws-sdk-react-native.js +1974 -1691
- package/node_modules/aws-sdk/dist/aws-sdk.js +219 -185
- package/node_modules/aws-sdk/dist/aws-sdk.min.js +78 -78
- package/node_modules/aws-sdk/lib/config_service_placeholders.d.ts +0 -2
- package/node_modules/aws-sdk/lib/core.js +1 -1
- package/node_modules/aws-sdk/package.json +1 -1
- package/node_modules/call-bind/.eslintrc +0 -1
- package/node_modules/call-bind/.nycrc +0 -4
- package/node_modules/call-bind/CHANGELOG.md +35 -0
- package/node_modules/call-bind/README.md +63 -1
- package/node_modules/call-bind/index.js +10 -13
- package/node_modules/call-bind/package.json +33 -23
- package/node_modules/call-bind/test/callBound.js +0 -1
- package/node_modules/call-bind/test/index.js +18 -4
- package/node_modules/define-data-property/.eslintrc +24 -0
- package/node_modules/define-data-property/.github/FUNDING.yml +12 -0
- package/node_modules/define-data-property/.nycrc +13 -0
- package/node_modules/define-data-property/CHANGELOG.md +41 -0
- package/node_modules/define-data-property/LICENSE +21 -0
- package/node_modules/define-data-property/README.md +67 -0
- package/node_modules/define-data-property/index.d.ts +3 -0
- package/node_modules/define-data-property/index.d.ts.map +1 -0
- package/node_modules/define-data-property/index.js +68 -0
- package/node_modules/define-data-property/package.json +113 -0
- package/node_modules/define-data-property/test/index.js +392 -0
- package/node_modules/define-data-property/tsconfig.json +59 -0
- package/node_modules/has-property-descriptors/.eslintrc +13 -0
- package/node_modules/has-property-descriptors/.github/FUNDING.yml +12 -0
- package/node_modules/has-property-descriptors/.nycrc +9 -0
- package/node_modules/has-property-descriptors/CHANGELOG.md +16 -0
- package/node_modules/has-property-descriptors/LICENSE +21 -0
- package/node_modules/has-property-descriptors/README.md +43 -0
- package/node_modules/has-property-descriptors/index.js +33 -0
- package/node_modules/has-property-descriptors/package.json +70 -0
- package/node_modules/has-property-descriptors/test/index.js +57 -0
- package/node_modules/set-function-length/.eslintrc +27 -0
- package/node_modules/set-function-length/.github/FUNDING.yml +12 -0
- package/node_modules/set-function-length/.nycrc +13 -0
- package/node_modules/set-function-length/CHANGELOG.md +41 -0
- package/node_modules/set-function-length/LICENSE +21 -0
- package/node_modules/set-function-length/README.md +56 -0
- package/node_modules/set-function-length/env.js +19 -0
- package/node_modules/set-function-length/index.js +41 -0
- package/node_modules/set-function-length/package.json +84 -0
- package/node_modules/which-typed-array/CHANGELOG.md +14 -0
- package/node_modules/which-typed-array/index.js +4 -1
- package/node_modules/which-typed-array/package.json +3 -3
- package/package.json +3 -3
- package/node_modules/aws-sdk/apis/gamesparks-2021-08-17.examples.json +0 -5
- package/node_modules/aws-sdk/apis/gamesparks-2021-08-17.min.json +0 -1376
- package/node_modules/aws-sdk/apis/gamesparks-2021-08-17.paginators.json +0 -46
- package/node_modules/aws-sdk/clients/gamesparks.d.ts +0 -1344
- package/node_modules/aws-sdk/clients/gamesparks.js +0 -18
@@ -12,211 +12,211 @@ declare class Neptunedata extends Service {
|
|
12
12
|
constructor(options?: Neptunedata.Types.ClientConfiguration)
|
13
13
|
config: Config & Neptunedata.Types.ClientConfiguration;
|
14
14
|
/**
|
15
|
-
* Cancels a Gremlin query. See Gremlin query cancellation for more information.
|
15
|
+
* Cancels a Gremlin query. See Gremlin query cancellation for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelQuery IAM action in that cluster.
|
16
16
|
*/
|
17
17
|
cancelGremlinQuery(params: Neptunedata.Types.CancelGremlinQueryInput, callback?: (err: AWSError, data: Neptunedata.Types.CancelGremlinQueryOutput) => void): Request<Neptunedata.Types.CancelGremlinQueryOutput, AWSError>;
|
18
18
|
/**
|
19
|
-
* Cancels a Gremlin query. See Gremlin query cancellation for more information.
|
19
|
+
* Cancels a Gremlin query. See Gremlin query cancellation for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelQuery IAM action in that cluster.
|
20
20
|
*/
|
21
21
|
cancelGremlinQuery(callback?: (err: AWSError, data: Neptunedata.Types.CancelGremlinQueryOutput) => void): Request<Neptunedata.Types.CancelGremlinQueryOutput, AWSError>;
|
22
22
|
/**
|
23
|
-
* Cancels a specified load job. This is an HTTP DELETE request. See Neptune Loader Get-Status API for more information.
|
23
|
+
* Cancels a specified load job. This is an HTTP DELETE request. See Neptune Loader Get-Status API for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelLoaderJob IAM action in that cluster..
|
24
24
|
*/
|
25
25
|
cancelLoaderJob(params: Neptunedata.Types.CancelLoaderJobInput, callback?: (err: AWSError, data: Neptunedata.Types.CancelLoaderJobOutput) => void): Request<Neptunedata.Types.CancelLoaderJobOutput, AWSError>;
|
26
26
|
/**
|
27
|
-
* Cancels a specified load job. This is an HTTP DELETE request. See Neptune Loader Get-Status API for more information.
|
27
|
+
* Cancels a specified load job. This is an HTTP DELETE request. See Neptune Loader Get-Status API for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelLoaderJob IAM action in that cluster..
|
28
28
|
*/
|
29
29
|
cancelLoaderJob(callback?: (err: AWSError, data: Neptunedata.Types.CancelLoaderJobOutput) => void): Request<Neptunedata.Types.CancelLoaderJobOutput, AWSError>;
|
30
30
|
/**
|
31
|
-
* Cancels a Neptune ML data processing job. See The dataprocessing command.
|
31
|
+
* Cancels a Neptune ML data processing job. See The dataprocessing command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelMLDataProcessingJob IAM action in that cluster.
|
32
32
|
*/
|
33
33
|
cancelMLDataProcessingJob(params: Neptunedata.Types.CancelMLDataProcessingJobInput, callback?: (err: AWSError, data: Neptunedata.Types.CancelMLDataProcessingJobOutput) => void): Request<Neptunedata.Types.CancelMLDataProcessingJobOutput, AWSError>;
|
34
34
|
/**
|
35
|
-
* Cancels a Neptune ML data processing job. See The dataprocessing command.
|
35
|
+
* Cancels a Neptune ML data processing job. See The dataprocessing command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelMLDataProcessingJob IAM action in that cluster.
|
36
36
|
*/
|
37
37
|
cancelMLDataProcessingJob(callback?: (err: AWSError, data: Neptunedata.Types.CancelMLDataProcessingJobOutput) => void): Request<Neptunedata.Types.CancelMLDataProcessingJobOutput, AWSError>;
|
38
38
|
/**
|
39
|
-
* Cancels a Neptune ML model training job. See Model training using the modeltraining command.
|
39
|
+
* Cancels a Neptune ML model training job. See Model training using the modeltraining command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelMLModelTrainingJob IAM action in that cluster.
|
40
40
|
*/
|
41
41
|
cancelMLModelTrainingJob(params: Neptunedata.Types.CancelMLModelTrainingJobInput, callback?: (err: AWSError, data: Neptunedata.Types.CancelMLModelTrainingJobOutput) => void): Request<Neptunedata.Types.CancelMLModelTrainingJobOutput, AWSError>;
|
42
42
|
/**
|
43
|
-
* Cancels a Neptune ML model training job. See Model training using the modeltraining command.
|
43
|
+
* Cancels a Neptune ML model training job. See Model training using the modeltraining command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelMLModelTrainingJob IAM action in that cluster.
|
44
44
|
*/
|
45
45
|
cancelMLModelTrainingJob(callback?: (err: AWSError, data: Neptunedata.Types.CancelMLModelTrainingJobOutput) => void): Request<Neptunedata.Types.CancelMLModelTrainingJobOutput, AWSError>;
|
46
46
|
/**
|
47
|
-
* Cancels a specified model transform job. See Use a trained model to generate new model artifacts.
|
47
|
+
* Cancels a specified model transform job. See Use a trained model to generate new model artifacts. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelMLModelTransformJob IAM action in that cluster.
|
48
48
|
*/
|
49
49
|
cancelMLModelTransformJob(params: Neptunedata.Types.CancelMLModelTransformJobInput, callback?: (err: AWSError, data: Neptunedata.Types.CancelMLModelTransformJobOutput) => void): Request<Neptunedata.Types.CancelMLModelTransformJobOutput, AWSError>;
|
50
50
|
/**
|
51
|
-
* Cancels a specified model transform job. See Use a trained model to generate new model artifacts.
|
51
|
+
* Cancels a specified model transform job. See Use a trained model to generate new model artifacts. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelMLModelTransformJob IAM action in that cluster.
|
52
52
|
*/
|
53
53
|
cancelMLModelTransformJob(callback?: (err: AWSError, data: Neptunedata.Types.CancelMLModelTransformJobOutput) => void): Request<Neptunedata.Types.CancelMLModelTransformJobOutput, AWSError>;
|
54
54
|
/**
|
55
|
-
* Cancels a specified openCypher query. See Neptune openCypher status endpoint for more information.
|
55
|
+
* Cancels a specified openCypher query. See Neptune openCypher status endpoint for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelQuery IAM action in that cluster.
|
56
56
|
*/
|
57
57
|
cancelOpenCypherQuery(params: Neptunedata.Types.CancelOpenCypherQueryInput, callback?: (err: AWSError, data: Neptunedata.Types.CancelOpenCypherQueryOutput) => void): Request<Neptunedata.Types.CancelOpenCypherQueryOutput, AWSError>;
|
58
58
|
/**
|
59
|
-
* Cancels a specified openCypher query. See Neptune openCypher status endpoint for more information.
|
59
|
+
* Cancels a specified openCypher query. See Neptune openCypher status endpoint for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CancelQuery IAM action in that cluster.
|
60
60
|
*/
|
61
61
|
cancelOpenCypherQuery(callback?: (err: AWSError, data: Neptunedata.Types.CancelOpenCypherQueryOutput) => void): Request<Neptunedata.Types.CancelOpenCypherQueryOutput, AWSError>;
|
62
62
|
/**
|
63
|
-
* Creates a new Neptune ML inference endpoint that lets you query one specific model that the model-training process constructed. See Managing inference endpoints using the endpoints command.
|
63
|
+
* Creates a new Neptune ML inference endpoint that lets you query one specific model that the model-training process constructed. See Managing inference endpoints using the endpoints command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CreateMLEndpoint IAM action in that cluster.
|
64
64
|
*/
|
65
65
|
createMLEndpoint(params: Neptunedata.Types.CreateMLEndpointInput, callback?: (err: AWSError, data: Neptunedata.Types.CreateMLEndpointOutput) => void): Request<Neptunedata.Types.CreateMLEndpointOutput, AWSError>;
|
66
66
|
/**
|
67
|
-
* Creates a new Neptune ML inference endpoint that lets you query one specific model that the model-training process constructed. See Managing inference endpoints using the endpoints command.
|
67
|
+
* Creates a new Neptune ML inference endpoint that lets you query one specific model that the model-training process constructed. See Managing inference endpoints using the endpoints command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:CreateMLEndpoint IAM action in that cluster.
|
68
68
|
*/
|
69
69
|
createMLEndpoint(callback?: (err: AWSError, data: Neptunedata.Types.CreateMLEndpointOutput) => void): Request<Neptunedata.Types.CreateMLEndpointOutput, AWSError>;
|
70
70
|
/**
|
71
|
-
* Cancels the creation of a Neptune ML inference endpoint. See Managing inference endpoints using the endpoints command.
|
71
|
+
* Cancels the creation of a Neptune ML inference endpoint. See Managing inference endpoints using the endpoints command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:DeleteMLEndpoint IAM action in that cluster.
|
72
72
|
*/
|
73
73
|
deleteMLEndpoint(params: Neptunedata.Types.DeleteMLEndpointInput, callback?: (err: AWSError, data: Neptunedata.Types.DeleteMLEndpointOutput) => void): Request<Neptunedata.Types.DeleteMLEndpointOutput, AWSError>;
|
74
74
|
/**
|
75
|
-
* Cancels the creation of a Neptune ML inference endpoint. See Managing inference endpoints using the endpoints command.
|
75
|
+
* Cancels the creation of a Neptune ML inference endpoint. See Managing inference endpoints using the endpoints command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:DeleteMLEndpoint IAM action in that cluster.
|
76
76
|
*/
|
77
77
|
deleteMLEndpoint(callback?: (err: AWSError, data: Neptunedata.Types.DeleteMLEndpointOutput) => void): Request<Neptunedata.Types.DeleteMLEndpointOutput, AWSError>;
|
78
78
|
/**
|
79
|
-
* Deletes statistics for Gremlin and openCypher (property graph) data.
|
79
|
+
* Deletes statistics for Gremlin and openCypher (property graph) data. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:DeleteStatistics IAM action in that cluster.
|
80
80
|
*/
|
81
81
|
deletePropertygraphStatistics(callback?: (err: AWSError, data: Neptunedata.Types.DeletePropertygraphStatisticsOutput) => void): Request<Neptunedata.Types.DeletePropertygraphStatisticsOutput, AWSError>;
|
82
82
|
/**
|
83
|
-
* Deletes SPARQL statistics
|
83
|
+
* Deletes SPARQL statistics When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:DeleteStatistics IAM action in that cluster.
|
84
84
|
*/
|
85
85
|
deleteSparqlStatistics(callback?: (err: AWSError, data: Neptunedata.Types.DeleteSparqlStatisticsOutput) => void): Request<Neptunedata.Types.DeleteSparqlStatisticsOutput, AWSError>;
|
86
86
|
/**
|
87
|
-
* The fast reset REST API lets you reset a Neptune graph quicky and easily, removing all of its data. Neptune fast reset is a two-step process. First you call ExecuteFastReset with action set to initiateDatabaseReset. This returns a UUID token which you then include when calling ExecuteFastReset again with action set to performDatabaseReset. See Empty an Amazon Neptune DB cluster using the fast reset API.
|
87
|
+
* The fast reset REST API lets you reset a Neptune graph quicky and easily, removing all of its data. Neptune fast reset is a two-step process. First you call ExecuteFastReset with action set to initiateDatabaseReset. This returns a UUID token which you then include when calling ExecuteFastReset again with action set to performDatabaseReset. See Empty an Amazon Neptune DB cluster using the fast reset API. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ResetDatabase IAM action in that cluster.
|
88
88
|
*/
|
89
89
|
executeFastReset(params: Neptunedata.Types.ExecuteFastResetInput, callback?: (err: AWSError, data: Neptunedata.Types.ExecuteFastResetOutput) => void): Request<Neptunedata.Types.ExecuteFastResetOutput, AWSError>;
|
90
90
|
/**
|
91
|
-
* The fast reset REST API lets you reset a Neptune graph quicky and easily, removing all of its data. Neptune fast reset is a two-step process. First you call ExecuteFastReset with action set to initiateDatabaseReset. This returns a UUID token which you then include when calling ExecuteFastReset again with action set to performDatabaseReset. See Empty an Amazon Neptune DB cluster using the fast reset API.
|
91
|
+
* The fast reset REST API lets you reset a Neptune graph quicky and easily, removing all of its data. Neptune fast reset is a two-step process. First you call ExecuteFastReset with action set to initiateDatabaseReset. This returns a UUID token which you then include when calling ExecuteFastReset again with action set to performDatabaseReset. See Empty an Amazon Neptune DB cluster using the fast reset API. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ResetDatabase IAM action in that cluster.
|
92
92
|
*/
|
93
93
|
executeFastReset(callback?: (err: AWSError, data: Neptunedata.Types.ExecuteFastResetOutput) => void): Request<Neptunedata.Types.ExecuteFastResetOutput, AWSError>;
|
94
94
|
/**
|
95
|
-
* Executes a Gremlin Explain query. Amazon Neptune has added a Gremlin feature named explain that provides is a self-service tool for understanding the execution approach being taken by the Neptune engine for the query. You invoke it by adding an explain parameter to an HTTP call that submits a Gremlin query. The explain feature provides information about the logical structure of query execution plans. You can use this information to identify potential evaluation and execution bottlenecks and to tune your query, as explained in Tuning Gremlin queries. You can also use query hints to improve query execution plans.
|
95
|
+
* Executes a Gremlin Explain query. Amazon Neptune has added a Gremlin feature named explain that provides is a self-service tool for understanding the execution approach being taken by the Neptune engine for the query. You invoke it by adding an explain parameter to an HTTP call that submits a Gremlin query. The explain feature provides information about the logical structure of query execution plans. You can use this information to identify potential evaluation and execution bottlenecks and to tune your query, as explained in Tuning Gremlin queries. You can also use query hints to improve query execution plans. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows one of the following IAM actions in that cluster, depending on the query: neptune-db:ReadDataViaQuery neptune-db:WriteDataViaQuery neptune-db:DeleteDataViaQuery Note that the neptune-db:QueryLanguage:Gremlin IAM condition key can be used in the policy document to restrict the use of Gremlin queries (see Condition keys available in Neptune IAM data-access policy statements).
|
96
96
|
*/
|
97
97
|
executeGremlinExplainQuery(params: Neptunedata.Types.ExecuteGremlinExplainQueryInput, callback?: (err: AWSError, data: Neptunedata.Types.ExecuteGremlinExplainQueryOutput) => void): Request<Neptunedata.Types.ExecuteGremlinExplainQueryOutput, AWSError>;
|
98
98
|
/**
|
99
|
-
* Executes a Gremlin Explain query. Amazon Neptune has added a Gremlin feature named explain that provides is a self-service tool for understanding the execution approach being taken by the Neptune engine for the query. You invoke it by adding an explain parameter to an HTTP call that submits a Gremlin query. The explain feature provides information about the logical structure of query execution plans. You can use this information to identify potential evaluation and execution bottlenecks and to tune your query, as explained in Tuning Gremlin queries. You can also use query hints to improve query execution plans.
|
99
|
+
* Executes a Gremlin Explain query. Amazon Neptune has added a Gremlin feature named explain that provides is a self-service tool for understanding the execution approach being taken by the Neptune engine for the query. You invoke it by adding an explain parameter to an HTTP call that submits a Gremlin query. The explain feature provides information about the logical structure of query execution plans. You can use this information to identify potential evaluation and execution bottlenecks and to tune your query, as explained in Tuning Gremlin queries. You can also use query hints to improve query execution plans. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows one of the following IAM actions in that cluster, depending on the query: neptune-db:ReadDataViaQuery neptune-db:WriteDataViaQuery neptune-db:DeleteDataViaQuery Note that the neptune-db:QueryLanguage:Gremlin IAM condition key can be used in the policy document to restrict the use of Gremlin queries (see Condition keys available in Neptune IAM data-access policy statements).
|
100
100
|
*/
|
101
101
|
executeGremlinExplainQuery(callback?: (err: AWSError, data: Neptunedata.Types.ExecuteGremlinExplainQueryOutput) => void): Request<Neptunedata.Types.ExecuteGremlinExplainQueryOutput, AWSError>;
|
102
102
|
/**
|
103
|
-
* Executes a Gremlin Profile query, which runs a specified traversal, collects various metrics about the run, and produces a profile report as output. See Gremlin profile API in Neptune for details.
|
103
|
+
* Executes a Gremlin Profile query, which runs a specified traversal, collects various metrics about the run, and produces a profile report as output. See Gremlin profile API in Neptune for details. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ReadDataViaQuery IAM action in that cluster. Note that the neptune-db:QueryLanguage:Gremlin IAM condition key can be used in the policy document to restrict the use of Gremlin queries (see Condition keys available in Neptune IAM data-access policy statements).
|
104
104
|
*/
|
105
105
|
executeGremlinProfileQuery(params: Neptunedata.Types.ExecuteGremlinProfileQueryInput, callback?: (err: AWSError, data: Neptunedata.Types.ExecuteGremlinProfileQueryOutput) => void): Request<Neptunedata.Types.ExecuteGremlinProfileQueryOutput, AWSError>;
|
106
106
|
/**
|
107
|
-
* Executes a Gremlin Profile query, which runs a specified traversal, collects various metrics about the run, and produces a profile report as output. See Gremlin profile API in Neptune for details.
|
107
|
+
* Executes a Gremlin Profile query, which runs a specified traversal, collects various metrics about the run, and produces a profile report as output. See Gremlin profile API in Neptune for details. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ReadDataViaQuery IAM action in that cluster. Note that the neptune-db:QueryLanguage:Gremlin IAM condition key can be used in the policy document to restrict the use of Gremlin queries (see Condition keys available in Neptune IAM data-access policy statements).
|
108
108
|
*/
|
109
109
|
executeGremlinProfileQuery(callback?: (err: AWSError, data: Neptunedata.Types.ExecuteGremlinProfileQueryOutput) => void): Request<Neptunedata.Types.ExecuteGremlinProfileQueryOutput, AWSError>;
|
110
110
|
/**
|
111
|
-
* This commands executes a Gremlin query. Amazon Neptune is compatible with Apache TinkerPop3 and Gremlin, so you can use the Gremlin traversal language to query the graph, as described under The Graph in the Apache TinkerPop3 documentation. More details can also be found in Accessing a Neptune graph with Gremlin.
|
111
|
+
* This commands executes a Gremlin query. Amazon Neptune is compatible with Apache TinkerPop3 and Gremlin, so you can use the Gremlin traversal language to query the graph, as described under The Graph in the Apache TinkerPop3 documentation. More details can also be found in Accessing a Neptune graph with Gremlin. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that enables one of the following IAM actions in that cluster, depending on the query: neptune-db:ReadDataViaQuery neptune-db:WriteDataViaQuery neptune-db:DeleteDataViaQuery Note that the neptune-db:QueryLanguage:Gremlin IAM condition key can be used in the policy document to restrict the use of Gremlin queries (see Condition keys available in Neptune IAM data-access policy statements).
|
112
112
|
*/
|
113
113
|
executeGremlinQuery(params: Neptunedata.Types.ExecuteGremlinQueryInput, callback?: (err: AWSError, data: Neptunedata.Types.ExecuteGremlinQueryOutput) => void): Request<Neptunedata.Types.ExecuteGremlinQueryOutput, AWSError>;
|
114
114
|
/**
|
115
|
-
* This commands executes a Gremlin query. Amazon Neptune is compatible with Apache TinkerPop3 and Gremlin, so you can use the Gremlin traversal language to query the graph, as described under The Graph in the Apache TinkerPop3 documentation. More details can also be found in Accessing a Neptune graph with Gremlin.
|
115
|
+
* This commands executes a Gremlin query. Amazon Neptune is compatible with Apache TinkerPop3 and Gremlin, so you can use the Gremlin traversal language to query the graph, as described under The Graph in the Apache TinkerPop3 documentation. More details can also be found in Accessing a Neptune graph with Gremlin. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that enables one of the following IAM actions in that cluster, depending on the query: neptune-db:ReadDataViaQuery neptune-db:WriteDataViaQuery neptune-db:DeleteDataViaQuery Note that the neptune-db:QueryLanguage:Gremlin IAM condition key can be used in the policy document to restrict the use of Gremlin queries (see Condition keys available in Neptune IAM data-access policy statements).
|
116
116
|
*/
|
117
117
|
executeGremlinQuery(callback?: (err: AWSError, data: Neptunedata.Types.ExecuteGremlinQueryOutput) => void): Request<Neptunedata.Types.ExecuteGremlinQueryOutput, AWSError>;
|
118
118
|
/**
|
119
|
-
* Executes an openCypher explain request. See The openCypher explain feature for more information.
|
119
|
+
* Executes an openCypher explain request. See The openCypher explain feature for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ReadDataViaQuery IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
|
120
120
|
*/
|
121
121
|
executeOpenCypherExplainQuery(params: Neptunedata.Types.ExecuteOpenCypherExplainQueryInput, callback?: (err: AWSError, data: Neptunedata.Types.ExecuteOpenCypherExplainQueryOutput) => void): Request<Neptunedata.Types.ExecuteOpenCypherExplainQueryOutput, AWSError>;
|
122
122
|
/**
|
123
|
-
* Executes an openCypher explain request. See The openCypher explain feature for more information.
|
123
|
+
* Executes an openCypher explain request. See The openCypher explain feature for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ReadDataViaQuery IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
|
124
124
|
*/
|
125
125
|
executeOpenCypherExplainQuery(callback?: (err: AWSError, data: Neptunedata.Types.ExecuteOpenCypherExplainQueryOutput) => void): Request<Neptunedata.Types.ExecuteOpenCypherExplainQueryOutput, AWSError>;
|
126
126
|
/**
|
127
|
-
* Executes an openCypher query. See Accessing the Neptune Graph with openCypher for more information. Neptune supports building graph applications using openCypher, which is currently one of the most popular query languages among developers working with graph databases. Developers, business analysts, and data scientists like openCypher's declarative, SQL-inspired syntax because it provides a familiar structure in which to querying property graphs. The openCypher language was originally developed by Neo4j, then open-sourced in 2015 and contributed to the openCypher project under an Apache 2 open-source license.
|
127
|
+
* Executes an openCypher query. See Accessing the Neptune Graph with openCypher for more information. Neptune supports building graph applications using openCypher, which is currently one of the most popular query languages among developers working with graph databases. Developers, business analysts, and data scientists like openCypher's declarative, SQL-inspired syntax because it provides a familiar structure in which to querying property graphs. The openCypher language was originally developed by Neo4j, then open-sourced in 2015 and contributed to the openCypher project under an Apache 2 open-source license. Note that when invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows one of the following IAM actions in that cluster, depending on the query: neptune-db:ReadDataViaQuery neptune-db:WriteDataViaQuery neptune-db:DeleteDataViaQuery Note also that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
|
128
128
|
*/
|
129
129
|
executeOpenCypherQuery(params: Neptunedata.Types.ExecuteOpenCypherQueryInput, callback?: (err: AWSError, data: Neptunedata.Types.ExecuteOpenCypherQueryOutput) => void): Request<Neptunedata.Types.ExecuteOpenCypherQueryOutput, AWSError>;
|
130
130
|
/**
|
131
|
-
* Executes an openCypher query. See Accessing the Neptune Graph with openCypher for more information. Neptune supports building graph applications using openCypher, which is currently one of the most popular query languages among developers working with graph databases. Developers, business analysts, and data scientists like openCypher's declarative, SQL-inspired syntax because it provides a familiar structure in which to querying property graphs. The openCypher language was originally developed by Neo4j, then open-sourced in 2015 and contributed to the openCypher project under an Apache 2 open-source license.
|
131
|
+
* Executes an openCypher query. See Accessing the Neptune Graph with openCypher for more information. Neptune supports building graph applications using openCypher, which is currently one of the most popular query languages among developers working with graph databases. Developers, business analysts, and data scientists like openCypher's declarative, SQL-inspired syntax because it provides a familiar structure in which to querying property graphs. The openCypher language was originally developed by Neo4j, then open-sourced in 2015 and contributed to the openCypher project under an Apache 2 open-source license. Note that when invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows one of the following IAM actions in that cluster, depending on the query: neptune-db:ReadDataViaQuery neptune-db:WriteDataViaQuery neptune-db:DeleteDataViaQuery Note also that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
|
132
132
|
*/
|
133
133
|
executeOpenCypherQuery(callback?: (err: AWSError, data: Neptunedata.Types.ExecuteOpenCypherQueryOutput) => void): Request<Neptunedata.Types.ExecuteOpenCypherQueryOutput, AWSError>;
|
134
134
|
/**
|
135
|
-
*
|
135
|
+
* Retrieves the status of the graph database on the host. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetEngineStatus IAM action in that cluster.
|
136
136
|
*/
|
137
137
|
getEngineStatus(callback?: (err: AWSError, data: Neptunedata.Types.GetEngineStatusOutput) => void): Request<Neptunedata.Types.GetEngineStatusOutput, AWSError>;
|
138
138
|
/**
|
139
|
-
* Gets the status of a specified Gremlin query.
|
139
|
+
* Gets the status of a specified Gremlin query. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Gremlin IAM condition key can be used in the policy document to restrict the use of Gremlin queries (see Condition keys available in Neptune IAM data-access policy statements).
|
140
140
|
*/
|
141
141
|
getGremlinQueryStatus(params: Neptunedata.Types.GetGremlinQueryStatusInput, callback?: (err: AWSError, data: Neptunedata.Types.GetGremlinQueryStatusOutput) => void): Request<Neptunedata.Types.GetGremlinQueryStatusOutput, AWSError>;
|
142
142
|
/**
|
143
|
-
* Gets the status of a specified Gremlin query.
|
143
|
+
* Gets the status of a specified Gremlin query. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Gremlin IAM condition key can be used in the policy document to restrict the use of Gremlin queries (see Condition keys available in Neptune IAM data-access policy statements).
|
144
144
|
*/
|
145
145
|
getGremlinQueryStatus(callback?: (err: AWSError, data: Neptunedata.Types.GetGremlinQueryStatusOutput) => void): Request<Neptunedata.Types.GetGremlinQueryStatusOutput, AWSError>;
|
146
146
|
/**
|
147
|
-
* Gets status information about a specified load job. Neptune keeps track of the most recent 1,024 bulk load jobs, and stores the last 10,000 error details per job. See Neptune Loader Get-Status API for more information.
|
147
|
+
* Gets status information about a specified load job. Neptune keeps track of the most recent 1,024 bulk load jobs, and stores the last 10,000 error details per job. See Neptune Loader Get-Status API for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetLoaderJobStatus IAM action in that cluster..
|
148
148
|
*/
|
149
149
|
getLoaderJobStatus(params: Neptunedata.Types.GetLoaderJobStatusInput, callback?: (err: AWSError, data: Neptunedata.Types.GetLoaderJobStatusOutput) => void): Request<Neptunedata.Types.GetLoaderJobStatusOutput, AWSError>;
|
150
150
|
/**
|
151
|
-
* Gets status information about a specified load job. Neptune keeps track of the most recent 1,024 bulk load jobs, and stores the last 10,000 error details per job. See Neptune Loader Get-Status API for more information.
|
151
|
+
* Gets status information about a specified load job. Neptune keeps track of the most recent 1,024 bulk load jobs, and stores the last 10,000 error details per job. See Neptune Loader Get-Status API for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetLoaderJobStatus IAM action in that cluster..
|
152
152
|
*/
|
153
153
|
getLoaderJobStatus(callback?: (err: AWSError, data: Neptunedata.Types.GetLoaderJobStatusOutput) => void): Request<Neptunedata.Types.GetLoaderJobStatusOutput, AWSError>;
|
154
154
|
/**
|
155
|
-
* Retrieves information about a specified data processing job. See The dataprocessing command.
|
155
|
+
* Retrieves information about a specified data processing job. See The dataprocessing command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:neptune-db:GetMLDataProcessingJobStatus IAM action in that cluster.
|
156
156
|
*/
|
157
157
|
getMLDataProcessingJob(params: Neptunedata.Types.GetMLDataProcessingJobInput, callback?: (err: AWSError, data: Neptunedata.Types.GetMLDataProcessingJobOutput) => void): Request<Neptunedata.Types.GetMLDataProcessingJobOutput, AWSError>;
|
158
158
|
/**
|
159
|
-
* Retrieves information about a specified data processing job. See The dataprocessing command.
|
159
|
+
* Retrieves information about a specified data processing job. See The dataprocessing command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:neptune-db:GetMLDataProcessingJobStatus IAM action in that cluster.
|
160
160
|
*/
|
161
161
|
getMLDataProcessingJob(callback?: (err: AWSError, data: Neptunedata.Types.GetMLDataProcessingJobOutput) => void): Request<Neptunedata.Types.GetMLDataProcessingJobOutput, AWSError>;
|
162
162
|
/**
|
163
|
-
* Retrieves details about an inference endpoint. See Managing inference endpoints using the endpoints command.
|
163
|
+
* Retrieves details about an inference endpoint. See Managing inference endpoints using the endpoints command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetMLEndpointStatus IAM action in that cluster.
|
164
164
|
*/
|
165
165
|
getMLEndpoint(params: Neptunedata.Types.GetMLEndpointInput, callback?: (err: AWSError, data: Neptunedata.Types.GetMLEndpointOutput) => void): Request<Neptunedata.Types.GetMLEndpointOutput, AWSError>;
|
166
166
|
/**
|
167
|
-
* Retrieves details about an inference endpoint. See Managing inference endpoints using the endpoints command.
|
167
|
+
* Retrieves details about an inference endpoint. See Managing inference endpoints using the endpoints command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetMLEndpointStatus IAM action in that cluster.
|
168
168
|
*/
|
169
169
|
getMLEndpoint(callback?: (err: AWSError, data: Neptunedata.Types.GetMLEndpointOutput) => void): Request<Neptunedata.Types.GetMLEndpointOutput, AWSError>;
|
170
170
|
/**
|
171
|
-
* Retrieves information about a Neptune ML model training job. See Model training using the modeltraining command.
|
171
|
+
* Retrieves information about a Neptune ML model training job. See Model training using the modeltraining command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetMLModelTrainingJobStatus IAM action in that cluster.
|
172
172
|
*/
|
173
173
|
getMLModelTrainingJob(params: Neptunedata.Types.GetMLModelTrainingJobInput, callback?: (err: AWSError, data: Neptunedata.Types.GetMLModelTrainingJobOutput) => void): Request<Neptunedata.Types.GetMLModelTrainingJobOutput, AWSError>;
|
174
174
|
/**
|
175
|
-
* Retrieves information about a Neptune ML model training job. See Model training using the modeltraining command.
|
175
|
+
* Retrieves information about a Neptune ML model training job. See Model training using the modeltraining command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetMLModelTrainingJobStatus IAM action in that cluster.
|
176
176
|
*/
|
177
177
|
getMLModelTrainingJob(callback?: (err: AWSError, data: Neptunedata.Types.GetMLModelTrainingJobOutput) => void): Request<Neptunedata.Types.GetMLModelTrainingJobOutput, AWSError>;
|
178
178
|
/**
|
179
|
-
* Gets information about a specified model transform job. See Use a trained model to generate new model artifacts.
|
179
|
+
* Gets information about a specified model transform job. See Use a trained model to generate new model artifacts. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetMLModelTransformJobStatus IAM action in that cluster.
|
180
180
|
*/
|
181
181
|
getMLModelTransformJob(params: Neptunedata.Types.GetMLModelTransformJobInput, callback?: (err: AWSError, data: Neptunedata.Types.GetMLModelTransformJobOutput) => void): Request<Neptunedata.Types.GetMLModelTransformJobOutput, AWSError>;
|
182
182
|
/**
|
183
|
-
* Gets information about a specified model transform job. See Use a trained model to generate new model artifacts.
|
183
|
+
* Gets information about a specified model transform job. See Use a trained model to generate new model artifacts. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetMLModelTransformJobStatus IAM action in that cluster.
|
184
184
|
*/
|
185
185
|
getMLModelTransformJob(callback?: (err: AWSError, data: Neptunedata.Types.GetMLModelTransformJobOutput) => void): Request<Neptunedata.Types.GetMLModelTransformJobOutput, AWSError>;
|
186
186
|
/**
|
187
|
-
* Retrieves the status of a specified openCypher query.
|
187
|
+
* Retrieves the status of a specified openCypher query. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
|
188
188
|
*/
|
189
189
|
getOpenCypherQueryStatus(params: Neptunedata.Types.GetOpenCypherQueryStatusInput, callback?: (err: AWSError, data: Neptunedata.Types.GetOpenCypherQueryStatusOutput) => void): Request<Neptunedata.Types.GetOpenCypherQueryStatusOutput, AWSError>;
|
190
190
|
/**
|
191
|
-
* Retrieves the status of a specified openCypher query.
|
191
|
+
* Retrieves the status of a specified openCypher query. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
|
192
192
|
*/
|
193
193
|
getOpenCypherQueryStatus(callback?: (err: AWSError, data: Neptunedata.Types.GetOpenCypherQueryStatusOutput) => void): Request<Neptunedata.Types.GetOpenCypherQueryStatusOutput, AWSError>;
|
194
194
|
/**
|
195
|
-
* Gets property graph statistics (Gremlin and openCypher).
|
195
|
+
* Gets property graph statistics (Gremlin and openCypher). When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetStatisticsStatus IAM action in that cluster.
|
196
196
|
*/
|
197
197
|
getPropertygraphStatistics(callback?: (err: AWSError, data: Neptunedata.Types.GetPropertygraphStatisticsOutput) => void): Request<Neptunedata.Types.GetPropertygraphStatisticsOutput, AWSError>;
|
198
198
|
/**
|
199
|
-
* Gets a stream for a property graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetPropertygraphStream lets you collect these change-log entries for a property graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams.
|
199
|
+
* Gets a stream for a property graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetPropertygraphStream lets you collect these change-log entries for a property graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetStreamRecords IAM action in that cluster. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that enables one of the following IAM actions, depending on the query: Note that you can restrict property-graph queries using the following IAM context keys: neptune-db:QueryLanguage:Gremlin neptune-db:QueryLanguage:Opencypher See Condition keys available in Neptune IAM data-access policy statements).
|
200
200
|
*/
|
201
201
|
getPropertygraphStream(params: Neptunedata.Types.GetPropertygraphStreamInput, callback?: (err: AWSError, data: Neptunedata.Types.GetPropertygraphStreamOutput) => void): Request<Neptunedata.Types.GetPropertygraphStreamOutput, AWSError>;
|
202
202
|
/**
|
203
|
-
* Gets a stream for a property graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetPropertygraphStream lets you collect these change-log entries for a property graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams.
|
203
|
+
* Gets a stream for a property graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetPropertygraphStream lets you collect these change-log entries for a property graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetStreamRecords IAM action in that cluster. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that enables one of the following IAM actions, depending on the query: Note that you can restrict property-graph queries using the following IAM context keys: neptune-db:QueryLanguage:Gremlin neptune-db:QueryLanguage:Opencypher See Condition keys available in Neptune IAM data-access policy statements).
|
204
204
|
*/
|
205
205
|
getPropertygraphStream(callback?: (err: AWSError, data: Neptunedata.Types.GetPropertygraphStreamOutput) => void): Request<Neptunedata.Types.GetPropertygraphStreamOutput, AWSError>;
|
206
206
|
/**
|
207
|
-
* Gets a graph summary for a property graph.
|
207
|
+
* Gets a graph summary for a property graph. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetGraphSummary IAM action in that cluster.
|
208
208
|
*/
|
209
209
|
getPropertygraphSummary(params: Neptunedata.Types.GetPropertygraphSummaryInput, callback?: (err: AWSError, data: Neptunedata.Types.GetPropertygraphSummaryOutput) => void): Request<Neptunedata.Types.GetPropertygraphSummaryOutput, AWSError>;
|
210
210
|
/**
|
211
|
-
* Gets a graph summary for a property graph.
|
211
|
+
* Gets a graph summary for a property graph. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetGraphSummary IAM action in that cluster.
|
212
212
|
*/
|
213
213
|
getPropertygraphSummary(callback?: (err: AWSError, data: Neptunedata.Types.GetPropertygraphSummaryOutput) => void): Request<Neptunedata.Types.GetPropertygraphSummaryOutput, AWSError>;
|
214
214
|
/**
|
215
|
-
* Gets a graph summary for an RDF graph.
|
215
|
+
* Gets a graph summary for an RDF graph. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetGraphSummary IAM action in that cluster.
|
216
216
|
*/
|
217
217
|
getRDFGraphSummary(params: Neptunedata.Types.GetRDFGraphSummaryInput, callback?: (err: AWSError, data: Neptunedata.Types.GetRDFGraphSummaryOutput) => void): Request<Neptunedata.Types.GetRDFGraphSummaryOutput, AWSError>;
|
218
218
|
/**
|
219
|
-
* Gets a graph summary for an RDF graph.
|
219
|
+
* Gets a graph summary for an RDF graph. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetGraphSummary IAM action in that cluster.
|
220
220
|
*/
|
221
221
|
getRDFGraphSummary(callback?: (err: AWSError, data: Neptunedata.Types.GetRDFGraphSummaryOutput) => void): Request<Neptunedata.Types.GetRDFGraphSummaryOutput, AWSError>;
|
222
222
|
/**
|
@@ -224,115 +224,115 @@ declare class Neptunedata extends Service {
|
|
224
224
|
*/
|
225
225
|
getSparqlStatistics(callback?: (err: AWSError, data: Neptunedata.Types.GetSparqlStatisticsOutput) => void): Request<Neptunedata.Types.GetSparqlStatisticsOutput, AWSError>;
|
226
226
|
/**
|
227
|
-
* Gets a stream for an RDF graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetSparqlStream lets you collect these change-log entries for an RDF graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams.
|
227
|
+
* Gets a stream for an RDF graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetSparqlStream lets you collect these change-log entries for an RDF graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetStreamRecords IAM action in that cluster. Note that the neptune-db:QueryLanguage:Sparql IAM condition key can be used in the policy document to restrict the use of SPARQL queries (see Condition keys available in Neptune IAM data-access policy statements).
|
228
228
|
*/
|
229
229
|
getSparqlStream(params: Neptunedata.Types.GetSparqlStreamInput, callback?: (err: AWSError, data: Neptunedata.Types.GetSparqlStreamOutput) => void): Request<Neptunedata.Types.GetSparqlStreamOutput, AWSError>;
|
230
230
|
/**
|
231
|
-
* Gets a stream for an RDF graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetSparqlStream lets you collect these change-log entries for an RDF graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams.
|
231
|
+
* Gets a stream for an RDF graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetSparqlStream lets you collect these change-log entries for an RDF graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetStreamRecords IAM action in that cluster. Note that the neptune-db:QueryLanguage:Sparql IAM condition key can be used in the policy document to restrict the use of SPARQL queries (see Condition keys available in Neptune IAM data-access policy statements).
|
232
232
|
*/
|
233
233
|
getSparqlStream(callback?: (err: AWSError, data: Neptunedata.Types.GetSparqlStreamOutput) => void): Request<Neptunedata.Types.GetSparqlStreamOutput, AWSError>;
|
234
234
|
/**
|
235
|
-
* Lists active Gremlin queries. See Gremlin query status API for details about the output.
|
235
|
+
* Lists active Gremlin queries. See Gremlin query status API for details about the output. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Gremlin IAM condition key can be used in the policy document to restrict the use of Gremlin queries (see Condition keys available in Neptune IAM data-access policy statements).
|
236
236
|
*/
|
237
237
|
listGremlinQueries(params: Neptunedata.Types.ListGremlinQueriesInput, callback?: (err: AWSError, data: Neptunedata.Types.ListGremlinQueriesOutput) => void): Request<Neptunedata.Types.ListGremlinQueriesOutput, AWSError>;
|
238
238
|
/**
|
239
|
-
* Lists active Gremlin queries. See Gremlin query status API for details about the output.
|
239
|
+
* Lists active Gremlin queries. See Gremlin query status API for details about the output. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Gremlin IAM condition key can be used in the policy document to restrict the use of Gremlin queries (see Condition keys available in Neptune IAM data-access policy statements).
|
240
240
|
*/
|
241
241
|
listGremlinQueries(callback?: (err: AWSError, data: Neptunedata.Types.ListGremlinQueriesOutput) => void): Request<Neptunedata.Types.ListGremlinQueriesOutput, AWSError>;
|
242
242
|
/**
|
243
|
-
* Retrieves a list of the loadIds for all active loader jobs.
|
243
|
+
* Retrieves a list of the loadIds for all active loader jobs. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ListLoaderJobs IAM action in that cluster..
|
244
244
|
*/
|
245
245
|
listLoaderJobs(params: Neptunedata.Types.ListLoaderJobsInput, callback?: (err: AWSError, data: Neptunedata.Types.ListLoaderJobsOutput) => void): Request<Neptunedata.Types.ListLoaderJobsOutput, AWSError>;
|
246
246
|
/**
|
247
|
-
* Retrieves a list of the loadIds for all active loader jobs.
|
247
|
+
* Retrieves a list of the loadIds for all active loader jobs. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ListLoaderJobs IAM action in that cluster..
|
248
248
|
*/
|
249
249
|
listLoaderJobs(callback?: (err: AWSError, data: Neptunedata.Types.ListLoaderJobsOutput) => void): Request<Neptunedata.Types.ListLoaderJobsOutput, AWSError>;
|
250
250
|
/**
|
251
|
-
* Returns a list of Neptune ML data processing jobs. See Listing active data-processing jobs using the Neptune ML dataprocessing command.
|
251
|
+
* Returns a list of Neptune ML data processing jobs. See Listing active data-processing jobs using the Neptune ML dataprocessing command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ListMLDataProcessingJobs IAM action in that cluster.
|
252
252
|
*/
|
253
253
|
listMLDataProcessingJobs(params: Neptunedata.Types.ListMLDataProcessingJobsInput, callback?: (err: AWSError, data: Neptunedata.Types.ListMLDataProcessingJobsOutput) => void): Request<Neptunedata.Types.ListMLDataProcessingJobsOutput, AWSError>;
|
254
254
|
/**
|
255
|
-
* Returns a list of Neptune ML data processing jobs. See Listing active data-processing jobs using the Neptune ML dataprocessing command.
|
255
|
+
* Returns a list of Neptune ML data processing jobs. See Listing active data-processing jobs using the Neptune ML dataprocessing command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ListMLDataProcessingJobs IAM action in that cluster.
|
256
256
|
*/
|
257
257
|
listMLDataProcessingJobs(callback?: (err: AWSError, data: Neptunedata.Types.ListMLDataProcessingJobsOutput) => void): Request<Neptunedata.Types.ListMLDataProcessingJobsOutput, AWSError>;
|
258
258
|
/**
|
259
|
-
* Lists existing inference endpoints. See Managing inference endpoints using the endpoints command.
|
259
|
+
* Lists existing inference endpoints. See Managing inference endpoints using the endpoints command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ListMLEndpoints IAM action in that cluster.
|
260
260
|
*/
|
261
261
|
listMLEndpoints(params: Neptunedata.Types.ListMLEndpointsInput, callback?: (err: AWSError, data: Neptunedata.Types.ListMLEndpointsOutput) => void): Request<Neptunedata.Types.ListMLEndpointsOutput, AWSError>;
|
262
262
|
/**
|
263
|
-
* Lists existing inference endpoints. See Managing inference endpoints using the endpoints command.
|
263
|
+
* Lists existing inference endpoints. See Managing inference endpoints using the endpoints command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ListMLEndpoints IAM action in that cluster.
|
264
264
|
*/
|
265
265
|
listMLEndpoints(callback?: (err: AWSError, data: Neptunedata.Types.ListMLEndpointsOutput) => void): Request<Neptunedata.Types.ListMLEndpointsOutput, AWSError>;
|
266
266
|
/**
|
267
|
-
* Lists Neptune ML model-training jobs. See Model training using the modeltraining command.
|
267
|
+
* Lists Neptune ML model-training jobs. See Model training using the modeltraining command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:neptune-db:ListMLModelTrainingJobs IAM action in that cluster.
|
268
268
|
*/
|
269
269
|
listMLModelTrainingJobs(params: Neptunedata.Types.ListMLModelTrainingJobsInput, callback?: (err: AWSError, data: Neptunedata.Types.ListMLModelTrainingJobsOutput) => void): Request<Neptunedata.Types.ListMLModelTrainingJobsOutput, AWSError>;
|
270
270
|
/**
|
271
|
-
* Lists Neptune ML model-training jobs. See Model training using the modeltraining command.
|
271
|
+
* Lists Neptune ML model-training jobs. See Model training using the modeltraining command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:neptune-db:ListMLModelTrainingJobs IAM action in that cluster.
|
272
272
|
*/
|
273
273
|
listMLModelTrainingJobs(callback?: (err: AWSError, data: Neptunedata.Types.ListMLModelTrainingJobsOutput) => void): Request<Neptunedata.Types.ListMLModelTrainingJobsOutput, AWSError>;
|
274
274
|
/**
|
275
|
-
* Returns a list of model transform job IDs. See Use a trained model to generate new model artifacts.
|
275
|
+
* Returns a list of model transform job IDs. See Use a trained model to generate new model artifacts. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ListMLModelTransformJobs IAM action in that cluster.
|
276
276
|
*/
|
277
277
|
listMLModelTransformJobs(params: Neptunedata.Types.ListMLModelTransformJobsInput, callback?: (err: AWSError, data: Neptunedata.Types.ListMLModelTransformJobsOutput) => void): Request<Neptunedata.Types.ListMLModelTransformJobsOutput, AWSError>;
|
278
278
|
/**
|
279
|
-
* Returns a list of model transform job IDs. See Use a trained model to generate new model artifacts.
|
279
|
+
* Returns a list of model transform job IDs. See Use a trained model to generate new model artifacts. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ListMLModelTransformJobs IAM action in that cluster.
|
280
280
|
*/
|
281
281
|
listMLModelTransformJobs(callback?: (err: AWSError, data: Neptunedata.Types.ListMLModelTransformJobsOutput) => void): Request<Neptunedata.Types.ListMLModelTransformJobsOutput, AWSError>;
|
282
282
|
/**
|
283
|
-
* Lists active openCypher queries. See Neptune openCypher status endpoint for more information.
|
283
|
+
* Lists active openCypher queries. See Neptune openCypher status endpoint for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
|
284
284
|
*/
|
285
285
|
listOpenCypherQueries(params: Neptunedata.Types.ListOpenCypherQueriesInput, callback?: (err: AWSError, data: Neptunedata.Types.ListOpenCypherQueriesOutput) => void): Request<Neptunedata.Types.ListOpenCypherQueriesOutput, AWSError>;
|
286
286
|
/**
|
287
|
-
* Lists active openCypher queries. See Neptune openCypher status endpoint for more information.
|
287
|
+
* Lists active openCypher queries. See Neptune openCypher status endpoint for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
|
288
288
|
*/
|
289
289
|
listOpenCypherQueries(callback?: (err: AWSError, data: Neptunedata.Types.ListOpenCypherQueriesOutput) => void): Request<Neptunedata.Types.ListOpenCypherQueriesOutput, AWSError>;
|
290
290
|
/**
|
291
|
-
* Manages the generation and use of property graph statistics.
|
291
|
+
* Manages the generation and use of property graph statistics. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ManageStatistics IAM action in that cluster.
|
292
292
|
*/
|
293
293
|
managePropertygraphStatistics(params: Neptunedata.Types.ManagePropertygraphStatisticsInput, callback?: (err: AWSError, data: Neptunedata.Types.ManagePropertygraphStatisticsOutput) => void): Request<Neptunedata.Types.ManagePropertygraphStatisticsOutput, AWSError>;
|
294
294
|
/**
|
295
|
-
* Manages the generation and use of property graph statistics.
|
295
|
+
* Manages the generation and use of property graph statistics. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ManageStatistics IAM action in that cluster.
|
296
296
|
*/
|
297
297
|
managePropertygraphStatistics(callback?: (err: AWSError, data: Neptunedata.Types.ManagePropertygraphStatisticsOutput) => void): Request<Neptunedata.Types.ManagePropertygraphStatisticsOutput, AWSError>;
|
298
298
|
/**
|
299
|
-
* Manages the generation and use of RDF graph statistics.
|
299
|
+
* Manages the generation and use of RDF graph statistics. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ManageStatistics IAM action in that cluster.
|
300
300
|
*/
|
301
301
|
manageSparqlStatistics(params: Neptunedata.Types.ManageSparqlStatisticsInput, callback?: (err: AWSError, data: Neptunedata.Types.ManageSparqlStatisticsOutput) => void): Request<Neptunedata.Types.ManageSparqlStatisticsOutput, AWSError>;
|
302
302
|
/**
|
303
|
-
* Manages the generation and use of RDF graph statistics.
|
303
|
+
* Manages the generation and use of RDF graph statistics. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ManageStatistics IAM action in that cluster.
|
304
304
|
*/
|
305
305
|
manageSparqlStatistics(callback?: (err: AWSError, data: Neptunedata.Types.ManageSparqlStatisticsOutput) => void): Request<Neptunedata.Types.ManageSparqlStatisticsOutput, AWSError>;
|
306
306
|
/**
|
307
|
-
* Starts a Neptune bulk loader job to load data from an Amazon S3 bucket into a Neptune DB instance. See Using the Amazon Neptune Bulk Loader to Ingest Data.
|
307
|
+
* Starts a Neptune bulk loader job to load data from an Amazon S3 bucket into a Neptune DB instance. See Using the Amazon Neptune Bulk Loader to Ingest Data. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:StartLoaderJob IAM action in that cluster.
|
308
308
|
*/
|
309
309
|
startLoaderJob(params: Neptunedata.Types.StartLoaderJobInput, callback?: (err: AWSError, data: Neptunedata.Types.StartLoaderJobOutput) => void): Request<Neptunedata.Types.StartLoaderJobOutput, AWSError>;
|
310
310
|
/**
|
311
|
-
* Starts a Neptune bulk loader job to load data from an Amazon S3 bucket into a Neptune DB instance. See Using the Amazon Neptune Bulk Loader to Ingest Data.
|
311
|
+
* Starts a Neptune bulk loader job to load data from an Amazon S3 bucket into a Neptune DB instance. See Using the Amazon Neptune Bulk Loader to Ingest Data. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:StartLoaderJob IAM action in that cluster.
|
312
312
|
*/
|
313
313
|
startLoaderJob(callback?: (err: AWSError, data: Neptunedata.Types.StartLoaderJobOutput) => void): Request<Neptunedata.Types.StartLoaderJobOutput, AWSError>;
|
314
314
|
/**
|
315
|
-
* Creates a new Neptune ML data processing job for processing the graph data exported from Neptune for training. See The dataprocessing command.
|
315
|
+
* Creates a new Neptune ML data processing job for processing the graph data exported from Neptune for training. See The dataprocessing command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:StartMLModelDataProcessingJob IAM action in that cluster.
|
316
316
|
*/
|
317
317
|
startMLDataProcessingJob(params: Neptunedata.Types.StartMLDataProcessingJobInput, callback?: (err: AWSError, data: Neptunedata.Types.StartMLDataProcessingJobOutput) => void): Request<Neptunedata.Types.StartMLDataProcessingJobOutput, AWSError>;
|
318
318
|
/**
|
319
|
-
* Creates a new Neptune ML data processing job for processing the graph data exported from Neptune for training. See The dataprocessing command.
|
319
|
+
* Creates a new Neptune ML data processing job for processing the graph data exported from Neptune for training. See The dataprocessing command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:StartMLModelDataProcessingJob IAM action in that cluster.
|
320
320
|
*/
|
321
321
|
startMLDataProcessingJob(callback?: (err: AWSError, data: Neptunedata.Types.StartMLDataProcessingJobOutput) => void): Request<Neptunedata.Types.StartMLDataProcessingJobOutput, AWSError>;
|
322
322
|
/**
|
323
|
-
* Creates a new Neptune ML model training job. See Model training using the modeltraining command.
|
323
|
+
* Creates a new Neptune ML model training job. See Model training using the modeltraining command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:StartMLModelTrainingJob IAM action in that cluster.
|
324
324
|
*/
|
325
325
|
startMLModelTrainingJob(params: Neptunedata.Types.StartMLModelTrainingJobInput, callback?: (err: AWSError, data: Neptunedata.Types.StartMLModelTrainingJobOutput) => void): Request<Neptunedata.Types.StartMLModelTrainingJobOutput, AWSError>;
|
326
326
|
/**
|
327
|
-
* Creates a new Neptune ML model training job. See Model training using the modeltraining command.
|
327
|
+
* Creates a new Neptune ML model training job. See Model training using the modeltraining command. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:StartMLModelTrainingJob IAM action in that cluster.
|
328
328
|
*/
|
329
329
|
startMLModelTrainingJob(callback?: (err: AWSError, data: Neptunedata.Types.StartMLModelTrainingJobOutput) => void): Request<Neptunedata.Types.StartMLModelTrainingJobOutput, AWSError>;
|
330
330
|
/**
|
331
|
-
* Creates a new model transform job. See Use a trained model to generate new model artifacts.
|
331
|
+
* Creates a new model transform job. See Use a trained model to generate new model artifacts. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:StartMLModelTransformJob IAM action in that cluster.
|
332
332
|
*/
|
333
333
|
startMLModelTransformJob(params: Neptunedata.Types.StartMLModelTransformJobInput, callback?: (err: AWSError, data: Neptunedata.Types.StartMLModelTransformJobOutput) => void): Request<Neptunedata.Types.StartMLModelTransformJobOutput, AWSError>;
|
334
334
|
/**
|
335
|
-
* Creates a new model transform job. See Use a trained model to generate new model artifacts.
|
335
|
+
* Creates a new model transform job. See Use a trained model to generate new model artifacts. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:StartMLModelTransformJob IAM action in that cluster.
|
336
336
|
*/
|
337
337
|
startMLModelTransformJob(callback?: (err: AWSError, data: Neptunedata.Types.StartMLModelTransformJobOutput) => void): Request<Neptunedata.Types.StartMLModelTransformJobOutput, AWSError>;
|
338
338
|
}
|
@@ -1062,7 +1062,7 @@ declare namespace Neptunedata {
|
|
1062
1062
|
}
|
1063
1063
|
export interface GetSparqlStatisticsOutput {
|
1064
1064
|
/**
|
1065
|
-
* The HTTP return code of the request. If the request succeeded, the code is 200. See Common error codes for DFE statistics request for a list of common errors.
|
1065
|
+
* The HTTP return code of the request. If the request succeeded, the code is 200. See Common error codes for DFE statistics request for a list of common errors. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetStatisticsStatus IAM action in that cluster.
|
1066
1066
|
*/
|
1067
1067
|
status: String;
|
1068
1068
|
/**
|
@@ -1756,6 +1756,7 @@ declare namespace Omics {
|
|
1756
1756
|
export type ETagAlgorithm = "FASTQ_MD5up"|"BAM_MD5up"|"CRAM_MD5up"|string;
|
1757
1757
|
export type Encoding = string;
|
1758
1758
|
export type EncryptionType = "KMS"|string;
|
1759
|
+
export type EngineLogStream = string;
|
1759
1760
|
export type EscapeChar = string;
|
1760
1761
|
export type EscapeQuotes = boolean;
|
1761
1762
|
export type ExportJobId = string;
|
@@ -2597,12 +2598,20 @@ declare namespace Omics {
|
|
2597
2598
|
* The run's retention mode.
|
2598
2599
|
*/
|
2599
2600
|
retentionMode?: RunRetentionMode;
|
2601
|
+
/**
|
2602
|
+
* The reason a run has failed.
|
2603
|
+
*/
|
2604
|
+
failureReason?: RunFailureReason;
|
2605
|
+
/**
|
2606
|
+
* The location of the run log.
|
2607
|
+
*/
|
2608
|
+
logLocation?: RunLogLocation;
|
2600
2609
|
}
|
2601
2610
|
export type GetRunResponsePriorityInteger = number;
|
2602
2611
|
export type GetRunResponseStorageCapacityInteger = number;
|
2603
2612
|
export interface GetRunTaskRequest {
|
2604
2613
|
/**
|
2605
|
-
* The
|
2614
|
+
* The workflow run ID.
|
2606
2615
|
*/
|
2607
2616
|
id: RunId;
|
2608
2617
|
/**
|
@@ -2659,6 +2668,10 @@ declare namespace Omics {
|
|
2659
2668
|
* The instance type for a task.
|
2660
2669
|
*/
|
2661
2670
|
instanceType?: TaskInstanceType;
|
2671
|
+
/**
|
2672
|
+
* The reason a task has failed.
|
2673
|
+
*/
|
2674
|
+
failureReason?: TaskFailureReason;
|
2662
2675
|
}
|
2663
2676
|
export type GetRunTaskResponseCpusInteger = number;
|
2664
2677
|
export type GetRunTaskResponseGpusInteger = number;
|
@@ -4110,6 +4123,7 @@ declare namespace Omics {
|
|
4110
4123
|
export type RunArn = string;
|
4111
4124
|
export type RunExport = "DEFINITION"|string;
|
4112
4125
|
export type RunExportList = RunExport[];
|
4126
|
+
export type RunFailureReason = string;
|
4113
4127
|
export type RunGroupArn = string;
|
4114
4128
|
export type RunGroupId = string;
|
4115
4129
|
export type RunGroupList = RunGroupListItem[];
|
@@ -4204,6 +4218,17 @@ declare namespace Omics {
|
|
4204
4218
|
export type RunListItemStorageCapacityInteger = number;
|
4205
4219
|
export type RunListToken = string;
|
4206
4220
|
export type RunLogLevel = "OFF"|"FATAL"|"ERROR"|"ALL"|string;
|
4221
|
+
export interface RunLogLocation {
|
4222
|
+
/**
|
4223
|
+
* The log stream ARN for the engine log.
|
4224
|
+
*/
|
4225
|
+
engineLogStream?: EngineLogStream;
|
4226
|
+
/**
|
4227
|
+
* The log stream ARN for the run log.
|
4228
|
+
*/
|
4229
|
+
runLogStream?: RunLogStream;
|
4230
|
+
}
|
4231
|
+
export type RunLogStream = string;
|
4207
4232
|
export type RunName = string;
|
4208
4233
|
export type RunOutputUri = string;
|
4209
4234
|
export interface RunParameters {
|
@@ -4750,6 +4775,7 @@ declare namespace Omics {
|
|
4750
4775
|
export interface TagResourceResponse {
|
4751
4776
|
}
|
4752
4777
|
export type TagValue = string;
|
4778
|
+
export type TaskFailureReason = string;
|
4753
4779
|
export type TaskId = string;
|
4754
4780
|
export type TaskInstanceType = string;
|
4755
4781
|
export type TaskList = TaskListItem[];
|