How to use this script:
route53-zone-migrate.sh -s aws_source_profile -t aws_target_profile -d domain_name
-s, Uses a AWS CLI profile name for Route53 zone source account. -t, Uses a AWS CLI profile name for Route53 zone target account.
|# Script to replace EC2 instances in an ECS cluster's auto-scaling group after|
|# changing the AMI or instance type in the launch configuration. It|
|# checks for instances with the incorrect AMI or type, scales up the|
|# auto-scaling group with replacement instances, then drains the tasks|
|# from the old instances.|
|# Usage: aws-vault exec profile-name -- python3 replace_ecs_cluster_instances.py --group=asg-name --cluster=ecs-cluster-name --count=3|
$ git checkout --orphan NEWBRANCH $ git rm -rf .
--orphan creates a new branch, but it starts without any commit. After running the above command you are on a new branch "NEWBRANCH", and the first commit you create from this state will start a new history without any ancestry.
You can then start adding files and commit them and they will live in their own branch. If you take a look at the log, you will see that it is isolated from the original log.
Keeping the system updated is vital before starting anything on your system. This will prevent people to use known vulnerabilities to enter in your system.
sudo apt-get update sudo apt-get upgrade sudo apt-get autoremove sudo apt-get autoclean
|**Try to run**|
|Enter your token code: 123456|
|**Try exporting to an environment variable**|
|Copy, paste, and execute the 3-line export command output by the script.|