Copilot Content Exclusion Example

Search for a command to run...

No comments yet. Be the first to comment.
This series explores some of the best practices around securing your AI usage with Copilot being the main focus.
How to get all us-east-1 Public IP Addresses for EC2 If necessary - Mac (install brew, then install jq) and Linux below that: /bin/bash -c "$(curl -fsSL raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" brew install jq sudo apt install jq...
More details here: AWS Site-to-Site VPN Documentation I recently had to configure a Site-to-Site VPN connection between an AWS VPC and an Azure VNet. The appliance on the other end was able to ultimately talk to an EC2 instance after messing around w...

This is sort of a chicken and egg situation where the egg has to come before the chicken. The state file is important and it maintains your current state of all your Azure resources created via Terraform. There are many ways to get started, but this ...

3 ways to test DNS in the command line

Copilot has been great for our org, but it's a good idea to use a Content Exclusion policy to your GitHub repository settings to specify content that Copilot should ignore. With the increased use of the GitHub Copilot agent comes the need to keep things more secure. Read more from GitHub Docs
The first lines ensures that this is applied to all repos in your GitHub org. I like this method as well because it clearly defines line by line what should be excluded.
"*":
- "**/.env"
- "**/.env.*"
- "**/.aws/credentials"
- "**/.github/secrets/"
- "**/secrets.json"
- "**/*_history" # Shell history files
# --- Terraform files ---
- "**/.terraform/"
- "**/*.tfvars"
# --- Cetificate files ---
- "**/*.pem"
- "**/*.key"
- "**/*.p12"
- "**/*.crt"
# --- .NET files ---
- "**/secrets.json"
- "**/appsettings.*.json"
- "**/*.pubxml"
- "**/*.pubxml.user"
- "**/*.user"
- "**/*.suo"
# --- Kubernetes files ---
- "**/secrets/*.yaml"
- "**/sealed-secrets/*.yaml"
- "**/.kube/config"