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

[joysl] Neptune Autoscaling #180

Merged
merged 4 commits into from
Jan 17, 2024

Conversation

joysl
Copy link
Contributor

@joysl joysl commented Dec 14, 2023

With this commit, user can choose to enable Neptune Autoscaling along with following configurable paramters [TargetUtilization, MinCapacity,MaxCapacity]

Description

With this commit, user can choose to enable Neptune Autoscaling along with following configurable paramters [TargetUtilization, MinCapacity,MaxCapacity]

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • [x ] New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (existing code being refactored)
  • This change includes a documentation update

Submission Checklist

  • CI dry-run passing
  • Integration tests passing locally
  • [ x] Change logs generated
Additional Notes:

With this commit, user can choose to enable Neptune Autoscaling along with following configurable paramters [TargetUtilization, MinCapacity,MaxCapacity]
@joysl joysl changed the title [joysl] Neptune Autocaling [joysl] Neptune Autoscaling Dec 14, 2023
Copy link
Contributor

@canavandl canavandl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked out this CR and locally built/deployed the AssetLibrary module and confirmed that the Neptune autoscaling settings are applied as intended

Comment on lines +353 to +355
# Optional Neptune auto-scaling configuration
AutoScalingNeptuneNestedStack:
Type: AWS::CloudFormation::Stack
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Open question: What's the benefit of having this be a nested stack instead of part of the top-level one?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just decided to follow what was set for Lambda autoscaling which was a nested stack.

Copy link
Contributor

@canavandl canavandl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@canavandl canavandl merged commit bb27fb3 into aws:main Jan 17, 2024
1 check passed
@canavandl
Copy link
Contributor

Thanks @joysl !

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

Successfully merging this pull request may close these issues.

3 participants