Hi all, Considering suggested ideas I'm +1 for adding user role details in endpoints page and ARNs in the resources page. Also, +1 for adding a wizard for the first time users.
As @Kasun Thennakoon <kasu...@wso2.com> mentioned it'll be better if we could list down the ARNs when the user sets user role details(endpoint). Hence I have to add a new operation to API-M REST API to get ARNs using user role details. Thanks On Mon, Sep 2, 2019 at 9:40 AM Kasun Thennakoon <kasu...@wso2.com> wrote: > Hi All, > > While I'm +1 to add a wizard for onboarding users to AWS backend APIs, but > I don't think we should add a separate menu for AWS backends, IMHO we can > have AWS related configurations in the endpoints section. and have the ARN > selection in resources page? > I think it will be convenient for the user when we provide one place to > manage the resource-related attributes. > So in summary: > > > - Keep the backend related (AWS key/secret configurations) in the > endpoints page > - Provide the ARN selection option in resources page per operation, So > users will recognize that their API operations will be mapped to there ARNs > using the configurations in endpoints(backend configs). > > We could introduce a wizard for the first time users when the choose AWS > endpoint and walk through them in the process. > > Regards > ~KasunTe > -- *Binod Karunanayake* | Software Engineering Intern | WSO2 Inc. (m) +94716611642 | (e) bi...@wso2.com [image: http://wso2.com/signature] <http://wso2.com/signature>
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
