![]() After planning 27,000 layoffs, or what had been 9% of its roughly 300,000-person staff starting last year, it has since revealed more role reductions, at Amazon Fresh stores, for instance. Sales in Amazon's North America segment increased 11% to nearly $88 billion in the third quarter, and the company reported a $4.3 billion operating profit in the business in that region compared with an operating loss a year earlier.Īmazon has cut costs aggressively since that loss. The retailer invested heavily in recent years to make the service available in more places. The company has said a third-quarter shopping blitz known as Prime Day notched its biggest sales day ever, while a follow-up promotion period was its largest October holiday kickoff to date.Īmazon's same-day delivery services have also helped its margins by spurring shoppers to place more frequent and bigger orders. ![]() Several initiatives helped Amazon navigate the terrain. "We still see customers remaining cautious about price, trading down where they can and seeking out deals," he said.Ībating inflation helped lower some of Amazon's transportation spending, somewhat offset by fuel costs, he said. Net income rose to $9.9 billion in the third quarter from $2.87 billion a year earlier.ĬFO Olsavsky said the company in general saw strong demand in sales categories such as beauty and health, although discretionary spending was lower. What is Alarm Fatigue and how to deal with itįoto von Stephen Phillips - .Amazon's overall revenue in the third quarter rose 13% to $143.1 billion, beating Wall Street estimates of $141.41 billion, according to LSEG data. When everything is urgent, nothing is.(feel free to comment below if you have experience and opinions) Use cases Quickly discover and act on cost anomalies Gain near real-time visibility into anomalous spend with AWS Cost Anomaly Detection alert notifications in Microsoft Teams and Slack by using AWS Chatbot. I haven't tried that though, so I can tell you much more. AWS Chatbot lets you monitor, troubleshoot, and operate your AWS environments natively from within your chat channels. Since SNS can send emails without many hassles or configuration overhead it might be an easy solution. It seems you can send emails directly to slack by simply getting an email for your channel: ![]() While reading Slack documentation I found another option you might find interesting. The easiest way to find both the WorkspaceID and the ChannelID is to open your Slack Application in your browser and go to channel you want to become your recipient. So, basically, by getting rid of the Lambda, you are not going to pay for all the lambda invocations for every single slack notification, and you only pay, as before, only for the use of SNS.Īgain, hopefully you do not have millions of slack notifications every day, so costs could be quite irrelevant, but if you can have a simpler system for less money, why not?Įven migrating takes few minutes ( it definitely took me longer to write this post!) You pay only for the underlying services. There is no additional charge for AWS Chatbot. I might argue that you have less code to maintain, easier infrastructure, but that wouldn't be a great selling point - we are talking about one single Lambda, which we haven't touched in years - so let me say just this: Once you have your Client, your CDK stack will be able to create a SlackChannel Configuration.īut you are just exchanging Lambda with Chatbot, where's the gain? ![]() Reading again the docs here I realised that I was missing the main Workspace/Client Configuration.įrom your account console open AWS Chatbot and select create Client Configuration, grant the permissions for your AWS Chatbot to access your Slack workspace and voila'. In our new SlackNotification stack we still create a Topic, but then instead of creating a Lambda, you set up the configuration of your SlackBot. Of course, Chatbot does a lot more than receiving Slack Notifications - actually it is more a powerful tool to send messages from Slack in order to run some commands on your AWS resources (like launching deployments, starting instances, triggering lambdas and so on) but I will explain that in another post.īut for now let's focus on how Chatbot simplified our Monitoring system basically allowing us to get rid of the Lambda function. By using AWS Chatbot, you can receive alerts and run commands to return diagnostic information, invoke AWS Lambda functions, and create AWS Support cases so that your team can collaborate and respond to events faster. Recently I was setting up Slack Notifications for a new project on a new team and while I was checking out that old repo and some newer documentation I realised AWS ChatBot exists.ĪWS Chatbot is an interactive agent that makes it easier to monitor and interact with your AWS resources in your Slack channels and chat channels. It was as you can see already simple enough, and we used that for years already. Enter fullscreen mode Exit fullscreen mode
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |