You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular, one of the most common problems that on-prem software addresses is to eliminate any need for the software provider to ever have access to the customer's data.
Is this problem solved by AWS SaaS Boost? Does this provide a way to separate the container's software from the customer's data (for example, by mimicking a file system whereby the vendor provides the image that runs on Windows in %PROGRAMFILES%, and configures it to use a separate, customer-owned drive (mounted, for example, on %APPDATA%), which only the customer, and not the vendor, has access to?
Regardless of whether this capability exists or does not exist, data security is such a common barrier to enterprise-to-saas migration that it should be addressed in the documentation
This discussion was converted from issue #17 on May 18, 2021 15:59.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The user manual (https://github.com/awslabs/aws-saas-boost/blob/main/docs/user-guide.md) would be more complete if it described options or limitations relating to data security.
In particular, one of the most common problems that on-prem software addresses is to eliminate any need for the software provider to ever have access to the customer's data.
Is this problem solved by AWS SaaS Boost? Does this provide a way to separate the container's software from the customer's data (for example, by mimicking a file system whereby the vendor provides the image that runs on Windows in %PROGRAMFILES%, and configures it to use a separate, customer-owned drive (mounted, for example, on %APPDATA%), which only the customer, and not the vendor, has access to?
Regardless of whether this capability exists or does not exist, data security is such a common barrier to enterprise-to-saas migration that it should be addressed in the documentation
This is a 📕 documentation issue
Beta Was this translation helpful? Give feedback.
All reactions