How to log in to Amazon EC2 using PEM format from SecureCRT

本文涉及的产品
日志服务 SLS,月写入数据量 50GB 1个月
简介: SecureCRT requires both a private and a public key. Use the supplied key.pem file from EC2 here as your private key only in Windows for SecureCRT rename it to "key.

SecureCRT requires both a private and a public key. Use the supplied key.pem file from EC2 here as your private key only in Windows for SecureCRT rename it to "key." with no file type. Copy this down to a directory on your local Windows machine use it as Your Identity file in SCRT. Now we need a public key. You can create that below by following the bellow steps. Make sure that file has the same name as key. but ends in file type .pub so in other words key.pub. Save that also to your Windows PC in the same directory as the private key file "key.". Note the name does not have to be "key" but both have to be named the same except for the file type.

 

SecureCRT 6.2 and above:

Support for Amazon EC2 keys has been implemented in SecureCRT 6.5 beta 2 and later.

To use the Amazon EC2 private key:

 
  1. Create an SSH2 session
  2. Specify PublicKey as the authentication method in Session Options / SSH2
  3. Set the Amazon EC2 key as the private key to use for the session
    1. Select PublicKey in Session Options / SSH2
    2. Click the Properties button
    3. Select Use session public key setting
    4. Browse to or enter the path to the EC2 private key in the entry box under Use identity or certificate file
  4. Connect to the EC2 server
相关实践学习
日志服务之使用Nginx模式采集日志
本文介绍如何通过日志服务控制台创建Nginx模式的Logtail配置快速采集Nginx日志并进行多维度分析。
目录
相关文章
|
4月前
|
存储 数据安全/隐私保护
【Azure 环境】把OpenSSL生产的自签名证书导入到Azure Key Vault Certificate中报错
【Azure 环境】把OpenSSL生产的自签名证书导入到Azure Key Vault Certificate中报错
|
1月前
|
存储 网络安全
Curl error (60): SSL peer certificate or SSH remote key was not OK for https://update.cs2c.com.cn/NS/V10/V10SP2/os/adv/lic/base/x86_64/repodata/repomd.xml [SSL: no alternative certificate subject name matches target host name 'update.cs2c.com.cn']
【10月更文挑战第30天】在尝试从麒麟软件仓库(ks10-adv-os)下载元数据时,遇到 SSL 证书验证问题。错误提示为:`Curl error (60): SSL peer certificate or SSH remote key was not OK`。可能原因包括证书不被信任、证书与域名不匹配或网络问题。解决方法包括检查网络连接、导入 SSL 证书、禁用 SSL 证书验证(不推荐)、联系仓库管理员、检查系统时间和尝试其他镜像。
187 1
|
4月前
|
API 网络安全 开发工具
【Azure Developer - 密钥保管库 】使用 Python Azure SDK 实现从 Azure Key Vault Certificate 中下载证书(PEM文件)
【Azure Developer - 密钥保管库 】使用 Python Azure SDK 实现从 Azure Key Vault Certificate 中下载证书(PEM文件)
|
4月前
|
网络安全 数据安全/隐私保护
【Azure 应用服务】 在App Service中无法上传证书[Private Key Certificates (.pfx)],导入Azure Key Vault中的证书也无法成功
【Azure 应用服务】 在App Service中无法上传证书[Private Key Certificates (.pfx)],导入Azure Key Vault中的证书也无法成功
|
4月前
|
API 网络架构 开发者
【Azure Developer】使用 CURL 获取 Key Vault 中 Secrets 中的值
【Azure Developer】使用 CURL 获取 Key Vault 中 Secrets 中的值
|
关系型数据库 MySQL 数据库
MySQL8 的加密 Data-at-Rest Encryption ERROR 3185 (HY000):
MySQL 5.7.11引入了InnoDB表空间加密,该加密启用了对每表文件表空间的支持。
313 0
|
Linux 网络安全
Linux下的github 添加秘钥出错:Key is invalid. You must supply a key in OpenSSH public key for
Linux下的github 添加秘钥出错:Key is invalid. You must supply a key in OpenSSH public key for
Linux下的github 添加秘钥出错:Key is invalid. You must supply a key in OpenSSH public key for
|
数据安全/隐私保护
【错误记录】创建密钥报错 ( Key was created with errors: Warning: JKS 密钥库使用专用格式。建议使用 “ keyto “ 迁移到行业标准格式 PKCS12 )
【错误记录】创建密钥报错 ( Key was created with errors: Warning: JKS 密钥库使用专用格式。建议使用 “ keyto “ 迁移到行业标准格式 PKCS12 )
976 0
【错误记录】创建密钥报错 ( Key was created with errors: Warning: JKS 密钥库使用专用格式。建议使用 “ keyto “ 迁移到行业标准格式 PKCS12 )