aws_ec2_verified_access: Resource handler returned message: "null"

### Describe the bug

I'm creating aws verified access endpoint using cfn construct found [here](https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_ec2/CfnVerifiedAccessEndpoint.html). Before i deployed this part of the code, i was able to create Verified Access Trust Provider, Instance, Groups but failed when deploying the endpoint. Here is the code to deploy the endpoint
```
# Verified Access Endpoint
cfnVerifiedAccessEndpoint = ec2.CfnVerifiedAccessEndpoint(
self,
"CfnVerifiedAccessEndpoint",
application_domain="my-sandbox.com",
attachment_type="vpc",
domain_certificate_arn="my-dummy-cert-arn",
endpoint_domain_prefix="development",
endpoint_type="load-balancer",
verified_access_group_id=cfnVerifiedAccessGroup.attr_verified_access_group_id,
description="Verified Access Endpoint",
load_balancer_options=ec2.CfnVerifiedAccessEndpoint.LoadBalancerOptionsProperty(
load_balancer_arn="my-load-balancer-dummy-arn",
subnet_ids=["subnet-private-1", "subnet-private-2"],
),
security_group_ids= ["my-dummy-sg-id"],
)
```
but when i deploy it, i get this weird non descriptive error

`Resource handler returned message: "null" (RequestToken: d2ecd91a-a841-b67d-c5ca-6de761e1af83, HandlerErrorCode: InternalFailure)`

### Expected Behavior

Verified access endpoint is created

### Current Behavior

Deployment failed with non descriptive error message

### Reproduction Steps

Please view the code above

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### CDK CLI Version

2.117.0 (build 59d9b23)

### Framework Version

_No response_

### Node.js Version

v18.18.0

### OS

Windows

### Language

Python

### Language Version

Python 3.11.5

### Other information

_No response_

Start with the Python CfnVerifiedAccessEndpoint configuration in the issue and reproduce its deployment using the listed Verified Access resources. Trace the deployment response for this endpoint configuration and compare it with the AWS CDK construct documentation; done means the endpoint deploys successfully or reports a useful cause instead of a null InternalFailure.

Written by the indexing model from the issue text.