chore(aws): Add known issues/remarks for aws + express and infrastructure as code frameworks (#15472)

## DESCRIBE YOUR PR

This highlights common cases that might trip users up.

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [X] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## LEGAL BOILERPLATE

<!-- Sentry employees and contractors can delete or ignore this section.
-->

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

---------

Co-authored-by: Nicolas Hrubec <nico.hrubec@sentry.io>

Author: andreiborza

docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx

@@ -15,3 +15,19 @@ og_image: /og-images/platforms-javascript-common-troubleshooting.png
 Events might be missing right after a Lambda function coldstart. This is a [known issue](https://github.com/getsentry/sentry-javascript/issues/18107) which we are still investigating. Events are sent for subsequent function invocations.
 
 </Expandable>
+
+<Expandable permalink title="Span Names Show Lambda Function Name Instead of Request Path with Express">
+
+When using `@sentry/aws-serverless` with Express, span names are based on the AWS Lambda function name from the Lambda context, rather than the HTTP request path. This differs from `@sentry/node` behavior where span names show the request path.
+
+This is expected behavior for the AWS Lambda SDK. See the [related GitHub issue](https://github.com/getsentry/sentry-javascript/issues/15788) for more details.
+
+</Expandable>
+
+<Expandable permalink title="Missing Tracing Data when using Infrastructure as Code Frameworks (e.g. CDK, Serverless, SST, etc.)">
+
+When using Infrastructure as Code frameworks (e.g. CDK, Serverless, SST, etc.) that bundle everything into a single file, third-party libraries that need to be instrumented by Sentry (such as `express`, `pg`, etc.) must be marked as external and excluded from the bundle. If these libraries are bundled, Sentry cannot instrument them properly, resulting in missing tracing data.
+
+You can include them via a Lambda layer so that your function can still access them at runtime.
+
+</Expandable>