AWS eventbridge documentation change
Summary
Added documentation about connection authorization storage and encryption options, including details about using customer managed keys for secrets encryption
Security assessment
The changes document security-related features (secret storage and encryption options) but do not indicate a specific security vulnerability being addressed. The addition about customer managed keys enhances security documentation but doesn't reference a specific incident.
Diff
diff --git a/eventbridge/latest/userguide/eb-target-connection.md b/eventbridge/latest/userguide/eb-target-connection.md index 34148d73f..a2945c5b3 100644 --- a//eventbridge/latest/userguide/eb-target-connection.md +++ b//eventbridge/latest/userguide/eb-target-connection.md @@ -2,0 +3,2 @@ +Storing connection authorization + @@ -36,0 +39,4 @@ For more information, see [Call HTTPS APIs in Step Functions workflows](https:// +Connections are reusable. You can use the same connection to the same API for multiple EventBridge API destinations or Step Functions tasks, as long as the authentication method is the same. If API destinations or tasks require different authentication, then you must create separate connections. + +## Storing connection authorization parameters in AWS Secrets Manager + @@ -41 +47 @@ EventBridge connections support the following authentication methods: basic, OAu -Connections are reusable. You can use the same connection to the same API for multiple EventBridge API destinations or Step Functions tasks, as long as the authentication method is the same. If API destinations or tasks require different authentication, then you must create separate connections. +While by default EventBridge uses an AWS owned key to encrypt and decrypt the connection secret, you can specify a customer managed key for EventBridge to use instead. For more information, see [Encrypting connections](./encryption-connections.html).