- Newest
- Most votes
- Most comments
Hi Safwan,
I'll try to clarify your concerns regarding AWS Athena and Lambda function role name limits.
For the AWS Athena maximum number of rows per query result page, the limit is set to 1000 rows. This is designed to optimize performance and manageability. To handle larger datasets in a single operation, consider utilizing the Athena API or CLI for pagination support, allowing you to programmatically retrieve and process data beyond the initial 1000 rows without needing to increase this limit directly.
Regarding the maximum length of role names for Lambda functions, which is capped at 64 characters, this limit is enforced by AWS to ensure consistency across services. There's no provision for extending this limit. A common workaround is to revise the naming strategy for auto-generated role names to ensure they remain within this limit. For roles that are exceeding this length, consider simplifying the naming convention or using abbreviations to fit the required constraints.
Both of these limits are integral to AWS service designs, focusing on maintaining a balance between flexibility and the underlying infrastructure's efficiency and security. For scenarios where these limits pose a challenge, adapting your implementation strategy is recommended.
Hope this helps!
Relevant content
- asked 2 years ago
- asked 2 months ago
- asked 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you for your response. Regarding the limitation on function names, we acknowledge and will adjust our application accordingly to fit within the prescribed constraints.
However, concerning the issue with AWS Athena's query result page limit, we are currently facing challenges despite utilizing the suggested solution. Some of our queries, particularly those requiring extensive data processing, are taking approximately 5 minutes solely to retrieve the data. Considering the additional time required for analyzing this data, the overall waiting period for our clients becomes excessively long.
In light of this, we kindly request your assistance in exploring alternative solutions. Our aim is to minimize the waiting time for our clients while ensuring efficient data retrieval and analysis processes. Any guidance or suggestions you can provide would be greatly appreciated.
Thank you for your attention to this matter. We look forward to your prompt assistance.
Best regards,