Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Configuring service domains - AWS SimSpace Weaver

Configuring service domains

The presence of launch_apps_per_worker: in a domain configuration indicates that it is a service domain that has service apps. SimSpace Weaver starts and stops service apps for you. When SimSpace Weaver starts and stops an app, the app is considered to have a managed lifecycle . SimSpace Weaver currently supports starting 1 or 2 service apps on each and every worker.

Example of a domain configured to launch 1 service app on each worker
domains: MyServiceDomain: launch_apps_per_worker: count: 1 app_config: package: "s3://weaver-myproject-111122223333-app-zips-us-west-2/PlayerConnectionServiceApp.zip" launch_command: ["PlayerConnectionServiceApp"] required_resource_units: compute: 1 endpoint_config: ingress_ports: - 9000 - 9001
Example of a domain configured to launch 2 service apps on each worker
domains: MyServiceDomain: launch_apps_per_worker: count: 2 app_config: package: "s3://weaver-myproject-111122223333-app-zips-us-west-2/PlayerConnectionServiceApp.zip" launch_command: ["PlayerConnectionServiceApp"] required_resource_units: compute: 1 endpoint_config: ingress_ports: - 9000 - 9001
PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.