Create an AWS configuration object, depending on the credential provider type.
- For more information on how to use awsConfig objects, see API Workflow - Manage AWS Configurations.
- For more information on credential provider types, see Configure for AWS.
NOTE: APIs for AWS configs apply only to instances of the Designer Cloud powered by Trifacta® platform
that are hosted on AWS and configured for
user mode of authentication. These configuration objects can be assigned to individual users as needed.
NOTE: Each request to the Designer Cloud powered by Trifacta® platform must include authentication credentials. See https://api.trifacta.com/ee/6.8/index.html#section/Authentication.
Request Body - default credential provider:
If the credential provider has been set to
default, then individual users must provide their own AWS key/secret combinations. The following is an example request for such an AWS configuration object:
Request Body - temporary credential provider:
If the credential provider type is set to
temporary, then you can use a request similar to the following to create an AWS configuration object that uses the specified IAM role for authentication:
Response Status Code - Success:
201 - Created
Response Body - default credential provider:
Response Body - temporary credential provider:
(optional) When creating an AWS configuration, an administrator can insert the personId parameter to assign the configuration to the internal identifier for the user.
If this parameter is not included, the AWS configuration is assigned to the user who created it.
NOTE: An AWSConfig object can only be assigned at the time of its creation. Each object can be assigned to a single user.
For more information, see API AWSConfigs Get v4.
This page has no comments.