You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Display project costs on Registry app for public cloud projects by pulling total expenses for each namespace from AWS and Azure APIs. Include a link to the detailed cost dashboard in AWS/Azure for further information.
Technical Details
Collaborate with the public cloud team to obtain read-only access to the API endpoints.
Research AWS and Azure API endpoints to pull the current billing data.
Explore both:
AWS
Azure
Confirm whether expense data is accessible via these API endpoints and investigate tools (packages) provided by AWS and Azure to simplify API usage.
Check the characteristics of access tokens, such as expiration dates and fine-grained access control, to ensure minimum privilege for the registry app.
Definition of Done (DOD)
Write a basic script to pull expense data from AWS and Azure as a comment of this ticket.
The text was updated successfully, but these errors were encountered:
junminahn
changed the title
Public Cloud total expense information
Integrate Public Cloud Project Cost Display for AWS and Azure
Sep 18, 2024
junminahn
changed the title
Integrate Public Cloud Project Cost Display for AWS and Azure
Research on integration Public Cloud Project Cost Display for AWS and Azure
Sep 18, 2024
After a conversation with Prabhu, the task was put on hold. It was determined that creating a user role for retrieving budget/cost data is not possible due to security concerns. The public cloud team will explore a solution to provide the app-dev team with the necessary credentials at a later time.
Description
Display project costs on Registry app for public cloud projects by pulling total expenses for each namespace from AWS and Azure APIs. Include a link to the detailed cost dashboard in AWS/Azure for further information.
Technical Details
Definition of Done (DOD)
The text was updated successfully, but these errors were encountered: