A security clearance is a status granted to individuals allowing them access to classified information (state or organizational secrets) or to restricted areas, after completion of a thorough background check.
The term “security clearance” is also sometimes used in private organizations that have a formal process to vet employees for access to sensitive information. A clearance by itself is normally not sufficient to gain access; the organization must also determine that the cleared individual needs to know specific information. No one is supposed to be granted automatic access to classified information solely because of rank, position, or a security clearance.
Agile is a mindset for a high-performance team with commitments to willingly respond or harness changes and continuously deliver valuable products for customer’s satisfaction and competitive advantages through collaboration with them.
A high-performance team is cross-functional and self-organizing. Continuous delivery suggests delivering products iteratively and incrementally; that is, to deliver products with added values in a short timescale frequently or in a sustainable pace.
- Lean Thinking
- Agile Mindset
- Methodology (Approaches or Methods)
User stories are usually written down with index cards for further conversation and confirmation. Odds are we feel quite comfortable with the typical user story format evolved over time at Connextra as the following:
As a [type of user]
I want to [do something]
So that I can [get some benefit]
With this simple template, we can start off conversation for details and define acceptance criteria for confirmation. It’s about time to write the acceptance criteria onto the flip side of your user story card.
When describing the acceptance criteria, using Gherkin syntax as follows is beneficial both to the user and developer.
Given [preconditions or context]
A user can develop the acceptance criteria in plain English using Gherkin syntax with quite limited keywords, while the developer can incorporate it into the testing framework, such as SpecFlow, Cucumber, Fit/FitNesse, and the like, to automate the testing and documentation work.
S3 endpoint not shown in the Route 53 alias dropdown list
- Create a S3 bucket with a DNS-compliant name; say, amazon.nlabs.tw
- Make the bucket a static web site and public accessible
- Route 53
- Create a zone, amazon.nlabs.tw
- Create an A record with proprietary Route 53 alias
- Leave the A record name blank
- Set alias option to Yes and choose the S3 endpoint from the dropdown list
- the S3 bucket name should be DNS-compliant
- the S3 bucket name should match the Route 53 zone name
- if S3 bucket name doesn’t match Route 53 zone name, the S3 endpoint would not be shown in the dropdown list automatically.