The issue:
Resource user is missing
The problem:
Cloud watch retention is 90 days
We fetch the resource user from cloud watch
If the resource create > 90 days, so no indication for the resource user
The solution:
Create a database with dedicate table for AWS resource id. store resource id (primary key) and its fields (user | cost($) | state | instance type | launch time | name | cluster owner)
We can use Dynamodb service for it.
So we will fetch the first the user data according resource id from the table and if it is not there go to cloud watch and update the database with new record of resource and user.
Also we can update the Dynamodb with the latest status (cost($) | state | launch time)
The issue:
Resource user is missing
The problem:
Cloud watch retention is 90 days
We fetch the resource user from cloud watch
If the resource create > 90 days, so no indication for the resource user
The solution:
Create a database with dedicate table for AWS resource id. store resource id (primary key) and its fields (user | cost($) | state | instance type | launch time | name | cluster owner)
We can use Dynamodb service for it.
So we will fetch the first the user data according resource id from the table and if it is not there go to cloud watch and update the database with new record of resource and user.
Also we can update the Dynamodb with the latest status (cost($) | state | launch time)