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

feat: Include cost explorer to default console services in iam-read-only-policy module #186

Conversation

Andrey9kin
Copy link
Contributor

Description

Added Cost Explorer to default console services defaults.

Motivation and Context

AWS updated home screen and now it shows data from cost explorer thus generating Cloud Trail accessed denied events if policy does not container Cost Explorer

Breaking Changes

N/A

How Has This Been Tested?

  • I have tested and validated these changes using one or more of the provided examples/* projects
    Plus local tests

… services to allow after AWS home screen update

Signed-off-by: Andrey Devyatkin <andrey.devyatkin@fivexl.io>
@Andrey9kin Andrey9kin changed the title feat: iam-read-only-policy - include cost explorer to default console… feat: Update iam-read-only-policy - include cost explorer to default console services Feb 2, 2022
@antonbabenko antonbabenko changed the title feat: Update iam-read-only-policy - include cost explorer to default console services feat: Include cost explorer to default console services in iam-read-only-policy module Feb 2, 2022
@antonbabenko antonbabenko merged commit e701139 into terraform-aws-modules:master Feb 2, 2022
antonbabenko pushed a commit that referenced this pull request Feb 2, 2022
## [4.11.0](v4.10.1...v4.11.0) (2022-02-02)

### Features

* Include cost explorer to default console services in `iam-read-only-policy` module ([#186](#186)) ([e701139](e701139))
@antonbabenko
Copy link
Member

This PR is included in version 4.11.0 🎉

@Andrey9kin Andrey9kin deleted the update-console-defaults branch February 2, 2022 13:36
@github-actions
Copy link

github-actions bot commented Nov 9, 2022

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants