Tools: Level 0 of my DevOps journey

Level 0 DevOps Summary: What I’ve Done 1 Created and Connected to an EC2 Instance You launched an AWS EC2 instance (Linux-based). Connected to it successfully using WSL on your local machine. Verified that you can log in and run commands on the server. 2 Configured SSH for Easy Access Updated your SSH config on WSL (~/.ssh/config) to simplify connections. Corrected HostName usage (only hostname/IP, not username). Verified key permissions (chmod 600) to ensure secure SSH access. Created an alias ec2-dev for simplified connections: 3 Configured SSH on Windows Updated C:\Users\alok.ssh\config for PowerShell access. Adjusted IdentityFile to use full Windows path: Fixed permissions and verified connections. Tested connecting via ssh ec2-dev in PowerShell successfully. 4 Connected to EC2 from VS Code Installed Remote - SSH extension in VS Code. Configured VS Code to use the same SSH config file. Connected to EC2 from VS Code seamlessly: Now your editor, terminal, and files are directly on the remote server. 5 Key Takeaways / Level 0 Achievements You can SSH into EC2 from WSL, Windows, and VS Code. You understand SSH config, host aliases, and identity files. You can now start remote development, scripting, and deployments. You have the foundation to start automating tasks, using Git, and deploying apps. At this point, you have full remote access setup, which is the foundation of all DevOps work. Everything from CI/CD pipelines to automation and deployment starts here. Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse CODE_BLOCK: Host ec2-dev HostName ec2-100-27-225-48.compute-1.amazonaws.com User ec2-user IdentityFile ~/.ssh/server.pem IdentitiesOnly yes Enter fullscreen mode Exit fullscreen mode CODE_BLOCK: Host ec2-dev HostName ec2-100-27-225-48.compute-1.amazonaws.com User ec2-user IdentityFile ~/.ssh/server.pem IdentitiesOnly yes CODE_BLOCK: Host ec2-dev HostName ec2-100-27-225-48.compute-1.amazonaws.com User ec2-user IdentityFile ~/.ssh/server.pem IdentitiesOnly yes CODE_BLOCK: IdentityFile C:\Users\alok\.ssh\server.pem Enter fullscreen mode Exit fullscreen mode CODE_BLOCK: IdentityFile C:\Users\alok\.ssh\server.pem CODE_BLOCK: IdentityFile C:\Users\alok\.ssh\server.pem - You launched an AWS EC2 instance (Linux-based). - Connected to it successfully using WSL on your local machine. - Verified that you can log in and run commands on the server. - Updated your SSH config on WSL (~/.ssh/config) to simplify connections. - Corrected HostName usage (only hostname/IP, not username). - Verified key permissions (chmod 600) to ensure secure SSH access. - Created an alias ec2-dev for simplified connections: - Updated C:\Users\alok.ssh\config for PowerShell access. - Adjusted IdentityFile to use full Windows path: - Fixed permissions and verified connections. - Tested connecting via ssh ec2-dev in PowerShell successfully. - Installed Remote - SSH extension in VS Code. - Configured VS Code to use the same SSH config file. - Connected to EC2 from VS Code seamlessly: - Now your editor, terminal, and files are directly on the remote server. - You can SSH into EC2 from WSL, Windows, and VS Code. - You understand SSH config, host aliases, and identity files. - You can now start remote development, scripting, and deployments. - You have the foundation to start automating tasks, using Git, and deploying apps.