AWS eventbridge documentation change
Summary
Updated documentation to replace 'AWS CloudFormation' with 'CloudFormation' throughout the document for terminology consistency
Security assessment
The changes are purely branding/terminology updates removing 'AWS' from CloudFormation references. No security vulnerabilities, mitigations, or new security features are mentioned. The existing security context around webhook secrets and signature validation remains unchanged.
Diff
diff --git a/eventbridge/latest/userguide/eb-saas-furls.md b/eventbridge/latest/userguide/eb-saas-furls.md index 226b952a4..321a6920d 100644 --- a//eventbridge/latest/userguide/eb-saas-furls.md +++ b//eventbridge/latest/userguide/eb-saas-furls.md @@ -5 +5 @@ -Step 1: Create the AWS CloudFormation stackStep 2: Create a GitHub webhookSet up a connection to a TwilioUpdate webhook secret or auth tokenUpdate Lambda functionAvailable event typesQuotas, error codes, and retrying delivery +Step 1: Create the CloudFormation stackStep 2: Create a GitHub webhookSet up a connection to a TwilioUpdate webhook secret or auth tokenUpdate Lambda functionAvailable event typesQuotas, error codes, and retrying delivery @@ -13 +13 @@ In order for the Inbound Webhook to be accessible by our partners, we're creatin -Your Amazon EventBridge [event bus](./eb-event-bus.html) can use an [AWS Lambda function URL](https://docs.aws.amazon.com/lambda/latest/dg/lambda-urls.html) created by an AWS CloudFormation template to receive [events](./eb-events.html) from supported SaaS providers. With function URLs, the event data is sent to a Lambda function. The function then converts this data into an event that can be ingested by EventBridge and sent to an event bus for processing. Once the event is on an event bus, you can use rules to filter the events, apply any configured input transformations, and then route it to the correct target. +Your Amazon EventBridge [event bus](./eb-event-bus.html) can use an [AWS Lambda function URL](https://docs.aws.amazon.com/lambda/latest/dg/lambda-urls.html) created by an CloudFormation template to receive [events](./eb-events.html) from supported SaaS providers. With function URLs, the event data is sent to a Lambda function. The function then converts this data into an event that can be ingested by EventBridge and sent to an event bus for processing. Once the event is on an event bus, you can use rules to filter the events, apply any configured input transformations, and then route it to the correct target. @@ -19 +19 @@ Creating Lambda function URLs will increase your monthly costs. For more informa -To set up a connection to EventBridge, you first select the SaaS provider that you want to set up a connection with. Then, you provide a _signing secret_ that you’ve created with that provider, and select the EventBridge event bus to send events to. Finally, you use an AWS CloudFormation template and create the needed resources to complete the connection. +To set up a connection to EventBridge, you first select the SaaS provider that you want to set up a connection with. Then, you provide a _signing secret_ that you’ve created with that provider, and select the EventBridge event bus to send events to. Finally, you use an CloudFormation template and create the needed resources to complete the connection. @@ -32 +32 @@ The following SaaS providers are currently available for use with EventBridge us - * Step 1: Create the AWS CloudFormation stack + * Step 1: Create the CloudFormation stack @@ -49 +49 @@ The following SaaS providers are currently available for use with EventBridge us -## Step 1: Create the AWS CloudFormation stack +## Step 1: Create the CloudFormation stack @@ -73 +73 @@ First, use the Amazon EventBridge console to create a CloudFormation stack: - * **I acknowledge that AWS CloudFormation might create IAM resources.** + * **I acknowledge that CloudFormation might create IAM resources.** @@ -75 +75 @@ First, use the Amazon EventBridge console to create a CloudFormation stack: - * **I acknowledge that AWS CloudFormation might create IAM resources with custom names.** + * **I acknowledge that CloudFormation might create IAM resources with custom names.** @@ -77 +77 @@ First, use the Amazon EventBridge console to create a CloudFormation stack: - * **I acknowledge that AWS CloudFormation might require the following capability:`CAPABILITY_AUTO_EXPAND`** + * **I acknowledge that CloudFormation might require the following capability:`CAPABILITY_AUTO_EXPAND`** @@ -94 +94 @@ To set up a connection between Twilio and EventBridge, first set up the connecti -### Step 2: Create the AWS CloudFormation stack +### Step 2: Create the CloudFormation stack @@ -116 +116 @@ To set up a connection between Twilio and EventBridge, first set up the connecti - * **I acknowledge that AWS CloudFormation might create IAM resources.** + * **I acknowledge that CloudFormation might create IAM resources.** @@ -118 +118 @@ To set up a connection between Twilio and EventBridge, first set up the connecti - * **I acknowledge that AWS CloudFormation might create IAM resources with custom names.** + * **I acknowledge that CloudFormation might create IAM resources with custom names.** @@ -120 +120 @@ To set up a connection between Twilio and EventBridge, first set up the connecti - * **I acknowledge that AWS CloudFormation might require the following capability: CAPABILITY_AUTO_EXPAND** + * **I acknowledge that CloudFormation might require the following capability: CAPABILITY_AUTO_EXPAND** @@ -137 +137 @@ After you set up the Lambda function URL, you need to give it to Twilio so that -GitHub doesn’t support having two secrets at the same time. You may experience resource downtime while the GitHub secret and the secret in the AWS CloudFormation stack are out of sync. GitHub messages sent while the secrets are out of sync will fail becaue of incorrect signatures. Wait until the GitHub and CloudFormation secrets are in sync, then try again. +GitHub doesn’t support having two secrets at the same time. You may experience resource downtime while the GitHub secret and the secret in the CloudFormation stack are out of sync. GitHub messages sent while the secrets are out of sync will fail becaue of incorrect signatures. Wait until the GitHub and CloudFormation secrets are in sync, then try again. @@ -141 +141 @@ GitHub doesn’t support having two secrets at the same time. You may experience - 2. Open the AWS CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). + 2. Open the CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). @@ -166 +166 @@ It may take up to one hour for the secret to propagate. To reduce this downtime, -Twilio doesn’t support having two secrets at the same time. You may experience resource downtime while the Twilio secret and the secret in the AWS CloudFormation stack are out of sync. Twilio messages sent while the secrets are out of sync will fail because of incorrect signatures. Wait until the Twilio and CloudFormation secrets are in sync, then try again. +Twilio doesn’t support having two secrets at the same time. You may experience resource downtime while the Twilio secret and the secret in the CloudFormation stack are out of sync. Twilio messages sent while the secrets are out of sync will fail because of incorrect signatures. Wait until the Twilio and CloudFormation secrets are in sync, then try again. @@ -170 +170 @@ Twilio doesn’t support having two secrets at the same time. You may experience - 2. Open the AWS CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). + 2. Open the CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). @@ -197 +197 @@ The Lambda function that's created by the CloudFormation stack creates the basic - 1. Open the AWS CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). + 1. Open the CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/).