“Run Chrome on AWS” can mean two different things: use Chrome on your own computer to connect to an AWS-hosted service, or run a browser inside a remote AWS session. For managed remote browser or application access, AWS WorkSpaces Applications is a documented option. AWS documentation also shows how to launch Chromium in a Linux WorkSpaces Applications session. That example is not an installation guide for Google Chrome on a general-purpose EC2 instance.
First decide where Chrome should run
The right setup depends on where the browser executable and web page need to be. A local browser can act as a client for an AWS service; a remote browser runs inside an AWS-hosted session.
| What you need | Where the browser runs | Relevant AWS approach |
|---|---|---|
| Use a browser to access an AWS remote service | On your local computer | Use a supported browser and follow that service’s access requirements. AWS WorkSpaces Applications supports access through an HTML5-capable browser. Check the current WorkSpaces Applications requirements. |
| Provide users with a browser running remotely | Inside a streamed application session | WorkSpaces Applications has a documented Linux example that launches Chromium and registers it as an application. |
| Install and operate Google Chrome directly on a self-managed EC2 instance | On your EC2 host | The AWS sources cited here do not establish current installation, update, or security-hardening steps for this setup. Use current official AWS and Google Chrome instructions rather than treating the WorkSpaces Applications Chromium example as an EC2 procedure. |
Use Chrome to access an AWS-hosted service
If Chrome is only the client, install or update it on the endpoint device and check the requirements for the specific AWS service. The browser requirement depends on the service and client platform; AWS’s WorkSpaces browser requirements page describes support for the three most recent major browser versions, a requirement that can change. Verify the current requirements before deployment.
This arrangement does not put the Chrome process on AWS. The AWS service supplies the remote application or session, while Chrome on the user’s computer displays or connects to it.
#1 Best Overall
Run a browser in a managed WorkSpaces Applications session
AWS describes WorkSpaces Applications as a managed application-streaming service: AWS manages the hosting resources and says the service scales automatically. In its Linux session-context example, AWS demonstrates launching Chromium with a script, registering that script as an application through Image Assistant, and then creating an image, fleet, and stack. This is a service-specific Chromium example, not a general-purpose Google Chrome-on-EC2 setup. See AWS’s session-context example and the WorkSpaces Applications service overview.
What the documented workflow covers
- Prepare the Linux environment for the WorkSpaces Applications image according to the current AWS guide.
- Create a launch script for Chromium and configure it as the session-context script described in the guide.
- Use Image Assistant to register the script as an application in the image.
- Create and test the image, then create a fleet and stack so users can access the streamed application.
Follow AWS’s current instructions for the script contents, image preparation, fleet settings, and stack setup; those details are specific to the service and can change. The session-context documentation cautions that session context is visible to the user. Do not place passwords, access keys, or other sensitive information in it, and validate the context before relying on it.
Choose what happens to web content and user peripherals
Keep pages in the remote session or redirect selected URLs
By default, do not assume that content opens locally. WorkSpaces Applications can be configured to redirect matching URL patterns from the streamed session to the user’s local browser. An administrator controls which patterns redirect; destinations that do not match remain in the remote session. AWS says redirection can reduce latency and server-side resource use for resource-intensive web content, but it is a configuration option, not a guarantee for every URL. Review AWS URL-redirection configuration.
Use a webcam or microphone for calls
AWS documents local webcam and microphone redirection for streamed sessions accessed through Chromium-based browsers. It requires browser permission for the camera or microphone as well as administrator-side configuration. Check the service guidance and test the actual endpoint and peripherals; support should not be assumed for every device or setup. See AWS’s webcam and microphone guidance.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
Chrome on EC2: what to verify before building it
A self-managed EC2 browser host is a different operating model from WorkSpaces Applications. You are responsible for the host and browser lifecycle, but the AWS material cited in this guide does not provide a current, verified procedure for installing, updating, or hardening Google Chrome on EC2. It would be unsafe to present the managed-service Chromium example as though it supplied those steps.
- Confirm the intended operating system and whether Google Chrome, rather than Chromium, is required.
- Consult current official installation and update guidance from Google for that operating system, and current AWS documentation for the EC2 image and access model.
- Define how users reach the browser, how sessions are isolated, and how browser and operating-system updates are applied.
- Do not expose a remote browser or desktop directly to the public internet without a reviewed access-control and security design.
Troubleshoot the setup by locating the failure
First identify whether the problem is on the local browser-client path or inside the remote session. These are different environments and require different checks.
- The AWS access page will not open: Check that the endpoint browser and operating system meet the current requirements for the specific AWS service. Browser support changes over time.
- The streamed Chromium application does not launch: Check the script and application registration against the WorkSpaces Applications session-context guide, then verify the image was built and published with the intended application.
- A page opens remotely when you expected it locally: Check administrator-configured URL patterns and confirm that the destination matches a configured rule. Redirection is selective.
- A camera or microphone is unavailable: Check local browser permissions and administrator-side redirection configuration, then test the endpoint device.
- You are following the Chromium example on EC2: Stop and use instructions specific to the EC2 operating system and Google Chrome. The streaming-service example does not establish EC2 installation or maintenance steps.
Or skip the browser setup
If your goal is simply to capture a web page rather than provide users with an interactive remote browser, ScreenshotNeo can return a screenshot or PDF with one GET request. Its capture process accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. ScreenshotNeo also provides an MCP server for AI agents, with tools for screenshots, page information, and PDF capture. Learn about ScreenshotNeo.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month—no card required.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsFrequently Asked Questions
Does the WorkSpaces Applications example install Google Chrome on EC2?
No. It documents launching Chromium in a Linux WorkSpaces Applications session, not installing Google Chrome on a general-purpose EC2 instance.
Best Value
Can users open every streamed-session URL in their local browser?
No. Local opening depends on administrator-configured URL patterns; unmatched destinations remain in the remote session.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
