All REST Endpoints

ACLs
Access Control List (ACL) is a collection of security rules. You can use ACLs to control the traffic between instances. To control traffic from and to Compute Classic instances, you can apply ACLs to:

* virtual NICs of Compute Classic instances in the same IP network

* virtual NICs of a transit node, such as the VPN gateway or Internet gateway node

The default ACL allows traffic to all virtual NICs in an IP network.

Create an ACL
Method: post
Path: /network/v1/acl/
Delete an ACL
Method: delete
Path: /network/v1/acl/{name}
Retrieve Details of all ACLs in a Container
Method: get
Path: /network/v1/acl/{container}/
Retrieve Details of an ACL
Method: get
Path: /network/v1/acl/{name}
Update an ACL
Method: put
Path: /network/v1/acl/{name}
Accounts
An account is used in Compute Classic to store credentials that must be used to access another service. For example, you use an account to define the credentials and other details of the Oracle Cloud Infrastructure Object Storage Classic instance in which you store machine images.

You can view accounts using the HTTP requests listed below.

Retrieve Details of all Accounts in a Container
Method: get
Path: /account/{container}/
Retrieve Details of an Account
Method: get
Path: /account/{name}
Retrieve Names of all Accounts and Subcontainers in a Container
Method: get
Path: /account/{container}
Retrieve Names of Containers
Method: get
Path: /account/
Authenticate
A POST request to this resource authenticates the specified user and returns an authentication cookie, which you can specify in subsequent API calls to Compute Classic.
Authenticate User
Method: post
Path: /authenticate/
Backup Configurations
You can schedule backups to be taken automatically at defined intervals. Scheduling a backup creates a snapshot of the specified storage volume and the snapshot is stored in the associated Oracle Cloud Infrastructure Object Storage Classic instance.

You can add, delete, update, and retrieve details of backup configurations using the HTTP requests listed below.

These endpoints are not available on Oracle Cloud Machine.

Create a Backup Configuration
Method: post
Path: /backupservice/v1/configuration
Delete a Backup Configuration
Method: delete
Path: /backupservice/v1/configuration/{name}
Retrieve Details of a Backup Configuration
Method: get
Path: /backupservice/v1/configuration/{name}
Retrieve Details of All Backup Configurations
Method: get
Path: /backupservice/v1/configuration
Update a Backup Configuration
Method: put
Path: /backupservice/v1/configuration/{name}
Backups
Allows you to create a backup right away using a specified backup configuration. You can also view scheduled backups and their status, or delete a specified backup and the corresponding snapshot.

These endpoints are not available on Oracle Cloud Machine.

Create a Backup
Method: post
Path: /backupservice/v1/backup
Delete a Backup
Method: delete
Path: /backupservice/v1/backup/{name}
Retrieve Details of all Backups
Method: get
Path: /backupservice/v1/backup
Retrieves Details of the Specified Backup
Method: get
Path: /backupservice/v1/backup/{name}
IPAddressAssociations
The association between an IP address reservation and a virtual NIC.Among all the IP address associations on a single virtual NIC, all the reachable IP address prefixes must be non-overlapping (excluding the 'default' prefix), and at most one IP address pool may have the 'default' reachable IP address prefix.
Create an IP Address Association for IP Networks
Method: post
Path: /network/v1/ipassociation/
Delete an IP Address Association Used in IP Networks
Method: delete
Path: /network/v1/ipassociation/{name}
Retrieve Details of all IP Address Associations in a Container
Method: get
Path: /network/v1/ipassociation/{container}/
Retrieve Details of an IP Address Association Used in IP Networks
Method: get
Path: /network/v1/ipassociation/{name}
Update an IP Address Association Used in IP Networks
Method: put
Path: /network/v1/ipassociation/{name}
IPAddressPrefixSets
An IP address prefix set lists IPv4 addresses in the CIDR address prefix format.
Create an IP Address Prefix Set
Method: post
Path: /network/v1/ipaddressprefixset/
Delete an IP Address Prefix Set
Method: delete
Path: /network/v1/ipaddressprefixset/{name}
Retrieve Details of all IP Address Prefix Sets in a Container
Method: get
Path: /network/v1/ipaddressprefixset/{container}/
Retrieve Details of an IP Address Prefix Set
Method: get
Path: /network/v1/ipaddressprefixset/{name}
Update an IP Address Prefix Set
Method: put
Path: /network/v1/ipaddressprefixset/{name}
IPAddressReservations
A reservation of a NAT IPv4 address, which can be associated to one or more virtual NICs for routing outside of an IP network / IP network exchange using NAT.
Create an IP Address Reservation for IP Networks
Method: post
Path: /network/v1/ipreservation/
Delete an IP Address Reservation Used in IP Networks
Method: delete
Path: /network/v1/ipreservation/{name}
Retrieve Details of all IP Address Reservations in a Container
Method: get
Path: /network/v1/ipreservation/{container}/
Retrieve Details of an IP Address Reservation Used in IP Networks
Method: get
Path: /network/v1/ipreservation/{name}
Update an IP Address Reservation Used in IP Networks
Method: put
Path: /network/v1/ipreservation/{name}
IPAssociations
An IP association is a link between an IP reservation and the vcable of an instance. A vcable is an attachment point to a specific network interface of an instance. A vcable is created automatically when an instance is created and is deleted when the instance is deleted.

You can create, delete, and view IP associations using the HTTP requests listed below.

Create an IP Association
Method: post
Path: /ip/association/
Delete an IP Association
Method: delete
Path: /ip/association/{name}
Retrieve Details of all IP Associations in a Container
Method: get
Path: /ip/association/{container}/
Retrieve Details of an IP Association
Method: get
Path: /ip/association/{name}
Retrieve Names of all IP Associations and Subcontainers in a Container
Method: get
Path: /ip/association/{container}
Retrieve Names of Containers
Method: get
Path: /ip/association/
IPNetworkExchanges
An IP network exchange can include multiple IP networks, but an IP network can be added to only one IP network exchange. For more information, see Managing IP Networks in Using Oracle Cloud Infrastructure Compute Classic.

You can create, view, and delete IP network exchange using the HTTP requests listed below.

Create an IP Network Exchange
Method: post
Path: /network/v1/ipnetworkexchange/
Delete an IP Network Exchange
Method: delete
Path: /network/v1/ipnetworkexchange/{name}
Retrieve Details of all IP Network Exchanges in a Container
Method: get
Path: /network/v1/ipnetworkexchange/{container}/
Retrieve Details of an IP Network Exchange
Method: get
Path: /network/v1/ipnetworkexchange/{name}
IPNetworks
An IP network allows you to define an IP subnet in your account. The size of the IP subnet and the set IP addresses in the subnet are determined by the IP address prefix that you specify while creating the IP network. These IP addresses aren't part of the common pool of Oracle-provided IP addresses used by the shared network. When you add an instance to an IP network, the instance is assigned an IP address in that subnet. You can assign IP addresses to instances either statically or dynamically, depending on your business needs. So you have complete control over the IP addresses assigned to your instances. For more information, see Managing IP Networks in Using Oracle Cloud Infrastructure Compute Classic
Create an IP Network
Method: post
Path: /network/v1/ipnetwork/
Delete an IP Network
Method: delete
Path: /network/v1/ipnetwork/{name}
Retrieve Details of all IP Networks in a Container
Method: get
Path: /network/v1/ipnetwork/{container}/
Retrieve Details of an IP Network
Method: get
Path: /network/v1/ipnetwork/{name}
Update an IP Network
Method: put
Path: /network/v1/ipnetwork/{name}
IPReservations
An IP reservation is the allocation of a public IP address from an IP address pool. After creating an IP reservation, you can associate it with an instance by using an IP association, to enable access between the Internet and the instance.

You can add, delete, update, and view IP reservations using the HTTP requests listed below.

Create an IP Reservation
Method: post
Path: /ip/reservation/
Delete an IP Reservation
Method: delete
Path: /ip/reservation/{name}
Retrieve Details of all IP Reservations in a Container
Method: get
Path: /ip/reservation/{container}/
Retrieve Details of an IP Reservation
Method: get
Path: /ip/reservation/{name}
Retrieve Names of all IP Reservations and Subcontainers in a Container
Method: get
Path: /ip/reservation/{container}
Retrieve Names of Containers
Method: get
Path: /ip/reservation/
Update an IP Reservation
Method: put
Path: /ip/reservation/{name}
ImageListEntries
Each machine image in an image list is identified by an image list entry.

You can create, and delete image list entries using the HTTP requests listed below.

Create an Image List Entry
Method: post
Path: /imagelist/{name}/entry/
Delete an Image List Entry
Method: delete
Path: /imagelist/{name}/entry/{version}
Retrieve Details of an Image List Entry
Method: get
Path: /imagelist/{name}/entry/{version}
ImageLists
An image list is a collection of Compute Classic machine images. Each machine image in an image list is identified by a unique entry number.

When you create an instance, by using a launch plan for example, you must specify the image list that contains the machine image you want to use.

You can create, delete, update and view image lists using the HTTP requests listed below.

Create an Image List
Method: post
Path: /imagelist/
Delete an Image List
Method: delete
Path: /imagelist/{name}
Retrieve Details of all Image Lists in a Container
Method: get
Path: /imagelist/{container}/
Retrieve Details of an Image List
Method: get
Path: /imagelist/{name}
Retrieve Names of all Image Lists and Subcontainers in a Container
Method: get
Path: /imagelist/{container}
Retrieve Names of Containers
Method: get
Path: /imagelist/
Update an Image List
Method: put
Path: /imagelist/{name}
InstanceConsoles
You can use the console output of an instance to diagnose failures that occurred while booting the instance. The instanceconsole object is created when an instance is launched, and it is destroyed when the instance is deleted.
Retrieve Details of an Instance Console
Method: get
Path: /instanceconsole/{name}
Instances
A Compute Classic instance is a virtual machine running a specific operating system and with CPU and memory resources that you specify. See About Instances in Using Oracle Cloud Infrastructure Compute Classic.

You can view and delete instances using the HTTP requests listed below.

Delete an Instance
Method: delete
Path: /instance/{name}
Retrieve Details of all Instances in a Container
Method: get
Path: /instance/{container}/
Retrieve Details of an Instance
Method: get
Path: /instance/{name}
Retrieve Names of all Instances and Subcontainers in a Container
Method: get
Path: /instance/{container}
Retrieve Names of Containers
Method: get
Path: /instance/
Update an Instance
Method: put
Path: /instance/{name}
LaunchPlans
A launch plan is a JSON-formatted file that defines the properties of one or more instances. You can use a launch plan to quickly create and start multiple, nonpersistent instances in Compute Classic. Note that while you can reuse your launch plan JSON file to create instances any number of times, the launch plan itself does not persist in Compute Classic.

When you create an instance, the initial state is preparing, as Compute Classic allocates resources and prepares to create the instance. Next, the state changes to initializing, which indicates that the specified image is being installed. When initializing is complete, the state changes to running, which indicates that the OS has started. When an instance is in the running state, you can connect to it.

Create Instances Using Launch Plans
Method: post
Path: /launchplan/
MachineImages
A machine image is a template of a virtual hard disk of a specific size with an installed operating system. You use machine images to create virtual machine instances in Compute Classic.

You can create, view, and delete machine images using the HTTP requests listed below.

Create a Machine Image
Method: post
Path: /machineimage/
Delete a Machine Image
Method: delete
Path: /machineimage/{name}
Retrieve Details of a Machine Image
Method: get
Path: /machineimage/{name}
Retrieve Details of all Machine Images in a Container
Method: get
Path: /machineimage/{container}/
Retrieve Names of all Machine Images and Subcontainers in a Container
Method: get
Path: /machineimage/{container}
Retrieve Names of Containers
Method: get
Path: /machineimage/
OSSContainers
An OSSContainer is a container in Oracle Cloud Infrastructure Object Storage Classic. You can create Oracle Cloud Infrastructure Object Storage Classic containers using the Compute Classic API.
Create an Oracle Cloud Infrastructure Object Storage Classic Container
Method: post
Path: /integrations/osscontainer/
Delete an Oracle Cloud Infrastructure Object Storage Classic Container
Method: delete
Path: /integrations/osscontainer/{name}
Retrieve Details of all Oracle Cloud Infrastructure Object Storage Classic Containers in a Container
Method: get
Path: /integrations/osscontainer/{container}/
Retrieve Details of an Oracle Cloud Infrastructure Object Storage Classic Container
Method: get
Path: /integrations/osscontainer/{name}
Retrieve Names of all Oracle Cloud Infrastructure Object Storage Classic Containers and Subcontainers in a Container
Method: get
Path: /integrations/osscontainer/{container}
Retrieve Names of Containers
Method: get
Path: /integrations/osscontainer/
Update an Oracle Cloud Infrastructure Object Storage Classic Container
Method: put
Path: /integrations/osscontainer/{name}
OrchestrationObjects
An orchestration object is an object in Compute Classic which is managed by orchestration v2. It is the primary building block of an orchestration. Each object contains all the attributes for the compute, networking, or storage resource that you want to create. When you define an object in an orchestration, you can create dependencies with other objects by using references. See Object References and Relationships in Using Oracle Cloud Infrastructure Compute Classic.

Orchestrations are designed to handle up to 100 interdependent objects. Creating objects using other APIs may compromise your orchestration.

Note: You should always use your orchestrations to manage resources that you've reated using orchestrations. For example, use the OrchestrationObject API to add a security list to a running instance or to create a storage snapshot of an attached storage volume instead of using the SecLists or StorageSnapshots APIs respectively. Don't, for example, use the web console or the REST API to delete an object that you created using an orchestration. This could cause your orchestration to either attempt to re-create the object and associated resources, or to go into an error state.

Also remember that you shouldn't try to use or manage resources created using orchestrations v1 by referencing them in orchestrations v2, or vice versa.

You can add objects to, remove objects from, or update objects in an orchestration by using the HTTP requests listed below.

Create an Orchestration Object
Method: post
Path: /platform/v1/object/
Delete an Orchestration Object
Method: delete
Path: /platform/v1/object/{name}
Retrieve Details of all Orchestration Objects in a Container
Method: get
Path: /platform/v1/object/{container}/
Retrieve Details of an Orchestration Object
Method: get
Path: /platform/v1/object/{name}
Retrieve Names of all Orchestration Objects and Subcontainers in a Container
Method: get
Path: /platform/v1/object/{container}
Retrieve Names of Containers
Method: get
Path: /platform/v1/object/
Update an Orchestration Object
Method: put
Path: /platform/v1/object/{name}
OrchestrationV2s
An orchestration defines the attributes and interdependencies of a collection of compute, networking, and storage resources in Compute Classic. You can use orchestrations to automate the provisioning and lifecycle operations of an entire virtual compute topology.

In earlier versions of Compute Classic, you could use orchestrations v1 to create and manage resources. From release 17.1.2 onwards, you can also create and provision resources using orchestrations v2.

Note: You should always use your orchestrations to manage resources that you've created using orchestrations. Don't, for example, use the web console or the REST API to delete an object that you created using an orchestration. This could cause your orchestration to either attempt to re-create the object and associated resources, or to go into an error state.

Also remember that you shouldn't try to use or manage resources created using orchestrations v1 by referencing them in orchestrations v2, or vice versa.

For more information, see About Orchestrations v2.

Create an OrchestrationV2
Method: post
Path: /platform/v1/orchestration/
Delete an OrchestrationV2
Method: delete
Path: /platform/v1/orchestration/{name}
Retrieve Details of all OrchestrationV2 in a Container
Method: get
Path: /platform/v1/orchestration/{container}/
Retrieve Details of an OrchestrationV2
Method: get
Path: /platform/v1/orchestration/{name}
Retrieve Names of all OrchestrationV2 and Subcontainers in a Container
Method: get
Path: /platform/v1/orchestration/{container}
Retrieve Names of Containers
Method: get
Path: /platform/v1/orchestration/
Update an OrchestrationV2
Method: put
Path: /platform/v1/orchestration/{name}
Orchestrations
An orchestration defines the attributes and interdependencies of a collection of compute, networking, and storage resources in Compute Classic. You can use orchestrations to automate the provisioning and lifecycle operations of an entire virtual compute topology.

After creating an orchestration (in a JSON-formatted file) and adding it to Compute Classic, you can trigger the creation and removal all the resources defined in the orchestration with a single step.

An orchestration contains one or more object plans (oplans). The attributes that you can specify in an oplan vary depending on the object type (obj_type). For detailed information about the object types that you can create by using orchestrations and the attributes for each object type, see Attributes in Orchestrations in Using Oracle Cloud Infrastructure Compute Classic.

You can add, start, stop, get, update, and delete orchestrations using the following HTTP requests:

Add an Orchestration
Method: post
Path: /orchestration/
Delete an Orchestration
Method: delete
Path: /orchestration/{name}
Retrieve Details of all Orchestrations in a Container
Method: get
Path: /orchestration/{container}/
Retrieve Details of an Orchestration
Method: get
Path: /orchestration/{name}
Retrieve Names of all Orchestrations and Subcontainers in a Container
Method: get
Path: /orchestration/{container}
Retrieve Names of Containers
Method: get
Path: /orchestration/
Update an Orchestration
Method: put
Path: /orchestration/{name}
PrivateGateways
Create a private gateway when you want to set up a private data connection between subnets in your premises and IP networks in your Compute Classic account through Oracle Cloud Infrastructure FastConnect Classic edge routers.

These endpoints are not available on Oracle Cloud Machine.

Create a Private Gateway
Method: post
Path: /network/v1/privategateway/
Delete a Private Gateway
Method: delete
Path: /network/v1/privategateway/{name}
Retrieve Details of a Private Gateway
Method: get
Path: /network/v1/privategateway/{name}
Retrieve Details of all Private Gateways in a Container
Method: get
Path: /network/v1/privategateway/{container}/
Retrieve Names of all Private Gateways and Subcontainers in a Container
Method: get
Path: /network/v1/privategateway/{container}
Update a Private Gateway
Method: put
Path: /network/v1/privategateway/{name}
RebootInstanceRequests
You can reboot a running instance by creating a rebootinstancerequest object.
Create a Reboot Instance Request
Method: post
Path: /rebootinstancerequest/
Delete a Reboot Instance Request
Method: delete
Path: /rebootinstancerequest/{name}
Retrieve Details of a Reboot Instance Request
Method: get
Path: /rebootinstancerequest/{name}
Retrieve Details of all Reboot Instance Requests in a Container
Method: get
Path: /rebootinstancerequest/{container}/
Retrieve Names of all Reboot Instance Requests and Subcontainers in a Container
Method: get
Path: /rebootinstancerequest/{container}
Retrieve Names of Containers
Method: get
Path: /rebootinstancerequest/
RefreshTokens
Authentication tokens expire in 30 minutes. This request extends the expiry of the authentication token by 30 minutes from the time you run the command. It extends the expiry of the current authentication token, but not beyond the session expiry time, which is 3 hours.
Refresh an Authentication Token
Method: get
Path: /refresh/
Restores
You can schedule backups to be restored to a volumes. You can only restore a from completed backup.

These endpoints are not available on Oracle Cloud Machine.

Create a Restore
Method: post
Path: /backupservice/v1/restore
Delete Restore
Method: delete
Path: /backupservice/v1/restore/{name}
Retrieve Details of a Restore
Method: get
Path: /backupservice/v1/restore/{name}
Retrieve Details of all Restores
Method: get
Path: /backupservice/v1/restore
Routes
After creating IP networks and adding instances to the networks, you can specify connections between different networks by creating routes and IP network exchanges.

Route specifies the IP address of the destination as well as a vNICset which provides the next hop for routing packets. Using routes to enable traffic between subnets allows you to specify multiple routes to each IP network. Using vNICsets in routes also provides egress load balancing and high availability.

For more information, see Managing IP Networks in Using Oracle Cloud Infrastructure Compute Classic.

Create a Route
Method: post
Path: /network/v1/route/
Delete a Route
Method: delete
Path: /network/v1/route/{name}
Retrieve Details of a Route
Method: get
Path: /network/v1/route/{name}
Retrieve Details of all Routes in a Container
Method: get
Path: /network/v1/route/{container}/
Update a Route
Method: put
Path: /network/v1/route/{name}
SSHKeys
To connect to an instance using SSH, you must associate it with one or more SSH public keys. You must first generate the required SSH key pairs, by using a tool such as ssh-keygen, and then upload the public keys to Compute Classic.

You can add, delete, update, and view SSH public keys using the HTTP requests listed below. For instructions to generate SSH key pairs, see Generating an SSH Key Pair in Using Oracle Cloud Infrastructure Compute Classic.

Add an SSH Key
Method: post
Path: /sshkey/
Delete an SSH Key
Method: delete
Path: /sshkey/{name}
Retrieve Details of all SSH Keys in a Container
Method: get
Path: /sshkey/{container}/
Retrieve Details of an SSH Key
Method: get
Path: /sshkey/{name}
Retrieve Names of all SSH Keys and Subcontainers in a Container
Method: get
Path: /sshkey/{container}
Retrieve Names of Containers
Method: get
Path: /sshkey/
Update an SSH Key
Method: put
Path: /sshkey/{name}
ScreenCaptures
Captures the current screen of the specified instance in the PNG format. You can use the screen capture of an instance in the running state to diagnose failures. There may be cases when you cannot connect to an instance. In such cases, you can take a screen capture of the instance to identify the current state of the instance and to inspect any messages on the instance screen. Even after you delete an instance, the screen capture of the instance remains available.
Create a Screen Capture Request
Method: post
Path: /console/screencapture/
Delete a Screen Capture Request
Method: delete
Path: /console/screencapture/{name}
Retrieve Details of a Screen Capture Request
Method: get
Path: /console/screencapture/{name}
Retrieve Details of all Screen Capture Requests in a Container
Method: get
Path: /console/screencapture/{container}/
Retrieve Names of all Screen Capture Requests and Subcontainers in a Container
Method: get
Path: /console/screencapture/{container}
Retrieve Names of Containers
Method: get
Path: /console/screencapture/
Update a Screen Capture Request
Method: put
Path: /console/screencapture/{name}
SecApplications
A security application is an IP protocol-to-port mapping that you can use in security rules. In the web UI, security applications are called protocols. Compute Classic provides several predefined security applications. You can also define your own security applications.

You can create, delete, and view security applications using the HTTP requests listed below.

Create a Security Application
Method: post
Path: /secapplication/
Delete a Security Application
Method: delete
Path: /secapplication/{name}
Retrieve Details of a Security Application
Method: get
Path: /secapplication/{name}
Retrieve Details of all Security Applications in a Container
Method: get
Path: /secapplication/{container}/
Retrieve Names of all Security Applications and Subcontainers in a Container
Method: get
Path: /secapplication/{container}
Retrieve Names of Containers
Method: get
Path: /secapplication/
SecAssociations
A security association is a relationship between a security list and the vcable of an instance. The vcable is an attachment point to a specific network interface of an instance. The vcable enables dynamic association/disassociation of its instance with security lists. You can associate up to eight security lists with a given vcable. This limit includes security lists specified in the instance configuration (for example, in a launch plan) as well as new security associations added after creating instances.

Note that when a security list is deleted, all the security associations involving that security list are also deleted.

You can create, delete, and view security associations using the HTTP requests listed below.

Create a Security Association
Method: post
Path: /secassociation/
Delete a Security Association
Method: delete
Path: /secassociation/{name}
Retrieve Details of a Security Association
Method: get
Path: /secassociation/{name}
Retrieve Details of all Security Associations in a Container
Method: get
Path: /secassociation/{container}/
Retrieve Names of all Security Associations and Subcontainers in a Container
Method: get
Path: /secassociation/{container}
Retrieve Names of Containers
Method: get
Path: /secassociation/
SecIPLists
A security IP list is a set of IP addresses or subnets external to the instances you create in Compute Classic. These lists can then be used as a source when you define security rules.

Note that, a security IP list named /oracle/public/public-internet is predefined in Compute Classic. You can use this security IP list as the source in a security rule to permit traffic from any host on the Internet.

You can create, delete, update, and view security IP lists using the HTTP requests listed below.

Create a Security IP List
Method: post
Path: /seciplist/
Delete a Security IP List
Method: delete
Path: /seciplist/{name}
Retrieve Details of a Security IP List
Method: get
Path: /seciplist/{name}
Retrieve Details of all Security IP Lists in a Container
Method: get
Path: /seciplist/{container}/
Retrieve Names of all Security IP Lists and Subcontainers in a Container
Method: get
Path: /seciplist/{container}
Retrieve Names of Containers
Method: get
Path: /seciplist/
Update a Security IP List
Method: put
Path: /seciplist/{name}
SecLists
A security list is a group of one or more instances that you can specify as the destination or source in a security rule. Instances within a security list can communicate fully with one another on all ports. When you attach an instance to a security list, the inbound and outbound policies defined in the security list are applicable to that instance. All instances within a security list can communicate fully with one another on all protocols and ports.

While creating an instance, if you do not attach it to any security list, the instance gets attached automatically to the predefined /Compute-identity_domain/default/default security list, which has the inbound policy set to DENY and the outbound policy set to PERMIT.

You can create, delete, update, and view security lists using the HTTP requests listed below. For more information about security lists, see About Security Lists in Using Oracle Cloud Infrastructure Compute Classic.

Create a Security List
Method: post
Path: /seclist/
Delete a Security List
Method: delete
Path: /seclist/{name}
Retrieve Details of a Security List
Method: get
Path: /seclist/{name}
Retrieve Details of all Security Lists in a Container
Method: get
Path: /seclist/{container}/
Retrieve Names of all Security Lists and Subcontainers in a Container
Method: get
Path: /seclist/{container}
Retrieve Names of Containers
Method: get
Path: /seclist/
Update a Security List
Method: put
Path: /seclist/{name}
SecRules
A security rule defines network access over a specified protocol between instances in two security lists, or from a set of external hosts (an IP list) to instances in a security list.

Security rules tie the security list, security IP list, and security application entities together.

You can create, delete, update, and view security rules using the HTTP requests listed below. For more information about security rules, see About Security Rules in Using Oracle Cloud Infrastructure Compute Classic.

Create a Security Rule
Method: post
Path: /secrule/
Delete a Security Rule
Method: delete
Path: /secrule/{name}
Retrieve Details of a Security Rule
Method: get
Path: /secrule/{name}
Retrieve Details of all Security Rules in a Container
Method: get
Path: /secrule/{container}/
Retrieve Names of all Security Rules and Subcontainers in a Container
Method: get
Path: /secrule/{container}
Retrieve Names of Containers
Method: get
Path: /secrule/
Update a Security Rule
Method: put
Path: /secrule/{name}
SecurityProtocols
A security protocol allows you to specify a transport protocol and the source and destination ports to be used with the specified protocol.

It is used for matching packets in a security rule.

When you create a security rule, the protocols and ports of the specified security protocols are used to determine the type of traffic that is permitted by that security rule. If you don't specify protocols and ports in a security protocol, traffic is permitted over all protocols and ports.

You can specify a security protocol in multiple security rules. So if you have a protocol that you want to use in a number of security rules, you don't have to create the protocol multiple times.

Create a Security Protocol for IP Networks
Method: post
Path: /network/v1/secprotocol/
Delete a Security Protocol Used in IP Networks
Method: delete
Path: /network/v1/secprotocol/{name}
Retrieve Details of a Security Protocol Used in IP Networks
Method: get
Path: /network/v1/secprotocol/{name}
Retrieve Details of all Security Protocols in a Container
Method: get
Path: /network/v1/secprotocol/{container}/
Update a Security Protocol Used in IP Networks
Method: put
Path: /network/v1/secprotocol/{name}
SecurityRules
A security rule permits traffic from a specified source or to a specified destination. You must specify the direction of a security rule - either ingress or egress. In addition, you can specify the source or destination of permitted traffic, and the security protocol and port used to send or receive packets. Each of the parameters that you specify in a security rule provides a criterion that the type of traffic permitted by that rule must match. Only packets that match all of the specified criteria are permitted. If you don't specify match criteria in the security rule, all traffic in the specified direction is permitted. The primary function of security rules is to help identify the type of traffic to be allowed in the IP network.
Create a Security Rule for IP Networks
Method: post
Path: /network/v1/secrule/
Delete a Security Rule Used in IP Networks
Method: delete
Path: /network/v1/secrule/{name}
Retrieve Details of a Security Rule Used in IP Networks
Method: get
Path: /network/v1/secrule/{name}
Retrieve Details of all Security Rules in a Container
Method: get
Path: /network/v1/secrule/{container}/
Update a Security Rule Used in IP Networks
Method: put
Path: /network/v1/secrule/{name}
Shapes
A shape is a resource profile that specifies the number of OCPUs and the amount of memory to be allocated to an instance in Compute Classic. The shape determines the type of disk drive that your instance uses. If you select a general purpose or high-memory shape, a hard-disk drive is used. If you select a high-I/O shape, an NVM Express solid-state drive is used. High-I/O shapes also determine the size of the root disk.

Note: High-I/O shapes aren't available in all sites.

For more information about shapes, see About Machine Images and Shapes in Using Oracle Cloud Infrastructure Compute Classic.

Retrieve Details of a Shape
Method: get
Path: /shape/{name}
Retrieve Details of all Shapes
Method: get
Path: /shape/
Snapshots
Instance snapshots provide an easy way to create a customized machine image using an existing instance as a template. You can then use this customized machine image to create multiple instances with identical configurations. To clone an instance using an instance snapshot, first create an instance using an appropriate machine image. This instance must use a nonpersistent boot volume. Deleting an instance shuts off and deletes the virtual machine (VM), destroying all customizations made since launch. To preserve the changes made to a VM after launch, create a new machine image of the modified VM by taking a snapshot of the instance. Add this new machine image to an image list, and then use it to create a new instance.

You can create, delete, and view snapshots of an instance using the HTTP requests listed below.

Create an Instance Snapshot
Method: post
Path: /snapshot/
Delete an Instance Snapshot
Method: delete
Path: /snapshot/{name}
Retrieve Details of all Instance Snapshots in a Container
Method: get
Path: /snapshot/{container}/
Retrieve Details of an Instance Snapshot
Method: get
Path: /snapshot/{name}
Retrieve Names of all Instance Snapshots and Subcontainers in a Container
Method: get
Path: /snapshot/{container}
Retrieve Names of Containers
Method: get
Path: /snapshot/
StorageAttachments
A storage attachment is an association between a storage volume and an instance. You can associate a volume to only one instance at a time. You can detach a volume from an instance by deleting the relevant storage attachment.

You can create, delete, and view storage attachments by using the HTTP requests listed below.

Create a Storage Attachment
Method: post
Path: /storage/attachment/
Delete a Storage Attachment
Method: delete
Path: /storage/attachment/{name}
Retrieve Details of a Storage Attachment
Method: get
Path: /storage/attachment/{name}
Retrieve Details of all Storage Attachments in a Container
Method: get
Path: /storage/attachment/{container}/
Retrieve Names of all Storage Attachments and Subcontainers in a Container
Method: get
Path: /storage/attachment/{container}
Retrieve Names of Containers
Method: get
Path: /storage/attachment/
StorageProperties
Storage properties are used to describe the characteristics of storage pools and are used to determine volume placement within a pool when a volume is created.

You must specify a storage property while creating a storage volume. For storage volumes that require low latency and high IOPS, such as for storing database files, select the /oracle/public/storage/latency storage property. For all other storage volumes, select /oracle/public/storage/default.

You can view storage properties using the HTTP requests listed below.

Retrieve Details of a Storage Property
Method: get
Path: /property/storage/{name}
Retrieve Details of all Storage Properties in a Container
Method: get
Path: /property/storage/{container}/
Retrieve Names of all Storage Properties and Subcontainers in a Container
Method: get
Path: /property/storage/{container}
Retrieve Names of Containers
Method: get
Path: /property/storage/
StorageSnapshots
Creating a snapshot of a storage volume enables you to capture all the data stored on the storage volume. You can retain snapshots as a backup, or use them to create new, identical storage volumes.

If you take multiple snapshots of a storage volume, each snapshot captures all the data stored on the storage volume. You can create either colocated or remote storage volume snapshots.

  • Colocated snapshots: Snapshots are stored in the same physical location as the original storage volume and each snapshot uses the same amount of storage as the original volume. Colocated snapshots and volumes from colocated snapshots can be created very quickly. Colocated snapshots are useful for quickly restoring storage volumes within a site. However, you can't restore volumes across sites using colocated snapshots.
  • Remote snapshots: Snapshots aren't stored in the same location as the original storage volume. Instead, they are reduced and stored in the associated Oracle Cloud Infrastructure Object Storage Classic instance. Remote snapshots are useful if your domain spans multiple sites. With remote snapshots, you can create a snapshot in one site, then switch to another site and create a copy of the storage volume on that site. However, creating a remote snapshot and restoring a storage volume from a remote snapshot can take quite a long time depending on the size of the storage volume, as data is written to and from the Oracle Cloud Infrastructure Object Storage Classic instance.

Create a Storage Volume Snapshot
Method: post
Path: /storage/snapshot/
Delete a Storage Volume Snapshot
Method: delete
Path: /storage/snapshot/{name}
Retrieve Details of a Storage Volume Snapshot
Method: get
Path: /storage/snapshot/{name}
Retrieve Details of all Storage Volume Snapshots in a Container
Method: get
Path: /storage/snapshot/{container}/
Retrieve Names of all Storage Volume Snapshots and Subcontainers in a Container
Method: get
Path: /storage/snapshot/{container}
Retrieve Names of Containers
Method: get
Path: /storage/snapshot/
StorageVolumes
A storage volume is virtual disk drive that provides block storage for Compute Classic instances. For more information, see About Storage Volumes in Using Oracle Cloud Infrastructure Compute Classic.

You can create, delete, update, and view storage volumes by using the HTTP requests listed below.

Create a Storage Volume
Method: post
Path: /storage/volume/
Delete a Storage Volume
Method: delete
Path: /storage/volume/{name}
Retrieve Details of a Storage Volume
Method: get
Path: /storage/volume/{name}
Retrieve Details of all Storage Volumes in a Container
Method: get
Path: /storage/volume/{container}/
Retrieve Names of all Storage Volumes and Subcontainers in a Container
Method: get
Path: /storage/volume/{container}
Retrieve Names of Containers
Method: get
Path: /storage/volume/
Update a Storage Volume
Method: put
Path: /storage/volume/{name}
VPNEndpointV2s
Use this API to set up a VPN connection between your data center and IP networks in your Compute Classic site. This provides a secure communication channel between your data center and instances that are added to your IP networks. To set up a VPN connection, see Workflow for Setting Up a VPN Connection in Using Oracle Cloud Infrastructure Compute Classic.

These endpoints are not available on Oracle Cloud Machine.

Create a VPN Endpoint V2
Method: post
Path: /vpnendpoint/v2/
Delete a VPN Endpoint V2
Method: delete
Path: /vpnendpoint/v2/{name}
Retrieve Details of a VPN Endpoint V2
Method: get
Path: /vpnendpoint/v2/{name}
Retrieve Details of all VPN Endpoint V2s in a Container
Method: get
Path: /vpnendpoint/v2/{container}/
Update a VPN Endpoint V2
Method: put
Path: /vpnendpoint/v2/{name}
VPNEndpoints
You can create secure IPSec-based tunnels between your data center and the instances in your Compute Classic site to securely access your instances. A vpnendpoint object represents a VPN tunnel to your Compute Classic site. You can create up to 20 VPN tunnels to your Compute Classic site. You can use any internet service provider to access your Compute Classic site, provided you have a VPN device to terminate an IPSec VPN tunnel.

You can create, delete, update and view VPN endpoints using the HTTP requests listed below.

These endpoints are not available on Oracle Cloud Machine.

Create a VPN Endpoint
Method: post
Path: /vpnendpoint/
Delete a VPN Endpoint
Method: delete
Path: /vpnendpoint/{name}
Retrieve Details of a VPN Endpoint
Method: get
Path: /vpnendpoint/{name}
Retrieve Details of all VPN Endpoints in a Container
Method: get
Path: /vpnendpoint/{container}/
Update a VPN Endpoint
Method: put
Path: /vpnendpoint/{name}
VirtualNICSets
A Virtual NIC Set, or vNICset, is a collection of one or more vNICs. You must specify a vNICset when you create a route. When a vNICset containing multiple vNICs is used in a route, Equal Cost Multipath (ECMP) anycast routing is implemented. Traffic routed by that route is load balanced across all the vNICs in the vNICset. Using vNICsets with multiple vNICs also ensures high availability for traffic across the specified vNICs.
Create a Virtual NIC Set
Method: post
Path: /network/v1/vnicset/
Delete a Virtual NIC Set
Method: delete
Path: /network/v1/vnicset/{name}
Retrieve Details of a Virtual NIC Set
Method: get
Path: /network/v1/vnicset/{name}
Retrieve Details of all Virtual NIC Sets in a Container
Method: get
Path: /network/v1/vnicset/{container}/
Update a Virtual NIC Set
Method: put
Path: /network/v1/vnicset/{name}
VirtualNICs
A Virtual NIC, or vNIC, is a virtual network interface card that enables an instance to be associated with a network. Instances created after mid-September 2016 using Oracle-provided images support eight vNICs, enabling each instance to be associated with up to eight networks. Virtual NIC is created when you launch an instance using an orchestration and in the network attributes you specify the IP network or shared network that each vNIC of an instance should be associated with. For more information, see Instance Attributes in Using Oracle Cloud Infrastructure Compute Classic.
Retrieve Details of a Virtual NIC
Method: get
Path: /network/v1/vnic/{name}
Retrieve Details of all Virtual NICs in a Container
Method: get
Path: /network/v1/vnic/{container}/