There are 0 repository under efs-volume topic.
Terraform module to provision AWS Backup, a fully managed backup service that makes it easy to centralize and automate the back up of data across AWS services such as EBS volumes, RDS databases, DynamoDB tables, EFS file systems, and AWS Storage Gateway volumes.
A terraform module for a highly available Jenkins deployment.
Deploy Infrastructure website on AWS and integrating with EFS using Terraform
Deploy wordpress docker app to AWS ec2 to 2 AZ using Terraform and setting up from backup via Ansible.
Faster storage operations using multiprocessing in python
ECS-EFS integration with Terraform
CI-CD pipeline through Github workflow actions present in .github folder along with Terraform code present in modules folder & environment/demo folder
Automated Pipeline with Github actions + Terraform + Docker Containers to deploy the Bitcoin Image in AWs
Distributed TensorFlow training using Amazon SageMaker
Amazon Web Services is a subsidiary of Amazon that provides on-demand cloud computing platforms and APIs to individuals, companies, and governments, on a metered pay-as-you-go basis. In this repositorie you'll find notes and explanion in pt-BR about the examination AWS Solutions Architect by Andre Iacono.
AWS CDK Python example of a serverless JupyterHub/Pluto with persistent storage on EFS.
EFS terraform module
It is an application with PHP with a database. I just tell you the project baseline. There was a website like (blog.com) that website is used for upload blogs/images and there have millions of clients and heavy traffic from viewers. But it's another portion like (blog.com/admin) this section is only used, admins/creators. So, there has no heavy traffic with this URL. So, I have designed to structure to separate servers for viewers and creators through application load balancers (Target group). I know all you have doubts about how to manage the creator's database sync with the viewer's database. I overcome with used an RDS-Master server for admin/creators and I have built RDS-Replica servers to connect with viewers servers. Once, if you have any updates on creators/admin servers you saved a replica stop script on your master server and first stop the replica script then update your kinds of stuff on the master server, and then you can start the server through the same script as the scripts run time new data sync to the viewer's server and new database changes applied to the replica servers.