Skip to content

Commit ec8f000

Browse files
palpatimjosefaidt
andcommitted
Update src/pages/[platform]/build-a-backend/data/connect-to-existing-data-sources/connect-postgres-mysql-database/index.mdx
Co-authored-by: josef <[email protected]>
1 parent deef7bd commit ec8f000

File tree

1 file changed

+1
-1
lines changed
  • src/pages/[platform]/build-a-backend/data/connect-to-existing-data-sources/connect-postgres-mysql-database

1 file changed

+1
-1
lines changed

src/pages/[platform]/build-a-backend/data/connect-to-existing-data-sources/connect-postgres-mysql-database/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ Amplify creates an [AWS Lambda](https://aws.amazon.com/lambda) function using a
121121

122122
However, if your database uses a custom or self-signed SSL certificate, you can upload the PEM-encoded public CA certificate to your Amplify project as a secret when you generate the database configuration, and specify that secret when generating the schema from your database:
123123

124-
```
124+
```bash title="Terminal" showLineNumbers={false}
125125
npx ampx sandbox secret set CUSTOM_SSL_CERT < /path/to/custom/ssl/public-ca-cert.pem
126126
npx ampx generate schema-from-database --connection-uri-secret SQL_CONNECTION_STRING --ssl-cert-secret CUSTOM_SSL_CERT --out amplify/data/schema.sql.ts
127127
```

0 commit comments

Comments
 (0)