terraform-aws-django
aws-cli
Our great sponsors
terraform-aws-django | aws-cli | |
---|---|---|
8 | 48 | |
27 | 14,885 | |
- | 1.3% | |
0.0 | 9.8 | |
over 1 year ago | 3 days ago | |
HCL | Python | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-aws-django
-
My Infrastructure as Code Rosetta Stone - Deploying the same Django application on AWS ECS Fargate with CDK, Terraform and Pulumi
terraform-aws-django
-
This is how you want to manage your Terraform modules
+1 for release-please. Here's an example of how I maintain my module's changelog with 13 lines of yaml in a GitHub Action using release-please: https://github.com/briancaffey/terraform-aws-django/blob/main/.github/workflows/release-please.yml
-
Scenario based question for DevOps Engineers out there
Here are some other questions that would be good to ask about the infrastructure: * What AWS account will this run in? Who has access to that account? Are SSO permission sets used? * What DNS records will be used to access the frontend and the backend? Are these two services accessed via the same record URL? For example, all do you to only send example.com/api/* traffic to the backend and then send all other example.com/* to the Angular frontend? Or do you want to use api.example.com for all API traffic and example.com for the Angular site. What about non-prod environments? Will you use alpha.example.com for a staging environment for a non-prod environment named alpha? * You mentioned that the team will be using Terraform heavily, how will you be splitting up your modules? When you run Terraform's apply command, does it update a single set of infrastructure for your entire application, or do you run terraform apply several times for different groups of resources, such as a networking stack (with VPC), data stack (with RDS) and application stack (for ECS resources), for example? You will probably use terraform remote state to manage these different logical components and the data dependencies they have between each other. * Another related question is how you are running pipelines for Terraform? I would use something like GitHub Actions. When a pipeline runs, you should see the output of a terraform plan stage and then the pipeline should pause for manual approval after the changes have been reviewed. This can be done with GitHub environments, for example, and other CI/CD tools can also do this. * What happens when you need to change an environment variable? This can be a complicated question. Environments that are not secrets might be stored in a terraform.tfvars file, or might be stored in environment variables in your pipeline in the form of TFVAR{name}, so this implies that changing an environment variable is an infrastructure change. You want to keep your infrastructure deployments separate from your application deployments. If you are using ECS, you probably want to use ignore_changes for the task definitions referenced by the services. This will create a new task definition, but it will not be used by the new services. When you do an application update, the service may use this new task definition with the updated environment variable. * Another question: does anyone on the team need direct access to the database? Is there a bastion host used in the infrastructure that can people can connect to the DB with via port forwarding? I hope these questions are helpful. I have thought about a lot of these and have been exploring their answers with an open source project focused on a containerized, database-backed Python web app (made with Django) that I deploy on AWS with ECS Fargate, and I have another repo with Terraform modules for deploying application infrastructure. Here's the application repo: https://github.com/briancaffey/django-step-by-step and here is the Terraform module repo: https://github.com/briancaffey/terraform-aws-django. Please let me know if you have any questions
-
The appropriate way to deploy full stack app on ECS
Here's the Terraform code: https://github.com/briancaffey/terraform-aws-django
-
Django Docker Containers and good example projects
Here's one of my practice projects that I use for learning and practicing deployments. It is a simple microblogging application that implements the application both using the MTV paradigm and the REST/SPA paradigm. My deployment efforts are narrowly focused on ECS Fargate, one of several ways to run containers on AWS, and I also focus on using Terraform and GitHub Actions to both build infrastructure and deploy new versions of the application. terraform-aws-django is repo that contains all of the Terraform code that is used to build the application. Happy to answer any questions about these repos!
-
Best practices for manually accessing interactive shells and databases for web apps running on ECS Fargate
Here is the repo where I have things set up in Terraform: https://github.com/briancaffey/terraform-aws-django/tree/main/modules/internal/bastion
-
Setting up ad hoc development environments for Django applications with AWS ECS, Terraform and GitHub Actions
terraform-aws-django
-
Having issues running terraform init in a directory containing only a tfvars file that references remote git repo source
source = "git::https://github.com/briancaffey/terraform-aws-django.git?ref=v0.0.2" region="us-east-1" ...
aws-cli
-
Top 10 CLI Tools for DevOps Teams
The AWS CLI is a must-have tool if your team relies on Amazon Web Services. It lets you effortlessly interact with AWS services, orchestrate resource management, and automate tasks from the comfort of your terminal. Once you get used to the tool, you'll notice how convenient and quick it is to fit into your processes – especially compared to going through AWS's web-based user interface.
-
My First Impressions of Nix
Just for your consideration, the network effect is very real with package managers, too:
https://search.nixos.org/packages?channel=23.05&show=awscli2 is 2.11.27 (even on the "unstable" channel), versus https://formulae.brew.sh/formula/awscli#default that is 2.12.1, which correctly is the most current (https://github.com/aws/aws-cli/tags)
- It is not possible to install ARM64 AWS CLI
- [Engineering_Stuff] S3FS-FUSE - Permet de monter votre lien de seau S3 / Minio vers votre répertoire local
-
s3fs-fuse - allows to mount your s3/minio bucket link to your local directory
s3fs allows Linux, macOS, and FreeBSD to mount an S3 bucket via FUSE(Filesystem in Userspace). s3fs makes you operate files and directories in S3 bucket like a local file system. s3fs preserves the native object format for files, allowing use of other tools like AWS CLI.
-
AWS Announces Open Source Mountpoint for Amazon S3
AFAIK it's still a Python package: https://github.com/aws/aws-cli/tree/2.11.6
-
AWS S3 storage class invalid - DEEP_ARCHIVE - why?
Check CLI version, it looks like the earliest version that had DEEP_ARCHIVE support was 1.16.133 (https://github.com/aws/aws-cli/commit/55efab102f774ef17bf51ad32e939e4e03a5ff8a)
- Can we run AWS CLI to generate reports for all regions?
-
Event Based System with Localstack (Elixir Edition): Uploading files to S3 with PresignedURL's
And this is the init_localstack.sh file content, a unique thing about localstack its that you can move all strings like an aws-cli tool, also the container deletes all the content and config once the container stops, so the script file must create all the resources that you need from Localstack
-
You can update phone number using CLI
It can? I created a pull request for this that hasn't been merged yet: https://github.com/aws/aws-cli/pull/6365
What are some alternatives?
terraform-aws-ecs-alb-service-task - Terraform module which implements an ECS service which exposes a web service via ALB.
rclone - "rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
pulumi-aws-django - A Pulumi package for deploying Django applications to AWS using ECS Fargate and other managed services
boto3 - AWS SDK for Python
terraform-aws-ad-hoc-environments - Shared resources for supporting multiple ad hoc environments in an AWS account for software development teams
SAWS - A supercharged AWS command line interface (CLI).
briancaffey
httpie - 🥧 HTTPie CLI — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.
ps-menu - Simple powershell menu to render interactive console menu
thefuck - Magnificent app which corrects your previous console command.
cdk-django - A CDK library that provides high-level constructs for hosting Django applications on AWS
aws-vault - A vault for securely storing and accessing AWS credentials in development environments