Change Requests

In the Service Portal, you may be able to request a change to your services, if your administrator has configured change requests for those services.

A service could be a single inventoried resource or virtual service, or it could be a combination of resources and virtual resources. Examples of changes that you could request include:

  • Decommission a database.
  • Change the owner of an auto scaling group.
  • Add more memory, CPU, or storage resources to a VM.

Typically, change requests are made for inventoried resources; that is, resources that are well-known objects in your cloud accounts' virtualized infrastructure that you can often directly manage through the Service Portal. For examples of actions that may be performed on inventoried resources, see Daily Operations and Service Management.

You may also be able to request changes for XaaS (Anything-as-a-Service) resources, which can include:

  • Generic resources that belong to AWS stacks, GCP deployments, or Azure Resource Groups.
  • Terraform resources.

    To view XaaS resources, select Applications from the menu on the left, then click the hyperlinked name of an AWS stack, GCP deployment, Azure Resource Group, or a Terraform backend. In the details page, expand the Resources section.

After submitting a request

What occurs after you submit a change request depends on the process that your administrator has configured. For example, with a simple change request to modify a resource, the change could happen automatically. In other cases, the change request may email a specific person for an approval, which may or may not be granted.

Some requests for resource changes may involve an automatic reboot during change request fulfillment. For information on whether a reboot is performed for resource changes, see Resource Changes That Require Reboots.