dmost714

var build_no = 30;

dmost714

import { Authenticator, View, Image, Text, Heading, useTheme, useAuthenticator } from '@aws-amplify/ui-react'
import { BrowserRouter } from "react-router-dom"
import { Routes, Route } from "react-router-dom"
import AppRoutes from "./AppRoutes"
import MarketingPage from './routes/MarketingPage'
import logoSvg from './logo.svg'

function App() {
  const { route, user, signOut } = useAuthenticator(context => [context.route, context.user, context.isPending])

dmost714

const getCampaign = /* GraphQL */ `
  query GetCampaign($id: ID!) {
    getCampaign(id: $id) {
      id
      status
      title
      postcardDesignId
      landingPage
      createdAt
      updatedAt

dmost714

const axios = require('axios')
const gql = require('graphql-tag')
const graphql = require('graphql')
const { print } = graphql

const listContacts = /* GraphQL */ `
  query ListContacts(
    $filter: ModelContactFilterInput
    $limit: Int
    $nextToken: String

dmost714

How to expose an Amplify Custom category as an ENVIRONMENT variable in an Amplify Lambda

These are notes I wrote to myself, but if they help you please leave a note and let me know. And any tips are certainly appreciated.

TL;DR

To reference your custom category resource from your lambda:

1. amplify add custom to make custom category "XXX"
2. Add Outputs to XXX-cloudformation-template.json

dmost714

Amplify Lambda URLs

TL;DR

With AWS Amplify, you can use amplify add api to create REST APIs using API Gatway and Lambdas. However, I wanted to try out the new Lambda Url feature for a simple public webhook.

Steps involved

1. Make your "Webhook" Lambda
2. Create a custom reasource "Webhooks".
3. Give it access to the "Webhook" lambda

dmost714

[
  {
    "Action": [
      "SES:SendEmail"
    ],
    "Resource": [
      {
        "Fn::Join": [
          ":",
          [

dmost714

In the front-end package.json file, add 'amplify:xxx' lines to the script section for each lambda that uses typescript.
Amplify will call those automatically when you build. You can `yarn amplify:nameOfYourLambda` to manually build the lambda.
  "scripts": {
    "dev": "vite",
    "build": "tsc && vite build",
    "test": "vitest",
    "test:ui": "vitest --ui",
    "coverage": "vitest run --coverage",
    "preview": "vite preview",
    "amplify:nameOfYourLambda": "cd amplify/backend/function/nameOfYourLambda/src && yarn && yarn build;cd -",

dmost714

{
  "AWSTemplateFormatVersion": "2010-09-09",
  "Parameters": {
    "env": {
      "Type": "String"
    }
  },
  "Resources": {
    "SNSTOPIC": {
      "Type": "AWS::SNS::Topic",

dmost714

import { DynamoDBClient, PutItemCommand, PutRequest } from "@aws-sdk/client-dynamodb"
import { BatchWriteCommandInput, BatchWriteCommandOutput, DynamoDBDocumentClient, QueryCommand, QueryCommandInput, QueryCommandOutput } from "@aws-sdk/lib-dynamodb"
import { BatchWriteCommand } from "@aws-sdk/lib-dynamodb"
import internal from 'node:stream'

// https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ReservedWords.html

const ddbClient = new DynamoDBClient({})

const marshallOptions = {