AWS glue documentation change
Summary
Removed Visual ETL UI configuration instructions and associated screenshot reference
Security assessment
Removal of UI-specific instructions appears to be content reorganization rather than security-related. No evidence this change addresses a specific vulnerability.
Diff
diff --git a/glue/latest/dg/connecting-to-data-teradata-nos.md b/glue/latest/dg/connecting-to-data-teradata-nos.md index f870b8449..69dc9370e 100644 --- a/glue/latest/dg/connecting-to-data-teradata-nos.md +++ b/glue/latest/dg/connecting-to-data-teradata-nos.md @@ -5 +5 @@ -Creating a Teradata NOS connection Reading from Teradata tables Writing to Teradata tablesTeradata connection option referenceProvide Options in AWS Glue Visual ETL UI +Creating a Teradata NOS connection Reading from Teradata tables Writing to Teradata tablesTeradata connection option reference @@ -25,2 +24,0 @@ For more information about Teradata, consult the [Teradata documentation](https: - * Provide Options in AWS Glue Visual ETL UI - @@ -51 +49 @@ To connect to Teradata NOS from AWS Glue, you will need to create and store your - * When selecting Key/value pairs, create a pair for the key USERNAME with the value `teradataUsername`. + * When selecting Key/value pairs, create a pair for the key user with the value `teradataUsername`. @@ -53 +51 @@ To connect to Teradata NOS from AWS Glue, you will need to create and store your - * When selecting Key/value pairs, create a pair for the key PASSWORD with the value `teradataPassword`. + * When selecting Key/value pairs, create a pair for the key password with the value `teradataPassword`. @@ -130 +128 @@ Additionally, you can use Spark DataFrame API to read from Teradata tables. For - "user": "teradataUsername", # or use "username" as key here + "user": "teradataUsername", @@ -163 +161,8 @@ For example: -## Teradata connection option reference +### Create a Teradata job with AWS Glue Studio + +AWS Glue Studio supports the creation of AWS Glue jobs as a [ visual ETL job ](https://docs.aws.amazon.com/glue/latest/dg/job-editor-features.html). To configure a successful AWS Glue job, other than configuring the data source and target, you will need to provide below required properties in the Custom Teradata Vantage NOS properties in the UI: + + * `dbtable` + + * `staging_fs_url` + @@ -165 +170,3 @@ For example: -**Connection and Operation Options:** + + +## Teradata connection option reference @@ -169 +176 @@ For example: - * `staging_fs_url` — Required. Used for Read/Write. A writable location in Amazon S3, to be used for unloaded data when reading from Teradata, and for Parquet data to be loaded into Redshift when writing to Teradata. The S3 bucket must be in the same region as the region of your AWS Glue jobs. + * `staging_fs_url` — Required. Used for Read/Write. A writeable location in Amazon S3, to be used for unloaded data when reading from Teradata, and for Parquet data to be loaded into Redshift when writing to Teradata. The S3 bucket must be in the same region as the region of your AWS Glue jobs. @@ -194,21 +200,0 @@ See [Teradata Vantage connections](./aws-glue-programming-etl-connect-teradata-h -**Authorization Options:** - -Below are options used to provide AWS account credentials that the connector uses to access the staging Amazon S3 bucket. You can choose to (1) not provide any authorization options at all, and use temporary credentials generated from your AWS Glue execution role; or (2) provide an authorization object, `auth_object` you created; or (3) provide `aws_access_key_id and aws_secret_access_key` if using long term credentials, or provide `aws_access_key`, `aws_secret_access_key`, and `aws_session_token` if using temporary credentials. - - * `auth_object` – Optional. Used for accessing the staging Amazon S3 bucket. An authorization object string created in Teradata instance. If provided, the connector will use this authorization object to access the staging Amazon S3 bucket. If not provided, and `aws_access_key_id` and `aws_secret_access_key` are also not provided, a temporary credential will be retrieved from AWS Glue execution role and used by the connector. The AWS account associated with this authorization object must be in the same region as your AWS Glue jobs and your staging Amazon S3 bucket or configured with cross account trust. - - * `aws_access_key_id` – Optional. Used for accessing the staging Amazon S3 bucket. Part of an AWS account security credential. If `auth_object` is not provided, and `aws_access_key_id` is provided with `aws_secret_access_key`, the connector will use them to access staging Amazon S3 bucket. The AWS account associated with this access key must be in the same region as your AWS Glue jobs and your staging Amazon S3 bucket or configured with cross account trust. - - * `aws_secret_access_key` – Optional. Used for accessing the staging Amazon S3 bucket. Part of an AWS account security credential. If `auth_object` is not provided, and `aws_secret_access_key` is provided with `aws_access_key_id` , the connector will use them to access staging Amazon S3 bucket. The AWS account associated with this secret key must be in the same region as your AWS Glue jobs and your staging Amazon S3 bucket or configured with cross account trust. - - * `aws_session_token` – Optional. Used for accessing the staging Amazon S3 bucket. Part of a temporary AWS account security credential. Should be provided with `aws_access_key_id` and `aws_secret_access_key`. - - - - -## Provide Options in AWS Glue Visual ETL UI - -You can provide all above options in your visual ETL job UI. For connectionName option, you should choose it from the Teradata Vantage NOS connection drop down list. For all other options, you should provide them through the Custom Teradata Vantage NOS properties as key value pairs. - - -