Create Identities
As the operator is very protective, it is advisable to create additional identities with fewer rights.
Usually it makes sense to divide identities by teams/projects/areas.
In this example, we will divide the identities into teams.
For the sake of simplicity, we will continue to work on a terraforming project here.
In “real life” the configuration would be divided into several projects.
We will be creating identities for two teams.
- A_Team manages applications and is therefore a development team.
- Search_Team this manages the big data database and determines which team can access which data.
We will create three secrets:
- two managed by A_Team
- one managed by Search_Team, but with read access from A_Team
A_Team will create a service:
- with read-only access to the secrets
For this purpose, the team manages different iduvidual accesses to the Big Data application.
Create team identity
A-Team Identity:
Search_Team Identity:
Usually it makes sense to divide identities by teams/projects/areas.
In this example, we will divide the identities into teams.
For the sake of simplicity, we will continue to work with a single project folder.
In “real life” the configuration would be divided into several parts and could also be combined with terraform projects.
We will be creating identities for two teams.
- A_Team manages applications and is therefore a development team.
- Search_Team this manages the big data database and determines which team can access which data.
We will create three secrets:
- two managed by A_Team
- one managed by Search_Team, but with read access from A_Team
A_Team will create a service:
- with read-only access to the secrets
For this purpose, the team manages different iduvidual accesses to the Big Data application.
A-Team:
Search_Team: