Skip to content
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.

Commit

Permalink
chore: restrict Kibana user creation to be admin only (#420)
Browse files Browse the repository at this point in the history
  • Loading branch information
rsmayda authored Aug 21, 2021
1 parent 89ee8fd commit 68b4801
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions cloudformation/elasticsearch.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ Resources:
Type: AWS::Cognito::UserPool
Condition: isDev
Properties:
AdminCreateUserConfig:
AllowAdminCreateUserOnly: true
AutoVerifiedAttributes:
- email
UserPoolName: !Sub '${AWS::StackName}-Kibana'
Expand Down Expand Up @@ -86,8 +88,8 @@ Resources:
Metadata:
cfn_nag:
rules_to_suppress:
- id: W90
reason: 'We do not want a VPC for ElasticSearch. We are controlling access to ES using IAM roles'
- id: W90
reason: 'We do not want a VPC for ElasticSearch. We are controlling access to ES using IAM roles'
Properties:
EBSOptions: # Assuming ~100GB storage requirement for PROD; min storage requirement is ~290GB https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/sizing-domains.html
EBSEnabled: true
Expand Down

0 comments on commit 68b4801

Please sign in to comment.