aws-amplify / aws-amplify/amplify-hosting
[Request] show public endpoint of Amplify Functions
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
currently, in the Functions section of the Amplify Console, i can see "Functions added" and "Logs", then links to AWS Lambda and CloudWatch. This looks like a private lambda, with no indication of API Gateway on top of it. I have no idea what the actual public endpoint looks like.
**Describe the solution you'd like**
This detail could be inferred from implicit knowledge but the console should also make it explicit.
As a frontend developer, this is useful as:
- I might want to ping my endpoint without using [`API.get`](https://docs.amplify.aws/lib/restapi/fetch/q/platform/js#get-requests)
- it takes out the guesswork of knowing what the public endpoint path is so i can code against it
- I can click on it as a very rudimentary form of testing (i know that i have to do further testing inside the AWS Lambda UI or with `amplify mock`)


Contributor guide
Research direction
Start in the Functions section of the Amplify Console and review how its existing AWS Lambda and CloudWatch links are presented. Trace where API Gateway information could be surfaced for a function, then verify that the public endpoint is visible and usable as a clickable link without relying on API.get.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100