feat(efs): allow to specify az for one-zone

[pahud]

Issue # (if applicable)

This PR allows users to specify AZ for the one-zone filesystems through the vpcSubnets.availabilityZones. Before this PR, vpcSubnets is not allowed when oneZone is enabled, this PR removes the restriction and takes the following use cases into considerations:

• create a regional EFS file system with a mount target for each AZ
• create a one-zone EFS file system with mount target at the auto-selected AZ
• create a one-zone EFS file system at specified AZ with a single mount target at that AZ
• create a regional EFS file system with a single mount target at the specified AZ

Closes #30005

Reason for this change

Description of changes

Description of how you validated changes

1. Add additional unit tests.
2. I have deployed the code below and validated from my AWS console.

// create a regional EFS file system with a mount target for each AZ
new FileSystem(stack, 'FileSystem1', {
  vpc,
});

// create a one-zone EFS file system with mount target at the auto-selected AZ
new FileSystem(stack, 'FileSystem2', {
  vpc,
  oneZone: true,
});

// create a one-zone EFS file system at specified AZ with a single mount target at that AZ
new FileSystem(stack, 'FileSystem3', {
  vpc,
  oneZone: true,
  vpcSubnets: {
    availabilityZones: [vpc.availabilityZones[1]],
  },
});

// create a regional EFS file system with a single mount target at the specified AZ
new FileSystem(stack, 'FileSystem4', {
  vpc,
  vpcSubnets: {
    availabilityZones: [vpc.availabilityZones[2]],
  },
});

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

[nmussy]

Maybe add a check for

props.vpc.availabilityZones.includes(props.vpcSubnets.availabilityZones[0])

[pahud]

Nice catch! I'll add it in. Thanks.

[pahud]

OK this is a little tricky because vpc.availabilityZones could be dummy values if the context was not generated by the context provider. Let's only check that when we are confident they are neither dummy values nor unresolved tokens.

[nmussy]

Yeah good call, I only saw the unresolved tokens coming

[GavinZZ]

Nice, thanks!

[mergify]

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

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: f082a5f
• Result: SUCCEEDED
• Build Logs (available for 30 days)

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

[mergify]

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

[aws-cdk-automation]

Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one.