Springboot books

1. create Spring Boots projects

2. commit && push to GitHub

3. create .jar executable from Github with Jenkins

4. Upload manually .jar to AWS S3

5. connect AWS S3 to AWS AEB

6. AWS AEB deploy and publish

First at all, we create a. jar executable with Jenkins: link and after that we will upload this .jar package executable to S3 manually.

We should do in the near future the automation of this process (by jenkinsfile, for instance).

First at all, we create a bucket on AWS S3 and upload the spring boot snapshot.

So far, Object Ownership is disabled, to make our snapshot public we MUST enable it (but no now).

Properties bucket:

1. block public access,

2. versioning,

3. encryption,

4. taging and

5. policy.

Uploadinng spring boot snapshot ...

Once spring boot snapshot is uploaded we need it to be public, so let's operate upon its (1) ACL, (2) policy and (3) endpoint: link

So far, access is forbidden.

Now, the endpoint is open to all:

• bucket: springbootbookswebbuild

• region: eu-central-1

• amz domain: amazonaws.com

• object: springbootClient-0.0.1-SNAPSHOT.jar

https://springbootbookswebbuild.s3.eu-central-1.amazonaws.com/springbootClient-0.0.1-SNAPSHOT.jar

We are using AWS EAB to host, create an enviroment, run and publish.

We choose JAVA as platform to create the enviroment.

We may upload our package or connect a S3 bucket.

AWS AEB builds the enviroment and try to publish, but there are some severe problems ..

AEB is publishing on: http://springbootwebbooks-env.eba-rgmk4emu.eu-central-1.elasticbeanstalk.com/ but there is some data missing ...

Elastic Beanstalk > Environments > Springbootwebbooks-env > Configuration > Environment properties >

Add new variable : SERVER_PORT : 5000

AEB running: http://springbootwebbooks-env.eba-rgmk4emu.eu-central-1.elasticbeanstalk.com/