aws_apigateway: unable to add multi-level base path mappings

[VarunWachaspati]

Describe the bug

As per this AWS announcement post, API Gateway support multi-level path mappings like api/v2/action or api/example-api now.

Now when I try to add a base path mapping containing a slash(/) via CDK it throws an error even though the same can be achieved via the AWS console successfully.

Expected Behavior

Should be able to add multi-level base path mappings containing slashes(/) via CDK.

Current Behavior

Throws the following error when you try to add multi-level base path mapping in API Gateway -

Error: A base path may only contain letters, numbers, and one of "$-_.+!*'()", received: api/example-api
at new BasePathMapping (/tmp/artifact/node_modules/aws-cdk-lib/aws-apigateway/lib/base-path-mapping.js:1:759)

Reproduction Steps

Sample CDK code to reproduce the issue -

const domainName = apigateway.DomainName.fromDomainNameAttributes(this, 'DomainName', {
  domainName: 'domainName',
  domainNameAliasHostedZoneId: 'domainNameAliasHostedZoneId',
  domainNameAliasTarget: 'domainNameAliasTarget',
});

new apigateway.BasePathMapping(this, 'BasePathMapping', {
  domainName: domainName,
  restApi: api,
  basePath: 'api/example-api',
});

Possible Solution

Modify the following validation to accommodate slash(/) -

aws-cdk/packages/@aws-cdk/aws-apigateway/lib/base-path-mapping.ts

Lines 58 to 62 in 30301d9

	if (props.basePath && !Token.isUnresolved(props.basePath)) {
	if (!props.basePath.match(/^[a-zA-Z0-9$_.+!*'()-]+$/)) {
	throw new Error(`A base path may only contain letters, numbers, and one of "$-_.+!*'()", received: ${props.basePath}`);
	}
	}

I can contribute to fix this issue if the above proposed solution is acceptable.

Additional Information/Context

No response

CDK CLI Version

2.46.0

Framework Version

No response

Node.js Version

14.17.1

OS

MacOS Monterey 12.5

Language

Typescript

Language Version

No response

Other information

No response

[VarunWachaspati]

Also, if possible can anyone suggest a work around for this issue in the meanwhile. Would greatly appreciate it.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.