simple example

Author: sommeeeer

pages/aws/config/simple_example.mdx

@@ -4,19 +4,7 @@ Here you can find the most common `open-next.config.ts` file examples that you c
 
 ## Streaming with lambda
 
-<Callout type="warning" emoji="⚠️">
-  AWS has a bunch of different implementations of streaming in production. You
-  might be lucky and have a fully working one, but you might have one that are
-  not suitable for production. Be aware that there is nothing to do to prevent
-  AWS from breaking your deployment (same code and same runtime might break from
-  one day to another) [Thread
-  1](https://discord.com/channels/983865673656705025/1230482660913184800)
-  [Thread
-  2](https://discord.com/channels/983865673656705025/1249368592558985247) <br />{' '}
-  <br /> On some AWS accounts the response can hang if the body is empty. There
-  is a workaround for that on OpenNext 3.0.3+, setting environment variable
-  `OPEN_NEXT_FORCE_NON_EMPTY_RESPONSE` to `"true"`. This will ensure that the
-  stream body is not empty. <br /> <br />
+<Callout type="info" emoji="ℹ️">
   If you have an issue with streaming send a message on [discord](https://discord.com/channels/1283128968140161065/1286094576788177059)
   and contact AWS support to let them know of the issue.
 </Callout>
@@ -34,6 +22,10 @@ const config = {
 export default config;
 ```
 
+Be aware that there has been some issues in the past with AWS breaking streaming from one day to another. This seems to be resolved now.
+[Thread 1](https://discord.com/channels/983865673656705025/1230482660913184800)
+[Thread 2](https://discord.com/channels/983865673656705025/1249368592558985247)
+
 ## Splitting the server
 
 ```ts
@@ -105,7 +97,7 @@ export default config;
 ## Bundle for a classic Node server (With function splitting)
 
 <Callout type="info" emoji="i">
-This is not implemented in sst yet. You'll have to use your own IAC construct to deploy this.
+This is not implemented in SST yet. You'll have to use your own IAC construct to deploy this.
 
 Be aware that this uses the exact same system for ISR/SSG as the default lambda setup. So it will have to have all the proper permissions and env variable to interact with S3, DynamoDB and SQS (Or whatever you override it with). You can see [here](/aws/inner_workings/components/server/node#special-overrides) for more details
 </Callout>