Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhacement | Improve Workflow for MonthlyServicesUsage Lambda Function #653

Open
martingaleano opened this issue Nov 8, 2024 · 0 comments

Comments

@martingaleano
Copy link
Contributor

martingaleano commented Nov 8, 2024

Describe the Feature

  • The function shouldn't completely crash due to a specific error (such as trying to assume a nonexistent role).

  • The function shouldn't break so easily if it can't assume a role in another account

  • Add an alarm as part of the layer to notify when the function fails.

  • Document how to test the function.

  • Possible improvement: have the function resolve account IDs on its own.

  • Possible improvement: limit the function’s permissions to only those it truly needs.

Expected Behavior

  • A clear and concise description of what you expected to happen.

Use Case

Is your feature request related to a problem/challenge you are trying to solve? Please provide some additional context of why this feature or capability will be valuable.

Describe Ideal Solution

Some of these items could apply to all Lambda functions, not just the one that generates reports.

Alternatives Considered

Explain what alternative solutions or features you've considered.

Additional Context

This is the Slack link to the channel where we discuss this issue: https://binbashar.slack.com/archives/GG0PJ78J3/p1730993713083689

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant