Difference between revisions of "Git to AWS S3 System"

From Lingoport Wiki
Jump to: navigation, search
(Test)
Line 72: Line 72:
 
# You should see test.txt
 
# You should see test.txt
   
  +
</pre>
  +
  +
  +
== Project Config ==
  +
  +
First [[On-Boarding_New_Projects:On Boarding you Project]], but set the VCS details to 'None'. Then run the associated Jenkins job once (this pre-populates several directories). Note: The Jenkins Job is expected to fail as the setup is not yet complete.
  +
  +
Then, edit the file:
  +
  +
<code>/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<your group>/projects/<your project>/config/config_vcs.properties</code>
  +
  +
Adding the following:
  +
  +
<pre>
  +
...
  +
VCS_TYPE=S3
  +
...
  +
S3_BUCKET_URL=s3://my-bucket/optionalsubdirs
  +
...
  +
</pre>
  +
  +
If your bucket uses AES256 encryption, add the following at the end:
  +
  +
<pre>
  +
S3_OPTS=--sse AES256
  +
</pre>
  +
  +
Otherwise, leave blank:
  +
  +
<pre>
  +
S3_OPTS=
 
</pre>
 
</pre>

Revision as of 16:54, 6 December 2021

Install AWS Client V2

On the Unix box, install AWS Client (Version 2). To do so, follow this link

Or quickreference on Linux is:

$ whoami
# should be root, or a user with 'sudo' access

$ curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
$ unzip awscliv2.zip
$ sudo ./aws/install

AWS User

The system authenticates to S3 by providing an AWS aws_access_key_id and the associated aws_secret_access_key.

Most common is to create a service account to provide these credentials.

Please find associated aws documentation here

The provided account must have permissions to read, download from, and write to, the associated AWS S3 bucket.

Storing the AWS Credentials

As the 'jenkins' user on the target system, create /var/lib/jenkins/.aws (~/.aws as 'jenkins'), along with a .aws/config and .aws/credentials.

Examples:

$ whoami
jenkins

$ mkdir -p ~/.aws

$ : #Substitute your region for us-east-1 as needed:

$ cat <<EOF >> ~/.aws/config
[default]
region=us-east-1
output=json
EOF

$ : # Fill in the aws_access_key_id and aws_secret_access_key per your organization's AWS service account:

$ cat <<EOF >> ~/.aws/credentials
[default]
aws_access_key_id=<access key id associated with read+write access to the target S3 bucket per your Org>
aws_secret_access_key=<secret access key associated with the aws_access_key_id above>
notes="S3 Read+Write access for <your Org>"
EOF

Test

Make sure you can read, download from, and write to the target s3 bucket. From the system, try running:

echo "Testing view access:"
aws s3 ls s3://<your bucket>/<optional path>

echo "Testing write access:"
echo "Write me." > test.txt 
aws s3 cp test.txt s3://<your bucket>/<optional path>/test.txt   # --SSE AES256 # <--- uncomment that if encryption is required and your org uses the default AES256 
encryption. Or replace with other settings as needed.

echo "Testing download access:" 
rm test.txt  # remove it so that you have to get it back from s3
aws s3 cp s3://<your bucket>/<optional path>/test.txt .
ls 
# You should see test.txt 


Project Config

First On-Boarding_New_Projects:On Boarding you Project, but set the VCS details to 'None'. Then run the associated Jenkins job once (this pre-populates several directories). Note: The Jenkins Job is expected to fail as the setup is not yet complete.

Then, edit the file:

/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<your group>/projects/<your project>/config/config_vcs.properties

Adding the following:

...
VCS_TYPE=S3
...
S3_BUCKET_URL=s3://my-bucket/optionalsubdirs
...

If your bucket uses AES256 encryption, add the following at the end:

S3_OPTS=--sse AES256

Otherwise, leave blank:

S3_OPTS=