In the process of migrating Legacy Applications to an AWS cloud instance. Our Legacy system contains sensitive private data of users. AWS engineers are saying they need access to our data early and they have not built out the environment yet. I found online that access to the data is needed once in the TEST and VALIDATION phase of the project. Does the AWS cloud engineer need access to my real data to figure out how to install databases and applications even if they haven't built out the future environment yet?
Generally, AWS engineers do not need access to real data to figure out how to install databases and applications. you can setup a process to ensure strong security measures are followed. Few Recommendations: 1. Use sample or dummy data to set up and test the environment. This allows AWS engineers to configure and troubleshoot without needing access to sensitive information. 2. If real data must be used early in the process, consider data masking techniques to anonymize sensitive information. 3. Discuss your concerns with the AWS engineers and establish clear protocols for data access and security.
On-premises computing can offer businesses more control over their data and applications.40%
On-premises computing can be more secure than cloud computing, since data is stored on-site.39%
On-premises computing can be more reliable than cloud computing, since it is not subject to outages.6%
All of the above.13%
View Results
I am looking for an EDI parser which is a light weight, SaaS and can be run as serverless (recommended) to perform EDI transaction (834, 837 etc) HIPAA validation. So far, I could find Edifecs, ediFabric, Stedi and IBM ITX in the market. Can anyone provide their experience or recommendation on different tools on the market that we should evaluate?
Generally, AWS engineers do not need access to real data to figure out how to install databases and applications. you can setup a process to ensure strong security measures are followed.
Few Recommendations:
1. Use sample or dummy data to set up and test the environment. This allows AWS engineers to configure and troubleshoot without needing access to sensitive information.
2. If real data must be used early in the process, consider data masking techniques to anonymize sensitive information.
3. Discuss your concerns with the AWS engineers and establish clear protocols for data access and security.