GRANT ALL PRIVILEGES ON db_name.* to 'new_user'@'hostname' IDENTIFIED BY 'password';

Can’t take much credit for this how to guide. I followed the post on the forum (below) and can confirm that it does work.

Tools/Materials needed:

• Star head screw drivers (large and small head)
• Small flat head screw driver
• 4 core electrical cable
• Cable stripper

Steps to install:

**Make sure power to boiler is turned off at the fuse box and tested**

1. Hook up electrical cable to heat link as shown:

N – Neutral – Blue wire

L – Live – Brown wire

2 – (Common) – Grey wire

3 – (Call for heat) – Black wire

I can’t take any credit for this script. Rich Adams created it and shared kindly on github:

https://gist.github.com/richadams/384020d6e4e6d4f400d7

Steps:

1. Login to AWS account

2. IAM > Users > Username > Security Credentials > Create Access Key

3. Add ‘Access key Id’ and ‘Secret access key’ to relevant section in the script

4. Make sure script is executable (chmod +x)

5. Run script, outputting security groups to text file i.e.

sh aws_security_group_details.sh >> aws_all_regions_secgroups.txt

6. Remove access key from AWS > IAM if not longer required

Code below in case the version is removed from github:

openssl rsa -in input_file -out output_file

The following IP ranges need allowed through your firewall on the port you have specified in the health check:

{
"ip_prefix": "54.183.255.128/26",
"region": "us-west-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.228.16.0/26",
"region": "eu-west-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.232.40.64/26",
"region": "sa-east-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.241.32.64/26",
"region": "us-west-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.243.31.192/26",
"region": "us-east-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.244.52.192/26",
"region": "us-west-2",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.245.168.0/26",
"region": "us-west-2",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.248.220.0/26",
"region": "ap-northeast-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.250.253.192/26",
"region": "ap-northeast-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.251.31.128/26",
"region": "ap-southeast-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.252.79.128/26",
"region": "ap-southeast-2",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.252.254.192/26",
"region": "ap-southeast-2",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "54.255.254.192/26",
"region": "ap-southeast-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "107.23.255.0/26",
"region": "us-east-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "176.34.159.192/26",
"region": "eu-west-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{
"ip_prefix": "177.71.207.128/26",
"region": "sa-east-1",
"service": "ROUTE53_HEALTHCHECKS"
},
{

Official IP Ranges from AWS – https://ip-ranges.amazonaws.com/ip-ranges.json