AWS: Panic/exit if can't collect costexplorer data

[Pokom]

We've ran into scenarios where we can't access the costexpolorer API and the application continues running. This happened when upgrading aws-go-sdk-v2 which had a major breaking change and took us the better part of a week to realize it before downgrading the package. One thing I think we can do is when instantiating the costexplorer client is to make a "ping" call to validate we've got a connection. If not, the application should halt and ensure we don't take down the working deployment.

[ohyesgocool]

Hi @Pokom ,
Shall i pick this up ? If yes you can assign it to me 🙂

[Pokom]

Hi @ohyesgocool let me review this issue and provide a bit better direction. The application has evolved considerably since I created this(It is the 6th issue after all) and I just want to make sure you don't invest time in the wrong direction.