Draft: Add details on proposed AWS SSO with Okta IdP for GitLab AWS Realms.
Why is this change being made?
This change is to document processes to be followed as https://gitlab.com/gitlab-com/gl-security/zero-trust/okta/-/issues/218 is implemented to provide a scalable way to provide administrative access to the GitLab AWS organization.
- Proposing
GitLab AWS Realms
as the MECEFU reference for all AWS accounts related to the organization ofGitLab AWS Master
to avoid confusion with other "Infrastructure" related related resources.
@mjozenazemian @cmccarty @hasharma For review and additions that are relevant to the AWS organization work recently reassigned.
cc @jeffersonmartin @pkaldis @dawsmith
References gitlab-com/sandbox-cloud/issue-tracking#17.
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what -
Assign this change to the correct DRI - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
-
If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping(this requirement has been removed pending identification of a new DRI for the handbook)@gl-static-site-editor
in a comment for a review and merge. For example changes to.gitlab-ci.yml
, JavaScript/CSS/Ruby code or the layout files.
Edited by Antony Saba