AWS SSM (Secure Session Manager) is now the preferred way to connect to apps and services within a private VPC from an external location.

For the uninitiated, AWS services are all accessibile from within AWS (of course dependent on your config) but are not typically accessible from outside of your AWS VPC. If one would like to take advantage of an AWS hosted service or instance special steps must be taken to help get outside apps access to things "inside" of the network.

For example, if one is using an aurora DB it is preferred to keep the DB server private and only allow access via a defined route. Traditionally this is done with a "bastion" or "jump" server to bridge the gap between external and internal traffic.

However, AWS and devs alike now recommend the use of AWS SSM
due to some key advantages:
- More durable setup, no worries re: ssh tunnel failure which can happen time to time.
- SSM manages auth, more secure than IP address + SSH key setup
- No need for SSH rotation/management. SSM does this automagically
- SSM server can live INSIDE the vpc which is HUGE, less exposure, improved protection from attacks

Let's get it done :)

Thanks!

From Wordfence:
We tested this issue using the Breeze plugin and found two problems.

This affects Wordfence’s two-factor authentication, if one or more users has set up two-factor authentication, and the reCAPTCHA feature, so using either or both of those features would be broken by Breeze modifying our script tags.

In Breeze’s “Advanced Options”, under “Delay JS inline scripts”, you can remove the line that says “nonce” to avoid having our script deferred.

You will also need to turn off the “JS” option under “Minifcation” in Breeze’s settings. We don’t know why they are modifying our script tag when minification is off but not on, but they have removed parameters that are necessary when loading Google’s api.js file.

Enabling JS minification may work on your site, but that has the potential to break other scripts. You can try it if you like, but be sure to test your site’s functionality if you do. Otherwise, we recommend disabling Breeze temporarily, until their next release that may fix these new issues.

Me: I tried the above suggestion which did not work. Cloudways have downgraded Breeze to an earlier version for me.

Can you please fix the compatibility issue.

Thank you

I know you have git web hook and git deployment via a pull but I would love to see more functionality here. For example Envoyer.io and runcloud.io offer no downtime full pull with ability to run commands such as composer update. Also to be able to store say 6 versions of recent pulls.

You could have a releases folder and a current folder with a symlink to the latest release. This would enable the new website to only go live one full set of files and commands have been executed before updating symlink. Also enables you to go back to an older version incase of a mistake.