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

fix(aws-ec2): change maxAZs default for VPCs to 3 #1543

Merged
merged 2 commits into from
Jan 15, 2019

Conversation

rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented Jan 14, 2019

For most users, default deployments of a VPC in us-east-1 would fail
because that region has more AZs (6) than the allowed EIP allocations in
an acccount (5).

This is a very poor experience. Plus, it is wasteful since there is
not much additional value in using more than 3 AZs for a VPC.

Fixes #996.


Pull Request Checklist

  • Testing
    • Unit test added
    • CLI change?: manually run integration tests and paste output as a PR comment
    • cdk-init template change?: coordinated update of integration tests with team
  • Docs
    • jsdocs: All public APIs documented
    • README: README and/or documentation topic updated
  • Title and Description
    • Change type: title prefixed with fix, feat will appear in changelog
    • Title: use lower-case and doesn't end with a period
    • Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
    • Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"
  • Sensitive Modules (requires 2 PR approvers)
    • IAM Policy Document (in @aws-cdk/aws-iam)
    • EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
    • Grant APIs (only if not based on official documentation with a reference)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

For most users, default deployments of a VPC in `us-east-1` would fail
because that region has more AZs (6) than the allowed EIP allocations in
an acccount (5).

This is a very poor experience. Plus, it is wasteful since there is
not much additional value in using more than 3 AZs for a VPC.

Fixes #996.
@rix0rrr rix0rrr requested a review from a team as a code owner January 14, 2019 14:08
@@ -58,7 +58,7 @@ export interface VpcNetworkProps {
* If the region has more AZs than you want to use (for example, because of EIP limits),
* pick a lower number here. The AZs will be sorted and picked from the start of the list.
*
* @default All AZs in the region
* @default 3
Copy link
Contributor

Choose a reason for hiding this comment

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

Indicate what users should do if they want to use all AZs (even if it's "99")

@rix0rrr rix0rrr merged commit 32a4b29 into master Jan 15, 2019
@rix0rrr rix0rrr deleted the huijbers/default-3-azs branch January 15, 2019 09:14
@NGL321 NGL321 added the contribution/core This is a PR that came from AWS. label Sep 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

VPC: Default AZs to 3
3 participants