Integrate an AWS RDS Database with Your Velo Site

I am able to view AWS/MySQL DB content fine in preview mode, but not on the live site. I'm presuming the issue is that "permission config not defined". Where is that setting in the AWS configuration? I've gone over everything a 1000 times. 😫 Please help. Thanks!

I am facing the below Issue.

Everything given in configuration has been done except the below instance role in Security. It is showing could not find any roles where as in IAM Console it is declared.

@Maxim Polski can you tell me where I am wrong?

Hi folks!

Can I have some additional clarity on configuring permissions when integrating an AWS RDS db? Specifically, within my AWS Secrets Manager, can you provide a clearer example of a Key and a clearer example of a stringified Value when doing permissions? And what, if anything, should be done to modify the Configuration settings inside of the App Runner? I have not been able to get Permissions to work, and it seems as if it should be simple.

Thanks!

Nick

hi Maxim Polski

I managed to solve it , recreated the whole thing from scratch and it worked fine. Mapped in Wix.

The issue now is, how do it use that mapped DB in wix code for wix queries? I tried to use it in normal ways using wixdata.query("database") and it gave me error as below

i managed to get the AppRunner role using the udpate - thanks for that but i am getting below message now, what could be wrong?

Hi, I am trying to connect AWS RDS Database following the guide above, but get the following result, any clue?

Below is my config, App Runner

IAM

Secrets

DB

Hey Luke, AppRunnerRDSAccessRole is the default role for app runner services, it should be exists in every AWS account, but in case it doesn't, a new role that will work with AppRunner can be created. There are 2 ways to create a new role: 1. Creating a new role via AWS-CLI 2. Editing existing role to work with AppRunner service

Creating a new role via AWS-CLI:

1. Create a file called trust-policy.json, and paste the next trust relationships specifies:

{
    "Version": "2012-10-17",
    "Statement": [
      {
        "Effect": "Allow",
        "Principal": {
          "Service": "tasks.apprunner.amazonaws.com"
        },
        "Action": "sts:AssumeRole"
      }
    ]
  }

2. Open your terminal in the directory where trust-policy.json is stored and use the create-role command.

aws iam create-role --role-name velo-external-db-adapter --assume-role-policy-document file://trust-policy.json 

3. Then you should see the new role in the roles list and in the app runner configuration screen under security - instance role list, don't forget to attach the needed permissions.

Editing existing role to work with AppRunner service: 1. Create new role, no matter to what aws service 2. Then look for it in the role list and click on it 3. Click on the Trust relationships tab, and click on edit trust relationship. 4. Paste the next Policy Document:

{
    "Version": "2012-10-17",
    "Statement": [
      {
        "Effect": "Allow",
        "Principal": {
          "Service": "tasks.apprunner.amazonaws.com"
        },
        "Action": "sts:AssumeRole"
      }
    ]
  }

5. Click on Update Trust Policy 6. Attach the needed permission (according to the docs) That's it, you should see the role in app runner configuration screen under the security - instance list.

Let us know if you succeeded

Hi Marlowe,

Any idea why there might only be 3 roles available and it doesn't seem to include the AppRunnerRDSAccessRole?

Any help gratefully received! :)

Luke