Skip to main content

AWS Account Setup

AWS Account Setup

Amazon Web Services (AWS) is a major cloud platform youโ€™ll use in several HackerOps labs for deploying infrastructure, managing security services, and practicing real-world cloud scenarios.

Tip

Free Tier: AWS offers a generous free tier that covers most lab activities. Youโ€™ll need a credit card for verification, but wonโ€™t be charged for basic usage.

Create AWS Account

Sign up: AWS Free Tier

If youโ€™re new to AWS, follow the account creation process with your email and credit card information.

Create IAM User for Labs

Caution

Security Best Practice: Never use your root AWS account for day-to-day activities. Always create IAM users with specific permissions.

For HackerOps labs, youโ€™ll need programmatic access to AWS services. Hereโ€™s how to set up a dedicated IAM user:

  1. Access IAM Console - Sign in to AWS Console, search for โ€œIAMโ€ in the services search bar, and click on โ€œIAMโ€ to open the Identity and Access Management console

  2. Create New User - In the IAM dashboard, click โ€œUsersโ€ in the left sidebar, then click โ€œAdd usersโ€ button and enter username: hackerops-labs

  3. Configure Access Type - Select โ€œAccess key - Programmatic accessโ€ to provide API access needed for Terraform and CLI tools

  4. Set Permissions - Choose โ€œAttach existing policies directlyโ€, then search for and select โ€œAdministratorAccessโ€ (Note: This gives full access - only use for learning environments)

  5. Review and Create - Skip tags (optional for labs), review the configuration, and click โ€œCreate userโ€

  6. Save Credentials - Download the CSV file or copy both the Access Key ID and Secret Access Key (you wonโ€™t be able to see the secret key again!)

Caution

Security Warning: These keys provide full access to your AWS account. Never share them or commit them to GitHub. Delete this user when you complete the course.

Install AWS CLI

The AWS Command Line Interface is essential for lab automation:

Configure AWS CLI

Set up your credentials for CLI and Terraform access:

Terminal window
# Configure AWS CLI with your credentials
aws configure
# You'll be prompted for:
# AWS Access Key ID: [Enter your Access Key]
# AWS Secret Access Key: [Enter your Secret Key]
# Default region name: us-east-1
# Default output format: json

Test Your Setup

Verify everything is working:

Terminal window
# Test AWS CLI access
aws sts get-caller-identity
# Should return your user information
# {
# "UserId": "AIDACKCEVSQ6C2EXAMPLE",
# "Account": "123456789012",
# "Arn": "arn:aws:iam::123456789012:user/hackerops-labs"
# }

Tip

Success! If you see your user information, AWS is properly configured and ready for the labs.

Next Steps

With AWS configured:

  1. Set up other cloud platforms - Azure and DigitalOcean
  2. Start Lab 1 - Begin with infrastructure deployment
  3. Monitor your usage - Check AWS billing dashboard regularly

Cost Management

Caution

Important: Always clean up resources after labs to avoid unexpected charges. Most labs include cleanup instructions.

Recommended practices:

  • Set up billing alerts for amounts over $10
  • Use AWS Cost Explorer to monitor spending
  • Delete resources immediately after completing labs
  • Consider using AWS Free Tier eligible services when possible