- S3 - Perhaps: CloudFront, SQS, SES § Stay away from EC2/Servers § Security: Easy as one-offs § No “Policies” implemented yet § “Just seeing what this is all about” Progressions in Cloud Adoption
the Cloud § IAM (Credentials) § VPC (Secure network) § AWS Direct Connect (just another data center) § Cloud policies begin to be formed § Critical evolution point
Servers, Enable SaaS § EC2 - Basic “data center migration” - Just another server type available… § Multiple AZs/Regions - Part of multi-datacenter resiliency strategy § Independently: SaaS usage increases - Non-critical or internal uses first
Servers § EC2 as a server choice - Data center migration - Often done when apps need a hardware refresh - Redundant data center § Application doesn’t change, just where it runs
Cloud Committed § Lambda § Data Pipeline § Kinesis § Machine Learning § Using cloud-unique capabilities - Cloud provider specific - Close tie to specific cloud provider
Load Balancing – Networking – External services Visibility into CloudWatch § AWS metrics on New Relic Dashboards AWS çè New Relic work together EC2 Instance Application & Application Microservices New Relic Application Monitoring Server OS Server (Virtual) Hardware New Relic Server Monitoring CloudWatch AWS CONSOLE DASHBOARDS