103 results found

1. Enhanced Multi-org Email Notification Management

   Hello Product Team,

   I am writing to submit a feature request to address a critical issue we are facing with the management of AWS Root Account email notifications for multiple orgs under our management.

   Issue Summary:
   Currently, when we onboard subsidiaries and assign dedicated AWS Management Account Root email addresses, all notifications are being directed to the same mailbox. This setup results in important notifications being shared across subsidiaries, leading to potential security and privacy concerns. More context on the issue can be found in the related Zendesk ticket: https://doitintl.zendesk.com/agent/tickets/171678

   What is expected :
   We would like a feature that allows us to manage email notifications for each subsidiary independently, ensuring that each organisation receives only the notifications intended for them, without any leakage of information to other subsidiaries.

   Suggested Solutions:
   Implement a way to segregate email notifications at the root level based on the subsidiary.
   Provide a dashboard or tool within the DoIT console that allows for granular control of notification settings for multiple organisations.

   Impact:
   This issue is causing significant concern within our org, as it affects our ability to maintain confidentiality and proper governance across our subsidiaries. It is imperative that we find a solution to manage these notifications effectively and securely.

   Merci :)

   Hello Product Team,

   I am writing to submit a feature request to address a critical issue we are facing with the management of AWS Root Account email notifications for multiple orgs under our management.

   Issue Summary:
   Currently, when we onboard subsidiaries and assign dedicated AWS Management Account Root email addresses, all notifications are being directed to the same mailbox. This setup results in important notifications being shared across subsidiaries, leading to potential security and privacy concerns. More context on the issue can be found in the related Zendesk ticket: https://doitintl.zendesk.com/agent/tickets/171678

   What is expected :
   We would like a feature that… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Discovery  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Alerts for unused BQ tables

   Upon reviewing our usage statistics, we have noticed that there are numerous tables within our BigQuery environment that have been inactive for an extended period, some dating back more than three months. These unused tables are not only occupying valuable storage space but also incurring unnecessary costs for our organization.
   To address this issue proactively, we would like to explore the possibility of setting up a system where your team sends us periodic reminder emails whenever they identify tables that have been inactive for more than three months. This would enable us to review and determine whether these tables are still needed for our business operations. If not, we can take appropriate actions to archive or delete them, thus optimizing our BigQuery usage and reducing costs.

   Upon reviewing our usage statistics, we have noticed that there are numerous tables within our BigQuery environment that have been inactive for an extended period, some dating back more than three months. These unused tables are not only occupying valuable storage space but also incurring unnecessary costs for our organization.
   To address this issue proactively, we would like to explore the possibility of setting up a system where your team sends us periodic reminder emails whenever they identify tables that have been inactive for more than three months. This would enable us to review and determine whether these tables are… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Discovery  ·  0 comments  ·  BigQuery Lens  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Use BQ Lens feature without Advanced company level permissions for DoIT

   I am writing to propose an enhancement to the BQ Lens feature within the DoiT Console. This suggestion stems from our recent experiences and challenges while trying to integrate BQ Lens into our systems at Froomle.

   Current Challenge:
   The BQ Lens feature currently requires granting organization-level permissions to DoiT for data sinking from all projects within an organization. This requirement is not compatible with our company’s security policies, which strictly adhere to the Principle of Least Privileges and Infrastructure as Code (IaC) protocols.

   Proposed Enhancement:
   We propose an alternative approach where clients can manage the data sinking process internally, providing DoiT with access only to specific datasets necessary for the BQ Lens feature. This would allow clients to maintain control over their data and comply with their internal security standards.

   Benefits of the Proposed Enhancement:

   Enhanced Security Compliance: Clients can maintain strict control over data access, aligning with various security frameworks and internal policies.
   Flexibility: Provides a more adaptable solution for clients with different security needs and organizational structures.
   Increased Adoption: This enhancement could encourage wider usage of the BQ Lens feature among clients who are currently hesitant due to security concerns.
   Client Trust: Demonstrates DoiT's commitment to accommodating clients’ security needs, fostering trust and long-term partnerships.
   We believe this enhancement will not only address our current needs but will also be beneficial for other DoiT clients facing similar challenges.

   Thank you for considering this enhancement request. We look forward to a positive response and are willing to provide further details or participate in discussions to expedite this process.

   Best Regards,

   Matthias Verstappen

   I am writing to propose an enhancement to the BQ Lens feature within the DoiT Console. This suggestion stems from our recent experiences and challenges while trying to integrate BQ Lens into our systems at Froomle.

   Current Challenge:
   The BQ Lens feature currently requires granting organization-level permissions to DoiT for data sinking from all projects within an organization. This requirement is not compatible with our company’s security policies, which strictly adhere to the Principle of Least Privileges and Infrastructure as Code (IaC) protocols.

   Proposed Enhancement:
   We propose an alternative approach where clients can manage the data sinking process internally, providing… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  BigQuery Lens  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close