Merge branch 'main' into replace-logos

Author: MaedahBatool

docs/admin/config/webhooks/incoming.mdx

@@ -291,7 +291,7 @@ To retain webhook logs for one day:
 ```json
 {
   "webhook.logging": {
-    "enabled": false,
+    "enabled": true,
     "retention": "24h"
   }
 }

docs/admin/deploy/machine-images/aws-ami.mdx

@@ -8,6 +8,14 @@ Following these docs will provision the following resources:
 - A root EBS volume with 50GB of storage
 - An additional EBS volume with 500GB of storage for storing code and search indices
 
+### Sourcegraph AMI account ID
+
+All Sourcegraph AMIs are published from one of the following AWS accounts:
+
+- Account ID: `840044800169`
+- Account ID: `870751268155`
+
+
 ### Instance size chart
 
 Select an AMI according and instance type to the number of users and repositories you have using this table. If you fall between two sizes, choose the larger of the two.
@@ -26,7 +34,7 @@ Click [here](https://github.com/sourcegraph/deploy#amazon-ec2-amis) to see the c
 
 **The default AMI username is `ec2-user`.**
 
-<Callout type="note">AMIs are optimized for the specific set of resources provided by the instance type, please ensure you use the correct AMI for the associated EC2 instance type. You can [resize your EC2 instance anytime](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html), but your Sourcegraph AMI must match accordingly. If needed, follow the [upgrade steps](#upgrade) to switch to the correct AMI image that is optimized for your EC2 instance type.</Callout>
+<Callout type="note">While we recommend certain image types in our sizing chart, AMIs will dynamically use the resources available on the EC2 instance type they are deployed to, provided the minimum amount of resources needed is available. If you would like to resize your EC2 instance, follow the [upgrade steps](#upgrade) to switch to the correct AMI image that is optimized for your EC2 instance type.</Callout>
 
 ---
 
@@ -35,7 +43,7 @@ Click [here](https://github.com/sourcegraph/deploy#amazon-ec2-amis) to see the c
 1. In the [instance size chart](#instance-size-chart), click the link for the AMI that matches your deployment size.
 2. Choose **Launch instance from AMI**.
 3. Name your instance.
-4. Select an **instance type** according to [the sizing chart](#instance-size-chart).
+4. Select an **instance type** according to [the sizing chart](#instance-size-chart) or your needs.
 5. **Key pair (login)**: Select or create a new Key Pair for connecting to your instance securely (this may be required in the event you need support).
 6. **Network settings**:
    - Under "Auto-assign public IP" select "Enable".