What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
“Run Chrome on AWS” can mean two different things: use Chrome on your computer to connect to an AWS-hosted service, or run a browser inside a remote AWS session. AWS documents both browser access and managed application streaming, including a Linux Chromium example for WorkSpaces Applications. Those are not instructions for installing Google Chrome on a general-purpose EC2 instance.
First decide where the browser should run
| What you need | Where the browser runs | Relevant AWS option |
|---|---|---|
| Open an AWS-hosted workspace or streamed application | On your local computer; Chrome is the client | WorkSpaces Applications browser access, subject to AWS’s current browser and platform requirements |
| Give users a browser running in a remote session | In the streamed AWS session | WorkSpaces Applications; AWS documents a Linux Chromium example |
| Install and operate Google Chrome directly on an EC2 instance | On a self-managed EC2 host | The AWS sources cited here do not establish current install, update, or security instructions for this setup |
The distinction matters: a local Chrome window used to reach a remote service is not a browser hosted on AWS. Likewise, AWS’s Linux Chromium example is specific to WorkSpaces Applications, not a general Chrome-on-EC2 recipe.
As an Amazon Associate I earn from qualifying purchases.
Use Chrome to access an AWS-hosted service
If your goal is simply to connect to WorkSpaces Applications, use a supported HTML5-capable browser on the local endpoint. AWS’s browser requirements page describes support for the three most recent major browser versions; browser support can change, so check the current WorkSpaces Applications browser requirements for the service and endpoint platform you use.
Recommended Free Tools
This approach leaves the browser executable on the user’s computer. It does not install Chrome in an AWS session. Check the applicable service setup and access instructions as well as endpoint compatibility before rolling it out.
#1 Best Overall
Host a browser in a managed AWS session
What WorkSpaces Applications manages
Amazon WorkSpaces Applications is AWS’s managed application-streaming service. AWS says it manages the resources needed to host and run applications and scales automatically. Users access streamed applications on demand; this is a managed streaming model rather than a procedure for setting up a browser on a self-managed EC2 machine.
What the Linux Chromium example covers
AWS’s Linux session-context example launches Chromium with a script and registers that script as an application using Image Assistant. The documented flow continues through creating an image, fleet, and stack. Follow the current AWS instructions for those service-specific steps; do not treat the example as Google Chrome installation instructions for EC2.
AWS warns that session context is visible to the user. Do not put secrets or other sensitive information in it, and validate the values before relying on them.
Choose remote or local handling for web content
WorkSpaces Applications supports administrator-configured host-to-client URL redirection. URL patterns determine which destinations open in the user’s local browser; destinations that do not match remain in the remote session. AWS says redirecting resource-intensive web content can reduce latency and server-side resource use. It is an option to configure, not a claim that every URL redirects or that redirection is enabled by default. See AWS’s URL redirection documentation.
- Keep content in the streamed session when it needs to remain within that remote browser context.
- Configure patterns for content that should open locally, and verify the behavior with the URLs users need.
- Consider the endpoint’s browser and network context when deciding whether local opening is appropriate.
Use a webcam or microphone in a streamed browser
For audio and video use, AWS documents local webcam and microphone redirection with Chromium-based browsers. The user must grant camera and microphone permissions in the local browser, and an administrator must configure the relevant service settings. Device behavior can vary, so verify the actual endpoint and peripheral setup rather than assuming every camera or microphone will work. See AWS’s webcam and microphone redirection guidance.
Chrome on EC2: what to verify before proceeding
If you specifically need Google Chrome installed on a general-purpose EC2 host, the sources available here do not substantiate a current installation procedure, update strategy, or hardening checklist. Do not copy the WorkSpaces Applications Chromium script into an EC2 deployment and assume it is equivalent. Before proceeding, consult current official Google Chrome and AWS instructions for the instance operating system, package source, browser updates, user permissions, and remote-display approach.
Rank #4
Also decide how the browser will be accessed, who can reach the host, what data may enter browser sessions, and how browser and operating-system updates will be applied. Those choices are operational requirements, not solved merely by installing a browser.
Troubleshoot the common architecture mismatches
- Chrome opens locally, but you expected it to run in AWS: you are using the browser as a client. Use the WorkSpaces Applications streamed-app route if users need the browser executable in the remote session.
- The Linux example does not work as an EC2 installation: it is a WorkSpaces Applications session-context example that uses Chromium and Image Assistant, not general EC2 setup guidance.
- A URL still opens remotely: URL redirection depends on administrator-configured patterns. Check whether the destination matches a configured pattern and review the service’s redirection settings.
- A meeting cannot use a camera or microphone: confirm Chromium-based browser access, local browser permissions, and administrator-side configuration; then test the specific endpoint and device.
- A browser version is rejected or unsupported: re-check AWS’s current browser requirements for the service, endpoint OS, and browser version rather than relying on an old compatibility assumption.
Or skip the browser setup
If your actual task is to capture a website rather than provide users with an interactive remote browser, ScreenshotNeo is a website screenshot API and MCP server. One GET request can return an image or PDF; it is a different solution from hosting Chrome for interactive use. See the ScreenshotNeo website.
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. Cookie banners, newsletter popups, and chat widgets can be removed before capture; bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Sign up free for ScreenshotNeo.
Frequently Asked Questions
Does AWS’s Chromium example install Google Chrome on EC2?
No. It is a Linux Chromium example for WorkSpaces Applications, using a script registered with Image Assistant.
Can a streamed browser open selected pages on my computer?
Yes, WorkSpaces Applications offers administrator-configured URL redirection based on URL patterns.
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.
