AWS Developer Ecosystem.pdf
0 likes•54 views
This document discusses the typical practices for onboarding to AWS cloud services, software development, and infrastructure management. It outlines the common services used for identity and access management (IAM), software development including source control and packaging, cloud services like compute and databases, and infrastructure management. It also describes better practices such as using IAM roles instead of long-term access keys, setting budget alerts, leveraging services like CodeCommit and CodePipeline for development, choosing the appropriate cloud service based on needs and pricing, and implementing infrastructure as code and monitoring for management.
AWS Developer Ecosystem.pdf
- 7. Cloud On-Boarding ● IAM Users ● IAM Role ● IAM Single Sign-On ● Billing and Budget ● AWS Organization ● Account Service Control Policies Software Development ● CodeCommit ● CodePipeline ● CodeBuild ● S3 Cloud Services ● EC2 ● Beanstalk ● AppRunner ● Lambda ● API Gateway ● Load Balancer ● Auto-scaling ● DynamoDB Infrastructure Management ● CloudFormation ● Terraform ● CloudTrail ● Config ● AWS Systems Manager
- 10. Typical Practices ● Use AWS Console ● Use Root Account for EVERYTHING ● Create IAM Users ● Create and Use IAM Access Keys ● Create Roles with broad privileges ● Create Resources but Don’t Cleanup ● Root User is shared across multiple users ● No Billing Assessment ● No Monthly Budget Alerts
- 11. Demo
- 13. ● Private Git Repositories ● Software Packaging ○ Front-End ○ Backend-End ○ Mobile App ● Artifact Repository for Dependencies ○ Startup Scripts ○ Mobile App APKs ○ Node NPM Modules Typical Process
- 14. Demo
- 16. ● Use EC2 for (Almost) Everything ● Use Default VPC ● Avoid Price Comparison across different AWS Services ○ EC2 is cheaper than RDS ○ RDS is cheaper than Aurora ○ AppRunner is cheaper than EC2 ○ Lambda is cheaper than AppRunner/EC2 ○ DynamoDB is cheaper than MongoDB ○ S3 is cheaper than EC2 Volumes (EBS) ● Avoid Software Packaging ○ Using Source files vs Docker or Packages Typical Practices
- 17. Compute EC2 IaaS Lambda FaaS CaaS AppRunner CaaS Beanstalk PaaS Lightsail IaaS ECS CaaS EKS CaaS
- 20. Networking / Content Delivery API Gateway Load Balancer CloudFront Route53
- 22. Cloud Management
- 23. ● Console or Click-based Infrastructure ● No Governance Practices ● No Monitoring in place Typical Practices
- 25. Demo
- 26. Summary ● Keep Root Account isolated from application accounts ● Use Short-term Access vs Long-term - IAM SSO vs IAM User ● Use Roles vs Access Keys, If you have to use Keys, then use rotate those keys regularly ● Always configure budget alerts ● CodeCommit, CodeBuild and CodePipeline makes the software packaging very simple and private ● There are multiple AWS services for same use case, if possible, assess alternate services as well ● All Production environments are managed by Infra Code, learn if you don’t know already ● Keep an eye on your access activities with CloudTrail and Config ● Cloud is not CHEAP
- 27. Thank You!! LinkedIn AWS Surat Group