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(ecs): default Service throws in a VPC without private subnets #7188

Merged
merged 1 commit into from
Apr 6, 2020

Conversation

rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented Apr 6, 2020

Commit Message

People like to create VPCs without private subnets, as the NAT
gateways (or NAT instances) can be expensive.

The default settings of an ECS Service is to create themselves
in a PRIVATE subnet, instead of the "default selection order" of
Private -> Isolated -> Public. Now use the default selection
(by not supplying a subnetType at all).

Fixes #7062.

End Commit Message


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

People like to create VPCs without private subnets, as the NAT
gateways (or NAT instances) can be expensive.

The default settings of an ECS Service to to create themselves
in a PRIVATE subnet, instead of the "default selection order" of
Private -> Isolated -> Public. Now use the default selection
(by not supplying a `subnetType` at all).

Fixes #7062.
@rix0rrr rix0rrr requested a review from a team April 6, 2020 09:36
@rix0rrr rix0rrr self-assigned this Apr 6, 2020
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Apr 6, 2020
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
  • Commit ID: 94695d9
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify
Copy link
Contributor

mergify bot commented Apr 6, 2020

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot merged commit 0ef6a95 into master Apr 6, 2020
@mergify mergify bot deleted the huijbers/ecs-service-subnet-defaults branch April 6, 2020 11:40
horsmand pushed a commit to horsmand/aws-cdk that referenced this pull request Apr 8, 2020
…s#7188)

People like to create VPCs without private subnets, as the NAT
gateways (or NAT instances) can be expensive.

The default settings of an ECS Service is to create themselves
in a PRIVATE subnet, instead of the "default selection order" of
Private -> Isolated -> Public. Now use the default selection
(by not supplying a `subnetType` at all).

Fixes aws#7062.
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.

There are no 'Private' subnet groups in this VPC. Available types: Public
3 participants