diff --git a/docs/images/integrations/aws/integrations-amplify-app-id.png b/docs/images/integrations/aws/integrations-amplify-app-id.png new file mode 100644 index 000000000..a89fa3eaf Binary files /dev/null and b/docs/images/integrations/aws/integrations-amplify-app-id.png differ diff --git a/docs/images/integrations/aws/integrations-amplify-env-console.png b/docs/images/integrations/aws/integrations-amplify-env-console.png new file mode 100644 index 000000000..5ad0ba792 Binary files /dev/null and b/docs/images/integrations/aws/integrations-amplify-env-console.png differ diff --git a/docs/integrations/cloud/aws-amplify.mdx b/docs/integrations/cloud/aws-amplify.mdx new file mode 100644 index 000000000..e22fb8008 --- /dev/null +++ b/docs/integrations/cloud/aws-amplify.mdx @@ -0,0 +1,72 @@ +--- +title: "AWS Amplify" +description: "Learn how to sync secrets from Infisical to AWS Amplify." +--- + +Prerequisites: + +- Set up and add envars to [Infisical Cloud](https://app.infisical.com) + +## Sync Secrets On Build + +This approach enables the synchronization of secrets from Infisical to AWS Amplify during container build. + + + + Go to your project settings in the Infisical dashboard to generate a [service token](/documentation/platform/token). This service token will allow you to authenticate and fetch secrets from Infisical. Once you have created a service token with the required permissions, you’ll need to provide the token to the CLI installed in your Docker container. + + + ![aws amplify env console](../../images/integrations/aws/integrations-amplify-env-console.png) + 1. In the Amplify console, choose App Settings, and then select Environment variables. + 2. In the Environment variables section, select Manage variables. + 3. Under Variable, enter the key **INFISICAL_TOKEN**. For the value, enter the generated service token from the previous step. + 4. Click save. + + + In the prebuild phase, add the command in AWS Amplify to install the Infisical CLI. + + ```yaml + build: + phases: + preBuild: + commands: + - sudo curl -1sLf 'https://dl.cloudsmith.io/public/infisical/infisical-cli/setup.rpm.sh' | sh && yum install -y infisical + ``` + + + You can now pull secrets from Infisical using the CLI and save them as a `.env` file. To do this, modify the build commands. + + ```yaml + build: + phases: + build: + commands: + - INFISICAL_TOKEN=${INFISICAL_TOKEN} + - infisical export --format=dotenv > .env + - + ``` + + + +## Sync Secrets Using AWS SSM Parameter Store + +[Environment secrets](https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html#environment-secrets) are similar to environment variables, but they are AWS Systems Manager (SSM) Parameter Store key-value pairs that can be encrypted. By using Infisical AWS SSM integration, you can synchronize secrets from Infisical to SSM, which in turn synchronizes secrets to your AWS Amplify environment secrets. + + + + Follow the [Infisical AWS SSM Parameter Store Integration Guide](./aws-parameter-store) to set up Infisical integration, up to the path option. + + + ![amplify app id](../../images/integrations/aws/integrations-amplify-app-id.png) + 1. Open your AWS Amplify App console. + 2. Go to **Actions >> View App Settings** + 3. The App ID will be the last part of the App ARN field after the slash. + + + You need to set the path in the format `/amplify/[amplify_app_id]/[environment]` as the path option in AWS SSM Parameter Infisical Integration. + + + + +Accessing an environment secret during a build is similar to accessing environment variables, except that environment secrets are stored in `process.env.secrets` as a JSON string. + diff --git a/docs/mint.json b/docs/mint.json index 8335c8bd6..ee77917a7 100644 --- a/docs/mint.json +++ b/docs/mint.json @@ -277,7 +277,8 @@ "group": "AWS", "pages": [ "integrations/cloud/aws-parameter-store", - "integrations/cloud/aws-secret-manager" + "integrations/cloud/aws-secret-manager", + "integrations/cloud/aws-amplify" ] }, "integrations/cloud/vercel",