Skip to content

Update README.md - #4

Open
weisisheng wants to merge 1 commit into
baileytec-labs:mainfrom
weisisheng:patch-1
Open

weisisheng wants to merge 1 commit into
baileytec-labs:mainfrom
weisisheng:patch-1

Conversation

@weisisheng

Copy link
Copy Markdown
  • service quota issue which hampers dev

+ service quota issue which hampers dev
@sean-bailey

Copy link
Copy Markdown
Contributor

Thanks, @weisisheng ! I've not heard of those limitations yet. You wouldn't by any chance have a link to include in that line in the Readme to how to detect/change the hidden service limit, would you?

@weisisheng

weisisheng commented Jun 1, 2023 •

Copy link
Copy Markdown
Author

I deleted the stack and lost the lambda logs...

here are some quick refs on aws forum with responses by technical support:

https://repost.aws/questions/QUiKQO44fIT6OeVlDi8ejg8g/cannot-set-lambda-memory-larger-than-3gb

"Your account is still too new to access the full capacity of Lambda. It's recommended to new customers to use their account for up to six months before querying capacity access issues. I appreciate your patience while this issue was reviewed and I trust that it gives you more clarity on next steps. Thank you for choosing AWS!"

https://repost.aws/questions/QUKruWYNDYTSmP17jCnIz6IQ/questions/QUKruWYNDYTSmP17jCnIz6IQ/unable-to-set-lambda-memory-over-3008mb?

"Lambda functions with memory configuration greater than 3GB are currently unavailable for first time use in some regions. We are working on restoring this feature and mitigations are in progress. If you urgently require to use your function with memory greater than 3GB, please raise a support ticket and request that the limit get raised for your account."

FWIW, it took me 3 days to get approval and I am testing again soon.

HTH, V.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants