Security News
pnpm 10.0.0 Blocks Lifecycle Scripts by Default
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
route53-updater
Advanced tools
The route53-updater
module can update a Route 53 Record Set with the current IP or hostname of an machine. This can be useful if you have a single instance running in an auto scaling group. During startup of the EC2 instance you call the route53-updater
to update the DNS entry to the new IP.
Port of https://github.com/taimos/route53-updater/
Install route53-updater globally
npm install route53-updater -g
Create or update the DNS CNAME entry for test.yourdomain.com to point to the public hostname of the EC2 instance
route53-updater --action UPDATE --hostedZoneName yourdomain.com. --recordSetName test.yourdomain.com.
or
route53-updater --action UPDATE --hostedZoneId XXXXXXXXXXXXX --recordSetName test.yourdomain.com.
The assumed defaults are
route53-updater --action UPDATE --hostedZoneName yourdomain.com. --recordSetName test.yourdomain.com. --ttl 60 --metadata public-hostname --type CNAME
By default route53-updater will lookup the IP address against the Amazon Metadata Service. If running outside Amazon, you can use the first IPv4 address on an interface by specifying an --iface option
route53-updater --action UPDATE --hostedZoneName yourdomain.com. --recordSetName test.yourdomain.com. --iface eth0
The instance running the script needs the following IAM access rights:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Stmt1424083772000",
"Effect": "Allow",
"Action": [
"route53:ChangeResourceRecordSets",
"route53:ListHostedZones",
"route53:ListResourceRecordSets",
"route53:GetChange"
],
"Resource": [
"*"
]
}
]
}
Supported parameters:
action
: String (required)
UPDATE
: Update the DNS entry (delete if exists, and create)DELETE
: Create the DNS entryCREATE
: Create the DNS entry or fail if existinghostedZoneName
: String (either hostedZoneName
or hostedZoneId
is required) - Name of your hosted zone (Must end with an dot!)hostedZoneId
: String (either hostedZoneName
or hostedZoneId
is required) - Id of your hosted zonerecordSetName
: String (required) - Name of your record set (XYZ.hostedZoneName)ttl
: Number (optional, default 60) - TTL in secondsmetadata
: String (optional, default public-hostname) - Metadata field to use as the value (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html)type
: String (optional, default CNAME) - Type of record set (http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html)No breaking changes!
Added "route53:GetChange"
to the IAM access rights.
FAQs
Updating a Route53 resource set with meta-data of EC2 instance
The npm package route53-updater receives a total of 15 weekly downloads. As such, route53-updater popularity was classified as not popular.
We found that route53-updater demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.