| Staging Environment | AWS Staging Environment | - Cloud Console access is restricted only to authorized persons
- SSH access is protected by keys and MFA
- Database access is possible only from the internal network
- Kubernetes access is possible only from the internal network
- Only minimal permissions are granted
- No unauthorized access
| AWS Stage Separated AWS Account for the Stage resources. Permissions - StageAdmins : Can list, create, delete, modify AWS resources.
- StageFTT : Can list, create, delete, modify AWS resources relted to Atlassian Forge Apps.
- StageContainerImageAdmins : Can list, create, delete, modify (in snapshot repositories) Docker images.
- StageContainerImageReaders : Can list Docker images.
- StageSupport : an list, create, delete, modify Kubernetes resources and list Docker images.
- InfraBackup : Can list, create, delete, modify items in the Backup S3 Bucket.
- StageEticmaTechUsers : Can list, create, delete, modify ETICMA app related resources w/o MFA.
- StageAdmins
3 DevOps Engineer
3 Infrastructure Engineer ( 3 Contractor ) - StageFTT
3 Software Developer
1 Product Owner - StageContainerImageAdmins
1 Technical Account - StageContainerImageReaders
1 Technical Account - StageSupport
3 Software Developer - InfraBackup
1 Technical Account - StageEticmaTechUsers
1 Technical Account AWS Stage Bastion EC2 instance to access the Stage internal network and databases. Permissions - Root : Can administer Linux OS.
- User : Can log in and access the internal network of the Staging environment.
- Root
2 DevOps Engineer
3 Infrastructure Engineer ( 3 Contractor ) - User
1 DevOps Engineer
10 Software Developer
2 Test Engineer
1 Support Agent |
