Gremlin’s Post

How confident are you in your AWS deployment’s ability to handle unexpected outages? If your answer is, “not very,” we hear you! That’s exactly why we created our new primer, “Closing the AWS Reliability Gap.” In it, you’ll discover: ➡️ How to proactively scan and test for reliability risks ➡️ How to standardize reliability measurement with scoring ➡️ How to automate reliability management Download your copy now and start building a more resilient system. https://ow.ly/nkhg50RHFEh

Don't wait until your next AWS outage to build a reliability strategy. Our new primer, "Closing the AWS Reliability Gap," covers all the actionable tips you need to improve the stability and performance of your deployments. You’ll discover: 🚀 How to proactively scan and test for reliability risks 🚀 How to standardize reliability measurement with scoring 🚀 How to automate reliability management Grab your copy here: https://ow.ly/FcrQ50RHI7N

Building on AWS can be a double-edged sword. Automatic scaling, region/zone redundancy, and managed services can improve the resiliency of your systems. On the other hand, you have a more complex system, which means more potential points of failure. Our brand-new primer on reliability management on AWS covers: ➡️ The shared responsibility resilience model ➡️ Proactively scanning and testing for reliability risks ➡️ Standardizing reliability measurement with scoring ➡️ Automating reliability management Don’t wait until your next outage—download your copy and start building a more resilient, reliable system: https://ow.ly/fNfB50RHHRy

The Six Pillars of AWS Well-Architected Framework. What is your No. 1 priority while architecting on AWS? - Operational Excellence - Security - Reliability - Performance Efficiency - Cost Optimization

Hi Everyone, Here is my new blog, in which I discussed about Centralized VPC Endpoints. In a case when you have multiple VPCs. Lets say you have an dedicated VPC for Networking or shared services and you want to access AWS services across all the VPCs, you may go with this approach. There are multiple advantages out of this use case like costing, you don't have to create VPC endpoints in each VPC, instead you can create a single VPC endpoint for each services and you can access across all VPCs with private connection. In this approach, the traffic will not route over the internet, will be routed within the AWS backend network #aws #devops #minfy #minfydevops

One of the most costly parts of AWS for many teams is the NAT Gateway. AWS Managed NAT Gateways allow components running in your private network (VPC) to reach internet resources and other AWS resources. You pay a flat fee hour to have them enabled and an additional fee based on the amount of traffic flowing through them. If you have multiple VPCs and multiple accounts that each have their own NAT Gateways the costs can be quite high for the flat fee components. One approach you could take is to use a Transit Gateway and have all the VPCs connected to it and use 1 or a small number of NAT Gateways that all the VPCs share. This article from Emsii shows all the details required to set this up. https://lnkd.in/e5z62-zH

AWS SUPPORT PLANS [FULL COMPARISON] Confused about which AWS support plan is right for you? Check out our latest video for a comprehensive comparison of AWS support plans. We break down the five different AWS support plans, highlighting their features and benefits in an easy-to-understand table. This guide will help you make an informed decision on the best plan for your needs. https://lnkd.in/euaucnUA 

They say if you're the smartest person in the room, you're in the wrong room. Well, with Dmytro Sirant around, I am always safe 😁 Amazon Web Services (AWS) please take a look at his article. It looks like something that might be valuable for your customers! #AWS #CloudWatchLogs #CostOptimisation #BugOrFeature #RDSProxy

One of the most costly parts of AWS for many teams is the NAT Gateway. AWS Managed NAT Gateways allow components running in your private network (VPC) to reach internet resources and other AWS resources. You pay a flat fee hour to have them enabled and an additional fee based on the amount of traffic flowing through them. If you have multiple VPC's with multiple accounts that each have their own NAT Gateways the costs can be quite high for the flat fee components. One approach is to take a Transit Gateway and have all the VPC's connected to it and use 1 or a small number of NAT Gateways that all the VPC's share. Link: to article from Emsii

Struggling to decide which Availability Zones will work best for your VMs or EKS deployments? Choosing the right availability zones for your AWS environment is critical. Here’s how Spot can help: https://lnkd.in/ekJS7Hq7