update live-events page with Shalev

Author: sivanel97

docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/installations/live-events.md

@@ -11,12 +11,7 @@ import Image from "@theme/IdealImage";
 Port's AWS integration supports real-time event processing, allowing for accurate representation of your AWS infrastructure inside Port. This guide explains how to set up live events for your AWS resources.
 
 :::info Current Limitations
-Live events are currently only available for:
-- **Single account installations** (not multi-account).
-- **Default Terraform installation** with support for three resource types by default:
-  - `EC2 Instances`.
-  - `S3 Buckets`.
-  - `CloudFormation Stacks`.
+Live events are currently only available for **Single account installations** (not multi-account).
 :::
 
 ## Prerequisites
@@ -35,8 +30,6 @@ Before setting up live events, ensure you have:
 
 ## How live events work
 
-<img src='/img/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/live-events-diagram.svg' width='50%' border='1px' />
-
 The live events flow follows these steps:
 
 1. **AWS Services** generate events when resources change.
@@ -45,6 +38,9 @@ The live events flow follows these steps:
 4. **API Gateway** receives the events and forwards them to Port.
 5. **Port Integration** processes the events and updates your software catalog.
 
+<img src='/img/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/live-events-diagram.svg' width='50%' border='1px' />
+<br></br>
+
 ## Setup methods
 
 <Tabs>
@@ -184,93 +180,23 @@ Replace `"AWS::SSM::Parameter"` with the appropriate AWS resource type:
 </TabItem>
 </Tabs>
 
-## Testing your setup
-
-### Verify existing rules
-
-If you have other live event rules (e.g., S3 Bucket sync), verify they're working:
-
-1. Go to **EventBridge** → **Rules**.
-2. Check that your rules are **Enabled**.
-3. Look for any recent invocations in the **Metrics** tab.
-
-### Test live events
-
-1. **Trigger a test event**:
-   - Modify/create a resource (e.g., create an SSM Parameter).
-   - Update an existing resource.
-   - Delete a resource.
-
-2. **Verify in Port**:
-   - Check your software catalog for real-time updates.
-   - Look for the resource changes in Port's interface.
-
-### Example test for SSM parameters
-
-1. Go to **Systems Manager** → **Parameter Store**
-2. Create a new parameter:
-   - Name: `/test/my-parameter`
-   - Type: `String`
-   - Value: `test-value`
-3. Check Port for the new parameter entity.
 
-## Troubleshooting
+## Supported AWS services
 
-### Common issues
+The complete list of AWS services that support live events can be found [here](https://docs.aws.amazon.com/cloudcontrolapi/latest/userguide/supported-resources.html).
 
-**Events not appearing in Port:**
-- Verify the EventBridge rule is enabled
-- Check that the API Gateway endpoint is correct
-- Ensure the Port API key is valid
-- Verify the input transformer mapping is correct
+### Add other services
 
-**Wrong resource type in Port:**
-- Check the `resource_type` field in your input transformer template
-- Ensure it matches the expected AWS resource type
+To add live events for additional AWS services, follow these steps:
+1. Identify the service's event source and detail type.
+2. Create an EventBridge rule with the appropriate pattern.
+3. Configure the input transformer with the correct resource type.
 
-**Missing headers:**
-- Verify both `Content-Type` and `x-port-aws-ocean-api-key` headers are set
-- Check that the API key is the correct one for your Port environment
+:::info Default Terraform installation
 
-### Debugging Steps
-
-1. **Check EventBridge Metrics**:
-   - Go to EventBridge → Rules → Your Rule → Metrics
-   - Look for successful invocations and any errors
-
-2. **Check API Gateway Logs**:
-   - Go to API Gateway → Your API → Stages → production → Logs
-   - Look for incoming requests and any errors
-
-3. **Verify Event Pattern**:
-   - Test your event pattern with sample events
-   - Use EventBridge's "Test pattern" feature
-
-## Supported AWS Services
-
-The following AWS services can be configured for live events:
-
-| Service | Event Source | Detail Type | Resource Type |
-|---------|--------------|-------------|---------------|
-| EC2 | `aws.ec2` | `EC2 Instance State-change Notification` | `AWS::EC2::Instance` |
-| S3 | `aws.s3` | `Object Created`, `Object Deleted` | `AWS::S3::Bucket` |
-| CloudFormation | `aws.cloudformation` | `CloudFormation Stack State Change` | `AWS::CloudFormation::Stack` |
-| Systems Manager | `aws.ssm` | `Parameter Store Change` | `AWS::SSM::Parameter` |
-
-:::info Adding More Services
-To add live events for additional AWS services, follow the same pattern:
-1. Identify the service's event source and detail type
-2. Create an EventBridge rule with the appropriate pattern
-3. Configure the input transformer with the correct resource type
+with support for three resource types by default:
+  - `EC2 Instances`.
+  - `S3 Buckets`.
+  - `CloudFormation Stacks`.
 :::
 
-## Next Steps
-
-After setting up live events:
-
-1. **Monitor Performance**: Keep an eye on EventBridge metrics and API Gateway logs.
-2. **Scale as Needed**: Add more resource types as your requirements grow.
-3. **Optimize Patterns**: Fine-tune event patterns to reduce noise and improve performance.
-
-For more advanced configuration options, see the [AWS integration examples](../examples/examples.md).
-