Skip to content

Commit d52b6ff

Browse files
palpatimjosefaidt
andauthored
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 38d9cb8 commit d52b6ff

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
@@ -133,7 +133,7 @@ Amplify creates an [AWS Lambda](https://aws.amazon.com/lambda) function using a
133133

134134
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:
135135

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

0 commit comments

Comments
 (0)