Skip to main content

AWS Developer

This section contains my notes in preparation for the AWS Developer Associate exam.

I took a course from Pearson/O'Reilly by Nick Garner. All source code from that course is made publicly available at https://bitbucket.org/awsdevguru/awsdevassoc.

Overview

In-Scope Services

  • IAM
  • Cognito
  • AWS WAF
  • AWS Certificate Manager
  • Key Management Service
  • Serverless Application Model
  • AWS SDKs
  • Cloud Development Kit
  • Lambda
  • Elastic Beanstalk
  • Simple Storage Service (S3)
  • Relational Database Service (RDS)
  • DynamoDB
  • ElastiCache
  • MemoryDB for Redis
  • Elastic Block Store
  • Amplify
  • CloudShell
  • CodeGuru
  • Cloud9
  • CodeStar
  • CodeArtifact
  • CodeBuild
  • CodeCommit
  • CodeDeploy
  • CodePipeline
  • API Gateway
  • CloudFront
  • Elastic Compute Cloud (EC2)
  • Virtual Private Cloud (VPC)
  • Route 53
  • AppSync
  • EventBridge
  • Simple Notification Service (SNS)
  • Simple Queue Service (SQS)
  • Step Functions
  • Kinesis
  • AWS Copilot
  • Elastic Container Registry (ECR)
  • Elastic Container Service (ECS)
  • Elastic Kubernetes Service (EKS)
  • CloudFormation
  • AppConfig
  • Systems Manager
  • Secrets Parameter Store
  • CloudWatch
  • X-Ray
  • CloudTrail
  • Athena
  • OpenSearch Service

AWS CLI Setup

The course demonstrated setting up and IAM user with programmatic access and then configuring the AWS CLI with the access key ID and secret access key.

However, the IAM Identity Center is a more secure way to manage access these days.

Why?

Using identity center, you can create a user that can log in via the console to grab limited temporary credentials as opposed to long-lasting hardcoded credentials tied to an IAM user.

An IAM user with long lasting credentials is still useful under some circumstances such as CI/CD pipelines or fully automated actions. But it's better to use identity center when possible.