cloudx-proxy 0.3.2__py3-none-any.whl → 0.3.4__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
cloudx_proxy/_version.py CHANGED
@@ -12,5 +12,5 @@ __version__: str
12
12
  __version_tuple__: VERSION_TUPLE
13
13
  version_tuple: VERSION_TUPLE
14
14
 
15
- __version__ = version = '0.3.2'
16
- __version_tuple__ = version_tuple = (0, 3, 2)
15
+ __version__ = version = '0.3.4'
16
+ __version_tuple__ = version_tuple = (0, 3, 4)
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.2
2
2
  Name: cloudx-proxy
3
- Version: 0.3.2
3
+ Version: 0.3.4
4
4
  Summary: SSH proxy command to connect VSCode with Cloud9/CloudX instance using AWS Systems Manager
5
5
  Author-email: easytocloud <info@easytocloud.com>
6
6
  License: MIT License
@@ -63,37 +63,45 @@ cloudX-proxy enables seamless SSH connections from VSCode to EC2 instances using
63
63
 
64
64
  ## Prerequisites
65
65
 
66
- 1. **AWS CLI v2** - [Installation Guide](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
67
- 2. **AWS Session Manager Plugin** - [Installation Guide](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html)
68
- 3. **OpenSSH Client**
66
+ 1. **AWS CLI v2** - Used to configure AWS profiles and credentials
67
+ - [Installation Guide](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
68
+ - Required for `aws configure` during setup
69
+ - Handles AWS credentials and region configuration
70
+
71
+ 2. **AWS Session Manager Plugin** - Enables secure tunneling through AWS Systems Manager
72
+ - [Installation Guide](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html)
73
+ - Provides the secure connection channel
74
+ - No need for public IP addresses or direct SSH access
75
+
76
+ 3. **OpenSSH Client** - Handles SSH key management and connections
69
77
  - Windows: [Microsoft's OpenSSH Installation Guide](https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse?tabs=gui)
70
78
  - macOS/Linux: Usually pre-installed
71
- 4. **uv** - Python package installer and resolver
79
+ - Manages SSH keys and configurations
80
+ - Provides the SSH client for VSCode Remote
81
+
82
+ 4. **uv** - Modern Python package installer and virtual environment manager
72
83
  ```bash
73
84
  pip install uv
74
85
  ```
75
- 5. **VSCode with Remote SSH Extension** installed
76
-
77
- ## AWS Credentials Setup
86
+ The `uvx` command from uv automatically:
87
+ - Creates an isolated virtual environment for each package
88
+ - Downloads and installs the package and its dependencies
89
+ - Runs the package without explicit environment activation
90
+
91
+ This means you can run cloudX-proxy directly with `uvx cloudx-proxy` without manually managing virtual environments or dependencies.
78
92
 
79
- 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:
80
- - Starting/stopping EC2 instances
81
- - Establishing SSM sessions
82
- - Pushing SSH keys via EC2 Instance Connect
93
+ 5. **VSCode with Remote SSH Extension** - Your development environment
94
+ - Provides the integrated development environment
95
+ - Uses the SSH configuration to connect to instances
96
+ - Handles file synchronization and terminal sessions
83
97
 
84
- 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.
98
+ ## Installation
85
99
 
86
- It is recommended to use --generate-directories and --use-ou-structure to create working directories for each account the user has access to.
87
-
88
- Everytime the user connects to the instance, `ssostart` will authenticate the user with AWS SSO and generate temporary credentials.
89
-
90
- This ensures you have the appropriate AWS access both for connecting to the instance and for working within it.
91
-
92
- 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.
100
+ The cloudX-proxy package is available on PyPI and can run using uvx without explicit installation.
93
101
 
94
102
  ## Setup
95
103
 
96
- cloudX-proxy now includes a setup command that automates the entire configuration process:
104
+ cloudX-proxy includes a setup command that automates the entire configuration process:
97
105
 
98
106
  ```bash
99
107
  # Basic setup with defaults (vscode profile and key)
@@ -109,7 +117,7 @@ uvx cloudx-proxy setup --aws-env prod
109
117
  The setup command will:
110
118
 
111
119
  1. Configure AWS Profile:
112
- - Creates/validates AWS profile with cloudX-{env}-{user} format
120
+ - Creates/validates AWS profile for IAM user in cloudX-{env}-{user} format
113
121
  - Supports AWS environment directories via --aws-env
114
122
  - Uses aws configure for credential input
115
123
 
@@ -130,25 +138,56 @@ The setup command will:
130
138
  - Offers to wait for setup completion
131
139
  - Monitors setup progress
132
140
 
133
- ### Example SSH Configuration
141
+ ### SSH Configuration
134
142
 
135
- The setup command generates a configuration structure like this:
143
+ The setup command configures SSH to use cloudX-proxy as a ProxyCommand, enabling seamless connections through AWS Systems Manager. For example, running:
144
+
145
+ ```bash
146
+ uvx cloudx-proxy setup --profile myprofile --ssh-key mykey
147
+ ```
148
+
149
+ Will create a configuration like this:
136
150
 
137
151
  ```
138
152
  # Base environment config (created once per environment)
139
- Host cloudx-{env}-*
153
+ Host cloudx-dev-*
140
154
  User ec2-user
141
- IdentityAgent ~/.1password/agent.sock # If using 1Password
142
- IdentityFile ~/.ssh/vscode/key.pub # .pub for 1Password, no .pub otherwise
143
- IdentitiesOnly yes # If using 1Password
144
- ProxyCommand uvx cloudx-proxy connect %h %p --profile profile --aws-env env
145
-
146
- # Host entries (added for each instance)
147
- Host cloudx-{env}-hostname
148
- HostName i-1234567890
155
+ IdentityFile ~/.ssh/vscode/mykey
156
+ ProxyCommand uvx cloudx-proxy connect %h %p --profile myprofile --ssh-key mykey
157
+
158
+ # Host entry (added for specific instance)
159
+ Host cloudx-dev-myserver
160
+ HostName i-0123456789abcdef0
161
+ ```
162
+
163
+ Allowing the user to:
164
+
165
+ ```bash
166
+ ssh cloudx-dev-myserver
167
+ scp cloudx-dev-myserver:/path/to/file /local/path/to/file
149
168
  ```
169
+ without the need to provide any further credentials.
170
+
171
+ In these examples, ssh will use cloudx-proxy to connect to AWS with the `myprofile` credentials, allowing it to check the instance state and start the instance if it's stopped. Next cloudx-proxy will use `myprofile` to push the public part of the key `mykey` to the instance using SSM. Finally a tunnel is created between the local machine and the instance, using the SSM plugin, allowing SSH to connect to the instance using the private part of the `mykey` key.
172
+
173
+ VSCode will be able to connect to the instance using the same SSH configuration.
150
174
 
151
- When adding new instances to an existing environment, the setup command will only add the specific host entry, preserving the existing environment configuration.
175
+ ### SSH Configuration Details
176
+ The setup command creates:
177
+
178
+ 1. A base configuration for each environment (cloudx-{env}-*) with:
179
+ - User and key settings
180
+ - 1Password integration if selected
181
+ - ProxyCommand with appropriate parameters
182
+
183
+ 2. Individual host entries for each instance:
184
+ - Uses consistent naming (cloudx-{env}-hostname)
185
+ - Maps to instance IDs automatically
186
+ - Inherits environment-level settings
187
+
188
+ When adding new instances to an existing environment, you can choose to:
189
+ - Override the environment configuration with new settings
190
+ - Add instance-specific settings while preserving the environment config
152
191
 
153
192
  ### VSCode Configuration
154
193
 
@@ -160,7 +199,7 @@ When adding new instances to an existing environment, the setup command will onl
160
199
  "remote.SSH.connectTimeout": 90
161
200
  }
162
201
  ```
163
-
202
+ This extra long timeout is necessary to account for the time it takes to start the instance and establish the connection.
164
203
  ## Usage
165
204
 
166
205
  ### Command Line Options
@@ -228,27 +267,28 @@ Note: The connect command is typically used through the SSH ProxyCommand configu
228
267
  5. VSCode will handle the rest, using cloudX-proxy to establish the connection
229
268
 
230
269
  ## AWS Permissions
270
+ ### IAM User Permissions
231
271
 
232
- The AWS user/role needs these permissions:
233
-
234
- ```json
235
- {
236
- "Version": "2012-10-17",
237
- "Statement": [
238
- {
239
- "Effect": "Allow",
240
- "Action": [
241
- "ec2:StartInstances",
242
- "ec2:DescribeInstances",
243
- "ssm:StartSession",
244
- "ssm:DescribeInstanceInformation",
245
- "ec2-instance-connect:SendSSHPublicKey"
246
- ],
247
- "Resource": "*"
248
- }
249
- ]
250
- }
251
- ```
272
+ The AWS IAM user has to be member of the AWS IAM Group that is created as part of the cloudX environment.
273
+ The group uses ABAC (Attribute Based Access Control) to allow access to the instances based on the tags.
274
+ The ABAC tag defaults to `cloudxuser` and should have the value of the username of the user that owns the instance.
275
+
276
+ Example:
277
+ - AWS IAM User `cloudx-dev-user1` is connecting to an instance with the tag `cloudxuser=cloudx-dev-user1`
278
+
279
+ Note: This user should be created using the cloudX-user product from Service Catalog in the AWS Console. This assures proper permissions and naming conventions. The user in the example is member of the `dev` group, part as part of the `cloudx-dev` environment.
280
+
281
+ The EC2 instance should have the tag `cloudxuser` with the value of the username of the user that is connecting to the instance. This is automatically set when the instance is created using the cloudX-instance product from Service Catalog in the AWS Console.
282
+
283
+ ### EC2 Instance Permissions
284
+
285
+ The EC2 instance has a profile/role that provides enough permissions to allow the AWS SSM agent to connect to the instance, as well as
286
+ - CodeArtifact read only access, to use as a source for pip
287
+ - CodeCommit read only access, to pull code from the repository for installation
288
+ - Organizations read only access, to create aws sso configuration
289
+ - EC2 basic access, to allow the instance to introspect for tags and other metadata
290
+
291
+ These permissions are required to bootstrap the instance, so that after creation the instance can perform software installation and configuration without a user being present.
252
292
 
253
293
  ## Troubleshooting
254
294
 
@@ -0,0 +1,11 @@
1
+ cloudx_proxy/__init__.py,sha256=ZZ2O_m9OFJm18AxMSuYJt4UjSuSqyJlYRaZMoets498,61
2
+ cloudx_proxy/_version.py,sha256=gK2CDe_mbvAwKw5ZjOIg75LuB0kCZ4LyDYjtXPapvJw,411
3
+ cloudx_proxy/cli.py,sha256=Ph-m8lDsdU2zZab9Y6YgBBzd_UDouBnfNrYFFx0bI_E,3426
4
+ cloudx_proxy/core.py,sha256=WjKoqMmmnt6e_4JMeq4gTka75JAvQcMUs9r9XUBLmFE,7289
5
+ cloudx_proxy/setup.py,sha256=Y8YYMJ47fb57FAr6llQaFGuVOQ-fstYEg_Pdv5uCd-A,22486
6
+ cloudx_proxy-0.3.4.dist-info/LICENSE,sha256=i7P2OR4zsJYsMWcCUDe_B9ZfGi9bU0K5I2nKfDrW_N8,1068
7
+ cloudx_proxy-0.3.4.dist-info/METADATA,sha256=WAcs0mWx3clQqk-1oNNk9Jqu2hBrlbWG6Ujr5n5lDhU,14037
8
+ cloudx_proxy-0.3.4.dist-info/WHEEL,sha256=In9FTNxeP60KnTkGw7wk6mJPYd_dQSjEZmXdBdMCI-8,91
9
+ cloudx_proxy-0.3.4.dist-info/entry_points.txt,sha256=HGt743N2lVlKd7O1qWq3C0aEHyS5PjPnxzDHh7hwtSg,54
10
+ cloudx_proxy-0.3.4.dist-info/top_level.txt,sha256=2wtEote1db21j-VvkCJFfT-dLlauuG5indjggYh3xDg,13
11
+ cloudx_proxy-0.3.4.dist-info/RECORD,,
@@ -1,11 +0,0 @@
1
- cloudx_proxy/__init__.py,sha256=ZZ2O_m9OFJm18AxMSuYJt4UjSuSqyJlYRaZMoets498,61
2
- cloudx_proxy/_version.py,sha256=9jP8Fo8egXoMs_T3DFqSuJYg4n9o9mnwYubl_hnut4k,411
3
- cloudx_proxy/cli.py,sha256=Ph-m8lDsdU2zZab9Y6YgBBzd_UDouBnfNrYFFx0bI_E,3426
4
- cloudx_proxy/core.py,sha256=WjKoqMmmnt6e_4JMeq4gTka75JAvQcMUs9r9XUBLmFE,7289
5
- cloudx_proxy/setup.py,sha256=Y8YYMJ47fb57FAr6llQaFGuVOQ-fstYEg_Pdv5uCd-A,22486
6
- cloudx_proxy-0.3.2.dist-info/LICENSE,sha256=i7P2OR4zsJYsMWcCUDe_B9ZfGi9bU0K5I2nKfDrW_N8,1068
7
- cloudx_proxy-0.3.2.dist-info/METADATA,sha256=4AL8y6Qeg--nos0FquyZcxUSXY-EkuUBwgSqZ0-5hCw,11736
8
- cloudx_proxy-0.3.2.dist-info/WHEEL,sha256=In9FTNxeP60KnTkGw7wk6mJPYd_dQSjEZmXdBdMCI-8,91
9
- cloudx_proxy-0.3.2.dist-info/entry_points.txt,sha256=HGt743N2lVlKd7O1qWq3C0aEHyS5PjPnxzDHh7hwtSg,54
10
- cloudx_proxy-0.3.2.dist-info/top_level.txt,sha256=2wtEote1db21j-VvkCJFfT-dLlauuG5indjggYh3xDg,13
11
- cloudx_proxy-0.3.2.dist-info/RECORD,,