<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>...at an AWS event :: English</title>
    <link>http://localhost:1313/10_prerequisites/aws_event/index.html</link>
    <description>Attending an AWS hosted event To complete this workshop, you will be provided with an AWS account via the AWS Event Engine service. A team hash will be provided to you by event staff. Included in this environment will be a VS Code Server IDE and an EKS Kubernetes cluster pre-provisioned both pre-configured for your convenience.&#xA;Warning If you are currently logged in to an AWS Account, you can log out using this link</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <atom:link href="http://localhost:1313/10_prerequisites/aws_event/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VSCode Server Setup</title>
      <link>http://localhost:1313/10_prerequisites/aws_event/13_vscode-server/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/10_prerequisites/aws_event/13_vscode-server/index.html</guid>
      <description>Accessing the VS Code Server Step 1: Locate Event Outputs Go to the Event Outputs section in the workshop portal. You will find the following details: VSCODEURL: This is the URL to access the VS Code server. Password: This is the password required to log in to the server. Step 2: Copy the Password Copy the Password value to your clipboard. Step 3: Access the VS Code Server Click on the VSCODEURL link in the Event Outputs section. A browser window will open, prompting you to enter a password. Step 4: Enter the Password Paste the password you copied earlier into the password field. Click Login to proceed. Step 5: Start Coding! You now have access to the VS Code server, which is securely fronted by CloudFront. Note: Ensure you use the latest version of your browser for the best experience. If you encounter issues accessing the server, try clearing your browser cache or contacting the workshop support team.</description>
    </item>
  </channel>
</rss>