Inquiry Regarding AWS Service Limits

0

I am writing to inquire about two specific limits within AWS services and to explore the possibility of adjusting them to better suit our requirements.

  1. Maximum Number of Rows Per Query Result Page: We have noticed that the maximum number of rows that can be retrieved per page of query results, within AWS Athena service, is currently limited to 999. However, our use case requires the ability to retrieve a larger number of rows in a single page. Could you please provide guidance on whether it's possible to increase this limit or if there are alternative solutions available?
  2. Maximum Length of Role Name for Lambda Functions: In our development process, we encountered a limitation where the auto-generated role name for a Lambda function exceeds the maximum allowable length of 64 characters. This constraint has caused some challenges in our implementation. Is there a possibility to extend the maximum length of the role name for Lambda functions beyond 64 characters, or are there recommended workarounds for managing this limitation effectively?

We greatly appreciate your assistance in addressing these inquiries. Any insights or recommendations you can provide would be invaluable for our project. Thank you for your attention to this matter. We look forward to your prompt response. Best regards,

Safwan
asked a month ago117 views
1 Answer
0
Accepted Answer

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!

profile picture
answered a month ago
profile pictureAWS
EXPERT
reviewed a month 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,

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions