Need AWS Appsync/Amplify API GraphQL schema and custom resolver or lambda expert -- 2
Budget: $30 – $250 AUD
I am looking for an AWS Appsync/Amplify API GraphQL expert wizard who knows how to design relational schemas and custom resolvers or lambdas to help me manage data and permissions for my project.
Main issues:
- bulk (with CSV) invitations of users, how to store them and how best to do it with these services
- storing status of invitation and displaying it in a users table that shows users and invited users and their status (pending / active) - ideally without having to merge the results of a list query to two separate tables.
- making a user an admin over one or more other documents in other tables (CRUD without a schema directive specific enough so we need to use fields from the user document or some other table)
I have the entities and schema in mind as well as a lot of the access patterns but I need help with custom business logic to authorise and deny certain actions based on individual field values of different documents and any suggestions on improving the design.
Skills and experience needed for this job include:
- Familiar with the latest v2 transformer API, including @primaryKey, @index, @hasMany, @hasOne, etc.
- Strong knowledge and experience with AWS Appsync/Amplify API
- Expertise in designing custom GraphQL schemas
- Proficiency in building custom resolvers and lambda functions
- Familiarity with scalable applications
If you have the necessary skills and experience, please reach out to discuss the project further.
Main issues:
- bulk (with CSV) invitations of users, how to store them and how best to do it with these services
- storing status of invitation and displaying it in a users table that shows users and invited users and their status (pending / active) - ideally without having to merge the results of a list query to two separate tables.
- making a user an admin over one or more other documents in other tables (CRUD without a schema directive specific enough so we need to use fields from the user document or some other table)
I have the entities and schema in mind as well as a lot of the access patterns but I need help with custom business logic to authorise and deny certain actions based on individual field values of different documents and any suggestions on improving the design.
Skills and experience needed for this job include:
- Familiar with the latest v2 transformer API, including @primaryKey, @index, @hasMany, @hasOne, etc.
- Strong knowledge and experience with AWS Appsync/Amplify API
- Expertise in designing custom GraphQL schemas
- Proficiency in building custom resolvers and lambda functions
- Familiarity with scalable applications
If you have the necessary skills and experience, please reach out to discuss the project further.