Using AWS CostExplorer to find forgotten services
In this post I’ll give an introduction to Budgets, and walk through using Cost Explorer to find a forgotten Sagemaker notebook.
In this post I’ll give an introduction to Budgets, and walk through using Cost Explorer to find a forgotten Sagemaker notebook.
In the following examples, I’ll show how to renew certs with domains hosted on AWS/Route53 and GoDaddy. I run certbot with scripts within a docker container (to simplify automation), however you can use CLI.
The ability to experiment is one of the unsung benefits of cloud computing. It was, in fact what drew me to AWS in 2008. At Chariot, we have multiple sandbox environments, some for specific projects and some for general play, and recommend that our clients do the same. However, sandboxes need some controls, to ensure that they don’t become a source of runaway costs.
I’ve been experimenting with Workspaces for a week now, and have configured an instance for aws re:Invent for those times I want to hack. Coupled with an iPad Air, a bluetooth mouse, and the keyboard case, I have desktop I can pull up anywhere.
Chariot’s AWS Practice Lead, Keith Gregory, recaps his experience at Amazon’s re:Invent conference in 2019.
If you weren’t able to attend our IoT on AWS one-day conference, here’s a recap.
Given that hardcoding is a bad idea, how should you manage your AWS keys? AWS gives you three options, which we analyze in this post.
A Chariot team led by Eric Snyder migrates a local media giant’s data to the Amazon Web Services cloud.
In this 45 minute talk, Ken Rimple gives a quick overview of AWS CodeBuild, then dives into a few of the challenges he’s faced, from dealing with build errors properly, configuring CodeBuild to run inside of AWS, testing locally so you don’t go crazy waiting for 15 minutes each time you deploy a new build, how to properly access your build artifacts and reports, running tools like Cypress, to building and deploying Docker containers to ECS, and more.
Amazon Web Services (AWS) is a collection of nearly 200 services. They can be intimidating to the newcomer, and offer many opportunities for mistakes: some expensive, some just inconvenient. In this Lunch and Learn, our panel of AWS experts look at some of the mistakes they made, and how these could have been avoided.
Sorry, no posts were found.
Looking to discuss an AWS project with our team? Contact us.