cloudx-proxy 0.1.1__tar.gz

cloudx_proxy-0.1.1/.github/workflows/release.yml

@@ -0,0 +1,67 @@
+name: Release
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: "lts/*"
+
+      - name: Setup Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: '3.x'
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install build twine
+
+      - name: Install semantic-release
+        run: |
+          npm install -g semantic-release @semantic-release/changelog @semantic-release/git
+
+      - name: Get Version
+        id: semantic
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          version=$(npx semantic-release --dry-run --initial-version 2025.1.0 | grep -oP 'The next release version is \K[0-9]+\.[0-9]+\.[0-9]+' || echo "")
+          if [ -n "$version" ]; then
+            echo "new_release_version=$version" >> $GITHUB_OUTPUT
+            echo "Version to be released: $version"
+          else
+            echo "No new version to be released"
+            exit 0
+          fi
+
+      - name: Create Release
+        if: steps.semantic.outputs.new_release_version != ''
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: npx semantic-release --initial-version 2025.1.0
+
+      - name: Build package
+        if: steps.semantic.outputs.new_release_version != ''
+        env:
+          SETUPTOOLS_SCM_PRETEND_VERSION: ${{ steps.semantic.outputs.new_release_version }}
+        run: python -m build
+
+      - name: Publish to PyPI
+        if: steps.semantic.outputs.new_release_version != ''
+        env:
+          TWINE_USERNAME: __token__
+          TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
+        run: twine upload dist/*

cloudx_proxy-0.1.1/.gitignore

@@ -0,0 +1,39 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# Version file generated by setuptools_scm
+cloudx_client/_version.py
+
+# Virtual Environment
+venv/
+env/
+ENV/
+
+# IDE
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db

cloudx_proxy-0.1.1/.releaserc

@@ -0,0 +1,38 @@
+{
+    "branches": ["main"],
+    "tagFormat": "v${version}",
+    "repositoryUrl": "https://github.com/easytocloud/cloudX-proxy.git",
+    "plugins": [
+        ["@semantic-release/commit-analyzer", {
+            "preset": "angular",
+            "releaseRules": [
+                {"type": "feat", "release": "minor"},
+                {"type": "fix", "release": "patch"},
+                {"type": "docs", "release": "patch"},
+                {"type": "style", "release": "patch"},
+                {"type": "refactor", "release": "patch"},
+                {"type": "perf", "release": "patch"},
+                {"type": "test", "release": "patch"},
+                {"type": "build", "release": "patch"},
+                {"type": "ci", "release": "patch"},
+                {"type": "chore", "release": "patch"}
+            ]
+        }],
+        "@semantic-release/release-notes-generator",
+        [
+            "@semantic-release/changelog",
+            {
+                "changelogFile": "CHANGELOG.md"
+            }
+        ],
+        [
+            "@semantic-release/git",
+            {
+                "assets": [
+                    "CHANGELOG.md"
+                ]
+            }
+        ],
+        "@semantic-release/github"
+    ]
+}

cloudx_proxy-0.1.1/CHANGELOG.md

@@ -0,0 +1,21 @@
+## [0.1.1](https://github.com/easytocloud/cloudX-proxy/compare/v0.1.0...v0.1.1) (2025-02-09)
+
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [0.1.0](https://github.com/easytocloud/cloudX-proxy/releases/tag/v0.1.0) (2025-02-09)
+
+Initial release with core functionality:
+
+### Features
+
+* SSH proxy command for connecting VSCode to EC2 instances via SSM
+* AWS profile configuration with cloudX-{env}-{user} format
+* SSH key management with 1Password integration
+* Environment-specific SSH config generation
+* Instance setup status verification
+* Cross-platform support (Windows, macOS, Linux)
+* Automatic instance startup if stopped
+* SSH key distribution via EC2 Instance Connect
+* SSH tunneling through AWS Systems Manager

cloudx_proxy-0.1.1/CONTRIBUTING.md

@@ -0,0 +1,27 @@
+# Contributing to cloudX-proxy
+
+## Development Setup
+
+1. Clone the repository
+2. Install development dependencies:
+   ```bash
+   pip install -e ".[dev]"
+   ```
+
+## Publishing to PyPI
+
+The package is automatically published to PyPI via GitHub Actions when a new release is created. Setup:
+
+1. Register project on PyPI
+2. Generate API token in PyPI (Account Settings → API tokens)
+3. Add token as GitHub secret named `PYPI_TOKEN`
+
+## Versioning
+
+The project uses semantic-release for versioning, starting at version 2025.1.0. Version numbers are automatically determined based on commit messages following the conventional commits specification.
+
+The GitHub Actions workflow will:
+1. Determine next version based on commits
+2. Update CHANGELOG.md
+3. Create GitHub release
+4. Publish to PyPI

cloudx_proxy-0.1.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 easytocloud
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

cloudx_proxy-0.1.1/PKG-INFO

@@ -0,0 +1,253 @@
+Metadata-Version: 2.2
+Name: cloudx-proxy
+Version: 0.1.1
+Summary: SSH proxy command to connect VSCode with Cloud9/CloudX instance using AWS Systems Manager
+Author-email: easytocloud <info@easytocloud.com>
+License: MIT License
+        
+        Copyright (c) 2025 easytocloud
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+        
+Project-URL: Homepage, https://github.com/easytocloud/cloudX-proxy
+Project-URL: Repository, https://github.com/easytocloud/cloudX-proxy
+Project-URL: Issues, https://github.com/easytocloud/cloudX-proxy/issues
+Project-URL: Changelog, https://github.com/easytocloud/cloudX-proxy/blob/main/CHANGELOG.md
+Keywords: aws,vscode,cloud9,cloudX,ssm,ssh,proxy
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: System :: Systems Administration
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: boto3>=1.34.0
+Requires-Dist: click>=8.1.0
+
+# cloudX-proxy
+
+A cross-platform SSH proxy command for connecting VSCode to CloudX/Cloud9 EC2 instances using AWS Systems Manager Session Manager.
+
+## Overview
+
+cloudX-proxy enables seamless SSH connections from VSCode to EC2 instances using AWS Systems Manager Session Manager, eliminating the need for direct SSH access or public IP addresses. It handles:
+
+- Automatic instance startup if stopped
+- SSH key distribution via EC2 Instance Connect
+- SSH tunneling through AWS Systems Manager
+- Cross-platform support (Windows, macOS, Linux)
+
+## Prerequisites
+
+1. **AWS CLI v2** - [Installation Guide](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
+2. **AWS Session Manager Plugin** - [Installation Guide](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html)
+3. **OpenSSH Client**
+   - Windows: [Microsoft's OpenSSH Installation Guide](https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse?tabs=gui)
+   - macOS/Linux: Usually pre-installed
+4. **uv** - Python package installer and resolver
+   ```bash
+   pip install uv
+   ```
+5. **VSCode with Remote SSH Extension** installed
+
+## AWS Credentials Setup
+
+The proxy expects to find AWS credentials in a profile named 'vscode' by default. These credentials should be the Access Key and Secret Key that were created by deploying the cloudX-user stack in your AWS account. The cloudX-user stack creates an IAM user with the minimal permissions required for:
+- Starting/stopping EC2 instances
+- Establishing SSM sessions
+- Pushing SSH keys via EC2 Instance Connect
+
+Once the SSH session is established, the user has to further configure the instance using `generate-sso-config` tool. This is a one-time setup unless the user's access to AWS accounts changes, in which case the user should re-run the `generate-sso-config` tool.
+
+It is recommended to use  --generate-directories and --use-ou-structure to create working directories for each account the user has access to.
+
+Everytime the user connects to the instance, `ssostart` will authenticate the user with AWS SSO and generate temporary credentials. 
+
+This ensures you have the appropriate AWS access both for connecting to the instance and for working within it.
+
+The proxy also supports easytocloud's AWS profile organizer. If you use multiple AWS environments, you can store your AWS configuration and credentials in `~/.aws/aws-envs/<environment>` directories and use the `--aws-env` option to specify which environment to use.
+
+## Setup
+
+cloudX-proxy now includes a setup command that automates the entire configuration process:
+
+```bash
+# Basic setup with defaults (vscode profile and key)
+uvx cloudx-proxy setup
+
+# Setup with custom profile and key
+uvx cloudx-proxy setup --profile myprofile --ssh-key mykey
+
+# Setup with AWS environment
+uvx cloudx-proxy setup --aws-env prod
+```
+
+The setup command will:
+
+1. Configure AWS Profile:
+   - Creates/validates AWS profile with cloudX-{env}-{user} format
+   - Supports AWS environment directories via --aws-env
+   - Uses aws configure for credential input
+
+2. Manage SSH Keys:
+   - Creates new SSH key pair if needed
+   - Offers 1Password integration options:
+     * Using 1Password SSH agent
+     * Storing private key as 1Password document
+
+3. Configure SSH:
+   - Creates ~/.ssh/vscode/config with proper settings
+   - Sets up environment-specific configurations
+   - Configures ProxyCommand with all necessary parameters
+   - Ensures main ~/.ssh/config includes the configuration
+
+4. Verify Instance Setup:
+   - Checks instance setup status
+   - Offers to wait for setup completion
+   - Monitors setup progress
+
+### Example SSH Configuration
+
+The setup command generates a configuration structure like this:
+
+```
+# Base environment config (created once per environment)
+Host cloudx-{env}-*
+    User ec2-user
+    IdentityAgent ~/.1password/agent.sock  # If using 1Password
+    IdentityFile ~/.ssh/vscode/key.pub    # .pub for 1Password, no .pub otherwise
+    IdentitiesOnly yes                    # If using 1Password
+    ProxyCommand uvx cloudx-proxy connect %h %p --profile profile --aws-env env
+
+# Host entries (added for each instance)
+Host cloudx-{env}-hostname
+    HostName i-1234567890
+```
+
+When adding new instances to an existing environment, the setup command will only add the specific host entry, preserving the existing environment configuration.
+
+### VSCode Configuration
+
+1. Install the "Remote - SSH" extension in VSCode
+2. Configure VSCode settings:
+   ```json
+   {
+       "remote.SSH.configFile": "~/.ssh/vscode/config",
+       "remote.SSH.connectTimeout": 90
+   }
+   ```
+
+## Usage
+
+### Command Line
+
+```bash
+# Setup new environment and instance
+uvx cloudx-proxy setup --profile myprofile --aws-env prod
+
+# Add instance to existing environment
+uvx cloudx-proxy setup --profile myprofile --aws-env prod
+
+# Connect to instance
+uvx cloudx-proxy connect i-0123456789abcdef0 22 --profile myprofile --aws-env prod
+
+# Connect with custom port
+uvx cloudx-proxy connect i-0123456789abcdef0 2222 --profile myprofile
+
+# Connect with different region
+uvx cloudx-proxy connect i-0123456789abcdef0 22 --region us-east-1
+
+# Connect with custom key
+uvx cloudx-proxy connect i-0123456789abcdef0 22 --key-path ~/.ssh/custom_key.pub
+```
+
+### VSCode
+
+1. Click the "Remote Explorer" icon in the VSCode sidebar
+2. Select "SSH Targets" from the dropdown
+3. Your configured hosts will appear (e.g., cloudx-dev)
+4. Click the "+" icon next to a host to connect
+5. VSCode will handle the rest, using cloudX-proxy to establish the connection
+
+## AWS Permissions
+
+The AWS user/role needs these permissions:
+
+```json
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "ec2:StartInstances",
+                "ec2:DescribeInstances",
+                "ssm:StartSession",
+                "ssm:DescribeInstanceInformation",
+                "ec2-instance-connect:SendSSHPublicKey"
+            ],
+            "Resource": "*"
+        }
+    ]
+}
+```
+
+## Troubleshooting
+
+1. **Setup Issues**
+   - If AWS profile validation fails, ensure your user ARN matches the cloudX-{env}-{user} format
+   - For 1Password integration, ensure the CLI is installed and you're signed in
+   - Check that ~/.ssh/vscode directory has proper permissions (700)
+   - Verify main ~/.ssh/config is writable
+
+2. **Connection Timeout**
+   - Ensure the instance has the SSM agent installed and running
+   - Check that your AWS credentials have the required permissions
+   - Verify the instance ID is correct
+   - Increase the VSCode SSH timeout if needed
+
+3. **SSH Key Issues**
+   - If using 1Password SSH agent, verify agent is running (~/.1password/agent.sock exists)
+   - Check file permissions (600 for private key, 644 for public key)
+   - Verify the public key is being successfully pushed to the instance
+   - For stored keys in 1Password, ensure you can access them via the CLI
+
+4. **AWS Configuration**
+   - Confirm AWS CLI is configured with valid credentials
+   - Default region is eu-west-1 if not specified in profile or command line
+   - If using AWS profile organizer, ensure your environment directory exists at `~/.aws/aws-envs/<environment>/`
+   - Verify the Session Manager plugin is installed correctly
+   - Check that the instance has the required IAM role for SSM
+
+5. **Instance Setup Status**
+   - If setup appears stuck, check /home/ec2-user/.install-running exists
+   - Verify /home/ec2-user/.install-done is created upon completion
+   - Check instance system logs for setup script errors
+
+## License
+
+MIT License - see LICENSE file for details

cloudx_proxy-0.1.1/README.md

@@ -0,0 +1,203 @@
+# cloudX-proxy
+
+A cross-platform SSH proxy command for connecting VSCode to CloudX/Cloud9 EC2 instances using AWS Systems Manager Session Manager.
+
+## Overview
+
+cloudX-proxy enables seamless SSH connections from VSCode to EC2 instances using AWS Systems Manager Session Manager, eliminating the need for direct SSH access or public IP addresses. It handles:
+
+- Automatic instance startup if stopped
+- SSH key distribution via EC2 Instance Connect
+- SSH tunneling through AWS Systems Manager
+- Cross-platform support (Windows, macOS, Linux)
+
+## Prerequisites
+
+1. **AWS CLI v2** - [Installation Guide](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
+2. **AWS Session Manager Plugin** - [Installation Guide](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html)
+3. **OpenSSH Client**
+   - Windows: [Microsoft's OpenSSH Installation Guide](https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse?tabs=gui)
+   - macOS/Linux: Usually pre-installed
+4. **uv** - Python package installer and resolver
+   ```bash
+   pip install uv
+   ```
+5. **VSCode with Remote SSH Extension** installed
+
+## AWS Credentials Setup
+
+The proxy expects to find AWS credentials in a profile named 'vscode' by default. These credentials should be the Access Key and Secret Key that were created by deploying the cloudX-user stack in your AWS account. The cloudX-user stack creates an IAM user with the minimal permissions required for:
+- Starting/stopping EC2 instances
+- Establishing SSM sessions
+- Pushing SSH keys via EC2 Instance Connect
+
+Once the SSH session is established, the user has to further configure the instance using `generate-sso-config` tool. This is a one-time setup unless the user's access to AWS accounts changes, in which case the user should re-run the `generate-sso-config` tool.
+
+It is recommended to use  --generate-directories and --use-ou-structure to create working directories for each account the user has access to.
+
+Everytime the user connects to the instance, `ssostart` will authenticate the user with AWS SSO and generate temporary credentials. 
+
+This ensures you have the appropriate AWS access both for connecting to the instance and for working within it.
+
+The proxy also supports easytocloud's AWS profile organizer. If you use multiple AWS environments, you can store your AWS configuration and credentials in `~/.aws/aws-envs/<environment>` directories and use the `--aws-env` option to specify which environment to use.
+
+## Setup
+
+cloudX-proxy now includes a setup command that automates the entire configuration process:
+
+```bash
+# Basic setup with defaults (vscode profile and key)
+uvx cloudx-proxy setup
+
+# Setup with custom profile and key
+uvx cloudx-proxy setup --profile myprofile --ssh-key mykey
+
+# Setup with AWS environment
+uvx cloudx-proxy setup --aws-env prod
+```
+
+The setup command will:
+
+1. Configure AWS Profile:
+   - Creates/validates AWS profile with cloudX-{env}-{user} format
+   - Supports AWS environment directories via --aws-env
+   - Uses aws configure for credential input
+
+2. Manage SSH Keys:
+   - Creates new SSH key pair if needed
+   - Offers 1Password integration options:
+     * Using 1Password SSH agent
+     * Storing private key as 1Password document
+
+3. Configure SSH:
+   - Creates ~/.ssh/vscode/config with proper settings
+   - Sets up environment-specific configurations
+   - Configures ProxyCommand with all necessary parameters
+   - Ensures main ~/.ssh/config includes the configuration
+
+4. Verify Instance Setup:
+   - Checks instance setup status
+   - Offers to wait for setup completion
+   - Monitors setup progress
+
+### Example SSH Configuration
+
+The setup command generates a configuration structure like this:
+
+```
+# Base environment config (created once per environment)
+Host cloudx-{env}-*
+    User ec2-user
+    IdentityAgent ~/.1password/agent.sock  # If using 1Password
+    IdentityFile ~/.ssh/vscode/key.pub    # .pub for 1Password, no .pub otherwise
+    IdentitiesOnly yes                    # If using 1Password
+    ProxyCommand uvx cloudx-proxy connect %h %p --profile profile --aws-env env
+
+# Host entries (added for each instance)
+Host cloudx-{env}-hostname
+    HostName i-1234567890
+```
+
+When adding new instances to an existing environment, the setup command will only add the specific host entry, preserving the existing environment configuration.
+
+### VSCode Configuration
+
+1. Install the "Remote - SSH" extension in VSCode
+2. Configure VSCode settings:
+   ```json
+   {
+       "remote.SSH.configFile": "~/.ssh/vscode/config",
+       "remote.SSH.connectTimeout": 90
+   }
+   ```
+
+## Usage
+
+### Command Line
+
+```bash
+# Setup new environment and instance
+uvx cloudx-proxy setup --profile myprofile --aws-env prod
+
+# Add instance to existing environment
+uvx cloudx-proxy setup --profile myprofile --aws-env prod
+
+# Connect to instance
+uvx cloudx-proxy connect i-0123456789abcdef0 22 --profile myprofile --aws-env prod
+
+# Connect with custom port
+uvx cloudx-proxy connect i-0123456789abcdef0 2222 --profile myprofile
+
+# Connect with different region
+uvx cloudx-proxy connect i-0123456789abcdef0 22 --region us-east-1
+
+# Connect with custom key
+uvx cloudx-proxy connect i-0123456789abcdef0 22 --key-path ~/.ssh/custom_key.pub
+```
+
+### VSCode
+
+1. Click the "Remote Explorer" icon in the VSCode sidebar
+2. Select "SSH Targets" from the dropdown
+3. Your configured hosts will appear (e.g., cloudx-dev)
+4. Click the "+" icon next to a host to connect
+5. VSCode will handle the rest, using cloudX-proxy to establish the connection
+
+## AWS Permissions
+
+The AWS user/role needs these permissions:
+
+```json
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "ec2:StartInstances",
+                "ec2:DescribeInstances",
+                "ssm:StartSession",
+                "ssm:DescribeInstanceInformation",
+                "ec2-instance-connect:SendSSHPublicKey"
+            ],
+            "Resource": "*"
+        }
+    ]
+}
+```
+
+## Troubleshooting
+
+1. **Setup Issues**
+   - If AWS profile validation fails, ensure your user ARN matches the cloudX-{env}-{user} format
+   - For 1Password integration, ensure the CLI is installed and you're signed in
+   - Check that ~/.ssh/vscode directory has proper permissions (700)
+   - Verify main ~/.ssh/config is writable
+
+2. **Connection Timeout**
+   - Ensure the instance has the SSM agent installed and running
+   - Check that your AWS credentials have the required permissions
+   - Verify the instance ID is correct
+   - Increase the VSCode SSH timeout if needed
+
+3. **SSH Key Issues**
+   - If using 1Password SSH agent, verify agent is running (~/.1password/agent.sock exists)
+   - Check file permissions (600 for private key, 644 for public key)
+   - Verify the public key is being successfully pushed to the instance
+   - For stored keys in 1Password, ensure you can access them via the CLI
+
+4. **AWS Configuration**
+   - Confirm AWS CLI is configured with valid credentials
+   - Default region is eu-west-1 if not specified in profile or command line
+   - If using AWS profile organizer, ensure your environment directory exists at `~/.aws/aws-envs/<environment>/`
+   - Verify the Session Manager plugin is installed correctly
+   - Check that the instance has the required IAM role for SSM
+
+5. **Instance Setup Status**
+   - If setup appears stuck, check /home/ec2-user/.install-running exists
+   - Verify /home/ec2-user/.install-done is created upon completion
+   - Check instance system logs for setup script errors
+
+## License
+
+MIT License - see LICENSE file for details

cloudx_proxy-0.1.1/cloudx_proxy/__init__.py

@@ -0,0 +1,3 @@
+from ._version import __version__
+
+__all__ = ['__version__']