CDK Node.js EC2 Instance Construct
This is a CDK Construct for creating an EC2 instance with Node.js installed.
You can use Node.js as soon as the EC2 instance starts.
Usage
Install the package:
npm install cdk-node-ec2-instance
Use it in your CDK stack:
import { NodeEc2Instance } from 'cdk-node-ec2-instance';
import * as ec2 from 'aws-cdk-lib/aws-ec2';
declare const vpc: ec2.IVpc;
// You can configure all properties of the EC2 instance
new NodeEc2Instance(this, 'Instance', {
vpc,
instanceType: ec2.InstanceType.of(ec2.InstanceClass.T3, ec2.InstanceSize.NANO),
machineImage: new ec2.AmazonLinuxImage({
generation: ec2.AmazonLinuxGeneration.AMAZON_LINUX_2023,
}),
nodeJsVersion: 'v20.13.1', // Optional property. Default is installing the latest LTS version
});
After the stack is deployed, you can SSH into the EC2 instance and use Node.js:
$ ssh ec2-user@<public-ip>
$ node --version
v20.13.1
user data
Installation of Node.js is done by user data script. You can see the script in the src/index.ts file.
nodejsUserData.addCommands(
'touch ~/.bashrc',
'curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash',
'source ~/.bashrc',
'export NVM_DIR="$HOME/.nvm"',
'[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"',
`nvm install ${props.nodeJsVersion ?? '--lts'}`,
// Note that the above will install nvm, node and npm for the root user.
// It will not add the correct ENV VAR in ec2-user's environment.
`cat <<EOF >> /home/ec2-user/.bashrc
export NVM_DIR="/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
EOF`);
Ofcourse, you can customize the additional user data script by calling instance.userData.addCommands() method.
declare const instance: NodeEc2Instance;
// install VScode for linux
instance.userData.addCommands(
'sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc',
'echo -e "[code]\nname=Visual Studio Code\nbaseurl=https://packages.microsoft.com/yumrepos/vscode\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc" | sudo tee /etc/yum.repos.d/vscode.repo > /dev/null',
'sudo dnf check-update',
'sudo dnf install -y code',
);
Metadata
Release files for node-ec2-instance 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| node-ec2-instance-0.0.7.tar.gz | 41.7 kB | Without provenance | Details for node-ec2-instance-0.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| node_ec2_instance-0.0.7-py3-none-any.whl | Python 3 | none | any | Details for node_ec2_instance-0.0.7-py3-none-any.whl |
Total release size: 82.0 kB
Release files / node-ec2-instance-0.0.7.tar.gz
| Download URL | node-ec2-instance-0.0.7.tar.gz |
|---|---|
| Size | 41.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8e22496f74f1ec310e0d9f3aa8bac8fdb27849803b87cb5d5ec33be2181f17b
|
|
BLAKE2b-256 checksum How to use checksums |
46a8e8d7c129c6b9677b664ddc3f18201df22babc5ef61104753481982505a5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Release files / node_ec2_instance-0.0.7-py3-none-any.whl
| Download URL | node_ec2_instance-0.0.7-py3-none-any.whl |
|---|---|
| Size | 40.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab3fbb79011e0d7271002b6d6166315c1d15e2f000b6e64c81115e4d377c4a82
|
|
BLAKE2b-256 checksum How to use checksums |
6a97f9cc45773dde43be82089da202ba4f5fcf23aa47f0d16f39d096717fdff0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Security for node-ec2-instance 0.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.