graph TD
A[Should I use an Angular module?] --> B{Is it a component?}
B -->|Yes| X[Don't use an Angular module]
B -->|No| C{Is it a directive?}
C -->|Yes| X
C -->|No| D{Is it a pipe?}
D -->|Yes| X
D -->|No| E{Is it a service?}
E -->|Yes| X
@Get('api/auth/sso/saml/login') | |
@UseGuards(SamlAuthGuard) | |
async samlLogin() { | |
//this route is handled by passport-saml | |
return; | |
} |
import * as cdk from "@aws-cdk/core"; | |
import * as wafv2 from "@aws-cdk/aws-wafv2"; | |
// This extends the base cdk stack properties to include a tag name input. | |
export interface StackProps extends cdk.StackProps { | |
tag: string; | |
applicationName?: string; | |
} | |
export class WAFStack extends cdk.Stack { |
# | |
# This small example shows you how to access JS-based requests via Selenium | |
# Like this, one can access raw data for scraping, | |
# for example on many JS-intensive/React-based websites | |
# | |
from time import sleep | |
from selenium import webdriver | |
from selenium.webdriver import DesiredCapabilities |
import { Router } from "express"; | |
import jwt from "jsonwebtoken"; | |
import jwkToPem from "jwk-to-pem"; | |
import * as Axios from 'axios'; | |
interface PublicKeys { | |
keys: PublicKey[]; | |
} | |
interface PublicKey { | |
alg: string; |
import cdk = require("@aws-cdk/core"); | |
import { Vpc, Port } from "@aws-cdk/aws-ec2"; | |
import { | |
Cluster, | |
ContainerImage, | |
AwsLogDriver, | |
FargatePlatformVersion, | |
NetworkMode, | |
CfnService, | |
} from "@aws-cdk/aws-ecs"; |
When it comes to databases and AWS VPC, best practice is to place your database in private subnet. By definition, private subnet in AWS is not reachable from the Internet because no Internet gateway is attached to private subnet. This is the way you protect your data. This kind of configuration is good for security but bad for data management.
How can you easily access and manage your secured data?
There are two basic ways to acees it.
- Access postgres RDS from bastion host. There are following requirements for this.
UPDATE (March 2020, thanks @ic): I don't know the exact AMI version but yum install docker
now works on the latest Amazon Linux 2. The instructions below may still be relevant depending on the vintage AMI you are using.
Amazon changed the install in Linux 2. One no-longer using 'yum' See: https://aws.amazon.com/amazon-linux-2/release-notes/
sudo amazon-linux-extras install docker
sudo service docker start
const AWS = require('aws-sdk'); | |
const client = new AWS.SecretsManager({}); | |
// Call the AWS API and return a Promise | |
function getAwsSecret(secretName) { | |
return client.getSecretValue({ SecretId: secretName }).promise(); | |
} | |
// Create a async function to use the Promise |
This migration path focuses on AngularJS UI Router and Angular Router interopability,
This method not good for everyone! The main characteristics of this path is that the AngularJS and Angular apps does not share the same layout. So new components are always introduced in Angular, old components are rewritten and downgraded for AngularJS. Migration of old modules happens at once, when almost all components are updated. UI Router states cannot be reused in Angular, so every state and listener should bre rewriten to routes and event listeners or strategies for Angular Router.