Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

beachcomberdigital's avatar

Envoyer and AWS using EC2

Been using envoyer for a bit now with success when paired with Forge and Linode, however I now have a project that changes my deployment pattern to Amazon AWS EC2 servers and just Envoyer.

I'm mainly running into problems getting the servers to provisioned correctly so that envoyer can connect to handle its deployment status. So far I've:

  • created an "envoyer" user account in IAM to run deployment tasks
  • created an "envoyer" group currently with the AmazonEC2FullAccess policy (i'm sure its generous with access and appreciate any suggestions on which policies are actually appropriate
  • created an "envoyer" security group account with the envoyer.io ip addresses (per the envoyer docs) whitelisted.

Where (i think) i am stuck: when i added the EC2 ip address to envoyer's server list, it gave me the public ssh key to to the server to close the loop - but i seem to be lost on how exactly to do that. I really wish there was some step-by-step guidelines on how to use AWS with Envoyer - hoping someone here can shed some light.

Any chance someone can outline the remaining steps that i may have missed - like i'm a five year old? :) . I'm still new to AWS which may be part of the challenge too.

Very much appreciated!

0 likes
0 replies

Please or to participate in this conversation.