Missing “Select Region” Element in AWS Lambda Onboarding instructions

[dalnoki]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/aws-serverless

SDK Version

Framework Version

Link to Sentry event

Reproduction Example/SDK Setup

Steps to Reproduce

In Step 2 of the onboarding flow for Configure AWS Lambda (Node) SDK (https://orgSlug.sentry.io/onboarding/setup-docs/?installationMethod=lambdaLayer), the instructions say:

“Start off by selecting the region you want to deploy your Lambda function to.”

However, in the actual UI there is no region selection element and no ARN is provided.
This makes it impossible to complete the step without leaving the onboarding flow.

Our docs however include a region selector and returns the correct ARN.

Expected Result

The onboarding flow should provide a way to obtain the correct region-specific ARN - either by showing a region selector with the matching ARN or by linking directly to the ARN generator page.

Actual Result

The onboarding shows no region selector, provides no ARN, and forces users to leave the flow to find the correct information elsewhere.

Additional Context

No response

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1226

[Lms24]

Thanks for reporting! Yeah, we need to fix this in the onboarding flow. We'll take a quick look and if necessary ask the TET team to take a look.

[Lms24]

lol we blocked our own request due to missing CORS settings 😅
So we already have a component in place that fetches the ARNs from our release registry. But since we instrument the request with our SDK, we attach our tracing headers. The registry's CORS settings block these headers. Let's see how we fix this

[Lms24]

Can confirm that this is fixed: