Tests need to run against the background of a known set of objects. This set of objects is called a test fixture. When you are writing tests you will often find that you spend more time writing the code to set up the fixture than you do in actually testing values.
The purpose of a test fixture is to ensure that there is a well known and fixed environment in which tests are run so that results are repeatable. Some people call this the test context.
Examples of fixtures:
Loading a database with a specific, known set of data Erasing a hard disk and installing a known clean operating system installation Copying a specific known set of files Preparation of input data and set-up/creation of fake or mock objects
One of the most time-consuming parts of writing tests is writing the code to set the world up in a known state and then return it to its original state when the test is complete. This known state is called the fixture of the test.
I am happy to share that have passed another AWS cloud certification exam. The training and sponsorship was provided by Rackspace Cloud (AWS partner). This exam “AWS Cloud Practitioner” is relatively very simple in comparison to “AWS Solutions Architect“. I finished it in almost half the time given in exam.
The certificate is issued by AWS Training and Certification.
Feel free to reach out to me if for any help, assistance, guidance or motivation related to AWS certification.
I have explained Auto Scaling with live demo using AWS ASG, SQS and Cloud Watch. Watch this short video to understand the elasticity and power of the cloud.
If you have many instances, managing the firewalls using Network ACL can be very useful. Otherwise, with Security group, you have to manually assign a security group to the instances.
State: Stateful or Stateless Security groups are stateful: This means any changes applied to an incoming rule will be automatically applied to the outgoing rule. e.g. If you allow an incoming port 80, the outgoing port 80 will be automatically opened. Network ACLs are stateless: This means any changes applied to an incoming rule will not be applied to the outgoing rule. e.g. If you allow an incoming port 80, you would also need to apply the rule for outgoing traffic.
Rules: Allow or Deny Security group support allow rules only (by default all rules are denied). e.g. You cannot deny a certain IP address from establishing a connection. Network ACL support allow and deny rules. By deny rules, you could explicitly deny a certain IP address to establish a connection example: Block IP address 123.201.57.39 from establishing a connection to an EC2 Instance.
Rule process order All rules in a security group are applied whereas rules are applied in their order (the rule with the lower number gets processed first) in Network ACL. i.e. Security groups evaluate all the rules in them before allowing a traffic whereas NACLs do it in the number order, from top to bottom.
Defense order Network ACL first layer of defense, whereas Security group is second layer of the defense for inbound/ingress traffic. Security group first layer of defense, whereas Network ACL is second layer of the defense for outbound/egress traffic.
Occurrence Subnet can have only one NACL, whereas Instance can have multiple Security groups.