Modernization of your AWS based SaaS platform - Short

Editor's Notes

• #21: (2 minutes) Unused Resources (30 seconds): Many AWS environments have resources running when they aren’t needed, leading to wasted costs. The classic example are development environments. Running them for 40 hours a week instead of 168 can yield very significant savings. Another one are QA, stress and training environments that are not needed at every stage of the lifecycle. You can script these to be deployed, terminated, and redeployed as needed, instead of paying for them 24/7.  Use AWS tools like Cost Explorer to quickly identify idle resources, expensive resources, and automate start/stop times to optimize usage. Oversized Resources (30 seconds): Over-provisioning resources can result in higher costs without added benefit, while undersizing can cause performance issues. Right-size your resources using AWS Compute Optimizer to ensure they match your actual needs. Review what you have in CloudWatch for your resources and make sure they are not idle or underused. Inappropriate Resources (30 seconds): Choosing the wrong type of resource, like using EC2 instead of Fargate, can create inefficiencies. Match workloads to the most suitable AWS services, such as using Fargate for serverless container tasks and EC2 for more persistent needs. Analysis and design work up front can save you big in the future. Discounting Schemes (30 seconds): AWS offers discounts through Reserved Instances, Savings Plans, and Spot Instances to reduce costs. Analyze your workload patterns and commit to the right discounting schemes to maximize savings. Savings plans are flexible and easy to get into, plus you can stack them if your needs expand. They’re available in 1 year and 3 year commitments, covering EC2, Fargate, Lambda and Sagemaker Conclusion (10 seconds): Regularly revisiting these opportunities ensures you're continually optimizing your AWS environment for performance and cost efficiency.
• #22: (1-2 mins) 1. Inappropriate Resources (EC2 vs. Fargate) (20 seconds): Proper design can yield the largest results. Prioritize evaluating whether your workloads are on the right resource type. Misalignments, like using EC2 instead of Fargate for containerized tasks, can lead to inefficiencies. Reassess your resource choices to ensure optimal performance and cost. 2. Rightsizing (20 seconds): Use Compute Optimizer and CloudWatch Memory metrics to right-size your EC2 instances, addressing unused or underused instances. Regularly monitor and adjust resources to match actual usage. 3. EC2-Other (EBS Unused/Underused) (20 seconds): Address unused or underutilized EBS volumes. These can accumulate costs without adding value. Watch out for unattached EBS volumes in your account. Use Trusted Advisor to identify and clean up these resources. 4. Egress (10 seconds): Prioritize managing and reducing data egress costs, which can be significant depending on your data transfer needs. 5. Well-Architected Pillars (10 seconds): Ensure your architecture aligns with AWS Well-Architected Framework principles to optimize across cost, performance, security, reliability, and operational excellence. 6. Discounting Options (20 seconds): Leverage Savings Plans for compute workloads and Reserved Instances for services like RDS and ElastiCache. Explore other commitment schemes to maximize savings across your environment. Conclusion (10 seconds): By focusing on these priorities, you can systematically improve the efficiency and cost-effectiveness of your AWS environment.
• #23: (2 mins) 1. Enterprise Agreement – Customer (20 seconds): Customer: Bulk discounting for your entire organization based on committed spend across various AWS services. Tailored agreements can significantly reduce costs for large-scale operations. 2. Enterprise Agreement – Service (20 seconds): Org - CloudFront: Specific service-level agreements provide discounts for targeted usage, like CloudFront. Ideal for organizations with significant use of particular AWS services or global distribution needs. 3. Service Tiering (20 seconds): Org: Discounts are available at the organizational level based on usage tiers. As your organization’s usage increases, costs can decrease, particularly in services like S3. 4. Savings Plans (20 seconds): EC2, Lambda, Fargate: Flexible discounting across compute services based on hourly usage commitments. These plans are ideal for organizations looking to optimize costs across multiple compute services. 5. Reserved Instances (20 seconds): EC2, RDS, ElastiCache: Commit to a certain level of usage over 1 or 3 years to receive substantial savings. Best for predictable workloads, ensuring consistent cost reductions. Conclusion (10 seconds): By strategically leveraging these discounting schemes, your organization can effectively manage AWS costs while maintaining high performance.
• #24: (2 mins) Slide Title: Sustainability in Technology 1. Industry Goals (30 seconds): AWS Goals: AWS is leading by example with ambitious goals like becoming Water Positive by 2030 and achieving 100% Renewable Energy by 2025. Partner Impact: Sustainability is a key focus, as seen in the MSP Audit, where one of 13 domains targets sustainability. Industry Impact: The Well-Architected Framework emphasizes sustainability as one of its six pillars, guiding best practices. Customer Impact: Customers gain visibility into their carbon footprint, both in proactive planning and reactive consumption. 2. Organizational Goals (20 seconds): Our Goals: Our aim is to influence and impact our customers through leadership in sustainability, ensuring that we drive positive change across the board. 3. Our Unique Position (20 seconds): We operate at the cross-section of customers, giving us a broad influence. We have the power to create influenced impact through our partnerships. Additionally, we can drive direct impact by optimizing our own operations and those of our customers. 4. Sustainability in Technology Starts with Optimization (20 seconds): True sustainability begins with optimizing costs and performance but goes beyond just that. Operational Parameters: Defining how “fast” something needs to be can significantly reduce unnecessary energy use. Service Selection: Choosing the right services, like avoiding running a 24-hour service for a work-day application, can influence both sustainability and cost optimization. Conclusion (10 seconds): In technology, sustainability is a continuous journey that starts with optimization and extends to thoughtful service selection and operational efficiency.
• #25: (1-2 minutes) 1. AWS Continues to Increase the Breadth and Depth of Their Service Offerings (30 seconds): AWS is constantly innovating, adding new services and features that often leave us thinking, “I wish it did that,” or “I didn’t know I needed that.” This continuous expansion makes AWS more versatile, enabling us to tackle challenges we couldn’t even imagine before. 2. It’s Easier to Get Started Today Than It Was Yesterday (30 seconds): Simplicity: AWS is increasingly user-friendly, with more intuitive interfaces and automation tools. Support: The support ecosystem has grown, with more resources, documentation, and community help available. Cost: AWS has introduced various pricing models and discounts, making it more affordable to experiment and scale. 3. Conclusion (30 seconds): When selecting your approach, always consider sustainability—think of Maslow’s Hammer: not every problem requires the same tool. Don’t forget about team enablement—your team’s ability to leverage these tools is just as important as the tools themselves. Remember, your potential is limited only by your imagination and your ability to execute on your ideas.