View and Download Peer Insights About
What Your Peers Are Saying About
Project Management Manager
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?
IT Manager
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.
See Full Discussion
20 Mar 20251.8k Views1 Comment
Data and Analytics Manager
Currently, in my organization, we have BI products built on top of a data warehouse implemented using PostgreSQL, following a snowflake schema architecture (fact and dimension tables). This structure has become extremely complex and hard to maintain. Updates are very costly, and I’m heavily dependent on a single person to keep it running. I’m considering moving to a cloud-based environment, such as AWS Redshift or Google BigQuery. Based on your experience, would migrating to one of these platforms help me move away from this complex snowflake architecture? Also, between the two solutions (AWS Redshift and Google BigQuery), which one would you recommend and why?
Principal Software Engineer, Data Engineering
It is better to analyze from the problem perspective. Whether you need a Snowflake schema, star schema, or one big table, it needs to be analyzed based on the user requirements, data volume, query patterns, business asks, latency requirements, etc. Changing the database/platforms might not solve the issue if you need a sustainable solution.
See Full Discussion
3 May 20251.9k Views3 Comments