Responsibilities and recovery
Know the task on each side of the account boundary.
Define responsibilities for installation, support, backup and emergency access in your own AWS account.
Divide the tasks for your installation
See your tasks alongside Tomstok’s tasks. Upcoming areas describe planned responsibilities. The sections below explain the boundaries; software versions and support access are explained further on the pages about updates and access.
| Area | Your business | Tomstok |
|---|---|---|
| The data foundation – the part that holds your data Upcoming | You review and carry out the creation of and changes to the data foundation yourselves. | Installs the application with the least possible privileges and without access to your data. |
| Software version | You must be able to choose the version and approve the timing. | Is designed so that a new version is only installed after you have approved it. |
| Support access | You must be able to approve the task and end date and stop access immediately. | Is designed so that the support employee activates access with a reason every time. |
| Backup and recovery Upcoming | You choose the policy and carry out recovery in your account. | Provides documented defaults and tools. |
| Emergency access Upcoming | You prepare emergency users and an emergency user pool in your account. | The emergency route is planned to work without Tomstok’s central administration. |
| AI budget | You define budgets, alerts and any stop actions in your account. | Sets no spending cap of its own – you control usage. |
You carry out changes to the data foundation
The plan is for a separate foundation for your data, where you review and execute its creation and any necessary changes yourselves. A software version requiring such a change should only be installable after you have completed it.
The plan is for Tomstok’s central administration to have no ability to create, change or delete the data foundation, and for its installation access to give no access to your business data.
Support requires your limited approval
You must be able to approve Tomstok support access to your environment, limit the task and set an end date. The Tomstok employee must activate access with a reason, and you must be able to stop it locally.
Support access is separate from Tomstok’s central administration. When support access expires, it does not revoke central administration’s standing administrator access. The plan remains to keep central administration’s access separate from your data and data foundation.
Explore the access boundariesAgree backup, keys and recovery for your installation
Backup, retention, targets for data loss and restoration time (RPO/RTO), and recovery tests must be agreed and documented for your installation. You choose the policy and carry out recovery in your AWS account; Tomstok must provide documented defaults and tools for the process.
Key responsibilities and rotation must also be agreed and documented: you are responsible for keys in your operational environment, while Tomstok is responsible for central administration’s keys. Recovery tests must cover the necessary keys and outages of central administration or your identity provider. Keeping data when the application is removed does not in itself constitute a backup.
Prepare a limited emergency route
Planned emergency access requires prepared emergency users, an available emergency user pool in your AWS account and a network connection. It must work when the primary login fails.
Access is limited to approved recovery actions: reading sanitised login status, fetching keys again from the already approved identity provider and clearing unfinished login attempts. It does not grant general access to business data or administrator privileges.
You choose the AI budget
You manage AI usage in your AWS account yourselves with AWS’s own quota and budget tools. Tomstok has no spending cap of its own on AI usage.
You define budgets, alerts and any stop actions for your account according to your own needs.
See Tomstok with your products in mind.
Talk to us about your product range and production requirements.