Security best practices for SimSpace Weaver - AWS SimSpace Weaver

Security best practices for SimSpace Weaver

This section describes security best practices that are specific to SimSpace Weaver. To learn more about security best practices in AWS, see Best Practices for Security, Identity, and Compliance.

Encrypt communications between your apps and their clients

SimSpace Weaver doesn't manage communications between your apps and their clients. You should implement some form of authentication and encryption for client sessions.

Periodically backup your simulation state

SimSpace Weaver doesn't save your simulation state. Simulations that are stopped (as a result of an API call, console option, or system crash) do not save their state and have no inherent way to recover them. Stopped simulations cannot be restarted. The only way to perform the equivalent of a restart is to recreate your simulation using the same configuration and data. You can use backups of your simulation state to initialize the new simulation. AWS offers highly reliable and available cloud storage and database services that you can use to save your simulation state.

Maintain your apps and SDKs

Maintain your apps, local installations of the AWS software development kits (SDKs), and the SimSpace Weaver app SDK. You can download and install new versions of the AWS SDKs. Test new versions of the SimSpace Weaver app SDK with non-production app builds to ensure that your apps continue to run as expected. You cannot update your apps in a running simulation. To update your apps:

  1. Update and test the app code locally (or in a test environment).

  2. Stop changing your simulation state and save it (if necessary).

  3. Stop your simulation (once stopped, it cannot be restarted).

  4. Delete your simulation (stopped simulations that aren't deleted count towards your service limits).

  5. Recreate your simulation with the same configuration and the updated app code.

  6. Initialize your simulation using saved state data (if available).

  7. Start your new simulation.


A new simulation created with the same configuration is separate from the old simulation. It will have a new simulation ID and send logs to a new log stream in Amazon CloudWatch.