-
Notifications
You must be signed in to change notification settings - Fork 13.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Amazon VPC question #4594
Comments
Hi @Ebazhanov I am interested in this issue. Can you plz assign me? |
[Ebazhanov#4594] New Amazon VPC questions
Created a PR - #4609 |
Hi @Ebazhanov I have worked on this issue and raised a PR #4611 Kindly merge it. |
@MakendranG #4609 is before #4611 ... @Ebazhanov plz merge #4609 |
@MakendranG I know you have created an issue + type this questions but you have to be proud that Sr.Engineer from https://www.linkedin.com/in/parikhparth23/ take your issue, Guys you both doing great contribution! 🍺 |
A single-tier application
A serverless application
A microservice application
A multi-tier application
Yes, the instance retains its private IP addresses
No, it retains only the public IP addresses.
No, it retains only the Elastic IP addresses.
No, it does not retain its private IP addresses.
All the Amazon EC2 instances you launch into a nondefault VPC are ______ by default.
stateless
protected
public
private
When you launch an instance into a dedicated-tenancy VPC, what happens?
Your instance is automatically a Dedicated instance, regardless of the instance's specific tenancy attribute.
You receive an error message notifying you that you must set your instance's tenancy attribute to dedicated.
Your instance launch fails, but AWS prompts you to launch a new one with the tenancy attribute set to dedicated.
Your instance launch fails immediately..
Use the _______ protocol in a VPC security group to communicate with a DB instance.
SSH
SSL
TCP
UDP
The text was updated successfully, but these errors were encountered: