Creating a Secure Virtual Machine Instance
Use Security Advisor to create a secure virtual machine (VM) instance in Compute. In this context, a secure instance is one with a boot volume that's encrypted with a customer-managed key and therefore meets minimum security requirements established by security zones.
In addition to creating the instance and associated boot volume, you create the Vault key that you want to use to encrypt the volume, and then you assign the key to the volume. (You can't use Security Advisor to assign existing encryption keys, but you can use an existing vault to create a new key.)
Using Security Advisor to create a VM instance has the following limitations.
- You can't configure private or public IP addresses for an instance.
- You can't change the image build. It always uses the latest version.
- You can't create the instance on a dedicated VM host, which lets you run the instance in isolation so that it's not running on shared infrastructure.
- You can't specify the volume performance settings for the boot volume.
- You can't use Security Advisor to generate SSH keys for you to remotely connect to the instance by using Secure Shell (SSH). You must generate SSH keys and have the public key available when you create the instance.
Other security considerations exist outside Security Advisor, such as the use of resources after you create them. We encourage you to learn more about Compute and Block Volume security features and best practices, and then implement them with the newly created resources. For more information, see Securing Compute, Securing Block Volume , and Best Practices for Your Compute Instances.
Using the Console
Before creating a secure instance you must have the required permissions and a virtual cloud network (VCN) must exist.