๐กExploring new development environments? AWS Lightsail offers cost-effective access to Windows and Linux operating systems. While primarily focusing on Windows connecting to Linux, this guide offers pathways for all. Get hands-on and explore a range of development opportunities affordably and flexibly. This guide helps you start, connect, and set up an alternative environment that suits your needs.
๐Table of Contents
- Introduction
- Working in a Windows Environment: Exploring WSL and Its Limitations
- Building Your Own Linux Development Environment
- Understanding Costs: AWS Lightsail Billing
- Final Thoughts and Considerations
Introduction
My everyday machine is Windows, serving me well for most tasks. However, I found it limiting for code development and AWS interactions. Navigating through PowerShell and the absence of essential CLI tools became obstacles (could you live without these cli tools?). This isn't about pitting one OS against another, but about enabling a smoother development journey. Here, I'll share a straightforward method to establish a Linux-based development environment.
โ๏ธ Utilizing AWS credits, I explored a cost-saving solution. This guide showcases how to set up a Linux environment on AWS Lightsail, offering an alternative OS for developers seeking flexibility. While I focus on enabling Linux for Windows users, Lightsail provides various OS types for diverse developer needs.
โThis solution will incur monthly charges that you have to be aware of (see the Understanding Costs: AWS Lightsail Billing).
Working in a Windows Environment: Exploring WSL and Its Limitations
While an apparent and straightforward alternative is using WSL on Windows (see here for setup instructions), my experience in Python and AWS SAM development revealed potential drawbacks. WSL often becomes unresponsive due to memory management inefficiencies. The memory allocation within WSL, managed by the Windows operating system, can lead to performance degradation and unresponsiveness, particularly evident when handling resource-intensive tasks in development environments. Despite my mighty 32GB RAM machine, every time I unleash sam local start-api with a medley of Lambda function fiestas, my WSL slowly morphs into the 'Snail Subsystem for Linux.' It huffs, puffs, and eventually naps, leaving me in the lurch. ๐
Building Your Own Linux Development Environment
โ Prerequisites
- An AWS Account
- VS Code on your Windows machine
๐ป Setting up an AWS Lightsail Instance
- Open Lightsail Console. And choose Create instance
- Choose the OS Only and your preferred Linux Distribution.
- Use either the Default key or create/upload your own. Download the key.
- Choose the instance plan. I wouldn't the smallest one, since it has only 512 MB of RAM. Go with a bit larger one. Give it a name, tags, and launch. After a couple of minutes, it'll be in the Running state.๐ค
- Time for some additional setup. Choose your instance and go to the Networking tab. I would recommend attaching a static IP so that you can easily reconnect to your instance. You can remove the HTTP rule from the IPv4 Firewall, we'll be connecting through SSH. Configure the SSH rule to allow connections only from your IP (you can keep the Allow Lightsail browser SSH option enabled so that you can easily connect to your instance through the AWS Console). Check your IP and replace it as Source IP:
You might want to disable the IPv6 networking if you're not planning on using it.
Connecting to Your Lightsail Instance with VS Code
- Store locally the SSH Key from the Lightsail console. Remember the path to the
.pemfile. - Start Visual Studio Code.
- Install the Remote Explorer extension through the Extensions menu.
- You should see the Open a Remote Window icon on the left bottom of VS Code.
Click on it and then choose Connect to Host.
And then Add New Host.
Give it a name like ubuntu@<your.lightsail.static.ip>. Select SSH configuration file or create it (on Windows it's usually stored atC:\Users\{USERNAME}\.ssh\config. The config file will open and then specify the path to the SSH key or rename the host if you want:
- Press F1 or Ctrl+Shift+P to open the command palette in VS Code. Type and select "Remote-SSH: Connect to Host...". Choose your Host. Choose Linux. Accept the fingerprint. ๐ And voila! You're connected!
- Using the left menu bar you can choose Explorer -> Open Folder to browse the instances file system:
๐ง Configuring the Development Environment
- Access the Terminal within Visual Studio Code: Once connected to your Lightsail instance via SSH in VS Code, go to the top menu and select Terminal > New Terminal. This action will open a new terminal window within VS Code, connected to your Lightsail instance.
- Start off with updating and upgrading the packages (below commands for Ubuntu):
sudo apt update
sudo apt upgrade
- Depending on your needs you might want to download additional packages. Ubuntu image comes with Python 3.10 installed.
- Let's install AWS CLI Install unzip
sudo apt install unzip
Download the AWS CLI
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
Unzip the downloaded package:
unzip awscliv2.zip
Run the installation script:
sudo ./aws/install
Verify the installation:
aws --version
Understanding Costs: AWS Lightsail Billing
๐ต One important aspect to note is that charges apply not only to actively running instances but also to stopped instances. Whether your Lightsail instance is actively running or stopped, you'll incur charges. According to Lightsail's documentation:
Q: When am I getting charged for a plan?
Your Lightsail instances are charged only when they're in the running or stopped state. If you delete your Lightsail instance before the end of the month, we only charge you a prorated cost, based on the total number of hours that you used your Lightsail instance.
AWS bills the instances by the hour, but advertises the monthly price by capping it for a whole month. For example, if you use a $5/1GB per month plan for 5 days, you will be charged 120 hours (5 days x 24 hours) at an hourly rate of $0.00672 (10 USD / 720 hours)(depending on the AWS Region). This amounts to $0.81 for 5 days of usage. More details on additional costs can be found here.
โญ But remember that the first three months are free! โญ
Final Thoughts and Considerations
๐ Cloud-based development environments offer enhanced productivity and flexibility. You can connect to your Linux instance on Lightsail from any machine supporting SSH and have a separate environment fitting your needs. Since there are many OS options to choose from you can start a Windows machine if that's what you need. While Windows Subsystem for Linux (WSL) is free, AWS Lightsail's Linux environment incurs additional costs. The crucial consideration is enabling both Linux users to initiate Windows and vice versa, balancing the limitations of local setups against the incurred expenses of cloud alternatives.
Cover image generated with AI. Content credentials: Generated with AI โ November 3, 2023 at 11:57 AM.
Top comments (1)
Amazing