Deploy to EC2 in private subnet
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
Following the AWS best practices EC2 instances should be in a private subnet without a public ip. PM2 deploy command is using a .pem file and hosts to deploy to instances. That is not possible in this situation.
Is it this something that can be considered to use something like EC2 Instance Connect Endpoint with pm2 to connect to private instances ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing PM2's deploy command and its use of the .pem file and hosts. Review how EC2 Instance Connect Endpoint could provide access to instances in a private subnet, then define the required configuration and verify that deployment works without a public IP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, node.js
- Domain
- cli, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100