-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial implementation #5
Draft
mcdonnnj
wants to merge
14
commits into
develop
Choose a base branch
from
first-commits
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This configuration will be a Terraform root module and so examples and documentation about using this configuration as a Terraform module are not needed.
It's easier to remove this configuration and build up our new configuration from a mostly clean slate.
Since this is for a single account setup it does not currently need to leverage multiple provider configurations. Also ensure that variable declrations have attributes sorted alphabetically.
These resources are copied from cisagov/cool-accounts/terraform.
These policies are sources from cisagov/cool-accounts/users.
These users are admin-like IAM users that can assume any role in the account and also have access from the AdministratorAccess and job-function/Billing AWS managed policies.
These alerts will go to the account email.
This is based on the configuration in cisagov/cool-accounts/images.
This configuration is copied from cisagov/cool-accounts/shared-services.
Update the README to reflect this project's purpose. The instructions for bootstrapping are pulled from the cisagov/cool-accounts/terraform README and were adapted to suite this project.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🗣 Description
This pull request is the initial implementation for the baseline Terraform that should be applied to an account that will host the CyHy scanning infrastructure.
💭 Motivation and context
Initially I wanted to pull the alerts for IAM/SSO user/group creation or modification that is present in COOL accounts. However, upon thinking about all of the artisinal resources that have been created in the account that hosts the CyHy scanning infrastructure I thought it would be worthwhile to create a baseline Terraform configuration in the same vein as what can be found in cisagov/cool-accounts.
🧪 Testing
In progress.
✅ Pre-approval checklist
to reflect the changes in this PR.