website logo
⌘K
Servers operating systems
Ubuntu
0 Software by name
A
B
C
D
E
F
G
H
I
J
M
N
O
P
R
S
V
W
0Software by uses
Advertisement
Affiliates
Agency
Antivirus
Audio
Calendar
CDN
Chat
Content creation
DNS
Graphics
Fonts
Images
Integrations
Learning
Legal conditions
Link shorteners
Mail
Maps
Migration
Mobile
Photos
Privacy
Productivity
SAAS
Scanning
SEO
Security
Server
Sound
Teamwork
Vectors
Video
VPN
Web access
Web optimization
Web development
Wiki
Amazon
Route 53
Concepts
Link
CDN
Saas vs Plugin
Content creation others
Dokuwiki
Code
Regex
Deal`s history
Instoo
Brandmentions
Companyhub
Connected
Deskera
Gist formerly convert fox
Wpinfy
Design
Domains
Entrepreneurship in internet
Webs for SAAS
Google
Google Chrome
Google sheets
Lists of tools
Hosting
DNS
Recomendations
Server panels
Security
Hosting companies
Controlling systems for hosting
SSH
Office
Excel
Word
Resources
Speed
UX
Tricks to improve UX
Windows
Problems
Wordpress
Errors
Gutenberg
Themes
Users
Docs powered by archbee 
8min

Amazon lightsail

What is the difference between Amazon EC and Amazon lightsail

"Amazon lightsail is a option limited version of amazon ec. It does run in amazon ec, but gives you less configuration possibilities and it is cheaper than amazon ec.

Here is the technical explanation from an user called Michael in stack overflow

Testing¹ reveals that Lightsail instances in fact are EC2 instances, from the t2 class of burstable instances.

EC2, of course, has many more instance families and classes other than the t2, almost all of which are more "powerful" (or better equipped for certain tasks) than these, but also much more expensive. But for meaningful comparisons, the 512 MiB Lightsail instance appears to be completely equivalent in specifications to the similarly-priced t2.nano, the 1GiB is a t2.micro, the 2 GiB is a t2.small, etc.

Lightsail is a lightweight, simplified product offering -- hard disks are fixed size EBS SSD volumes, instances are still billable when stopped, security group rules are much less flexible, and only a very limited subset of EC2 features and options are accessible.

It also has a dramatically simplified console, and even though the machines run in EC2, you can't see them in the EC2 section of the AWS console. The instances run in a special VPC, but this aspect is also provisioned automatically, and invisible in the console. Lightsail supports optionally peering this hidden VPC with your default VPC in the same AWS region, allowing Lightsail instances to access services like EC2 and RDS in the default VPC within the same AWS account.²

Bandwidth is unlimited, but of course free bandwidth is not -- however, Lightsail instances do include a significant monthly bandwidth allowance before any bandwidth-related charges apply.³ Lightsail also has a simplified interface to Route 53 with limited functionality.

But if those sound like drawbacks, they aren't. The point of Lightsail seems to be simplicity. The flexibility of EC2 (and much of AWS) leads inevitably to complexity. The target market for Lightsail appears to be those who "just want a simple VPS" without having to navigate the myriad options available in AWS services like EC2, EBS, VPC, and Route 53. There is virtually no learning curve, here. You don't even technically need to know how to use SSH with a private key -- the Lightsail console even has a built-in SSH client -- but there is no requirement that you use it. You can access these instances normally, with a standard SSH client.

¹Lightsail instances, just like "regular" EC2 (VPC and Classic) instances, have access to the instance metadata service, which allows an instance to discover things about itself, such as its instance type and availability zone. Lightsail instances are identified in the instance metadata as t2 machines.

²The Lightsail docs are not explicit about the fact that peering only works with your Default VPC, but this appears to be the case. If your AWS account was created in 2013 or before, then you may not actually have a VPC with the "Default VPC" designation. This can be resolved by submitting a support request, as I explained in Can't establish VPC peering connection from Amazon Lightsail (at Server Fault).

³The bandwidth allowance applies to both inbound and outbound traffic; after this total amount of traffic is exceeded, inbound traffic continues to be free, but outbound traffic becomes billable. See "What does data transfer cost?" in the Lightsail FAQ"

  1. Create a lightsail account.



Document image


2. Once you have the instance create a static ip.

Create and assign a Static IP address to an instance

Follow these steps to create a new static IP address and attach it to an instance in Lightsail.

  1. Sign in to the Lightsail console at https://lightsail.aws.amazon.com/.
  2. On the Lightsail home page, choose Networking.
  3. Choose Create static IP.
  4. Select the AWS Region where you want to create your static IP.
  5. Choose the Lightsail resource to which you want to attach the static IP.
  6. Enter a name for your static IP.
    • Must be unique within each AWS Region in your Lightsail account.
    • Must contain 2 to 255 characters.
    • Must start and end with an alphanumeric character or number.
    • Can include alphanumeric characters, numbers, periods, dashes, and underscores.
  7. Choose Create.

Now when you go to the home page, you see a static IP address that you can manage.

Document image


Also, on the Networking tab of your instance's management page, you'll see a blue pushpin next to your public IP address. This indicates that the IP address is now static.

Document image




Add file
or






3. Point the ip to the domain with name servers

create a zone



Document image






Create record set



Document image










Updated 03 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Amazon EC
Docs powered by archbee 
TABLE OF CONTENTS
Create and assign a Static IP address to an instance