# Page Not Found

The URL `aws/securing/secure-data-in-transit-and-at-rest-in-aws` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Secure data in transit and at rest in AWS](https://wiki.songer.pro/interviewing/aws/securing/how-do-you-secure-data-in-transit-and-at-rest-in-aws.md)
- [Secure data stored in the AWS with encryption](https://wiki.songer.pro/interviewing/aws/securing/how-do-you-secure-data-stored-in-the-aws-with-encryption.md)
- [Secure an application running on an EC2 instance](https://wiki.songer.pro/interviewing/aws/securing/how-can-you-secure-an-application-running-on-an-ec2-instance.md)
- [Ensure the security of user data stored in AWS](https://wiki.songer.pro/interviewing/aws/securing/what-steps-do-you-take-to-ensure-the-security-of-user-data-stored-in-aws.md)
- [Protect against security breaches on AWS?](https://wiki.songer.pro/interviewing/aws/securing/how-do-you-protect-against-security-breaches-on-aws.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://wiki.songer.pro/interviewing/aws/securing/how-do-you-secure-data-in-transit-and-at-rest-in-aws.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://wiki.songer.pro/interviewing/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://wiki.songer.pro/interviewing/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/interviewing/aws/securing/how-do-you-secure-data-in-transit-and-at-rest-in-aws.md`).

You may also use `Accept: text/markdown` header for content negotiation.