Swaraj Want Singh’s Post

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

I'm just wondering if it's something that Amazon Web Services (AWS) is going to fix or if it's not such a big deal as billing for S3 error messages. #AWS #CloudWatchLogs #CostOptimisation #BugOrFeature #RDSProxy

Finding the right DevOps and Cloud solutions isn’t always a walk in the park, but that’s what we’re here for. Our CTO Dmytro Sirant recently faced a tricky situation with AWS RDS Proxy logging and discovered some smart ways to save on costs there.  Amazon Web Services (AWS), you might want to check this out - it could really benefit your customers big time! #AWS #CloudWatchLogs #CostOptimisation #BugOrFeature #RDSProxy

So apparently if someone knows / guesses the name of your S3 bucket - even if it's private (!) - they can just bankrupt you by sending infinite PUT requests and there is nothing you can do about it. > requests get rejected > but AWS still counts it as a write operation against your account for which you have to pay at a rate of $0.005 per 1000 requests This seems insane. Especially because a lot of services rely on presigned URLs for uploads / downloads which exposes your bucket name to the client. In this case the author got their bill waved, but AWS support made it clear it's an exception not the rule. link to article: https://lnkd.in/gtmBhSYx

What do you do if all the API calls are failing and there is no error on the service ??? Has this ever happened with you ? Recently I faced this incident where all the containers were crashing but there was no error. The containers were exiting because of OOM. Unsure about what really happened dug further and saw an aws service was retrying like crazy 😅. And because of some initial failures, the retries bombarded the service and brought it almost completely down. Autoscaling was not quick enough to act, and the retries kept increasing. Scaling the service would generally be a good idea but even after 2x or 5x the number the service was not able to recover. Had to actually stop the aws service calls for a very small duration and let them fail for the service to recover properly and later processed those calls slowly😅 I found this one really interesting where there were no errors but just the sheer scale of retries brought the system down. Follow Arpit Adlakha for more !

AWS us-east-1 dumpster FIRE time..... So just as I am doing a massive deploy cross AWS accounts, the us-east-1 dumpster catches fire. Thank goodness we don't run life critical systems. How do folks deal with such failures during the middle of a deployment? Comment below.... #aws #us-east-1 #dumpster

𝗛𝗲𝗮𝗱𝘀 𝘂𝗽! 𝗔𝗪𝗦 𝗶𝘀 𝗠𝗮𝗸𝗶𝗻𝗴 𝗕𝗶𝗹𝗹𝗶𝗻𝗴 𝗠𝗼𝗿𝗲 𝗨𝘀𝗲𝗿-𝗙𝗿𝗶𝗲𝗻𝗱𝗹𝘆 𝗳𝗼𝗿 𝗦𝟯. Hey folks, just spotted some interesting news from AWS about S3 billing changes! As a fellow software engineer who relies on S3 for projects, this one caught my eye. 𝗛𝗲𝗿𝗲'𝘀 𝘁𝗵𝗲 𝗴𝗶𝘀𝘁: AWS is eliminating charges for certain error codes, specifically those pesky 403 Access Denied errors that come from unauthorized requests. This means you won't be billed for requests originating outside your AWS account or organization that try (and fail) to access your S3 buckets. Win-win, right? No more unexpected charges for unauthorized access attempts. Plus, no need to scramble and update your codebase – this change is automatic. For the curious cats out there, you can find a complete list of these free-to-use error codes on the AWS Billing documentation https://lnkd.in/d5MzfJsb. This is a great move by AWS towards making their services more cost-effective for users. It also simplifies billing and reduces the chance of surprise charges. What do you all think about this change? Have you ever been hit with unexpected S3 billing? Share your thoughts in the comments! #AWS #S3 #CloudStorage #Billing

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

AWS has introduced a new 7-day return window for Savings Plans, giving customers a handy "get out of jail free card" if an incorrect purchase is made or their requirements change soon after a purchase. Savings Plans offer savings of up to 72% compared to on-demand pricing, but require a usage commitment, typically measured in dollars per hour for a 1 or 3 year term. The 7-day return policy allows customers to return a Savings Plan purchase within one week if it doesn't align with their needs. This applies to Savings Plans with an hourly commitment of $100 or less. To initiate a return, customers can access the Savings Plans details page in AWS Cost Explorer and follow the steps. AWS Support will then process the refund, crediting the customer's account. This feature is a welcomed addition!

Did you know that each instance of Phoenix Pricing operates within a dedicated and secured AWS cluster? We possess the capability to assign or withdraw these instances to our clients and potential customers within a period of thirty minutes. Access to each instance is facilitated through a distinct URL, structured as follows: https://<unique_identifier>.phoenixpricing.eu