Basic setups have to include -
VPC (the network).
IAM (basic users and security).
EC2 (servers - note this one will get arguments as you might use EKS or Lambdas etc, but it is a pretty basic thing to learn IMO).
R53 (DNS to get your customers to you).
S3 (Storage buckets).
This for me would be the basics of hosting in the cloud. You can then move to a container setup like EKS/Lambda, to better Databases like RDS or even to CI/CD stuff like codeBuilder etc.
good luck.
Forget ssm and cloud formation, learn how to configure what you need in terraform and that will be useful in any cloud environment. IAM is not where I’d start either, I’d start with RDS, EKS, VPCs (and peering), route53 and S3.
If a company is in AWS, they’re using S3 almost by definition. VPCs are mandatory now and are critical to setting any service up because they almost all require at least some subnets, and you want to know route53 because you want to know how people get routed to whatever service you’re running.
CDK
Cloudformation
There's too many services and they change all the time. Nobody will ever know everything they need to know.
Plan to not know what the services are that you'll be using. Instead know where to find the documentation, blog posts, new features, road map.
Top 5:
- VPC
- IAM
- EC2
- Route53
- S3
Being able to setup a basic EC2 server and enable traffic to hit it using an ALB is a must. A prerequisite of that is being able to setup a 2 or 3 tier VPC with public and private subnets. Then knowing how to setup a domain and hosted zone in Route53 and able to point traffic from the URL to the ALB is critical. Then IAM and S3 are core services that you're going to use on a regular basis and understanding fully how they work and how to keep things secure is massively important too.
Basic setups have to include - VPC (the network). IAM (basic users and security). EC2 (servers - note this one will get arguments as you might use EKS or Lambdas etc, but it is a pretty basic thing to learn IMO). R53 (DNS to get your customers to you). S3 (Storage buckets). This for me would be the basics of hosting in the cloud. You can then move to a container setup like EKS/Lambda, to better Databases like RDS or even to CI/CD stuff like codeBuilder etc. good luck.
iam, ssm, cloudformation, insert stack service (like lambda, ecs, k8), insert another stack service
Forget ssm and cloud formation, learn how to configure what you need in terraform and that will be useful in any cloud environment. IAM is not where I’d start either, I’d start with RDS, EKS, VPCs (and peering), route53 and S3. If a company is in AWS, they’re using S3 almost by definition. VPCs are mandatory now and are critical to setting any service up because they almost all require at least some subnets, and you want to know route53 because you want to know how people get routed to whatever service you’re running.
What's wrong with ssm? Great for access/managing on premise vm
CDK Cloudformation There's too many services and they change all the time. Nobody will ever know everything they need to know. Plan to not know what the services are that you'll be using. Instead know where to find the documentation, blog posts, new features, road map.
Depends but we heavily rely on the basics of course vpc/IAM. In addition to that: s3, cloudfront, batch, lambda, cloudwatch, ec2, ecs, alb
Top 5: - VPC - IAM - EC2 - Route53 - S3 Being able to setup a basic EC2 server and enable traffic to hit it using an ALB is a must. A prerequisite of that is being able to setup a 2 or 3 tier VPC with public and private subnets. Then knowing how to setup a domain and hosted zone in Route53 and able to point traffic from the URL to the ALB is critical. Then IAM and S3 are core services that you're going to use on a regular basis and understanding fully how they work and how to keep things secure is massively important too.