AWS glue documentation change
Summary
Removed 'Integration states' section, updated branding from 'Amazon CloudWatch' to 'CloudWatch', fixed typographical errors in EventBridge rule prefixes, and updated navigation links.
Security assessment
The changes are primarily editorial and organizational, involving removal of a redundant section, branding updates, and typo corrections. There is no mention of security vulnerabilities, patches, or new security features. The reference to 'insufficient permissions' in the context of log events is not a new addition and does not indicate a security issue.
Diff
diff --git a/glue/latest/dg/zero-etl-monitoring.md b/glue/latest/dg/zero-etl-monitoring.md index 910073d7e..435cbfa75 100644 --- a//glue/latest/dg/zero-etl-monitoring.md +++ b//glue/latest/dg/zero-etl-monitoring.md @@ -7 +7 @@ -Integration statesViewing logsViewing metricsEvent notifications +Viewing logsViewing metricsEvent notifications @@ -11,21 +10,0 @@ Integration statesViewing logsViewing metricsEvent notifications -## Integration states - -The following integration states describe the integration: - - * `Creating` \- The integration is being created. - - * `Active` \- The integration is sending transactional data to the target. - - * `Modifying` \- The integration is being modified. - - * `Syncing` \- The integration has encountered a recoverable error and is re-seeding data. - - * `Needs attention` \- The integration encountered an event or error that requires manual intervention to resolve it. To fix the issue, follow the instructions in the error message on the integration details. - - * `Failed` \- The integration encountered an unrecoverable event or error. You must delete and recreate the integration. - - * `Deleting` \- The integration is being deleted. - - - - @@ -34 +13 @@ The following integration states describe the integration: -AWS Glue zero-ETL integrations generate Amazon CloudWatch logs for visibility into your data movement. Log events relating to each successful ingestion or any failures experienced due to problematic data records at source, or data write errors due to schema changes or insufficient permissions are emitted to a default log group created in a customer account. +AWS Glue zero-ETL integrations generate CloudWatch logs for visibility into your data movement. Log events relating to each successful ingestion or any failures experienced due to problematic data records at source, or data write errors due to schema changes or insufficient permissions are emitted to a default log group created in a customer account. @@ -36 +15 @@ AWS Glue zero-ETL integrations generate Amazon CloudWatch logs for visibility in -For each integration created, the log events for that integration will be collected under `/aws-glue/zeroETL-integrations/logs/` in Amazon Cloudwatch. Inside the log group, log messages will be split into log streams. Each integration created has a dedicated log stream to where all logs for that integration are written. For example, logs for an integration with IntegrationArn `arn:aws:glue:us-east-1:123456789012:integration:03cabe77-79e7-4b7a-b3da-8c160bea6bbf` can be found under /aws-glue/zeroETL-integrations/logs/03cabe77-79e7-4b7a-b3da-8c160bea6bbf. {IntegrationId} can be referenced from the {integrationArn} generated when an integration is created. +For each integration created, the log events for that integration will be collected under `/aws-glue/zeroETL-integrations/logs/` in CloudWatch. Inside the log group, log messages will be split into log streams. Each integration created has a dedicated log stream to where all logs for that integration are written. @@ -40 +19 @@ For each integration created, the log events for that integration will be collec -For a cross-account scenario, source processing Logs are emitted in the source account where the integration exists and target processing logs are emitted in the target account where the target database exists. +For a cross-account scenario, source processing logs are emitted in the source account where the integration exists and target processing logs are emitted in the target account where the target database exists. @@ -120 +99 @@ Log format: zero-ETL integrations emit four types of log messages: -Once an integration completes, you can see these Amazon Cloudwatch metrics generated in your account for each AWS Glue job run: +Once an integration completes, you can see these CloudWatch metrics generated in your account for each AWS Glue job run: @@ -156,3 +135 @@ Zero-ETL integrations use Amazon EventBridge to manage event notifications to ke -EventBridge provides an environment for you to write event rules, which can specify actions to take for specific events. You can also set up targets, which are resources that EventBridge can send an event to. A target can include an API destination, an Amazon CloudWatch log group, and others. For more information about rules, see [Amazon EventBridge rules](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-rules.html). For more information about targets, see [Amazon EventBridge targets](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-targets.html). - -To capture all Zero-ETL notifications, create an Eventbridge rule which matches the following: +To capture all Zero-ETL notifications, create an EventBridge rule which matches the following: @@ -163 +140 @@ To capture all Zero-ETL notifications, create an Eventbridge rule which matches - "prefix": "aws.glue-zero-etl“ + "prefix": "aws.glue-zero-etl" @@ -166 +143 @@ To capture all Zero-ETL notifications, create an Eventbridge rule which matches - "prefix": "Glue Zero ETL“ + "prefix": "Glue Zero ETL" @@ -169,0 +147 @@ To capture all Zero-ETL notifications, create an Eventbridge rule which matches +The following table includes zero-ETL integration events: @@ -171,3 +149 @@ To capture all Zero-ETL notifications, create an Eventbridge rule which matches -The following table includes zero-ETL integration events, with additional metadata: - -Customer-facing detail type | Explanation +Detail type | Explanation @@ -188 +164 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Using APIs +Creating and managing integrations @@ -190 +166 @@ Using APIs -Limitations +Schema unnesting & data partitioning