← CloudCédric MerlinFREN

Cloud galaxy Case 7 of 7

Changing databases without ever accessing them

The problem

Developers sometimes need to run scripts on test and production databases, without having direct access to those databases.

What I did

01

The script goes into Git

The developer pushes the script to a shared code repository.

02

A temporary container

An automation pipeline starts a temporary container, placed in the right network.

03

A badge for production

For production, a team must approve first.

04

Traced separately

The result goes to the monitoring tool, not to the deployment pipeline logs.

Diagram: a script passing through an airlock with no database keyA script is pushed to Git. An automation pipeline starts a temporary container in an airlock, with the door closed. Approval by a team opens the door for production. The container runs the script inside the database network, the result goes to the monitoring tool, the container disappears and the doors close again. The databases never had a key.GitAutomationproduction badgeMonitoring

The result

No standing access to the databases to run a script. Everything is traced.

0 standing access

to the databases to run a script

Stack

  • Automation
  • Temporary containers
  • Federated identity
  • Databases
  • Monitoring