Hackforge Academy

Explanation

AWS IAM stands for Identity and Access Management. It controls who can access AWS resources and what actions they are allowed to perform.

Code:

IAM
 ├── Users
 ├── Groups
 ├── Roles
 └── Policies

Explanation

Avoid hardcoding AWS access keys and secret keys inside Java source code or Git repositories.

Code:

Do not write:

aws.accessKey=YOUR_ACCESS_KEY
aws.secretKey=YOUR_SECRET_KEY

Use IAM roles or environment variables instead.

Explanation

An EC2 instance can use an IAM role to access AWS services without storing permanent credentials on the server.

Code:

EC2 Instance
      |
      v
IAM Role
      |
      v
S3 / RDS / CloudWatch Access

Explanation

IAM policies define the actions that a role or user can perform on AWS resources.

Code:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["s3:PutObject"],
      "Resource": "arn:aws:s3:::my-bucket/*"
    }
  ]
}

Explanation

Follow the principle of least privilege by granting only the permissions required by the Spring Boot application.

Code:

Required permission:
s3:PutObject

Avoid unnecessary permissions such as:
s3:DeleteBucket
s3:* 

Grant only the required actions.