You can access the services and resources that an Oracle Java Cloud
Service instance's node provides by logging into the node as the
opc user through SSH. You can use any SSH utility you want. For example, if you are using Windows, you might use PuTTY; if you are using Linux, you might use OpenSSH.
By default, only the
opc user can remotely connect to your nodes. You cannot use SSH to connect to a node as the
oracle user. After successfully connecting to a node, tasks such as starting and stopping the server and accessing the administrative logs should only be performed by the
Oracle Cloud uses SSH to access the nodes that comprise your service instances, in order to perform predefined Platform Service actions like backup and patching. You initiate these Platform Service actions from the web console, CLI, or REST API. A separate SSH key pair is used for each service instance to perform this internal communication. This SSH key is not available for ad hoc usage. You cannot delete this key from nodes or it will cause these Platform Service actions to fail. The key is only used under programmatic control and cannot be directly accessed by Oracle employees. All SSH actions performed by Oracle Cloud on your nodes are logged and can be audited. Oracle does not have access to any SSH keys residing on your nodes and has no way to access your nodes, unless you explicitly provide access to the keys for troubleshooting purposes.
Note:If you created your service instance in an Oracle Cloud Infrastructure Classic region and chose not to assign public IP addresses, then the nodes in your service instance are not directly accessible from the Internet. They are accessible only from within your private IP network, or from your on-premises data center over a VPN network.
Note:Prior to making changes to the operating system or the Oracle software on a node, see Administration Best Practices.