Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
a0b4f800
Commit
a0b4f800
authored
Jan 04, 2021
by
Craig Norris
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
AWS cost grammar fixes
Fixes a typo and some future tense.
parent
f8971bea
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
16 deletions
+15
-16
doc/install/aws/index.md
doc/install/aws/index.md
+15
-16
No files found.
doc/install/aws/index.md
View file @
a0b4f800
...
...
@@ -44,22 +44,21 @@ Below is a diagram of the recommended architecture.
## AWS costs
Here's a list of the AWS services we will use, with links to pricing information:
-
**EC2**
: GitLab will deployed on shared hardware which means
[
on-demand pricing
](
https://aws.amazon.com/ec2/pricing/on-demand/
)
will apply. If you want to run it on a dedicated or reserved instance,
consult the
[
EC2 pricing page
](
https://aws.amazon.com/ec2/pricing/
)
for more
information on the cost.
-
**S3**
: We will use S3 to store backups, artifacts, LFS objects, etc. See the
[
Amazon S3 pricing
](
https://aws.amazon.com/s3/pricing/
)
.
-
**ELB**
: A Classic Load Balancer will be used to route requests to the
GitLab instances. See the
[
Amazon ELB pricing
](
https://aws.amazon.com/elasticloadbalancing/pricing/
)
.
-
**RDS**
: An Amazon Relational Database Service using PostgreSQL will be used. See the
[
Amazon RDS pricing
](
https://aws.amazon.com/rds/postgresql/pricing/
)
.
-
**ElastiCache**
: An in-memory cache environment will be used to provide a
Redis configuration. See the
[
Amazon ElastiCache pricing
](
https://aws.amazon.com/elasticache/pricing/
)
.
GitLab uses the following AWS services, with links to pricing information:
-
**EC2**
: GitLab is deployed on shared hardware, for which
[
on-demand pricing
](
https://aws.amazon.com/ec2/pricing/on-demand/
)
applies.
If you want to run GitLab on a dedicated or reserved instance, see the
[
EC2 pricing page
](
https://aws.amazon.com/ec2/pricing/
)
for information about
its cost.
-
**S3**
: GitLab uses S3 (
[
pricing page
](
https://aws.amazon.com/s3/pricing/
)
) to
store backups, artifacts, and LFS objects.
-
**ELB**
: A Classic Load Balancer (
[
pricing page
](
https://aws.amazon.com/elasticloadbalancing/pricing/
)
),
used to route requests to the GitLab instances.
-
**RDS**
: An Amazon Relational Database Service using PostgreSQL
(
[
pricing page
](
https://aws.amazon.com/rds/postgresql/pricing/
)
).
-
**ElastiCache**
: An in-memory cache environment (
[
pricing page
](
https://aws.amazon.com/elasticache/pricing/
)
),
used to provide a Redis configuration.
## Create an IAM EC2 instance role and profile
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment