AWS glue documentation change
Summary
Removed detailed section about Unified connections features and considerations, replaced with simplified heading. Deleted content included security-related details about Secrets Manager integration, IAM permissions, and VPC requirements.
Security assessment
While removed content included security practices, there's no evidence this change addresses a specific vulnerability. Appears to be documentation restructuring rather than security remediation.
Diff
diff --git a/glue/latest/dg/glue-connections.md b/glue/latest/dg/glue-connections.md index 4b3f7c5c1..1e2ae0a84 100644 --- a/glue/latest/dg/glue-connections.md +++ b/glue/latest/dg/glue-connections.md @@ -5 +5 @@ -Overview of using connectors and connectionsUnified connections +Overview of using connectors and connections @@ -46,73 +45,0 @@ The following steps describe the overall process of using connectors in AWS Glue -## Unified connections - -With Unified connections, you can configure a data connection once, and it can be reused by various services for use cases in data integration, data analytics, and data science. You can create data connections through the AWS Glue console, or custom-built applications using unified data connectivity APIs. With Unified connections, you can set up a connection to a data source using a connection configuration template that is standardized for multiple services. These services (AWS Glue, Amazon SageMaker AI Unified Studio and Amazon Athena) can share and reuse the same connection with proper permission configuration. - -AWS Glue Studio now creates unified connections by default. In the AWS Glue console, you can see the version of the connection in the connections table on the connections page, on the connections detail page, and the connections table in the job details page. - -The connection version is visible on Connection details: - - - -The connection version is also visible when viewing all your Connections. - - - -Finally, connection version is visible in the Job details tab for a job. - - - -With version 2 connections, you have the following expanded data connectivity capabilities: - - * **Connection type discovery** : Support for creating connections using standardized templates. AWS Glue automatically discovers the connection types accessible by you and the required and optional inputs for a given connection type. - - * **Reusability** : Connection definitions that are reusable across AWS data processing engines and tools like AWS Glue, Amazon Athena, and Amazon SageMaker AI. Connections now contain AthenaProperties, SparkProperties, PythonProperties which allow to specify compute environment/service specific connection properties in addition to the common properties stored in ConnectionProperties. Athena now creates Connections in AWS Glue by specifying Athena specific properties in the AthenaProperties property map. - - * **Data preview** : Ability to browse metadata and preview data from connected sources. - - * **Connector metadata** : Reusable connections may be used in order to discover table metadata. - - * **Service linked secrets** : Users may provide necessary OAuth, basic or custom authentication credentials in the `CreateConnection` request. The CreateConnection API creates a Service Linked Secret in your account and stores the credentials on your behalf. - - - - -### Supported authentication types - -Unified connections supports the following authentication types: - - * **BASIC** – Most database connection types and existing AWS Glue connection types support basic authentication, which is a username and password. Previously, the naming of the keys in SecretsManager were connector specific and, for example, may have been user, username, userName, opensearch.net.http.auth.user, etc. This is where unified connections standardized basic authentication connection types on USERNAME and PASSWORD keys. - - * **OAUTH2** – The majority of newly launched SaaS connection types support OAuth2 protocol. - - * **CUSTOM** – A few connection types have some other authentication mechanism such as Google BigQuery where users are expected to provide the JSON which they get from Google BigQuery. - - - - -### Considerations - -When you create a unified connection for data sources, consider the following differences: - - * When creating a unified connection via AWS Glue Studio, user credentials are stored in AWS Secrets Manager instead of the connection itself. This means jobs now need access to Secrets Manager. - - * If jobs run in a VPC, they require either a VPC endpoint or NAT gateway to access AWS Secrets Manager and Secure Token Service (STS), which incurs additional costs. - - * For certain data sources (Redshift, SQL Server, MySQL, Oracle, PostgreSQL), creating a unified connection via AWS Glue Studio requires access to AWS STS and AWS Secrets Manager. This is necessary to establish a secure connection and retrieve the required credentials for accessing these data sources within your Virtual Private Cloud (VPC). - - * Creating a unified connection via AWS Glue Studio requires an IAM role with permissions to access AWS Secrets Manager and manage VPC resources (if using a VPC): - - * secretsmanager:GetSecretValue - - * secretsmanager:PutSecretValue - - * secretsmanager:DescribeSecret - - * ec2:CreateNetworkInterface - - * ec2:DeleteNetworkInterface - - * ec2:DescribeNetworkInterfaces - - - - @@ -127 +54 @@ Migrating to AWS Glue Schema Registry -Available connections +Unified connections