You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the linked article schema changes took place in metadata catalog by Security Lake version 2.0, however the current repository contains references to the formal version related QS objects with suffixes like "vpc_flow_1_0" (from amazon_security_lake_glue_db_eu_central_1.amazon_security_lake_table_eu_central_1_vpc_flow_1_0).
Current reference value should be "amazon_security_lake_glue_db_eu_central_1.amazon_security_lake_table_eu_central_1_vpc_flow_2_0".
Dear Dev team,
According to the linked article schema changes took place in metadata catalog by Security Lake version 2.0, however the current repository contains references to the formal version related QS objects with suffixes like "vpc_flow_1_0" (from amazon_security_lake_glue_db_eu_central_1.amazon_security_lake_table_eu_central_1_vpc_flow_1_0).
Current reference value should be "amazon_security_lake_glue_db_eu_central_1.amazon_security_lake_table_eu_central_1_vpc_flow_2_0".
https://docs.aws.amazon.com/security-lake/latest/userguide/subscriber-query-examples2.html
Can you please fix it this issue in order to the included CDK implementation be compatible with the platform?
Thank you for your assist and sooner issue resolution in advance.
Cheers & Happy Development,
Norbi
The text was updated successfully, but these errors were encountered: