The monthly SageMaker bill doubled. Tags are already on the resources, but nobody knows whether a forgotten training job, a 24×7 GPU endpoint, or data-capture storage drove the increase. What should they use?
Select an answer to reveal the explanation.
Short Explanation
The monthly SageMaker bill doubled, and tags are already on the resources. Open Cost Explorer and group by service, tag, and usage type. Debugger, Personalize, and a tighter monitor cadence are not that cost look.
Full Explanation
Cost Explorer can filter and group SageMaker spend by service, tag, and usage type so you can see whether training, a always-on GPU endpoint, or capture storage drove the increase. Debugger, Personalize, and Model Monitor are not that cost analysis.