Before you launch an instance, you should add security group rules to enable users to ping and use SSH to connect to the instance. Security groups are sets of IP filter rules that define networking access and are can be applied to all instances within a project. To do so, you either add rules to the default security group or group or add a new security group with rules.

...

This procedure enables SSH and ICMP (ping) access to instances. The rules apply can be applied to all instances within a given project, and should be set for every project unless there is a reason to prohibit SSH or ICMP access to the instances. This procedure can be adjusted as necessary to add additional security group rules to a project, if your cloud requires them.

...

It is recommended to insert the newly generated key in a text file, without extension, conventionally called id_rsa. The file should be placed in the ".ssh" folder, which should be located in the "Users \ nameUser \ .ssh" path. Moreover, if you want to change the permissions of the file, so that only you can read and write to the file, you can use the Linux chmod command (in this case chmod 600 PrivateKey.pemid_rsa).

Import a key pair

This procedure is an alternative to the one presented in the previous paragraph: you can generate a Key Pair on OpenStack and save the Private Key locally or, conversely, generate it locally and save the public part on OpenStack. To do this, you need to generate on the local machine, which you will use to connect via ssh, the key pair, using the command:

$ ssh-keygen -t rsa -f myKeyPair.key

...