Pre-work Checklist: DevOps-Security-Member: Mihir Modi

mihirmodi2561 commented 2 months ago

Prerequisite

We are looking forward to having you on our team. Please ensure you have prior experience with the HfLA website team before contributing to our repository.

Overview

As a new member on the HfLA devops-security team, fill in the following fields as you complete each onboarding item.

Special Notes

Keep this issue open until you've completed all steps, including learning to provide updates for longer tasks.
Normally, handle one issue at a time, but this one is an exception as it teaches how to manage multiple tasks.
Work on action items sequentially, but proceed if possible. For example, set up your dev environment without waiting for the weekly meeting.

Action Items

[x] Before starting to work on the below instructions, make sure to join the #ops Slack Channel. And are a member of devops-security repository.
[x] Self-assign this issue (gear in right side panel).
[x] Add this issue to the Project Board under the Projects section (gear in right side panel).
[x] Attend weekly team meeting, Wednesdays 6-8pm PST.
- [x] Note: There are no meetings on the 1st-7th of every month.
[x] Complete the steps in Creating a personal AWS account and Login as root user & setup MFA.
[x] Read and follow the instructions in Setting up IAM and AWS CLI for:
- [x] Creating an IAM User
- [x] Creating an IAM Group
- [x] Attaching IAM user to IAM Group
- [x] Providing AdministratorAccess policy to IAM group
- [x] Log in as the newly created user instead of continuing to log in as the root user (it is not recommended to login with root access).
- [x] Generating user access keys
[x] Complete the instructions in AWS Documentation and choose your operating system to install AWS CLI.
[x] Complete the instruction in AWS Documentation to setup the AWS CLI.
[x] Read follow the instructions in Creating a backend state.
[x] Install Terraform locally by following the instructions of the installation guide mentioned in Installing Terraform
[x] Install Terraform Docs locally by following the instructions of the installation guide mentioned in Installing Terraform docs
[x] Complete the instructions in Clone the repository
[x] Submit a new request to create new AWS user account and then self-assign this issue.
[x] Create a new branch from main by executing the command
```
git checkout -b issue-number-add-new-iam-user
```

[x] Navigate to the aws-user.tf file and add your user information and follow the below template.


module "iam_user_testiamuser" {
source = "./modules/aws-users"

user_name = "testiamuser"
user_tags = {
  "Project"      = "devops-security"
  "Access Level" = "1"
}
user_groups = ["read-only-group"]
}

[x] In your code editor navigate to terraform directory. cd terraform
[x] Execute the command terraform init to initialize terraform in the directory. Address any failures that arise (if any).
[x] Execute the command terraform plan this will output a plan replicating the same IAM resources as the devops security account. Address any failures that arise (if any).
[x] Then execute the command terraform apply this will create all of the resources that are currently managed by Devops Security. All of the resources created here incur zero cost except for the Dynamo DB installation, which should remain in the free tier.
- [ ] If you have cost concerns, Run a Terraform Destroy to take down all of the resources you created (don't worry, you can recreate them just as quickly).
[x] Once you have tested your changes, stage them in git with
- [x] git status command.
- [x] then git add path/to/file (you can copy from above output for the file path).
[x] Commit the changes by executing git commit -m "briefly describing the changes".
[ ] Push the changes with git push --set-upstream origin name-of-branch

mihirmodi2561 commented 2 months ago

Done prerequisite

ExperimentsInHonesty commented 2 months ago

@mihirmodi2561 You need to

[ ] edit the title of this issue to add your name
[ ] add it to the CoP: DevOps: Project Board
[ ] move it to the Questions column
[ ] add the 'ready for CoP Lead` label

mihirmodi2561 commented 2 months ago

I completed the first three tasks but was unable to complete 4th task.

ExperimentsInHonesty commented 1 month ago

@mihirmodi2561 we are waiting for you to come back to approve your PR. Are you coming back? If you do come back, please put this in the questions column, with a ready for CoP lead label

hackforla / devops-security