Contributions
Integrations before and after Private Publishing
We need to share an API with an external group of people and I know that I need to configure these users as Consumers since they will just be looking at the API contents and trying out the GET method. My dilemma is that we need to generate a Production AWS gateway from the Development one (Development environment can be volatile plus the data retrieved won't be live). Q) Can we keep the same integration but simply change the Dev Swagger Hub User environment access and secret keys to those of the Production Swagger Hub User to generate a Production API Gateway? Q) What happens to the integration and api key in Authorize once an API has been published? (Is the API key securely locked and does the integration disappear?)) Thanks Thanks392Views0likes0CommentsRe: Using AWS Gateway API keys for testing real servers on Swagger UI
OK @chichepo, I solved it but there must be a better way of making the server URL more covert. The steps for testing this is relatively easy to set up: In the sever:: url area of the definitions file, just add the full gateway endpoint including the region. Put the gateway's API key into the Authorized lock button next to the servers drop down and close its dialog box as soon as you add the api key. Test your access endpoints.1KViews1like0CommentsRe: Using AWS Gateway API keys for testing real servers on Swagger UI
Yeschichepo I have enclosed a screen scrape of a Get test in Postman. PREVIEW I can test in both AWS API Gateway to test the proxy lambda and I can also use Postman. I was successfully able to Get , Post, and Put data from and to my Dynamo DB table. I verified it worked. HOwever, for some reason even though I have Authorized the API Key and the bottom of the Swagger Hub definitions YAML contains the Gateways APP ID, I still have not been able to test the live AWS Development Gateway service. Maybe I am still doing something incorrect? Thaks chichepo PREVIEW chichepowrote: Hitonante727 you tried with postman and it works?1KViews0likes1CommentUsing AWS Gateway API keys for testing real servers on Swagger UI
HI I just need to make sure that I am understanding the testing for Swagger Hub UI: I have generated an AWS Gateway key for testing internally and also using Postman externally and want to test real servers on Swagger UI not mocks. I then take that API Key and in Swagger Hub UI I click on the authorize button that is near the upper right hand corner next to the server drop downs. I close the Authorize dialog box (See photo below) In my YAML definitions I have declared both my developer and production urls I added my security scheme and security definition. Q) I am wondering why I receive 403 forbidden responses when I test any of my access methods (Post, Get, Put) if these steps are correct? ThanksSolved1.1KViews0likes3CommentsRe: Issue Creating AWS API Gateway with API definitions due to a UnMarshall Exception Return Code 400
The issue is probably resides in the Swagger Hub User Role. If you create an Integration for AWS API Gateway with Lambda Sync:, Do not add any info for the Role step. Verify that the gateway adds all your paths from the OpenAPI3 Swagger YAML definition Create you Lambda separately since the ones auto-generated are mockups anyway. The take a look at the permissions on your SwaggerHug user and see which ones will allow Lambda generation if that's prefered.431Views0likes0Comments