Sunday, June 7, 2020

AWS Region and AZ, Availability Zone



Region 
is a cluster of data centers and AWS has Regions all around the world.
Region is a collection of AZs, Available Zones (usually 3, min =2 and max=6 )
Most AWS services are region scoped.
Region name can be us-east-1 , us-west-3

AZ , Availability Zone

  • Collection of discrete data centers with redundant power,network,connectivity.
  • Separate from each other -> isolate from disaster.
  • Connected with -> High bandwidth , Ultra low latency
  • Name can be  ex:  ap-southeast-2a, ap=southeast-2b, ap-southeast-2c
For more



AWS VPC



1.Which of the following is used to allow communication to go out from the VPC to the Internet?
Internet Gateway

2.What mechanism is used to ensure that Port 80 traffic is allowed into a subnet?
Network Access Control Lists (NACLs) can be used to allow and deny communication via a specific port into the subnet.
Incorrect. The Internet Gateway provides connectivity to the internet, but does not manage ports.


3.Which of the following is a valid route (IP CIDR Block) for connecting an EC2 hosted website instance to the internet?
0.0.0.0/0
This is a valid route for connecting an EC2 instance to the internet. 0.0.0.0/0 is the IP CIDR Block value that represents the internet as a whole.

Not Correct
----------
A route is not required to connect.
0.0.0.0/24
10.0.0.0/24

4.Which of the following are true about Network Access Control Lists (NACLs)?
Network ACLs are a numbered list of rules, evaluated in order, used to determine if traffic should be allowed in or out of a subnet.
Network ACLs are stateless.
All inbound and outbound traffic is automatically blocked except on the default NACL. The default NACL (pre-created by AWS for the default VPC) allows all traffic by default.

Incorrect
---------
Network ACLs are stateful.
Network ACLs are attached to the VPC to control all traffic in and out of a VPC.

Useful
-------
Network ACLs are stateless. This means that we must explicitly allow traffic inbound and outbound.
Network ACLs are attached to subnets, not to a VPC.

5.How many Availability Zones can one subnet utilize?
One
A subnet can only use one Availability Zone.

6.What is a VPC?
VPC stands for virtual private cloud. A VPC is a virtual network that is logically isolated from other VPCs in the AWS cloud.

7.Which of the following listed below are true about a VPC? (Choose all that apply)
A route entry is automatically added to the route table, to allow communication with the Internet in the Default VPC.
An Internet Gateway is created automatically for the Default VPC.
All communication is allowed, by default, between all subnets created in the Default VPC.
A VPC is automatically created by default on AWS accounts

https://docs.aws.amazon.com/vpc/latest/userguide/default-vpc.html
have a default VPC in each AWS Region.
default VPC is ready for you to use so that you don't have to create and configure your own VPC.


8.What is a subnet?
A subnet is a subdivision of an IP network.

A subnet is a subdivision of an IP network. An IP network is defined by an IP address and a subnet mask. When combined with a binary AND operation, they define the number of available networks and hosts available on an IP network. Those networks are subnets for that particular network.


Saturday, June 6, 2020

AWS Lamda



Few Questions



1.What is AWS Lambda?
AWS Lambda is a compute service that lets you run code without provisioning or managing servers.

2.Which of the following can be used to execute or invoke your Lambda code?
AWS Console
AWS CloudTrail
AWS S3
AWS SNS

EBS is a storage service and can not invoke Lambda. Lambda can be executed from the AWS Console. SNS, S3, and CloudTrail can also invoke the execution on a Lambda function.

3.What are the two primary ways you are charged for using Lambda?
Execution requests and execution duration

The two primary ways you are charged for using Lambda are the number of times your code is executed (execution request), and how long it takes for your code to execute (execution duration).

4.What AWS service will Lambda likely replace?
EC2

It is likely for Lambda to replace EC2 because EC2 is a computing service as well, but Lambda automates the entire infrastructure. This alleviates a lot of the pressure in creating an infrastructure because with Lambda you can let AWS managed that aspect of your business.

5. Which of the following describes serverless computing?
Serverless computing allows you to build and run applications and services without having to think about servers.

6.What are the current languages that Lambda supports?
Java, Go, PowerShell, Node.js, C#, Python, and Ruby code, and provides a Runtime API which allows other languages including Powershell.

7.What is the first step to creating a Lambda Function in the AWS Console?
Create a Function

8.Which of the following would be a good use case for AWS Lambda?
Trigger the processing of an image file in an S3 bucket.

below are not
Bulk storage of data.
To monitor the health of EC2 instances.
Install a SQL Database on Lambda to store data for a web application.

9.Which of the following services can directly trigger a Lambda function?
CloudWatch

below are invalid
Route Table, EC2, DNS









AWS Route 53


What is AWS Route 53
https://aws.amazon.com/route53/

Amazon Route 53 is a highly available and scalable cloud Domain Name System (DNS) web service. It is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating names like www.example.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other. Amazon Route 53 is fully compliant with IPv6 as well.

Amazon Route 53 effectively connects user requests to infrastructure running in AWS – such as Amazon EC2 instances, Elastic Load Balancing load balancers, or Amazon S3 buckets – and can also be used to route users to infrastructure outside of AWS. 

You can use Amazon Route 53 to configure DNS health checks to route traffic to healthy endpoints or to independently monitor the health of your application and its endpoints.

manage traffic globally through a variety of routing types

  • Latency Based Routing
  •  Geo DNS
  • Geoproximity
  • Weighted Round Robin

all of which can be combined with DNS Failover in order to enable a variety of low-latency, fault-tolerant architectures

easily manage how your end-users are routed to your application’s endpoints—whether in a single AWS region or distributed around the globe.

offers Domain Name Registration – you can purchase and manage domain names such as example.com and Amazon Route 53 will automatically configure DNS settings for your domains.

1.In a highly available and fault tolerant architecture, with multiple EC2 instances hosting a website, what is the purpose of Route 53?

To populate external DNS servers with domain/IP address information for the ELB, so that inbound traffic can be load balanced by the ELB between the EC2 instances.
Route 53 automatically sends your DNS record information to DNS servers and it is also where you decide where traffic requests for that domain/IP address are routed to.

2.Which of the following are Amazon Route 53 DNS record types?
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html
  1. A (address record)
  2. AAAA (IPv6 address record)
  3. CNAME (canonical name record)
  4. CAA (certification authority authorization)
  5. MX (mail exchange record)
  6. NAPTR (name authority pointer record)
  7. NS (name server record)
  8. PTR (pointer record)
  9. SOA (start of authority record)
  10. SPF (sender policy framework)
  11. SRV (service locator)
  12. TXT (text record)
  13. Amazon Route 53 also offers alias records, which are an Amazon Route 53-specific extension to DNS. You can create alias records to route traffic to selected AWS resources, including Amazon Elastic Load Balancing load balancers, Amazon CloudFront distributions, AWS Elastic Beanstalk environments, API Gateways, VPC interface endpoints, and Amazon S3 buckets that are configured as websites. Alias record typically have a type of A or AAAA, but they work like a CNAME record. Using an alias record, you can map your record name (example.com) to the DNS name for an AWS resource(elb1234.elb.amazonaws.com). Resolvers see the A or AAAA record and the IP address of the AWS resource.


3.When using CloudFront, what are the locations where the content is cached called?

Edge locations

4.Which of the following does Amazon Route 53 effectively connect user requests to? Choose all that apply.
ELB
S3
EC2

5.When you type a domain name (linuxacademy.com) into a web browser, what best describes the process that occurs to deliver the website content back to your browser?
The browser sends a request to a DNS server asking for the IP address associated with the domain name.

6.What AWS services could you use Route 53 with? Choose all that apply.
EC2
S3

7.What best describes Route 53?
A service to register domains and configure DNS records
Route 53 is the AWS service for managing domain names and DNS record sets.

8.What is the name of the AWS service that provides a Content Delivery Network?
CloudFront

9.What does DNS stand for?
Domain Name System


Friday, May 15, 2020

Gradle: error running Eureka server Returning 404 error

I am trying to run eureka server project via eclipse. It's one of the simplest , but trickiest ..

What i did.

1. Create Spring boot Eireka server with spring http://start.spring.io/
2. Added annotations and property files as needed

@EnableEurekaServer  for main class

and for application.yml

eureka:
   instance:
      hostname: localhost
   client: # Not a client, don't register with yourself
      registerWithEureka: false
      fetchRegistry: false
server:
   port: 1111 # HTTP (Tomcat) port

3. Run main class as Java aplication. Eclipse --> Run As --> Java Application
4. No errors in the console
5. hence i used port=1111
try with http://localhost:1111/

6. Getting 404 error



Whitelabel Error Page

This application has no explicit mapping for /error, so you are seeing this as a fallback.
Fri May 15 21:22:02 IST 2020
There was an unexpected error (type=Not Found, status=404).
No message available

7. Below attached the output in Eclipse console. Eclispe console output-1

8. Eureka server is up and running in port 1111. But in browser localhost:1111 --> Navigates to 404 error page

9. Let's try with gradle command line manually. Stop eclipse run.
10.  build the project and run

gradle buiild  --> Build succesful
gradle bootRun

11. Eureka server start up and running in port 1111
12. attached log in output-2








7. Eclipse console output-1
---------------------------------------

2020-05-15 21:24:45.865  INFO 19320 --- [  restartedMain] .e.DevToolsPropertyDefaultsPostProcessor : Devtools property defaults active! Set 'spring.devtools.add-properties' to 'false' to disable

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::        (v2.2.7.RELEASE)

2020-05-15 21:24:46.973  INFO 19320 --- [  restartedMain] c.e.r.RegisterServerApplication          : No active profile set, falling back to default profiles: default
2020-05-15 21:24:48.782  WARN 19320 --- [  restartedMain] o.s.boot.actuate.endpoint.EndpointId     : Endpoint ID 'service-registry' contains invalid characters, please migrate to a valid format.
2020-05-15 21:24:49.075  INFO 19320 --- [  restartedMain] o.s.cloud.context.scope.GenericScope     : BeanFactory id=6b8184a9-51b7-31fa-8e18-4982d979a052
2020-05-15 21:24:50.717  INFO 19320 --- [  restartedMain] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 1111 (http)
2020-05-15 21:24:50.739  INFO 19320 --- [  restartedMain] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2020-05-15 21:24:50.740  INFO 19320 --- [  restartedMain] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.34]
2020-05-15 21:24:51.090  INFO 19320 --- [  restartedMain] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2020-05-15 21:24:51.091  INFO 19320 --- [  restartedMain] o.s.web.context.ContextLoader            : Root WebApplicationContext: initialization completed in 4092 ms
2020-05-15 21:24:51.215  WARN 19320 --- [  restartedMain] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
2020-05-15 21:24:51.215  INFO 19320 --- [  restartedMain] c.n.c.sources.URLConfigurationSource     : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2020-05-15 21:24:51.245  INFO 19320 --- [  restartedMain] c.netflix.config.DynamicPropertyFactory  : DynamicPropertyFactory is initialized with configuration sources: com.netflix.config.ConcurrentCompositeConfiguration@379c1d6
2020-05-15 21:24:52.708  INFO 19320 --- [  restartedMain] c.s.j.s.i.a.WebApplicationImpl           : Initiating Jersey application, version 'Jersey: 1.19.1 03/11/2016 02:08 PM'
2020-05-15 21:24:52.826  INFO 19320 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using JSON encoding codec LegacyJacksonJson
2020-05-15 21:24:52.828  INFO 19320 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using JSON decoding codec LegacyJacksonJson
2020-05-15 21:24:53.403  INFO 19320 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using XML encoding codec XStreamXml
2020-05-15 21:24:53.404  INFO 19320 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using XML decoding codec XStreamXml
2020-05-15 21:24:54.445  WARN 19320 --- [  restartedMain] o.s.c.n.a.ArchaiusAutoConfiguration      : No spring.application.name found, defaulting to 'application'
2020-05-15 21:24:54.447  WARN 19320 --- [  restartedMain] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
2020-05-15 21:24:54.448  INFO 19320 --- [  restartedMain] c.n.c.sources.URLConfigurationSource     : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2020-05-15 21:24:55.235  INFO 19320 --- [  restartedMain] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
2020-05-15 21:24:55.865  INFO 19320 --- [  restartedMain] o.s.b.d.a.OptionalLiveReloadServer       : LiveReload server is running on port 35729
2020-05-15 21:24:56.516  WARN 19320 --- [  restartedMain] ockingLoadBalancerClientRibbonWarnLogger : You already have RibbonLoadBalancerClient on your classpath. It will be used by default. As Spring Cloud Ribbon is in maintenance mode. We recommend switching to BlockingLoadBalancerClient instead. In order to use it, set the value of `spring.cloud.loadbalancer.ribbon.enabled` to `false` or remove spring-cloud-starter-netflix-ribbon from your project.
2020-05-15 21:24:56.593  INFO 19320 --- [  restartedMain] o.s.c.n.eureka.InstanceInfoFactory       : Setting initial instance status as: STARTING
2020-05-15 21:24:56.658  INFO 19320 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Initializing Eureka in region us-east-1
2020-05-15 21:24:56.658  INFO 19320 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Client configured to neither register nor query for data.
2020-05-15 21:24:56.680  INFO 19320 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Discovery Client initialized at timestamp 1589558096678 with initial instances count: 0
2020-05-15 21:24:56.800  INFO 19320 --- [  restartedMain] c.n.eureka.DefaultEurekaServerContext    : Initializing ...
2020-05-15 21:24:56.804  WARN 19320 --- [  restartedMain] c.n.eureka.cluster.PeerEurekaNodes       : The replica size seems to be empty. Check the route 53 DNS Registry
2020-05-15 21:24:56.912  INFO 19320 --- [  restartedMain] c.n.e.registry.AbstractInstanceRegistry  : Finished initializing remote region registries. All known remote regions: []
2020-05-15 21:24:56.913  INFO 19320 --- [  restartedMain] c.n.eureka.DefaultEurekaServerContext    : Initialized
2020-05-15 21:24:56.934  INFO 19320 --- [  restartedMain] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path '/actuator'
2020-05-15 21:24:56.985  INFO 19320 --- [  restartedMain] o.s.c.n.e.s.EurekaServiceRegistry        : Registering application UNKNOWN with eureka with status UP
2020-05-15 21:24:57.022  INFO 19320 --- [      Thread-17] o.s.c.n.e.server.EurekaServerBootstrap   : Setting the eureka configuration..
2020-05-15 21:24:57.025  INFO 19320 --- [      Thread-17] o.s.c.n.e.server.EurekaServerBootstrap   : Eureka data center value eureka.datacenter is not set, defaulting to default
2020-05-15 21:24:57.026  INFO 19320 --- [      Thread-17] o.s.c.n.e.server.EurekaServerBootstrap   : Eureka environment value eureka.environment is not set, defaulting to test
2020-05-15 21:24:57.074  INFO 19320 --- [      Thread-17] o.s.c.n.e.server.EurekaServerBootstrap   : isAws returned false
2020-05-15 21:24:57.077  INFO 19320 --- [      Thread-17] o.s.c.n.e.server.EurekaServerBootstrap   : Initialized server context
2020-05-15 21:24:57.080  INFO 19320 --- [      Thread-17] c.n.e.r.PeerAwareInstanceRegistryImpl    : Got 1 instances from neighboring DS node
2020-05-15 21:24:57.081  INFO 19320 --- [      Thread-17] c.n.e.r.PeerAwareInstanceRegistryImpl    : Renew threshold is: 1
2020-05-15 21:24:57.081  INFO 19320 --- [      Thread-17] c.n.e.r.PeerAwareInstanceRegistryImpl    : Changing status to UP
2020-05-15 21:24:57.119  INFO 19320 --- [  restartedMain] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 1111 (http) with context path ''
2020-05-15 21:24:57.119  INFO 19320 --- [  restartedMain] .s.c.n.e.s.EurekaAutoServiceRegistration : Updating port to 1111
2020-05-15 21:24:57.137  INFO 19320 --- [      Thread-17] e.s.EurekaServerInitializerConfiguration : Started Eureka Server
2020-05-15 21:24:57.857  INFO 19320 --- [  restartedMain] c.e.r.RegisterServerApplication          : Started RegisterServerApplication in 13.609 seconds (JVM running for 14.866)
2020-05-15 21:25:57.104  INFO 19320 --- [a-EvictionTimer] c.n.e.registry.AbstractInstanceRegistry  : Running the evict task with compensationTime 0ms
2020-05-15 21:26:57.118  INFO 19320 --- [a-EvictionTimer] c.n.e.registry.AbstractInstanceRegistry  : Running the evict task with compensationTime 13ms
2020-05-15 21:27:57.118  INFO 19320 --- [a-EvictionTimer] c.n.e.registry.AbstractInstanceRegistry  : Running the evict task with compensationTime 0ms
2020-05-15 21:28:57.118  INFO 19320 --- [a-EvictionTimer] c.n.e.registry.AbstractInstanceRegistry  : Running the evict task with compensationTime 0ms
2020-05-15 21:29:57.119  INFO 19320 --- [a-EvictionTimer] c.n.e.registry.AbstractInstanceRegistry  : Running the evict task with compensationTime 0ms




12. output-2    gradle bootRun output
----------------------------------------------------------------


> Task :compileJava UP-TO-DATE
> Task :processResources UP-TO-DATE
> Task :classes UP-TO-DATE

> Task :bootRun
2020-05-15 21:38:16.878  INFO 17600 --- [  restartedMain] .e.DevToolsPropertyDefaultsPostProcessor : Devtools property defaults active! Set 'spring.devtools.add-properties' to 'false' to disable

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::        (v2.2.7.RELEASE)

2020-05-15 21:38:18.083  INFO 17600 --- [  restartedMain] c.e.r.RegisterServerApplication          : No active profile set, falling back to default profiles: default
2020-05-15 21:38:19.459  WARN 17600 --- [  restartedMain] o.s.boot.actuate.endpoint.EndpointId     : Endpoint ID 'service-registry' contains invalid characters, please migrate to a valid format.
2020-05-15 21:38:19.646  INFO 17600 --- [  restartedMain] o.s.cloud.context.scope.GenericScope     : BeanFactory id=d20a0ae6-0dc1-3853-b713-090cd5293043
2020-05-15 21:38:21.304  INFO 17600 --- [  restartedMain] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 1111 (http)
2020-05-15 21:38:21.326  INFO 17600 --- [  restartedMain] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2020-05-15 21:38:21.326  INFO 17600 --- [  restartedMain] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.34]
2020-05-15 21:38:21.687  INFO 17600 --- [  restartedMain] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2020-05-15 21:38:21.687  INFO 17600 --- [  restartedMain] o.s.web.context.ContextLoader            : Root WebApplicationContext: initialization completed in 3571 ms
2020-05-15 21:38:21.822  WARN 17600 --- [  restartedMain] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
2020-05-15 21:38:21.822  INFO 17600 --- [  restartedMain] c.n.c.sources.URLConfigurationSource     : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2020-05-15 21:38:21.841  INFO 17600 --- [  restartedMain] c.netflix.config.DynamicPropertyFactory  : DynamicPropertyFactory is initialized with configuration sources: com.netflix.config.ConcurrentCompositeConfiguration@689add69
2020-05-15 21:38:23.534  INFO 17600 --- [  restartedMain] c.s.j.s.i.a.WebApplicationImpl           : Initiating Jersey application, version 'Jersey: 1.19.1 03/11/2016 02:08 PM'
2020-05-15 21:38:23.785  INFO 17600 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using JSON encoding codec LegacyJacksonJson
2020-05-15 21:38:23.788  INFO 17600 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using JSON decoding codec LegacyJacksonJson
2020-05-15 21:38:24.206  INFO 17600 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using XML encoding codec XStreamXml
2020-05-15 21:38:24.206  INFO 17600 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using XML decoding codec XStreamXml
2020-05-15 21:38:24.848  WARN 17600 --- [  restartedMain] o.s.c.n.a.ArchaiusAutoConfiguration      : No spring.application.name found, defaulting to 'application'
2020-05-15 21:38:24.849  WARN 17600 --- [  restartedMain] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
2020-05-15 21:38:24.850  INFO 17600 --- [  restartedMain] c.n.c.sources.URLConfigurationSource     : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2020-05-15 21:38:25.108  INFO 17600 --- [  restartedMain] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
2020-05-15 21:38:25.698  INFO 17600 --- [  restartedMain] o.s.b.d.a.OptionalLiveReloadServer       : LiveReload server is running on port 35729
2020-05-15 21:38:26.601  WARN 17600 --- [  restartedMain] ockingLoadBalancerClientRibbonWarnLogger : You already have RibbonLoadBalancerClient on your classpath. It will be used by default. As Spring Cloud Ribbon is in maintenance mode. We recommend switching to BlockingLoadBalancerClient instead. In order to use it, set the value of `spring.cloud.loadbalancer.ribbon.enabled` to `false` or remove spring-cloud-starter-netflix-ribbon from your project.
2020-05-15 21:38:26.709  INFO 17600 --- [  restartedMain] o.s.c.n.eureka.InstanceInfoFactory       : Setting initial instance status as: STARTING
2020-05-15 21:38:26.773  INFO 17600 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Initializing Eureka in region us-east-1
2020-05-15 21:38:26.774  INFO 17600 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Client configured to neither register nor query for data.
2020-05-15 21:38:26.788  INFO 17600 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Discovery Client initialized at timestamp 1589558906785 with initial instances count: 0
2020-05-15 21:38:26.873  INFO 17600 --- [  restartedMain] c.n.eureka.DefaultEurekaServerContext    : Initializing ...
2020-05-15 21:38:26.879  WARN 17600 --- [  restartedMain] c.n.eureka.cluster.PeerEurekaNodes       : The replica size seems to be empty. Check the route 53 DNS Registry
2020-05-15 21:38:26.985  INFO 17600 --- [  restartedMain] c.n.e.registry.AbstractInstanceRegistry  : Finished initializing remote region registries. All known remote regions: []
2020-05-15 21:38:26.987  INFO 17600 --- [  restartedMain] c.n.eureka.DefaultEurekaServerContext    : Initialized
2020-05-15 21:38:27.012  INFO 17600 --- [  restartedMain] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path '/actuator'
2020-05-15 21:38:27.053  INFO 17600 --- [  restartedMain] o.s.c.n.e.s.EurekaServiceRegistry        : Registering application UNKNOWN with eureka with status UP
2020-05-15 21:38:27.058  INFO 17600 --- [      Thread-17] o.s.c.n.e.server.EurekaServerBootstrap   : Setting the eureka configuration..
2020-05-15 21:38:27.058  INFO 17600 --- [      Thread-17] o.s.c.n.e.server.EurekaServerBootstrap   : Eureka data center value eureka.datacenter is not set, defaulting to default
2020-05-15 21:38:27.060  INFO 17600 --- [      Thread-17] o.s.c.n.e.server.EurekaServerBootstrap   : Eureka environment value eureka.environment is not set, defaulting to test
2020-05-15 21:38:27.094  INFO 17600 --- [      Thread-17] o.s.c.n.e.server.EurekaServerBootstrap   : isAws returned false
2020-05-15 21:38:27.095  INFO 17600 --- [      Thread-17] o.s.c.n.e.server.EurekaServerBootstrap   : Initialized server context
2020-05-15 21:38:27.095  INFO 17600 --- [      Thread-17] c.n.e.r.PeerAwareInstanceRegistryImpl    : Got 1 instances from neighboring DS node
2020-05-15 21:38:27.096  INFO 17600 --- [      Thread-17] c.n.e.r.PeerAwareInstanceRegistryImpl    : Renew threshold is: 1
2020-05-15 21:38:27.096  INFO 17600 --- [      Thread-17] c.n.e.r.PeerAwareInstanceRegistryImpl    : Changing status to UP
2020-05-15 21:38:27.121  INFO 17600 --- [      Thread-17] e.s.EurekaServerInitializerConfiguration : Started Eureka Server
2020-05-15 21:38:27.140  INFO 17600 --- [  restartedMain] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 1111 (http) with context path ''
2020-05-15 21:38:27.141  INFO 17600 --- [  restartedMain] .s.c.n.e.s.EurekaAutoServiceRegistration : Updating port to 1111
2020-05-15 21:38:27.913  INFO 17600 --- [  restartedMain] c.e.r.RegisterServerApplication          : Started RegisterServerApplication in 12.488 seconds (JVM running for 13.927)

Gradle: Finding all gradle tasks

Gradle is very convenient build tool and if you  need to know the commands need to run you can get a brief description running  "gradle tasks" in the command prompt.
From all these few will used frequently

clean , build , bootRun

Below is the sample you may get

---------------------------------------------------------------------------------------------------------

C:\register-server>gradle tasks

> Task :tasks

------------------------------------------------------------
Tasks runnable from root project
------------------------------------------------------------

Application tasks
-----------------
bootRun - Runs this project as a Spring Boot application.

Build tasks
-----------
assemble - Assembles the outputs of this project.
bootJar - Assembles an executable jar archive containing the main classes and their dependencies.
build - Assembles and tests this project.
buildDependents - Assembles and tests this project and all projects that depend on it.
buildNeeded - Assembles and tests this project and all projects it depends on.
classes - Assembles main classes.
clean - Deletes the build directory.
jar - Assembles a jar archive containing the main classes.
testClasses - Assembles test classes.

Build Setup tasks
-----------------
init - Initializes a new Gradle build.
wrapper - Generates Gradle wrapper files.

Documentation tasks
-------------------
javadoc - Generates Javadoc API documentation for the main source code.

Help tasks
----------
buildEnvironment - Displays all buildscript dependencies declared in root project 'register-server'.
components - Displays the components produced by root project 'register-server'. [incubating]
dependencies - Displays all dependencies declared in root project 'register-server'.
dependencyInsight - Displays the insight into a specific dependency in root project 'register-server'.
dependencyManagement - Displays the dependency management declared in root project 'register-server'.
dependentComponents - Displays the dependent components of components in root project 'register-server'. [incubating]
help - Displays a help message.
model - Displays the configuration model of root project 'register-server'. [incubating]
outgoingVariants - Displays the outgoing variants of root project 'register-server'.
projects - Displays the sub-projects of root project 'register-server'.
properties - Displays the properties of root project 'register-server'.
tasks - Displays the tasks runnable from root project 'register-server'.

Verification tasks
------------------
check - Runs all checks.
test - Runs the unit tests.

Rules
-----
Pattern: clean: Cleans the output files of a task.
Pattern: build: Assembles the artifacts of a configuration.
Pattern: upload: Assembles and uploads the artifacts belonging to a configuration.

To see all tasks and more detail, run gradle tasks --all

To see more detail about a task, run gradle help --task

BUILD SUCCESSFUL in 1s
1 actionable task: 1 executed