« Previous
Next »
Summary
Wrapping up the AWS track with what you can ship and where to go next.
What you learned + OIDC trust policy
EXAMPLE
# AWS summary
You can now:
- Operate IAM with least privilege and OIDC federation
- Design VPCs with private subnets + endpoints
- Use S3 securely (BucketOwnerEnforced + Block Public Access)
- Run compute on Lambda, Fargate, or EC2 + SSM (no SSH)
- Persist data in RDS, DynamoDB, or Aurora
- Observe with CloudWatch, X-Ray, OpenTelemetry
- Secure with SCPs, GuardDuty, Config, IAM Access Analyzer
- Author IaC with CDK, Terraform, or CloudFormation
# Your next step - OIDC trust policy for GitHub Actions
{
'Version': '2012-10-17',
'Statement': [{
'Effect': 'Allow',
'Principal': {
'Federated': 'arn:aws:iam::111111111111:oidc-provider/token.actions.githubusercontent.com'
},
'Action': 'sts:AssumeRoleWithWebIdentity',
'Condition': {
'StringEquals': {
'token.actions.githubusercontent.com:aud': 'sts.amazonaws.com'
},
'StringLike': {
'token.actions.githubusercontent.com:sub': 'repo:me/app:ref:refs/heads/main'
}
}
}]
}
Why it matters
AWS rewards discipline. Multi-account + IaC + OIDC + Well-Architected covers most of what production needs. The next-level skills are cost engineering, multi-region resilience, and threat modelling against your specific workloads.
Tip: Tweak the snippet with Try it Yourself », then sit the quiz at the bottom of the page.
Example
Example
# Next: well-architected framework, Solutions Architect Associate, infra-as-code at scale.Try it Yourself »
« Previous
Next »
Discussion
Loading…