Skip to content

Commit 075c2c0

Browse files
chore(ec2): update link to v2 in SecurityGroup docs (#26257)
Update "Allowing Connections" link to v2 in [SecurityGroup docs](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.SecurityGroup.html). Before: https://docs.aws.amazon.com/cdk/api/latest/docs/aws-ec2-readme.html#allowing-connections which doesn't exist in v2 docs (so gets redirected to the v1 docs). After: https://docs.aws.amazon.com/cdk/api/latest/docs/aws-cdk-lib.aws_ec2-readme.html#allowing-connections ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
1 parent bd3b26a commit 075c2c0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

packages/aws-cdk-lib/aws-ec2/lib/security-group.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -346,7 +346,7 @@ export interface SecurityGroupImportOptions {
346346
* allow connections to and between constructs via--for example-- the `instance.connections`
347347
* object. Think of it as "allowing connections to your instance", rather than
348348
* "adding ingress rules a security group". See the [Allowing
349-
* Connections](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-ec2-readme.html#allowing-connections)
349+
* Connections](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-cdk-lib.aws_ec2-readme.html#allowing-connections)
350350
* section in the library documentation for examples.
351351
*
352352
* Direct manipulation of the Security Group through `addIngressRule` and

0 commit comments

Comments
 (0)