amazon web services - AWS API Gateway + Elastic Beanstalk and Microservices -

i'm going build microservices' architecture on aws , want ask clarify doubts.

my current general concept

i use api gateway, exposes microsevices' apis running in elastic beanstalk. place elastic beanstalk in vpc without direct access internet instances.

questions & doubts:

1. elastic beanstalk gets subdomain on application creation. subdomain should used api gateway integration type: aws service, in action configuration - right?
2. what represent single microservice? elastic beanstalk's application specific scalable microservice?
3. how microservices should communicate each other? there task im going use sqs (simple queue service). in other cases, better when 2 microservices communicates each other through api gateway rather directly - right?
4. test environment: structure should use in test environment (or staging env.)? think creating separate vpc elastic beanstalk , other amazon services.
5. test environment , api gateway: how should set api gateway? should allow clients access microservices in test environment if request has specific subdomain, like: test.mydomain.com/hello_world/say_hello. i'm not sure how use api gateway in ci/cd make fast , simple, without manual copying configuration test stage production stage. (i'm not expecting complex solution, hints components, parts, concepts use it. more details i'll find on own).
6. have experience in deploying apps elastic beanstalk using codep deploy and/or jenkins? i'm interesting in way better: jenkins, aws code deploy or jenkins+codedeploy.

thanks in advanced!

i'll answer points not opinion based:

1. elastic beanstalk gets subdomain on application creation. subdomain should used api gateway integration type: aws service, in action configuration - right?

no, aws service integration apply if calling elastic beanstalk service. calling own beanstalk instance use http integration.

2. what represent single microservice? elastic beanstalk's application specific scalable microservice?

this you, mentioned in comments, many customers choose via lambda functions rather beanstalk applications. using lambda has benefit not need managed scaling of beanstalk application.

4. test environment: structure should use in test environment (or staging env.)? think creating separate vpc elastic beanstalk , other amazon services.

just note here, api gateway cannot contact resources in vpc currently. beanstalk instance need publically accessible.

5. test environment , api gateway: how should set api gateway? should allow clients access microservices in test environment if request has specific subdomain, like: test.mydomain.com/hello_world/say_hello. i'm not sure how use api gateway in ci/cd make fast , simple, without manual copying configuration test stage production stage. (i'm not expecting complex solution, hints components, parts, concepts use it. more details i'll find on own).

you should take @ stage variables. allow use basic configuration differences between dev/test/prod stored in these variables.