File tree Expand file tree Collapse file tree 1 file changed +18
-3
lines changed Expand file tree Collapse file tree 1 file changed +18
-3
lines changed Original file line number Diff line number Diff line change 1313 - Includes some light justification verbiage for Anthropic
1414- Choose "Do it on your own" rather than as part of an event
1515 - This leads to a [ page describing what must be installed] ( https://catalog.workshops.aws/building-agentic-workflows/en-US/on_your_own )
16- - The IDE in particular will be VS Code Code-Server
16+ - The IDE in particular will be VS Code Server
17+
18+
19+ Now: Upon subsequent turns of fate I arrived at the following (as-yet-untested) recipe for setting up
20+ a VS Code Server instance on an AWS EC2 instance with Q Developer enabled and a few minor whistles
21+ and bells.
1722
1823
1924## Build a working environment on EC2 including Q Developer access
5560sudo systemctl enable --now code-server@ubuntu
5661```
5762
58- Here the 'your-secure-password' is an arbitrary password I select. I use it in
59- authenticating in to the VS Code Server instance: Prompted when navigating to
63+
64+ Warning: ` cert: false ` means no SSL/TLS certificate will be in play. Communication
65+ will be over unencrypted HTTP, not HTTPS. This is easily modified: One changes to
66+ the ` .config/code-server/config.yaml ` file: ` cert: true ` . The browser address still
67+ uses ` :8080 ` and we will see a browser warning 'Not secure'. To this we respond by
68+ clicking 'Advanced > Proceed` and we now have encrypted traffic. There is a more
69+ proper method of accomplishing this that involves using a domain name for the EC2;
70+ I skip this for now.
71+
72+
73+ Above note there is 'your-secure-password'. This is an arbitrary password I select.
74+ I use it in authenticating in to the VS Code Server instance: As prompted when navigating to
6075` http://ec2-ip-address:8080 ` .
6176
6277
You can’t perform that action at this time.
0 commit comments