Slider 1 mini Slider 2 mini

Sunday, 21 June 2026

Filled under:

Dhirendra

 BBS right for Mongo  - to scrap

+

AC22 - change ownership & how to rotate password


Upcoming

Vulnerability - Python, Azure CLI and __

Change the name of EPIC - make just "IDB migration to secure sharepoint"


to do

- Maintianance scope to scrap and

Other epic refinement

Posted By Nikhil06:02

Pitch for recording (Sunday)

Filled under:

90-second memory cue

  1. Intro
    Nikhil Kotak — Database SRE — Scrum Master for Emerging DB.

  2. Proud achievement
    PostgreSQL BCM automation.
    Manual checks → repeatable automation.
    Supported BCM BigRock events.
    Reduced manual effort by around 95%.
    Improved reliability, auditability and confidence.

  3. What motivates me at UBS
    Scale and impact of work.
    Small reliability improvements protect important business services.
    Opportunity to work with engineers, POs, ROs and management.
    Technical depth + delivery ownership.

  4. Favourite app
    LinkedIn.
    Learning, sharing, technology community, industry trends.
    Supports my growth mindset.

  5. Closing
    Proud to contribute through reliability, automation, collaboration and continuous improvement.


##################################################################################

 

Hi, my name is Nikhil Kotak. I currently work as a Site Reliability Engineer for databases, and I also support the Emerging Database team as Scrum Master.

One achievement I am especially proud of is my contribution to PostgreSQL reliability since PostgreSQL was introduced as a strategic database platform within the bank. During that phase, I also conducted brown bag sessions with stakeholders across APAC and EMEA to build awareness, confidence and alignment around the platform.

I then independently designed and developed PostgreSQL Business Continuity Management automation. This converted manual validation, high-availability checks, risk controls and evidence collection into a repeatable automated process. The automation supported multiple BCM BigRock events across Oracle and PostgreSQL databases and helped reduce manual effort by around 95%. I am proud of this because it improved reliability, consistency, auditability and confidence during critical continuity events.

I have also been involved in ML and AI-led automation initiatives, where we used intelligent automation to reduce repetitive manual ticket resolution and improve operational efficiency. This helped reduce manual resolution effort by around 22% over the past year.

What motivates and inspires me at UBS is the scale, trust and impact of the work. Having been with UBS for more than nine years, I have seen how reliability, discipline and continuous improvement directly support important business services.

In database reliability, improvements can protect important business services.. I am inspired by the opportunity to work with engineers, Product Owners, Reliability Owners and stakeholders, where I can combine technical depth, automation and delivery ownership to create reliable outcomes.

My favourite app is LinkedIn. For me, it is more than a networking app. It helps me learn from the technology community, share knowledge, follow industry trends and stay connected with experts across databases, cloud and AI.

Overall, I am proud to contribute through reliability, automation, collaboration and continuous improvement.

Posted By Nikhil03:51

Saturday, 20 June 2026

Filled under:

 My role sits

I work across

Over the recent period,

One of my key individual contributions has been PostgreSQL Business Continuity Management

.. contribution n numbers

Another important contribution has been in Oracle and LGTM onboarding

 s Scrum Master for the Emerging Database team, my contribution is not limited to meeting facilitation. I bring technical understanding into delivery discussions


From a Principles and Behaviors perspective, I try to demonstrate collaboration, growth, innovation and transformation in practical ways. I collaborate with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders to translate technical topics into clear actions. I support growth through certifications, technical blogging, knowledge sharing and mentoring new joiners. I innovate by converting manual, repetitive and evidence-heavy activities into automation. I support transformation by improving transparency, structured tracking and early risk visibility.


I have also been recognized by Oracle through its ACE community program for my technical contributions. This gives me exposure to Oracle product direction, new features and wider industry practices, which I can bring back into the organization.


Overall, I believe my impact goes beyond completing assigned tasks. I have taken ownership of complex and evolving areas, delivered measurable reliability improvements, supported team delivery, and contributed to better ways of working. These are the areas where I believe I am already demonstrating the ownership, maturity and wider influence expected at the target level.


--------------



“Reduced manual effort by around 95%, while improving consistency, auditability and confidence during critical events.”


_----------------------



Hi, my name is [Your Name]. I work as a Database Reliability Engineer / Site Reliability Engineer, and I also perform Scrum Master responsibilities for the Emerging Database team.

My role sits at the intersection of database reliability, operational resilience, automation and delivery coordination. I work across enterprise database technologies including Oracle, PostgreSQL and Emerging Database platforms, supporting production stability, business continuity readiness, backup governance, patching, automation and operational reporting.

Over the recent period, I have taken ownership of responsibilities beyond my core role, particularly in PostgreSQL Site Reliability Engineering and Scrum Master activities for the Emerging Database team. These areas require technical judgement, ownership, stakeholder coordination and the ability to bring structure to evolving topics.

One of my key individual contributions has been PostgreSQL Business Continuity Management automation. When PostgreSQL was introduced into the bank environment, I built strong engineering knowledge in this area and used that experience to design and develop automation for continuity events.

This work converted manual high availability checks, validation steps, risk controls and evidence requirements into a repeatable and consistent process. The automation has supported more than 7 business continuity events across a large database estate, including 200+ Oracle databases and 40+ PostgreSQL databases. It has reduced manual effort by around 95%, while improving consistency, auditability and confidence during critical events.

Another important area I have contributed to is improving operational visibility and observability across the database estate. My focus has been on making issues easier to detect, track and act upon by converting fragmented checks and manual follow-ups into more structured reporting and automation. This improves transparency for engineers and stakeholders, supports faster decision-making, and creates a stronger foundation for future enhancements around proactive monitoring, trend analysis and reliability insights.

I have also contributed to AI and ML-driven initiatives where automation was used to improve operational efficiency. By applying automation and intelligence-driven approaches to recurring support patterns, we reduced manual ticket resolution effort by around 22% over the past year. This reflects my focus on not just resolving issues, but improving the way issues are identified, routed and handled over time.

As Scrum Master for the Emerging Database team, my contribution is not limited to meeting facilitation. I bring technical understanding into delivery discussions, help clarify ambiguous work, surface blockers early, and keep the team focused on outcomes and accountability. I see this as an important bridge between engineering detail and business priorities.

From a Principles and Behaviors perspective, I try to demonstrate collaboration, growth, innovation and transformation in practical ways. I collaborate with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders to translate technical topics into clear actions. I support growth through certifications, technical blogging, knowledge sharing and mentoring new joiners. I innovate by converting manual, repetitive and evidence-heavy activities into automation. I support transformation by improving transparency, structured tracking and early risk visibility.

I have also been recognized by Oracle through its ACE community program for my technical contributions. This gives me exposure to Oracle product direction, new features and wider industry practices, which I can bring back into the organization.

Overall, I believe my impact goes beyond completing assigned tasks. I have taken ownership of complex and evolving areas, delivered measurable reliability improvements, improved observability and operational visibility, supported team delivery, and contributed to better ways of working. These are the areas where I believe I am already demonstrating the ownership, maturity and wider influence expected at the target level.

Posted By Nikhil05:55
Filled under:

 

Hi, my name is [Your Name]. I am currently working as a Database Reliability Engineer / Site Reliability Engineer, with additional responsibilities as Scrum Master for the Emerging Database team.

My role is focused on database reliability, operational resilience, automation and platform stability. I work across enterprise database technologies including Oracle, PostgreSQL and Emerging Database platforms. In this role, I contribute to production reliability, business continuity readiness, database automation, patching support, backup governance, operational reporting and cross-team coordination.

Over the last period, I have also stepped into wider responsibilities in two important areas: PostgreSQL Site Reliability Engineering and Scrum Master responsibilities for the Emerging Database team. These areas require technical judgement, ownership, stakeholder alignment and the ability to bring structure where topics are still evolving.

One of my key individual contributions has been PostgreSQL Business Continuity Management automation. I designed and developed this using my own PostgreSQL engineering knowledge, built from the time PostgreSQL was introduced within the bank environment. I converted high availability checks, validation steps, operational risks and evidence requirements into repeatable automation.

This automation has supported more than 7 business continuity events, covering 200+ Oracle databases and 40+ PostgreSQL databases, and has reduced manual effort by around 95%. More importantly, it has improved consistency, auditability and confidence during critical continuity events.

Another important area I contributed to is Oracle / LGTM onboarding. I analysed blockers related to standard ID and certificates, identified recurring host-level issues and helped convert fragmented failures into structured remediation actions. This helped move the work from reactive troubleshooting to more systemic resolution.

As Scrum Master for the Emerging Database team, my contribution goes beyond routine facilitation. I bring technical understanding into delivery discussions, help clarify ambiguous work, surface blockers early, and keep focus on outcomes and accountability. I see this as an important bridge between engineering detail and business priorities.

From a Principles & Behaviors perspective, I try to demonstrate collaboration, growth, innovation and transformation in practical ways. I collaborate with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders to translate technical topics into clear actions and decisions. I support growth through certifications, technical blogging, knowledge sharing and by acting as a buddy or mentor for new joiners. I innovate by converting manual, repetitive and evidence-heavy activities into automation. I help transform the way we work by improving transparency, structured tracking and early risk visibility.

I have also been recognized by Oracle through its community / ACE program for my technical contributions. This gives me exposure to Oracle product direction, new features and industry practices, which I can bring back into the organization.

Overall, I believe my impact is not limited to completing assigned tasks. I have taken ownership of complex and evolving areas, delivered measurable reliability improvements, supported team delivery and contributed to better ways of working. These are the areas where I believe I am already demonstrating the ownership, maturity and wider influence expected at the target rank.

Posted By Nikhil04:04

Friday, 19 June 2026

Filled under:

 

Based on the refined input, you can restructure the mail like this so it is clearer and action-oriented.


Subject: Action Required: Cosmos DB CMK Key Vault Access Update – Remediation Options

Dear User,

We are notifying you of an important update regarding encryption key management for your Cosmos DB account(s) using Customer-Managed Keys (CMK) within the UBS Prod tenant.

As per the latest Azure changes, the way Azure Key Vaults are accessed by Cosmos DB is changing. This impacts Cosmos DB accounts using CMK, regardless of whether the Key Vault is centrally managed or maintained within your own subscription.

To avoid service impact, the required remediation must be completed by December 2026.

Impact if no action is taken:
If the required action is not completed before the deadline, the affected Cosmos DB account may enter a failure state and become inaccessible.

Available Remediation Options

Please review and choose one of the following options based on your application setup and ownership model:

Option A: Create a new Key Vault and update Cosmos DB with the new Key Vault URI
This option allows you to continue using CMK by moving the encryption key to a Key Vault managed within your subscription and updating the Cosmos DB configuration with the new keyVaultKeyUri.

High-level steps:

  1. Create a new Key Vault with:

    • Soft Delete enabled
    • Purge Protection enabled
    • Valid RSA key of minimum 3072 bits
  2. Grant Cosmos DB access to the new Key Vault:

    • Assign permissions to the Cosmos DB managed identity
    • Required permissions: get, wrapKey, unwrapKey
    • Alternatively, assign the RBAC role: Key Vault Crypto Service Encryption User
  3. Update Cosmos DB to use the new Key Vault key URI.

  4. Allow Cosmos DB to complete the encryption key transition.

  5. Validate:

    • Read/write operations
    • customerManagedKeyStatus
    • Alerts/logs

Option B: Create a new Cosmos DB account with Microsoft-Managed Keys (MMK) and migrate data
Create a new Cosmos DB account configured with Microsoft-Managed Keys and migrate data from the existing CMK-enabled account using container copy.

Option C: Create a new Cosmos DB account using Point-in-Time Restore with MMK configuration
Create a new Cosmos DB account using Point-in-Time Restore and configure the restored account with Microsoft-Managed Keys.

Required Action

Please confirm which remediation option you would like to proceed with for your Cosmos DB account(s). Once confirmed, the Emerging Databases team can guide you on the next steps and required coordination.

For any questions or assistance, please reach out to DL-TS-HS-DB-EMERGINGDB-ENG.

Thanks & Regards,
Emerging Databases Team

Posted By Nikhil03:57
Filled under:

 

Subject: Q3 Objectives Alignment – Emerging DB

Hi Team,

Setting up this call to align on the Q3 objectives for Emerging DB, review key priorities, clarify scope/ownership, and identify any dependencies or blockers early.

Agenda:

  • Review proposed Q3 objectives
  • Align on priorities and expected outcomes
  • Identify dependencies, risks, and ownership
  • Confirm next steps for planning/tracking

Thanks,
Nikhil

Posted By Nikhil03:10
Filled under:

 

Posted By Nikhil00:40