How to Run and Manage Chrome on AWS

“Run Chrome on AWS” can mean two different things: use Chrome on your own computer to access an AWS service, or run a browser inside a remote AWS session. The setup depends on which one you mean.

To access a remote AWS desktop or streamed application: Chrome can be the local browser client. Check that the specific AWS service and your endpoint platform support it.
To run a browser remotely: Amazon WorkSpaces Applications is AWS’s managed application-streaming service. AWS documents a Linux Chromium example for that service.
To install Google Chrome directly on a general-purpose EC2 instance: the sources cited here do not establish current install, update, or hardening steps. Don’t treat the WorkSpaces Applications Chromium example as an EC2 installation guide.

This guide focuses on those documented options and their boundaries. It does not provide EC2 installation commands because the necessary current Chrome and AWS procedures are not established by the sources here.

1. Choose where Chrome should run

Need	Browser location	Relevant route
Open an AWS remote desktop or streamed app	Chrome runs on your computer and displays the remote session	Use the browser access option for that AWS service, if enabled and supported
Provide users a remote browser or application	The browser executable runs in a streamed session	Consider WorkSpaces Applications; AWS documents a Linux Chromium example
Run Chrome as a browser process on your own cloud VM	Chrome runs on a self-managed host, such as EC2	Use current official Chrome and AWS instructions for installation, updates, and security; this guide does not substantiate those steps

A browser client and a remote browser are not interchangeable. With browser access, Chrome is on the user’s device; the remote desktop or application is elsewhere. With application streaming, the browser process runs in the streamed environment and the user sees its session.

2. Use Chrome as the client for an AWS remote session

For Amazon WorkSpaces Applications, AWS documents HTML5 browser access from desktop computers and lists Google Chrome among supported browsers. Its documentation says the service supports the latest three major versions of supported browsers; verify the current requirements for your service and platform before rollout. AWS WorkSpaces Applications browser requirements

Confirm which AWS service hosts the desktop or streamed application. WorkSpaces Applications, Amazon WorkSpaces, and WorkSpaces Secure Browser have separate requirements.
Ask the service administrator whether browser access is enabled and obtain the organization’s sign-in or portal URL.
Open that URL in a supported, up-to-date Chrome version and sign in using the organization’s configured authentication.
If the session fails, check the service’s current browser and endpoint requirements, administrator settings, and network access. See Troubleshooting.

For Amazon WorkSpaces Web Access, current AWS documentation describes access to DCV-based Windows and Linux WorkSpaces and lists Chrome, Edge, Firefox, and Safari on supported desktop platforms, subject to version and platform requirements. The administrator must enable web access. This is a separate service route from WorkSpaces Applications. AWS WorkSpaces Web Access requirements

3. Run a browser in a managed streamed session

AWS describes WorkSpaces Applications as a managed application-streaming service: AWS manages the hosting resources and scales automatically. Its documentation includes an example that launches Chromium on Linux from a script, registers the script as an application with Image Assistant, and continues with image, fleet, and stack creation. This is a service-specific example, not instructions for installing Google Chrome on EC2. Amazon WorkSpaces Applications · AWS session-context example

Review AWS’s current WorkSpaces Applications prerequisites and decide whether a streamed application session fits your users’ needs.
Follow the current AWS Linux Chromium session-context example. It demonstrates launching Chromium with a script and registering that script through Image Assistant.
Complete the documented image, fleet, and stack setup for your environment, then validate the resulting session with representative users and pages.
Keep session context free of sensitive information. AWS cautions that session context is visible to the user; validate its contents before relying on it.
Document who maintains the image and how you will validate changes to the browser session as you update the environment.

The AWS example establishes a way to launch Chromium in this service. It does not establish that every Chrome-specific feature, extension, policy, or Google Chrome binary is available in that configuration. Check the applicable browser and service documentation for those requirements.

4. Decide where web content should render

In a streamed session, browser content normally runs in the remote environment. WorkSpaces Applications also documents host-to-client URL redirection: administrators configure URL patterns so matching destinations open in the user’s local browser. AWS says this can reduce latency and server-side resource use for resource-intensive web content. It is an administrator-configured option, not a blanket redirect for every URL. AWS URL redirection documentation

Before enabling a URL pattern, determine which destinations should stay in the remote session and which should open locally. Consider authentication, access to internal sites, and whether users’ local browsers are permitted to reach those destinations. Test the configured patterns with the applications and links users actually need.

5. Configure camera and microphone needs

For WorkSpaces Applications streaming sessions, AWS documents local webcam and microphone redirection through Chromium-based browsers, including Chrome and Edge. Users need to allow browser camera and microphone access, and the administrator may need to configure the service. Availability is not guaranteed for every device or setup. AWS video and audio guidance · AWS real-time audio-video configuration

Connect using a supported Chromium-based browser.
Allow camera and microphone access for the WorkSpaces Applications site when Chrome prompts you.
Enable the camera and microphone in the streaming session toolbar.
If the controls are absent, ask the administrator to verify service configuration and check that the browser supports the feature.

When several cameras or microphones are available, the selected device may need to be changed in browser settings. AWS notes that changing devices can require clearing the browser’s settings for the service site and starting a new session.

6. Chrome on EC2: what to verify before proceeding

“Chrome on EC2” specifically means installing and operating a browser on a self-managed compute host. That requires current instructions for the chosen operating system, Chrome distribution, package updates, display or headless operation, and security configuration. The research available for this article does not verify those details, so it would be misleading to provide copy-and-run installation commands.

Before implementing that architecture, consult current official Google Chrome and AWS documentation for your operating system and workload. Decide how the browser will be displayed or controlled, how it will receive security updates, what network access it needs, and how credentials and user data will be handled. If you need a managed streamed browser session, evaluate the WorkSpaces Applications route above instead.

7. Troubleshooting

Symptom	Likely cause	What to check
The AWS session page will not open or reports an unsupported browser	Browser version, endpoint platform, or service access is outside the current requirements	Check the exact service’s current browser and platform requirements; update Chrome if required.
Sign-in works but no streamed session starts	Browser access may not be enabled, or the portal/session configuration may be incomplete	Ask the administrator to verify access and service configuration. For WorkSpaces Web Access, AWS requires an administrator to enable it.
The remote session loads but a site is slow	Content is being rendered in the remote session, or the network/session has constraints	Check session and network conditions. For WorkSpaces Applications, ask whether administrator-configured URL redirection is appropriate for specific resource-intensive destinations.
A destination opens locally when it should stay remote	A configured URL pattern matches it	Review the administrator’s host-to-client URL patterns and test the adjusted rules.
Camera or microphone controls are missing	Browser permissions, browser capability, device availability, or administrator configuration	Use a supported Chromium-based browser, allow site permissions, verify local devices, and ask the administrator to check service configuration.
A different webcam or microphone keeps being selected	The browser may retain the site’s previous device choice	Set the intended default device in browser settings; AWS documents clearing site settings and starting a new session when changing devices in WorkSpaces Applications.
Instructions for Chromium do not work on EC2	The WorkSpaces Applications example is being applied to a different AWS architecture	Use current official instructions for the EC2 operating system and Chrome distribution. The streamed-session example is not an EC2 installation procedure.

8. Performance, reliability, and operating cost

Rendering location: local browser access and remote browser execution put browser work in different places. Choose based on the application’s session and data requirements.
Redirected content: AWS says host-to-client URL redirection can reduce latency and server-side resource use for resource-intensive content. Results depend on the destination and user connection; AWS’s statement is not a benchmark.
Browser versions: AWS browser support requirements can change. Recheck supported versions and platforms during rollout and maintenance.
Reliability: validate sign-in, session launch, required sites, and any camera, microphone, or URL redirection behavior in the target environment. The cited material does not provide an uptime figure or workload benchmark.
Cost: this research does not establish current AWS prices for a particular region, session configuration, or usage pattern. Consult current AWS pricing for the selected service and estimate based on your architecture and expected use.

Or skip the browser setup

If the job is to capture a website as an image or PDF, ScreenshotNeo provides a screenshot API and MCP server. One GET request returns a screenshot or PDF; there is no Chrome session to configure for this capture workflow. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Cookie banners, popups, and chat widgets are removed before the shot.
Bot checks, blank pages, and failed loads are never billed.
An MCP server lets AI agents use the take_screenshot, get_page_info, and capture_pdf tools.
The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000.

FAQ

Is Chrome on my computer the same as Chrome running on AWS?

No. In browser access, Chrome runs locally and connects to an AWS session. In a streamed browser setup, the browser executable runs in the remote environment.

Does the AWS Chromium example install Google Chrome on EC2?

No. It is an AWS WorkSpaces Applications example for launching Chromium in a Linux streamed session.

Can every URL open in my local browser from a streamed session?

Not by default. WorkSpaces Applications URL redirection uses administrator-configured URL patterns.

Can I use a webcam in a WorkSpaces Applications session?

AWS documents webcam and microphone redirection with Chromium-based browsers, subject to browser permissions and administrator configuration.