Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Jeff Finley
    @quickliketurtle
    :-)
    Riccardo Sirigu
    @ricsirigu
    Yes @quickliketurtle , the private storage that amplify creates with the prefix /private/${cognito-identity.amazonaws.com:sub}/ could be ok, but I forgot to mention that the cognito admin group must be able to write in both of those "folders".
    And I don't know how to model those requirements with a policy. Or am I overcomplicating things?
    Daniel S. Dantas
    @dantasfiles

    I have the documentation schema.graphql

    type Customer @model @key(fields: ["email"]) {
      email: String!
      username: String
    }

    I run amplify mock api and run the mutation

      createCustomer(input: {email: "bob@bob.com", username: "bob"}) {
        email
        username
      }

    I get the result:

    Error while executing Local DynamoDB
    ...
    ValidationException: One of the required keys was not given a value
    ah, amplify mock api gets confused if you change tables and keys too often, I had to manually delete the mock dynamodb table file and let amplify mock api rebuild a new one
    Patrick Harding
    @senorpatricio
    @BrandonShega did you get it figured out? we use SAML with Okta in our application.
    Daniel S. Dantas
    @dantasfiles

    in the example from the GraphQL transform documentation:

    type Customer @model
      @key(name: "byRepresentative", fields: ["accountRepresentativeID", "id"], queryField: "byRepresentative") {
      id: ID!
      accountRepresentativeID: ID!
    ...
    }

    Is there any difference between that and this different GSI (with no sort key "id")?

    type Customer @model
      @key(name: "byRepresentative", fields: ["accountRepresentativeID"], queryField: "byRepresentative") {
      id: ID!
      accountRepresentativeID: ID!
      ...
    }
    I'm trying to understand the details of the @key directive
    Gino-Casolaro
    @Gino-Casolaro
    Hey guys so I've been trying to get my web application up on Amplify-Cli but can't get it to render properly. I'm using handlebars and all of my files are .hbs files. Meaning when it asks for the main file (usually index.html) I instead try index.hbs but this doesn't render at all. Am I doing something wrong or is this not possible with hbs files?
    Daniel S. Dantas
    @dantasfiles
    so from this blog post, particularly the Find all songs for a SingerId example, it looks like the 2nd gsi with field accountRepresentativeID alone would be fine for that use case
    Wouter van den Broek
    @wbroek
    @Gino-Casolaro Maybe look at the redirects section in Amplify CLI There you can alter the behavoir of what files/extensions do/go to
    Amir Hajimirsadeghi
    @amirhajimirsadeghi
    Has anybody successfully set up aws amplify function with babel? Would love to look through an example
    Amir Hajimirsadeghi
    @amirhajimirsadeghi
    Or more specifically, has anybody successfully deployed a typescript express lambda?
    Alex T
    @alexdev888
    Is anybody test aws-amplify-angular with angular 9?
    is it working?
    Armon Raphiel
    @araphiel
    Hey good people, can anyone help answer questions about team IAM access?
    1. Does the Amplify Console require specific IAM actions?
    2. What is the best practice for allowing team CLI usage in a restricted environment?
      For example, can this list of IAM settings for CLI be restricted to things created by this IAM group
    1. Can you deploy lambda functions without the CLI? YAML / Console only?
    Jun
    @Jun711
    @araphiel yes, you can deploy lambda function via Console but there is a size limit of the code and dependencies that you are using
    Armon Raphiel
    @araphiel
    thanks @Jun711 is it as simple as adding an backend/api folder to the repo? or are you running the amplify cli during the codebuild stage?
    Brandon Shega
    @BrandonShega
    When using federated identity, what is the point of refreshing the underlying token that is used with federation? Doesn't amplify just give AWS credentials until logged out?
    Brandon Shega
    @BrandonShega
    <sigh> I cannot find any documentation around using okta with a user pool and identity pool in Amplify.
    Daniel S. Dantas
    @dantasfiles
    if I made a change to a category like auth in the CLI but haven't amplify pushed it yet, is there any way to restore that category (and only that category)?
    Wouter van den Broek
    @wbroek
    @dantasfiles you can pull what is on AWS but not by category. Not using git (other version control)?
    Daniel S. Dantas
    @dantasfiles
    @wbroek yeah, that's what I ended up doing, going back in time
    Wouter van den Broek
    @wbroek
    Cannot live without it (Git that is) :)
    Brandon Shega
    @BrandonShega
    Ya, I've followed all of that, I have it working, I just don't think it's working the right way.
    I just don't know what I'm supposed to do with amplify at this point, do I need to refresh Okta tokens? Do I need to refresh cognito user pool tokens? How often do I call federatedSignIn?
    Brandon Shega
    @BrandonShega
    Should I even be using a User Pool?
    Wouter van den Broek
    @wbroek
    @BrandonShega what are you trying to achieve then? Using other parts of (AWS) Amplify?
    Brandon Shega
    @BrandonShega
    Our web app uses AWS Lambda, so I have to get AWS credentials from an identity pool.
    Wouter van den Broek
    @wbroek
    You need a authenticated user to execute the lambda? Or can anyone do this?
    Brandon Shega
    @BrandonShega
    AuthenticatedUser
    well, an authenticated role
    The strange thing is that I think I'm using the user pool incorrectly. I have Okta as an IDP for cognito user pool and then user pool as an IDP for cognito identity pool. Seems like I should be able to skip that middle portion.
    tedhopps
    @tedhopps
    @BrandonShega are you just trying to use third party auth Okta solution for your user pool or do you actually need an identity pool to access AWS resources
    Alvin Crespo
    @alvincrespo

    Hey all! I'm trying to add the @key directive to an existing model, but getting the following error:

    ✖ An error occurred when pushing the resources to the cloud
    
    Attempting to edit the key schema of the ImageTable table in the Image stack.
    An error occured during the push operation: Attempting to edit the key schema of the ImageTable table in the Image stack.

    I'm not sure why that's happening?

    My updated schema.graphql:

    // amplify/backend/api/chainappterparty/schema.graphql
    type Image @model @key(fields: ["createdAt"]) {
      id: ID!
      long: String!
      lat: String!
      image: String!
      createdAt: String!
    }

    Previous schema.graphql:

    type Image @model {
      id: ID!
      long: String!
      lat: String!
      image: String!
    }
    Vinícius Montanheiro
    @vmontanheiro
    Guys I need your help about Federated SignIn with Google, I did setup in my React Native project without Expo.
    I received an error "Cannot read property 'redirectSignIn' of undefined", so I defined the redirectSignIn and redirectSignOut but
    I don't know what I need to do there, I got the Google informations but after the app opens a external browser and try access an URL.
    I already define the URL callback in the Google Cloud and Cognito but I still don't know how to configure the redirectSignIn and redirectSignOut in my app. Someone have an example ?
    Please.
    Daniel S. Dantas
    @dantasfiles
    @alvincrespo I don't think you can change the primary key (which was id but you're trying to make it createdAt) on a deployed dynamodb table
    Alvin Crespo
    @alvincrespo
    Ah ok. I was basically trying to add sorting by createdAt to my queries. Any recommended way?
    I was basing the above on this stack overflow answer, which I'm guessing is wrong? https://stackoverflow.com/questions/56488192/how-to-sort-on-a-field-in-list-query-in-aws-amplify
    Alvin Crespo
    @alvincrespo
    Guessing the only way is to recreate it.
    Daniel S. Dantas
    @dantasfiles
    @alvincrespo that example is fine, so you can use @key(fields: ["id", "createdAt"])to make id the partition key and createdAt the sort key
    I don't know if amplify will let push that change or if it'll make you remove the table first and recreate it because it's still a key change
    Alvin Crespo
    @alvincrespo
    and copy over any data
    Alvin Crespo
    @alvincrespo
    @dantasfiles Yeah no dice. I was able to run amplify publish and it runs, but som resources fail to deploy. Some resolvers fail, and then this one comes up:
    Resource Name: Image-uf7b2g3cyzbafnojjoi6x35gj4 (AWS::DynamoDB::Table)
    Event Type: update
    Reason: CloudFormation cannot update a stack when a custom-named resource requires replacing. Rename Image-uf7b2g3cyzbafnojjoi6x35gj4-master and update the stack again.
    Brandon Shega
    @BrandonShega
    @tedhopps we need an identity pool for AWS resources
    Pedro Bergamini
    @pedrobergamini
    hey!
    is there any way to work with kinesis video streams through amplify?
    Ghost
    @ghost~5acbf3c3d73408ce4f9502fd
    Hey does anyone have advice on the following: i'm running 'amplify update auth' in the CLI, in the docs it says it prompts you to setup federated logins but in the current version they are not there. how do i setup google auth for in js. All the google stuff is done, i just need to add some amplify code i think to get the sign in and popup going.
    Seth Mikkelsen
    @SolveForTech
    Super scrub here... I have several lambda functions in my project... when I perform an amplify push... it erases the contents of my lambda functions and resets them. How do I properly include updates to my functions for amplify?
    Wouter van den Broek
    @wbroek
    @SolveForTech use the clioud formation template for setting al your settings