This article explains how reading S3 Parquet data in Vertica using short-lived credentials over extended periods (e.g., ~60 minutes) may lead to failures due to credential expiration. It provides guidance on managing session duration and credential refresh strategies.
Environment
- Vertica Analytics Platform
- External tables using S3 Parquet data
- Short-lived AWS credentials
- Long-running queries or workloads
Situation
A user attempts to read S3 Parquet data continuously for approximately 60 minutes using short-lived AWS credentials. The workload spans multiple credential refresh windows, resulting in potential read failures or access errors.
