AWS

AWS для начинающих: аккаунты и IAM, сеть VPC, вычисления и масштабирование, базы данных, serverless, затраты, надёжность и инфраструктура как код — Terraform, CloudFormation, CDK.

Why it matters for UCP. The cloud is the second half of the runtime environment after Kubernetes: IAM roles instead of keys, managed PostgreSQL/Kafka instead of hand-rolled operations, secrets and observability as services. A developer who doesn't understand this model writes code that can't be deployed safely. Part of the training program.

The section is split into eighteen articles. The knowledge is portable: the "roles, managed data, secrets as a service" model works the same way across all the major clouds — AWS is the language of explanation here, not a lock-in.

Fundamentals and networking

  1. AWS fundamentals — account, IAM, regions, and VPC: where every cloud project begins.
  2. Networking: VPC, subnets, NAT — how networking works in AWS and how a public subnet differs from a private one.
  3. IAM: access, roles, policies — who can do what in an account, and why roles are more convenient than keys.

Compute

  1. Where to run your service: EC2, ECS, EKS, Lambda — four ways to stand up a backend and how to pick the right one.
  2. Scaling and availability — how to handle load and stay up through failures.
  3. Serverless: Lambda, API Gateway, Step Functions — code without servers: events, cold starts, orchestration.

Data

  1. Managed data: RDS, ElastiCache, SQS, MSK — what the cloud takes off your hands instead of your own PostgreSQL, Redis, and Kafka.
  2. DynamoDB: keys, indexes, when to use it instead of SQL — how AWS's NoSQL database works and which tasks it's better suited for.

Integration and operations

  1. AWS from Spring Boot: SDK v2, LocalStack — how to talk to the cloud from code and test without it.
  2. Security and observability: Secrets Manager, KMS, CloudWatch — where to store passwords and how to read logs and metrics.
  3. Cost optimization — how to pay less for AWS deliberately.
  4. Resilience and disaster recovery — multi-AZ, multi-region, RPO/RTO, and backups.
  5. The Well-Architected Framework: six pillars — a framework for evaluating your own architecture in the cloud.

Infrastructure as code

  1. Infrastructure as Code: fundamentals — what IaC is and why you describe infrastructure in code.
  2. Terraform: HCL, providers, state — the most popular IaC tool, explained through clear examples.
  3. CloudFormation: templates and stacks — the AWS-native way to describe resources.
  4. AWS CDK: infrastructure as a program — describing infrastructure in a familiar programming language.
  5. IaC in practice: state, secrets, delivery — what separates a tutorial example from a real project.