Skip to content

Commit f3c0042

Browse files
committed
docs: remove outdated AWS IAM section from Terraform introduction
1 parent 91eb727 commit f3c0042

File tree

1 file changed

+0
-25
lines changed

1 file changed

+0
-25
lines changed

Diff for: docs/terraform/introduction.md

-25
Original file line numberDiff line numberDiff line change
@@ -871,28 +871,3 @@ terraform {
871871
}
872872
}
873873
```
874-
875-
## Working With AWS
876-
877-
AWS is on of most popular cloud provider in the world. It has 100s of services from compute to AI. It's most global coverage and has the most data centers around the world. We need to create an AWS account to work with AWS services. We can use the free tier account to get started.
878-
879-
### IAM
880-
881-
When we create an AWS account, it a root user account and it has all the privileges to create, update, and delete resources. But it is not recommended to use the root user account to manage resources, like an Linux Root user account. We should create an IAM user account and use that account to manage resources. We can two kind of access, `Programmatic Access` and `Console Access`. We can use `Programmatic Access` to access AWS services using APIs and SDKs. We can use `Console Access` to access AWS services using the AWS Management Console.
882-
883-
The only ideal use case for root user account is to create an IAM user account and manage billing and other account level settings.
884-
885-
### IAM Policies
886-
887-
IAM policies are used to define permissions for IAM users, groups, and roles. IAM policies are JSON documents that specify the actions, resources, and conditions that are allowed or denied. We can attach policies to IAM users, groups, and roles to grant or restrict access to AWS services and resources.
888-
889-
Some other policies are:
890-
891-
![IAM Policies](https://github.com/user-attachments/assets/98237fdf-8ee8-4fee-bf5b-661dd50ea6ee)
892-
893-
### IAM Groups
894-
895-
IAM groups are used to group IAM users and apply policies to multiple users at once. For example, you can create a group called `developers` and attach a policy that allows access to EC2 instances. Then you can add IAM users to the `developers` group to grant them access to EC2 instances. It great when we have multiple users with the same permissions.
896-
897-
![IAM Groups](https://github.com/user-attachments/assets/be4e6aec-2fd8-4dde-b886-40953d556f1e)
898-

0 commit comments

Comments
 (0)