Pahud Hsieh comments

Results 356 comments of


                                            Pahud Hsieh

Amplify Backend Not Rolled Back on Frontend Build Failure

Hi @frederikbendel, Thank you for raising this question about Amplify's deployment behavior. You've identified an architectural consideration in how Amplify handles multi-phase deployments. Currently, Amplify treats backend and frontend deployments...

Using a.model() results in a database table for each model, which is an anti pattern of dynamodb

## Current vs Expected Behavior ### Current Behavior ```typescript // Current Amplify Gen 2 approach - creates separate tables const schema = a.schema({ Facility: a.model({ id: a.id().required(), name: a.string().required(), }),...

auth rule with .identityClaim("email::sub") returns only sub in queries

Hi @OperationalFallacy, Thank you for reporting this issue! This appears to be a bug in how the Amplify Backend client handles composite identity claims during read operations. ## Problem Confirmed...

auth rule with .identityClaim("email::sub") returns only sub in queries

The bug seems to be at https://github.com/aws-amplify/amplify-category-api/blob/857b38379d770faa29b8af41c91a540db1ec4ffd/packages/amplify-graphql-auth-transformer/src/vtl-generator/ddb/resolvers/helpers.ts#L358-L382 ``` When identityClaim("email::sub") is used: • Stored value: "[email protected]::sub123" • This function splits on "::" → ["[email protected]", "sub123"] • Takes the last element...

Using secret() in lambda causes "window is not defined"

## Current vs Expected Behavior ### Current (Problematic) Implementation ```typescript // User's incorrect attempt - causes "window is not defined" error import { secret } from "@aws-amplify/backend"; export const handler:...

AWS Transcribe Streaming WebSocket Disconnects Immediately

Hi @brightversion1, Thank you for the detailed issue report. However, this issue is **not related to Amplify Backend** - it's about integrating with the AWS Transcribe Streaming WebSocket API directly....

AI conversation stream

Hi @smoockpp, Thank you for the detailed bug report. This appears to be a legitimate issue where Bedrock throttling errors are being incorrectly transformed into ValidationException errors about blank ContentBlock...

aws-eks: HelmChart values discards null values

This is new to me, I appreciate it. Do you have any public doc link of any public helm charts with `null` in its values that we can reference?

(@aws_cdk): Python: incompatible interface implementations due to differing function argument names

transferring to jsii

core: referencing arrays/lists when using `crossRegionReferences` fails with "SerializationException: Start of list found where not expected"

Reproducible. This seems a bug to me. Let me simplify it with this PoC VpcStack ```ts export interface VpcStackProps extends cdk.StackProps { readonly cidr?: string; } export class VpcStack extends...