Sound effects on

Courses
Training
- Search
Pricing
Leaderboard
Community
- Guilds
- Blog

XP Potion

0 / 2 embers

0 / 3000 xp

click for more info

Complete a lesson to start your streak

click for more info

Difficulty: 10

click for more info

Not enough gems

Cost: 6 gems

1: AWS Lambda

incomplete

2: Deploy Lambda

incomplete

3: Testing Lambda Functions

incomplete

4: API Gateway

incomplete

5: CloudWatch Log Groups and Viewing Lambda Logs

incomplete

6: Other Lambda Use Cases

incomplete

7: Final Cleanup

incomplete

1: Cloud Computing

2: Networking - VPCs

3: EC2 - Elastic Compute Cloud

4: RDS - Relational Database Service

5: IAM - Identity and Access Management

6: Monitoring - CloudWatch

7: DNS – Route 53

8: S3 - Simple Storage Service

9: CDN – CloudFront

10: ECS - Elastic Container Service

11: Serverless Functions – Lambda

1: AWS Lambda

2: Deploy Lambda

3: Testing Lambda Functions

4: API Gateway

5: CloudWatch Log Groups and Viewing Lambda Logs

6: Other Lambda Use Cases

7: Final Cleanup

Back

ctrl+,

This lesson's interactive features are locked, please to keep using them

Final Cleanup

Great work!!! We're all done. You've built a ton of infrastructure across all of AWS' core services. Now let's make sure you don't have any leftover resources running that could lead to unexpected bills.

Cost check: Leaving old resources around (especially EC2, RDS, ALB, CloudFront, and Route 53) can continue billing.

If you're curious about your billing status, either now or in the future, you can always see where you stand by searching "Billing" in the AWS Console. It will break down all your costs by service and time.

Assignment

Delete all remaining patientping* course resources in your AWS account.

Use AWS Console search with the slug patientping to quickly find leftovers across services.

Make sure you've deleted this stuff that should have been deleted in earlier chapters:
- patientping-replica: RDS Read Replica
- patientping-db: RDS Database Instance
- patientping-private-subnet-group: RDS DB Subnet Group
- patientping-rds-sg: RDS Security Group
- patientping-cpu-alarm: CloudWatch Alarm
- patientping-dashboard: CloudWatch Dashboard
- patientping-monitoring: CloudWatch Log Group
- patientping-alerts: SNS Topic
- patientping-monitoring-role: IAM Role
- patientping-cloudwatch-logs-access: IAM Policy
- patientping-web-v2: EC2 Instance
- patientping-favicon-bucket-*: S3 Bucket
- patientping.internal: Route 53 Hosted Zone
- patientping-favicon-bucket-* (origin): CloudFront Distribution
- patientping-svc: ECS Service
- patientping-ecs: ECS Cluster
- patientping-ecs family: ECS Task Definitions
- patientping-ecs: ECR Repository
- patientping-alb: Application Load Balancer
- patientping-tg: Target Group
- patientping-internal: Security Group
- patientping-external: Security Group
- patientping-ecs-execution-role: IAM Role
- patientping-ecs-task-role: IAM Role
- patientping-ecs-execution-policy: IAM Policy
- patientping-ecs-task-policy: IAM Policy
- /ecs/patientping-ecs: CloudWatch Log Group
You can now also delete all this additional stuff:
- patientping: VPC
- patientping-public-a: Subnet
- patientping-public-b: Subnet
- patientping-private-a: Subnet
- patientping-private-b: Subnet
- patientping-igw: Internet Gateway
- patientping-public-rt: Route Table
- patientping-private-rt: Route Table
- patientping-web: EC2 Instance
- patientping-empty: EC2 Instance
- patientping-key: EC2 Key Pair
- patientping-public: Security Group
- patientping-web-base: AMI
- patientping-web-launcher: Launch Template
- patientping-admin-vinny: IAM User
- patientping-ec2-readers: IAM Group
- patientping-ec2-readonly: IAM Policy
- patientping-ec2-readonly-role: IAM Role
- patientping-deny-all: IAM Policy
- patientping-ssm-access: IAM Policy
- /DATABASE_URL: SSM Parameter
- /CMO_NAME: SSM Parameter
- patientping-ip-function: Lambda Function
- patientping-lambda-role: IAM Role
- patientping-ip-api: API Gateway HTTP API
- /aws/lambda/patientping-ip-function: CloudWatch Log Group

Run and submit the CLI tests.