Main Page: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
Welcome to the Renan Wiki. This platform is a high availability, production grade demonstration of how we can transform traditional web applications into modern, cloud native architectures. At its heart, this project represents a deliberate move away from the old reliance on physical hardware toward a serverless, security first mindset. This transition is brought to life through Infrastructure as Code concepts, using AWS Fargate to take manual server patching off the table. Beyond just being serverless, the platform is built with hardened security in mind. The entire stack is isolated within a custom Virtual Private Cloud (VPC) and uses enterprise grade encryption to protect data at every stage, including AES 256 storage encryption on RDS and enforced SSL/TLS for anything moving across the network. | Welcome to the Renan Wiki. This platform is a high availability, production grade demonstration of how we can transform traditional web applications into modern, cloud native architectures. At its heart, this project represents a deliberate move away from the old reliance on physical hardware toward a serverless, security first mindset. This transition is brought to life through Infrastructure as Code concepts, using AWS Fargate to take manual server patching off the table. Beyond just being serverless, the platform is built with hardened security in mind. The entire stack is isolated within a custom Virtual Private Cloud (VPC) and uses enterprise grade encryption to protect data at every stage, including AES 256 storage encryption on RDS and enforced SSL/TLS for anything moving across the network. | ||
To really get the most out of what I have built here, I encourage you to jump in and interact with the wiki's dynamic features. Feel free to contribute to our knowledge base or create your own pages to see how the containerized environment handles real activity. You can also test out the integration between the application and Amazon S3 by uploading your own files or images, just remember to upload them first and then use the standard wikitext syntax to display them. To keep everything organized and secure, you'll want to enable page protection on your contributions to make sure your hard work is preserved. Finally, you can see our "security at the edge" in action by noticing how the Application Load Balancer automatically handles encrypted HTTPS connections and directs everyone to the proper renanwiki.org domain. It's a setup designed to bridge the gap between complex network engineering and a smooth, user friendly experience. | To really get the most out of what I have built here, I encourage you to jump in and interact with the wiki's dynamic features. Feel free to contribute to our knowledge base or create your own pages to see how the containerized environment handles real activity. You can also test out the integration between the application and Amazon S3 by uploading your own files or images, just remember to upload them first and then use the standard wikitext syntax to display them. To keep everything organized and secure, you'll want to enable page protection on your contributions to make sure your hard work is preserved. | ||
Finally, you can see our "security at the edge" in action by noticing how the Application Load Balancer automatically handles encrypted HTTPS connections and directs everyone to the proper renanwiki.org domain. | |||
It's a setup designed to bridge the gap between complex network engineering and a smooth, user friendly experience. | |||
Revision as of 05:44, 28 April 2026
Welcome to the Renan Wiki. This platform is a high availability, production grade demonstration of how we can transform traditional web applications into modern, cloud native architectures. At its heart, this project represents a deliberate move away from the old reliance on physical hardware toward a serverless, security first mindset. This transition is brought to life through Infrastructure as Code concepts, using AWS Fargate to take manual server patching off the table. Beyond just being serverless, the platform is built with hardened security in mind. The entire stack is isolated within a custom Virtual Private Cloud (VPC) and uses enterprise grade encryption to protect data at every stage, including AES 256 storage encryption on RDS and enforced SSL/TLS for anything moving across the network. To really get the most out of what I have built here, I encourage you to jump in and interact with the wiki's dynamic features. Feel free to contribute to our knowledge base or create your own pages to see how the containerized environment handles real activity. You can also test out the integration between the application and Amazon S3 by uploading your own files or images, just remember to upload them first and then use the standard wikitext syntax to display them. To keep everything organized and secure, you'll want to enable page protection on your contributions to make sure your hard work is preserved. Finally, you can see our "security at the edge" in action by noticing how the Application Load Balancer automatically handles encrypted HTTPS connections and directs everyone to the proper renanwiki.org domain. It's a setup designed to bridge the gap between complex network engineering and a smooth, user friendly experience.
Consult the User's Guide for information on using the wiki software.