Overview
Fully Managed Geospatial Stack Geospatial Data Science, Visualization & Development Runs the full stack of PostgreSQL/PostGIS, CartoDB and Jupyter We take care of backups, upgrades & performance so you can focus on work
Highlights
- Fully Managed Geospatial Stack
- PostgreSQL/PostGIS, CartoDB and Jupyter
- Geospatial Data Science, Visualization & Development
Details
Typical total price
$1.484/hour
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Instance type | Product cost/hour | EC2 cost/hour | Total/hour |
---|---|---|---|
t2.small | $0.14 | $0.023 | $0.163 |
t2.medium | $0.20 | $0.046 | $0.246 |
t2.large | $0.24 | $0.093 | $0.333 |
t2.xlarge | $0.35 | $0.186 | $0.536 |
t2.2xlarge | $0.60 | $0.371 | $0.971 |
t3.small | $0.14 | $0.021 | $0.161 |
t3.medium | $0.20 | $0.042 | $0.242 |
t3.large | $0.24 | $0.083 | $0.323 |
t3.xlarge | $0.50 | $0.166 | $0.666 |
t3.2xlarge | $1.00 | $0.333 | $1.333 |
Additional AWS infrastructure costs
Type | Cost |
---|---|
EBS General Purpose SSD (gp2) volumes | $0.10/per GB/month of provisioned storage |
Vendor refund policy
1 week refund policy if usage is less than 10 USD
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
New Release: PostgreSQL 13 / PostGIS 3 Based on latest AWS Linux 2 Image
Additional details
Usage instructions
See this link for latest instructions: https://gist.github.com/sabman/e4b1a8b03f5249d07d8c26f76da8a6d4
A publicly accessible domain name is required. One way to do this is to point your DNS record to an elastic IP attached to the new instance. To do this after launching your instance do the following
-
- Attach Elastic IP to the instance
-
- Set up DNS record to point to Elastic IP. Make sure the DNS is resolving
-
- SSH into your instance ssh ec2-user@ur-domain.com
-
- Use the following init script replacing environment variables
https://gist.github.com/sabman/e4b1a8b03f5249d07d8c26f76da8a6d4