For automated Snowpipe loading from Amazon S3, object-created events from the S3 bucket are sent through Amazon SNS. Snowflake subscribes to the notification channel and receives information about newly created files.
The pipe is created with automatic ingestion enabled, normally by specifying AUTO_INGEST = TRUE and associating the pipe with the applicable SNS topic.
A scheduled task is not required because the cloud event notification triggers ingestion. Calling the Snowpipe REST API is an alternative ingestion approach, not part of the cloud-messaging configuration described in the question. External tables and materialized views are unrelated to the required Snowpipe notification flow.
References:
Snowflake Documentation - Automating Snowpipe for Amazon S3: https://docs.snowflake.com/en/user- guide/data-load-snowpipe-auto-s3 Snowflake SQL Reference - CREATE PIPE: https://docs.snowflake.com/en/sql-reference/sql/create-pipe
==

USE SECONDARY ROLES ALL: Activates all granted secondary roles for the current session.
USE SECONDARY ROLES NONE: Deactivates all active secondary roles for the current session.
Incorrect Commands: The options referencing " RESUME " , " SUSPEND " , and " ADD " are not valid commands in the context of secondary roles.
References:
Snowflake Documentation (USE SECONDARY ROLES): https://docs.snowflake.com/en/sql-reference/sql
/use-secondary-roles.html

When querying VARIANT columns (such as JSON), the values are often returned as strings . To convert them to usable SQL types, users must apply the CAST() function (e.g., CAST(column:value AS NUMBER)).
Reference:
Snowflake Docs: Querying Semi-Structured Data