KinesisAnalyticsv2 API error. VPC Configuration is expecting an JSON Array instead got JSON Object

### Name of the resource

AWS::CloudFormation::Stack

### Resource name

kinesisdatanalayticsv2

### Description

we did provided two sets of attributes to the Kinesis Analytics VPC Configuration - However it thrown us an error stating they are JSON Objects and not Arrays

The entire execution happened via Cloudformation YAMLs

Properties validation failed for resource KinesisAnalyticsFlinkApplication with message: #/ApplicationConfiguration/VpcConfigurations: expected type: JSONArray, found: JSONObject

Below is the definition of the resource (All the references are working well. aws cfn validation did not report any errors )

KinesisAnalyticsFlinkApplication:
Type: AWS::KinesisAnalyticsV2::Application
Properties:
RuntimeEnvironment: FLINK-1_11
ServiceExecutionRole: !Sub ${KinesisAnalyticsServiceRole.Arn}
ApplicationConfiguration:
ApplicationCodeConfiguration:
CodeContent:
S3ContentLocation:
BucketARN: !Ref FlinkApplicationS3BucketArn
FileKey: !Ref FlinkApplicationS3Path
CodeContentType: ZIPFILE
EnvironmentProperties:
PropertyGroups:
- PropertyGroupId: FlinkApplicationProperties
PropertyMap:
EventTime: true
# InputStreamName: !Sub ${KinesisStream}
Region: !Sub ${AWS::Region}
- PropertyGroupId: StreamProcessorProperties
PropertyMap:
application.greet.keyword: Welcome
FlinkApplicationConfiguration:
MonitoringConfiguration:
ConfigurationType: CUSTOM
LogLevel: INFO
MetricsLevel: TASK
ParallelismConfiguration:
ConfigurationType: 'CUSTOM'
Parallelism: 1
ParallelismPerKPU: 1
ApplicationSnapshotConfiguration:
SnapshotsEnabled: true
VpcConfigurations:
SecurityGroupIds:
- !Ref ApplicationSecurityGroup
- !Ref ApplicationSecurityGroup1
SubnetIds:
- !Ref PrivateSubnet1
- !Ref PrivateSubnet2

### Other Details

_No response_

Start with the reported AWS::KinesisAnalyticsV2::Application definition and the VpcConfigurations validation error. Compare the documented resource shape with the YAML shown, then determine whether the roadmap project has a relevant coverage or schema entry; done means the expected array structure or service discrepancy is clearly documented.

Written by the indexing model from the issue text.