{
  "id": 2182809,
  "title": "3 Ways to Manage Files in CloudShell",
  "url": "https://urgent.news/2026/08/20/3-ways-to-manage-files-in-cloudshell",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-20T16:48:35.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/aws/3-ways-to-manage-files-in-cloudshell-3j8n"
  },
  "original_language": "en",
  "account": "Working with files in CloudShell can be accomplished using multiple methods. The primary options include using Vim, Nano, or CloudShell's built-in edit command. If you are already familiar with Vim, using it may be the quickest approach as it allows you to remain within the terminal environment and leverage its powerful navigation and search capabilities. To make changes, simply exit Vim by typing ESC, followed by :wq to save and quit.\n\nFor those who prefer a more user-friendly terminal editor, Nano is an excellent choice. Nano has a straightforward learning curve and provides visual feedback with shortcuts displayed at the bottom of the screen. After making your modifications, save the file by pressing CTRL+O, and exit Nano by pressing CTRL+X. This process enables you to swiftly edit files when the need arises.\n\nLastly, if you do not wish to use a terminal editor, CloudShell provides an 'edit' command that opens the file in its integrated graphical editor. This option closely resembles using familiar graphical editors like VS Code. To save your changes, utilize CMD+S (CTRL+S on Windows/Linux) or the save icon. Depending on your familiarity and comfort with each editor, you can choose the most suitable option to efficiently manage files within CloudShell.",
  "summary": "So you've probably had to open CloudShell from time to time to poke at something quickly. Say I wanted to test pulling down an artifact from a private CodeArtifact registry. To do that, I'd need to tweak my ~/.npmrc so npm points at the right registry. Which raises the question: what's the best way to edit a file once you're in CloudShell? Let's look at a few options. Using vim I use Neovim btw…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}