Take action on Cloud Assets

Table of Contents

1. Introduction 

2. Accessing the Take Action Feature 

3. Asset types and  Cloud actions supported

4. Roles and Permissions - Prerequisite

5. Granting Agents Access to Take Action in Freshservice

Introduction

Effectively managing and performing actions on cloud resources can become challenging when they're spread out across various providers. It's easy to lose track and end up wasting resources or not using them efficiently. 

Introducing the Take Action feature in Freshservice Cloud management to automate actions on cloud resources directly from a single interface, eliminating the hassle of switching between multiple cloud applications for performing everyday actions.

 Below are the supported apps for the Take Action Feature.

→ AWS Cloud Management 

Note: The AWS Cloud Discovery application has now been renamed and updated to the AWS Cloud Management app. With this new update, admins can discover and perform cloud actions directly on the AWS Cloud resources from Freshservice. 

Accessing the Take Action feature

1. Take Action from Cloud Inventory
2. Take actions on impacted cloud assets directly from an Incident page 

Take Action from Cloud Inventory

1. Navigate to Admin → Assets → Cloud.
   
   
   
   

2. Select the respective Cloud asset and click the Take Action button on the top bar.
   
   
   
   

3. Choose the action you want to perform from the side pane that appears. 
   
   
   
   

4. Click the Initiate action button to perform the respective action on the cloud resource. 
   
   
   
   

5. A service request gets created to track the cloud action that was initiated.
   
   

6. Finally, a private note gets added and displays the status of the cloud action. 
   
   
   
    Quick actions on cloud assets directly from an incident ticket 
   
   

   1. Navigate to the ticket page and select the assets tab.

   
   
   
   

   
   Note: The assets associated with an Incident can be added manually to an incident or automatically added to the incident from an alert payload. 
   
   

   2. Click the Take action button across the asset where you want to perform the action. 
   
   
   
   
   
   3. Choose the respective action you want to perform on the cloud resource from the side pane.
   
   
   
   4. Click on the Initiate action to perform the respective action on the cloud resource. 
   
   
   
   5. A service request gets created to track the initiated cloud action.
   
   
   
   6. Finally, a private note gets added and displays the status of the cloud action.
   
   
   
   Supported Asset types and Cloud Actions for Take Action
   
   

   Asset types supported for Take Action	Cloud actions supported for Take Action
   Virtual Machine Disk Image Security Group Key Pair Subnet VPC	Start Instance - AWS Stop Instance - AWS Resize Instance - AWS Reboot Instance - AWS Terminate Instance - AWS Delete Disk - AWS Delete Image - AWS Delete Security Group - AWS Delete Key Pair - AWS Delete Subnet - AWS Delete VPC - AWS Detach Disk - AWS Attach Disk - AWS

   
   

   
   

   Steps to assign roles and permissions for AWS Take Action
   
   1. Use your AWS account ID or account alias, IAM user name, and password to sign in to the IAM console.
   
   2. Navigate to IAM > Users > Select the created user for Freshservice Integration> Add Permissions.
   
   
   
   
   

   3. Select the respective permission policy AmazonEC2FullAccess to be assigned to the user.
   
   
   
   4. Finally, click on Next and Add permissions. 
   
   

   
   
   

   
   
   
   Note: While we recommend using generic AmazonEC2FullAccess Action permissions for simplicity, users also have the option to grant specific asset-level permissions for the Cloud Take Action feature. However, it's important to note that they must regularly update the permission list to align with any changes to this feature. More info
   
   

   Granting Agents Access to Take Action in Freshservice

   
   

   1. To give agents access to the Take Action feature:

      - Go to Admin → Agent Groups.

      - Confirm that agents are added to the FS Cloud agent group to enable access to Take Action.

   
   

   2. Ensure no requesters are added to the FS Cloud Requester Restricted (Requester Group) to prevent access to the Take Action feature in Cloud management.