revamp ses

Author: HarshCasper

src/content/docs/aws/services/ses.md

@@ -1,6 +1,5 @@
 ---
 title: "Simple Email Service (SES)"
-linkTitle: "Simple Email Service (SES)"
 description: Get started with Amazon Simple Email Service (SES) on LocalStack
 tags: ["Free", "Base"]
 persistence: supported
@@ -11,12 +10,12 @@ persistence: supported
 Simple Email Service (SES) is an emailing service that can be integrated with other cloud-based services.
 It provides API to facilitate email templating, sending bulk emails and more.
 
-The supported APIs are available on the API coverage page for [SESv1]({{< ref "coverage_ses" >}}) and [SESv2]({{< ref "coverage_sesv2" >}}).
+The supported APIs are available on the API coverage page for [SESv1](), and [SESv2]().
 
-{{< callout "Note" >}}
+:::note
 Users on Free plan can use SES V1 APIs in LocalStack for basic mocking and testing.
 For advanced features like SMTP integration and other emulation capabilities, please refer to the Ultimate plan.
-{{< /callout >}}
+:::
 
 ## Getting Started
 
@@ -30,38 +29,43 @@ A verified identity appears as part of the 'From' field in the sent email.
 
 A singular email identity can be added using the `VerifyEmailIdentity` operation.
 
-{{< command >}}
-$ awslocal ses verify-email-identity --email [email protected]
+```bash
+awslocal ses verify-email-identity --email [email protected]
 
-$ awslocal ses list-identities
+awslocal ses list-identities
 {
     "Identities": [
         "[email protected]"
     ]
 }
-{{< /command >}}
+```
 
-{{< callout >}}
+:::note
 On AWS, verifying email identities or domain identities require additional steps like changing DNS configuration or clicking verification links respectively.
 In LocalStack, identities are automatically verified.
-{{< /callout >}}
+:::
 
 Next, emails can be sent using the `SendEmail` operation.
 
-{{< command >}}
-$ awslocal ses send-email \
+```bash
+awslocal ses send-email \
         --from "[email protected]"   \
         --message 'Body={Text={Data="This is the email body"}},Subject={Data="This is the email subject"}'   \
         --destination '[email protected]'
+```
+
+The following output is displayed:
+
+```bash
 {
     "MessageId": "labpqxukegeaftfh-ymaouvvy-ribr-qeoy-izfp-kxaxbfcfsgbh-wpewvd"
 }
-{{< /command >}}
+```
 
-{{< callout >}}
+:::note
 In LocalStack Community, all operations are mocked and no real emails are sent.
 In LocalStack Pro, it is possible to send real emails via an SMTP server.
-{{< /callout >}}
+:::
 
 ## Retrieve Sent Emails
 
@@ -70,56 +74,61 @@ Sent messages can be retrieved in following ways:
 - **API endpoint:** LocalStack provides a service endpoint (`/_aws/ses`) which can be used to return in-memory saved messages.
     A `GET` call returns all messages.
     Query parameters `id` and `email` can be used to filter by message ID and message source respectively.
-    {{< command >}}
-$ curl --silent localhost.localstack.cloud:4566/_aws/ses?email=[email protected] | jq .
-{
-  "messages": [
+
+    ```bash
+    curl --silent localhost.localstack.cloud:4566/_aws/ses?[email protected] | jq .
+    ```
+
+    The following output is displayed:
+
+    ```bash
     {
-      "Id": "dqxhhgoutkmylpbc-ffuqlkjs-ljld-fckp-hcph-wcsrkmxhhldk-pvadjc",
-      "Region": "eu-central-1",
-      "Destination": {
-        "ToAddresses": [
-          "[email protected]"
-        ]
-      },
-      "Source": "[email protected]",
-      "Subject": "This is the email subject",
-      "Body": {
-        "text_part": "This is the email body",
-        "html_part": null
-      },
-      "Timestamp": "2023-09-11T08:37:13"
+      "messages": [
+        {
+          "Id": "dqxhhgoutkmylpbc-ffuqlkjs-ljld-fckp-hcph-wcsrkmxhhldk-pvadjc",
+          "Region": "eu-central-1",
+          "Destination": {
+            "ToAddresses": [
+              "[email protected]"
+            ]
+          },
+          "Source": "[email protected]",
+          "Subject": "This is the email subject",
+          "Body": {
+            "text_part": "This is the email body",
+            "html_part": null
+          },
+          "Timestamp": "2023-09-11T08:37:13"
+        }
+      ]
     }
-  ]
-}
-    {{< /command >}}
+    ```
     A `DELETE` call clears all messages from the memory.
     The query parameter `id` can be used to delete only a specific message.
-    {{< command >}}
-    $ curl -X DELETE localhost.localstack.cloud:4566/_aws/ses?id=dqxhhgoutkmylpbc-ffuqlkjs-ljld-fckp-hcph-wcsrkmxhhldk-pvadjc
-    {{< /command >}}
-- **Filesystem:** All messages are saved to the state directory (see [filesystem layout]({{< ref "filesystem" >}})).
+
+    ```bash
+    curl -X DELETE localhost.localstack.cloud:4566/_aws/ses?id=dqxhhgoutkmylpbc-ffuqlkjs-ljld-fckp-hcph-wcsrkmxhhldk-pvadjc
+    ```
+- **Filesystem:** All messages are saved to the state directory (see [filesystem layout](/aws/capabilities/config/filesystem)).
     The files are saved as JSON in the `ses/` subdirectory and named by the message ID.
 
 ## SMTP Integration
 
 LocalStack Pro supports sending emails via an SMTP server.
 To enable this, set the connections parameters and access credentials for the server in the configuration.
-Refer to the [Configuration]({{< ref "configuration#emails" >}}) guide for details.
+Refer to the [Configuration](/aws/capabilities/config/configuration/#emails) guide for details.
 
-{{< callout "tip" >}}
+:::note
 If you do not have access to a live SMTP server, you can use tools like [MailDev](https://github.com/maildev/maildev) or [smtp4dev](https://github.com/rnwood/smtp4dev).
 These run as Docker containers on your local machine.
 Make sure they run in the same Docker network as the LocalStack container.
-{{< /callout >}}
+:::
 
 ## Resource Browser
 
 LocalStack Web Application provides a resource browser for managing email identities and introspecing sent emails.
 
-<img src="ses-resource-browser.png" alt="SES Resource Browser" title="SESE Resource Browser" width="900"/>
-<br/>
-<br/>
+![SES Resource Browser](/images/aws/ses-resource-browser.png)
 
 The Resource Browser allows you to perform following actions:
 - **Create Email Identity**: Create an email identity by clicking **Create Identity** and specifying the email address.