Merge branch 'upgrade-billing-info' of https://github.com/SumoLogic/sumologic-documentation into upgrade-billing-info

Author: JV0812

docs/platform-services/automation-service/app-central/integrations/any.run.md

@@ -6,8 +6,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 <img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/any.run.png')} alt="any.run" width="80"/>
 
-***Version: 1.3  
-Updated: Jun 15, 2023***
+***Version: 1.4  
+Updated: Feb 04, 2025***
 
 Gather detonation data for files and URL using `ANY.RUN`.
 
@@ -23,8 +23,8 @@ Sign in to ANY.RUN. Click on your profile on the left menu. In the API and Limit
 
 ## ANY.RUN in Automation Service and Cloud SOAR
 
-1. Access integrations in the [Automation Service](/docs/platform-services/automation-service/automation-service-integrations/#view-integrations) or [Cloud SOAR](/docs/cloud-soar/automation).
-1. After the list of the integrations appears, search for the integration and click on the row.
+1. Access integrations in the [Automation Service](/docs/platform-services/automation-service/automation-service-integrations/#view-integrations) or [Cloud SOAR](/docs/cloud-soar/automation). 
+1. After the list of the integrations appears, search for the integration and click on the row. 
 1. The integration details will appear. Click on the **"+"** button to add new Resource.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/any.run/any.run-3.png')} style={{border:'1px solid gray'}} alt="any.run-3" width="400"/>
 1. Populate all the required fields (\*):
    * **URL**. 'https://api.any.run'
@@ -39,3 +39,4 @@ Sign in to ANY.RUN. Click on your profile on the left menu. In the API and Limit
 * February 21, 2020 - First upload
 * February 13, 2023 - Integration refactored
 * June 15, 2023 (v1.3) - Updated the integration with Environmental Variables
+* February 04, 2025 (v1.4) - Updated the action Get Report with Environmental Variables

docs/platform-services/automation-service/app-central/integrations/aws-ec2.md

@@ -6,36 +6,37 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 <img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/aws.png')} alt="aws" width="50"/>
 
-***Version: 1.4  
-Updated: July 04, 2024***
+***Version: 1.5  
+Updated: Feb 04, 2025***
 
 Using the integration with EC2, you can enrich incidents with specific EC2 data, create and delete snapshots, work with elastic addresses and instances, and manipulate security groups. 
 
 ## Actions
 
-* **Describe Regions** (*Enrichment*) - Describes the Regions that are enabled for an account, or all Regions.
-* **Describe Instances** (*Enrichment*) - Describes the specified instances or all of AWS account's instances.
+* **Authorize Security Group Ingress Rule** (*Containment*) - Adds the specified ingress rules to a security group.
+* **Create Snapshot** (*Containment*) - Creates a new snapshot.
+* **Delete Security Group** (*Containment*) - Delete a security group.
+* **Delete Snapshot** (*Containment*) - Deletes an existing snapshot.
 * **Describe Addresses** (*Enrichment*) - Describes the specified Elastic IP addresses or all Elastic IP addresses.
-* **Describe Volumes** (*Enrichment*) - Describes the specified EBS volumes or all EBS volumes.
+* **Describe Instances** (*Enrichment*) - Describes the specified instances or all of AWS account's instances.
+* **Describe Instances V2** (*Enrichment*) - Describes the specified instances or all of AWS account's instances with pagination.
 * **Describe Key Pairs** (*Enrichment*) - Describes the specified key pairs or all key pairs.
-* **Describe VPCs** (*Enrichment*) - Describes one or more VPCs.
+* **Describe Regions** (*Enrichment*) - Describes the Regions that are enabled for an account, or all Regions.
 * **Describe Subnets** (*Enrichment*) - Describes one or more subnets.
 * **Describe Security Groups** (*Enrichment*) - Describes the specified security groups or all security groups.
 * **Describe Snapshots** (*Enrichment*) - Describes a specified EBS snapshots or all of the EBS snapshots available.
-* **Get Password Data** (*Enrichment*) - Retrieves the encrypted administrator password for a running Windows instance.
-* **Create Snapshot** (*Containment*) - Creates a new snapshot.
-* **Delete Snapshot** (*Containment*) - Deletes an existing snapshot.
+* **Describe Volumes** (*Enrichment*) - Describes the specified EBS volumes or all EBS volumes.
+* **Describe VPCs** (*Enrichment*) - Describes one or more VPCs.
 * **Disassociate Address** (*Containment*) - Disassociates an Elastic IP address from an instance or network interface it's associated with.
+* **Get Password Data** (*Enrichment*) - Retrieves the encrypted administrator password for a running Windows instance.
+* **Monitor Instance** (*Containment*) - Monitor a specific instance.
 * **Release Address** (*Containment*) - Releases the specified Elastic IP address.
+* **Reboot Instances** (*Containment*) - Reboot instances.
+* **Revoke Security Group Ingress Rule** (*Containment*) - Removes the specified ingress rules from a security group.
 * **Start Instance** (*Containment*) - Start an instance.
 * **Stop Instance** (*Containment*) - Stop an instance.
 * **Terminate Instance** (*Containment*) - Terminate an instance.
-* **Delete Security Group** (*Containment*) - Delete a security group.
-* **Monitor Instance** (*Containment*) - Monitor a specific instance.
 * **Unmonitor Instances** (*Containment*) - Discontinue monitoring of a specified instances.
-* **Reboot Instances** (*Containment*) - Reboot instances.
-* **Authorize Security Group Ingress Rule** (*Containment*) - Adds the specified ingress rules to a security group.
-* **Revoke Security Group Ingress Rule** (*Containment*) - Removes the specified ingress rules from a security group.
 
 **Supported Versions**
 
@@ -54,4 +55,5 @@ Using the integration with EC2, you can enrich incidents with specific EC2 data,
 	+ Updated action: Stop Instance (Resolved bug related to checkbox fields)
 + July 04, 2024 (v1.4)
 	+ Updated action: Describe Instances (Resolved bug related to Instance ID field)
-
++ February 04, 2025 (v1.5)
+    + Added action: Describe Instances V2

docs/platform-services/automation-service/automation-service-playbooks.md

@@ -210,10 +210,31 @@ A filter node filters results from the preceding action based on the condition y
 
 ## Playbook versioning
 
-Every time you edit a playbook, a new version of the playbook is saved. In the screen image below, notice how all the versions of the playbook are listed (#4 being the published version as indicated by the publish icon). Click on a version to edit it, and if you want, publish it. In this way, you maintain version control of your playbooks, and ensure that all versions are retained.
+### Autosave
+
+Every time you edit a playbook draft, the draft is automatically saved, and the following notification briefly appears in the lower right corner of the playbook screen:<br/><img src={useBaseUrl('img/platform-services/automation-service/autosave-playbook-1.png')} alt="Playbook autosave" style={{border:'1px solid gray'}} width="200"/>
+
+When the automatic save is complete, the following notification lets you know.<br/><img src={useBaseUrl('img/platform-services/automation-service/autosave-playbook-2.png')} alt="Playbook autosave complete" style={{border:'1px solid gray'}} width="200"/>
+
+To enable or disable autosave, use [playbook preferences](#playbook-preferences).
+
+### Versions
+
+To publish a playbook so that others may use it, click the publish button at the bottom of the playbook screen.<br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-publish-button.png')} alt="Playbook publish button" style={{border:'1px solid gray'}} width="300"/>
+
+Every time you publish a playbook, a new version of the playbook is retained. In the screen image below, notice how all the versions of the playbook are listed (#4 being the published version as indicated by the publish icon). Click on a version to edit it, and if you want, publish it. In this way, you maintain version control of your playbooks, and ensure that all versions are retained.
 
 <img src={useBaseUrl('img/platform-services/automation-service/playbook-versions.png')} alt="Playbook versions" style={{border:'1px solid gray'}} width="800"/>
 
+## Playbook preferences
+
+1. Click the preferences button in the upper-right corner of the screen.<br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-preferences.png')} alt="Playbook preferences button" style={{border:'1px solid gray'}} width="200"/>
+2. Configure preferences in the **Playbooks Preferences** screen.<br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-preferences-screen.png')} alt="Playbook preferences screen" style={{border:'1px solid gray'}} width="400"/>
+
+### Autosave preference
+
+Select **Enable Autosave for all playbooks** to ensure that while editing a playbook, all changes will be automatically saved to the draft. For more information, see [Autosave](#autosave).
+
 ## Import and export playbooks
 
 With the mechanism to import and export playbooks, you can move a playbook, along with all its configurations, from one instance to another. The file should be in tar.gz format and adhere to naming conventions.