Oracle Cloud Infrastructure Documentation

Moving Compute Resources to a Different Compartment

You can move Compute resources such as instances, instance pools, and custom images from one compartment to another.

When you move a Compute resource to a new compartment, associated resources such as boot volumes and VNICs are not moved.

After you move the resource to the new compartment, inherent policies apply immediately and affect access to the resource through the Console. For more information, see Managing Compartments.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment  you should work in.

For administrators: The following policies allow users to move Compute resources to a different compartment:

Allow group ComputeCompartmentMovers to manage instance-family in tenancy

Allow group ComputeCompartmentMovers to manage compute-management-family in tenancy

Allow group ComputeCompartmentMovers to manage auto-scaling-configurations in tenancy

If you're new to policies, see Getting Started with Policies and Common Policies.

Using the Console

To move an instance to a different compartment
To move an instance configuration to a different compartment
To move an instance pool to a different compartment
To move an autoscaling configuration to a different compartment
To move a custom image to a different compartment
To move a cluster network to a different compartment

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use these API operations to move Compute resources to different compartments: