5.10

3.35.3

skipCredentialsValidation: false,
 skipGetEc2Platforms: false,
 skipMetadataApiCheck: false,

[6:11 PM] /*
   *   s3 public access block
   */
const bucketNameList = ["prod-nueve-media-9184fce"]
const bucketIdList: pulumi.Output<string>[] = []

bucketNameList.forEach(bucketName => {
  // Create an AWS resource (S3 Bucket) 
  const bucket = new aws.s3.Bucket(bucketName, {});
  bucketIdList.push(bucket.id)
});

for (let index = 0; index < bucketIdList.length; index++) {
  new aws.s3.BucketPublicAccessBlock(`${bucketNameList[index]}-publicAccessBlock`, {
    bucket: bucketIdList[index],
    blockPublicAcls: true,
    blockPublicPolicy: true,
  });
}

Diagnostics:
  aws:s3:Bucket (s3-website-bucket):
    error: 1 error occurred:
    	* error configuring Terraform AWS Provider: AWS account ID not previously found and failed retrieving via all available methods. See <https://www.terraform.io/docs/providers/aws/index.html#skip_requesting_account_id> for workaround and implications. Errors: 2 errors occurred:

new awsx.ec2.Subnet

new aws.ec2.Subnet

new remote.Command("mysql-setup-execute", {
                    connection,
                    create: pulumi.interpolate`chmod 777 ./mysql-setup.sh; ./mysql-setup.sh`,
                    delete: "rm mysql-setup.sh",
                    environment: {
                        MASTER_USER: masterUsername,
                        MASTER_PASSWORD: masterPassword!,
                        DB_USERNAME: dbUsername,
                        DB_PASSWORD: dbUserPassword,
                        DB_NAME: dbName,
                        DB_HOST: dbHost
                    }
                }, { dependsOn: remoteFile });

#!/bin/bash

sudo yum -y install mariadb
mysql -u ${MASTER_USER} -p${MASTER_PASSWORD} -h${DB_HOST}<<MYSQL_SCRIPT

CREATE USER ${DB_USERNAME}@% IDENTIFIED BY '${DB_PASSWORD}';
GRANT ALL PRIVILEGES ON ${DB_NAME}.* TO '${USERNAME}'@'%';
FLUSH PRIVILEGES;
MYSQL_SCRIPT

GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -ldflags "-s -w" -tags lambda.norpc -o build/bootstrap

NewAssetArchive

Code: pulumi.NewAssetArchive(map[string]interface{}{
			"bootstrap": pulumi.NewFileAsset("../onboarding/cmd/onboarding/build/bootstrap"),
			"Makefile":  pulumi.NewFileAsset("../onboarding/cmd/onboarding/build/Makefile"),
		}),

build-Onboarding:
	cp ./bootstrap $(ARTIFACTS_DIR)/.

pulumi login

aws

pulumi import...

pulumi import aws:ec2/subnet:Subnet defaultVpcSubnet2d subnet-BLAHBLAHBLAHBLAH

warning: One or more imported inputs failed to validate. This is almost certainly a bug in the `aws` provider. The import will still proceed, but you will need to edit the generated code after copying it into your program.
    warning: aws:ec2/subnet:Subnet resource 'defaultVpcSubnet2d' has a problem: Conflicting configuration arguments: "availability_zone": conflicts with availability_zone_id. Examine values at 'Subnet.AvailabilityZone'.
    warning: aws:ec2/subnet:Subnet resource 'defaultVpcSubnet2d' has a problem: Conflicting configuration arguments: "availability_zone_id": conflicts with availability_zone. Examine values at 'Subnet.AvailabilityZoneId'.

aws:ec2:VpcPeeringConnection (eks-vpc-peer-to-rds-vpc):
    error: 1 error occurred:
        * updating urn:pulumi:dev::allrites-infrastructure::custom:resource:vpc$aws:ec2/vpcPeeringConnection:VpcPeeringConnection::eks-vpc-peer-to-rds-vpc: 1 error occurred:
        * error reading EC2 VPC Peering Connection (pcx-093563ee7db421f17): failed

Diagnostics:
  aws:ec2:Vpc (rds-vpc-vpc):
    error: deleting urn:pulumi:dev::allrites-infrastructure::aws:ec2/vpc:Vpc::rds-vpc-vpc: 1 error occurred:
        * error deleting EC2 VPC (vpc-076d9d57f5bfecac7): DependencyViolation: The vpc 'vpc-076d9d57f5bfecac7' has dependencies and cannot be deleted.
        status code: 400, request id: 8f586580-0c6f-4134-8606-e2c3aaa0c19f

  pulumi:pulumi:Stack (allrites-infrastructure-dev):
    error: update failed

-   ├─ aws:ec2:Vpc                             rds-vpc-vpc                        delete     completing deletion fro

aws:ec2:VpcPeeringConnection (us-data-vpc-peer-to-primary-data-vpc):
    error: 1 error occurred:
        * updating urn:pulumi:dev::allrites-infrastructure::custom:resource:vpc$aws:ec2/vpcPeeringConnection:VpcPeeringConnection::us-data-vpc-peer-to-primary-data-vpc: 1 error occurred:
        * Unable to modify EC2 VPC Peering Connection Options. EC2 VPC Peering Connection (pcx-074aa1572a7fa6704) is not active (current status: pending-acceptance). Please set the `auto_accept` attribute to `true` or activate the EC2 VPC Peering Connection manually.